[Desktop-packages] [Bug 2043538] Re: gnome-shell takes too much ram

[Daniel van Vugt]

Your log is being flooded with:

  ubuntu-appindicat...@ubuntu.com[2421]: unable to update icon for
multiload

which is also tracked as bug 1988791. So removing appindicators is the
first thing to try. The second thing is to remove other extensions.

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

Title:
  gnome-shell takes too much ram

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I had no memory problems with Ubuntu 20.04.
  After upgrading to Ubuntu 22.04, my 16GB laptop suffered from lack of memory.
  I upgraded to 48GB (!), and the memory still continues to fill.
  After a few days, with no program started, 12GB is taken. Gnome-shell alone 
is taking 17.4% of my 48GB.
  I guess it is suffering from a memory leak. 

  Description:Ubuntu 22.04.3 LTS

  gnome-shell:
Installé : 42.9-0ubuntu2
Candidat : 42.9-0ubuntu2
   Table de version :
   *** 42.9-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.0-2ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 07:04:21 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-31 (75 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  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/2043538/+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 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken

[Raziel Anarki]

here's the corresponing main.log:

> # cat main.log | grep "failed"
> 2023-11-24 08:28:40,359 ERROR Dist-upgrade failed: 'Broken packages after 
> upgrade: gnome-remote-desktop, gnome-shell, mutter'


** Attachment added: "main.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+attachment/5722923/+files/main.log

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

Title:
  Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop &
  gnome-shell packages are broken

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Running do-release-upgrade on 23.04 (lunar), **ubuntu-desktop-minimal
  based** install:

  2023-11-10 07:03:16,578 DEBUG nvidiaUpdate()
  2023-11-10 07:03:20,125 INFO no old nvidia driver installed, installing no new
  2023-11-10 07:03:20,125 DEBUG quirks: running PostDistUpgradeCache
  2023-11-10 07:03:20,125 DEBUG running Quirks.PostDistUpgradeCache
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-35 with
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-36 with 6.2.0-35
  2023-11-10 07:03:20,238 DEBUG Comparing 6.5.0-10 with 6.2.0-36
  2023-11-10 07:03:20,554 ERROR Dist-upgrade failed: 'Broken packages after 
upgrade: gnome-remote-desktop, gnome-shell'
  2023-11-10 07:03:20,564 DEBUG abort called

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+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 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken

[Raziel Anarki]

chi, i've just upgraded from LTS to 23.04 and (with virtually no extra
packages installed), and now i get the same error

ie: the upgrader thinking i need  ppa-purge,

while apt.log:

> # cat apt.log | grep "can't"
>libmutter-12-0:amd64 Depends on mutter-common-bin:amd64 < 44.3-0ubuntu1.1 
> -> 45.0-3ubuntu3.1 @ii umU > (= 44.3-0ubuntu1.1) can't be satisfied! (dep)
>libavcodec59:amd64 Depends on libswresample4:amd64 < 7:5.1.2-3ubuntu1 -> 
> 7:6.0-6ubuntu1 @ii umU Ib > (= 7:5.1.2-3ubuntu1) can't be satisfied! (dep)
>libevent-core-2.1-7a:amd64 Depends on libevent-core-2.1-7:amd64 < 
> 2.1.12-stable-8ubuntu3 -> 2.1.12-stable-9 @ii umU > (= 
> 2.1.12-stable-8ubuntu3) can't be satisfied! (dep)
>libavfilter8:amd64 Depends on libswresample4:amd64 < 7:5.1.2-3ubuntu1 -> 
> 7:6.0-6ubuntu1 @ii umU > (= 7:5.1.2-3ubuntu1) can't be satisfied! (dep)


** Attachment added: "apt.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+attachment/5722922/+files/apt.log

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

Title:
  Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop &
  gnome-shell packages are broken

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Running do-release-upgrade on 23.04 (lunar), **ubuntu-desktop-minimal
  based** install:

  2023-11-10 07:03:16,578 DEBUG nvidiaUpdate()
  2023-11-10 07:03:20,125 INFO no old nvidia driver installed, installing no new
  2023-11-10 07:03:20,125 DEBUG quirks: running PostDistUpgradeCache
  2023-11-10 07:03:20,125 DEBUG running Quirks.PostDistUpgradeCache
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-35 with
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-36 with 6.2.0-35
  2023-11-10 07:03:20,238 DEBUG Comparing 6.5.0-10 with 6.2.0-36
  2023-11-10 07:03:20,554 ERROR Dist-upgrade failed: 'Broken packages after 
upgrade: gnome-remote-desktop, gnome-shell'
  2023-11-10 07:03:20,564 DEBUG abort called

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+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 2043538] Re: gnome-shell takes too much ram

[Vincent Jaubert]

I doubt it is related to AppIndicators since i installed it to watch my memory 
problem ;)
But to left no stone unturned, i will try.

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

Title:
  gnome-shell takes too much ram

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I had no memory problems with Ubuntu 20.04.
  After upgrading to Ubuntu 22.04, my 16GB laptop suffered from lack of memory.
  I upgraded to 48GB (!), and the memory still continues to fill.
  After a few days, with no program started, 12GB is taken. Gnome-shell alone 
is taking 17.4% of my 48GB.
  I guess it is suffering from a memory leak. 

  Description:Ubuntu 22.04.3 LTS

  gnome-shell:
Installé : 42.9-0ubuntu2
Candidat : 42.9-0ubuntu2
   Table de version :
   *** 42.9-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.0-2ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 07:04:21 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-31 (75 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  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/2043538/+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 1100190]

[Qa-admin-q]

Dear Philipp Gassmann,

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

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

If you have time, please do the following:

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
  [Upstream] I/O Error while opening file from WebDAV over GVFS from
  Nautilus

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

Bug description:
  Problem description: 
  Error when opening a file from Nautilus with LibreOffice when the file is 
WebDAV mounted with GVFS.

  The Same file can be opened from the same location from within
  LibreOffice, with the Open File Dialogue. Then you get asked for the
  Username and Password and Libreoffice seems to access the file
  directly over HTTP.

  Steps to reproduce:
  1. Mount a DAV Folder with Nautilus. 
  URL in my Case: 
dav://admin@10.1.10.58:8080/alfresco/webdav/Sites/puzzletest/documentLibrary/Alfresco%20WebDAV%20Test/
  2. Open a file with LibreOffice by doubleclick or context menu from Nautilus.
  4. Error occurs.
  Exact message:
  (-) «General input/output error while accessing /home/pgassmann/.gvfs/WebDAV\ 
als\ admin\ auf\ 10.1.10.58%3A8080/Sites/puzzletest/documentLibrary/Alfresco\ 
WebDAV\ Test/Neu.odt.» [OK]

  Working Variant:
  1. = 1. above
  2. Start LibreOffice
  3. Open File dialogue from LibreOffice
  4. Select the same file and click Open.
  5. LibreOffice Dialogue: "Authentication Required", Enter user name and 
password for: "Alfresco DAV Server" on 10.1.10.58
  6. Enter Username and password, click OK
  7. File opens correctly

  LibreOffice Version:
  3.5.2-2ubuntu1

  Involved Software: 
  LibreOffice, Nautilus, GVFS, Alfresco

  Current behavior:
  Opening file from Nautilus causes Error,
  Opening from LibreOffice Open File dialogue asks for credentials and works 
correctly

  Expected behavior:
  Opening from Nautilus works.
  Opening from Open File dialog works without asking for credentials.

  Attachment: strace log from following actions:
  LANG=C libreoffice --strace
  successfully Open File from LibreOffice dialogue.
  Trying to open file from Nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice 1:3.5.4-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
  Uname: Linux 3.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Wed Jan 16 10:05:05 2013
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to precise on 2012-05-22 (238 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1100190/+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 2044420] Re: gtkpod segfaults when attempting to display songs

[Matthew Ruffell]

Upstream bug: https://gitlab.gnome.org/GNOME/glib/-/issues/3185

** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3185
   https://gitlab.gnome.org/GNOME/glib/-/issues/3185

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

Title:
  gtkpod segfaults when attempting to display songs

Status in glib2.0 package in Ubuntu:
  New
Status in gtkpod package in Ubuntu:
  New
Status in glib2.0 source package in Mantic:
  New
Status in gtkpod source package in Mantic:
  New
Status in glib2.0 source package in Noble:
  New
Status in gtkpod source package in Noble:
  New

Bug description:
  Open gtkpod, and select your ipod from the list. If it has more than
  one screenfull of songs to display in the list, gtkpod will
  immediately segfault.

  I haven't found a workaround yet.

  Broken on Mantic, works on Lunar.

  Thread 1 "gtkpod" received signal SIGSEGV, Segmentation fault.
  __GI___wcsxfrm_l (dest=0x0, src=0x0, n=0, l=0x76fff5a0 
<_nl_global_locale>) at ../string/strxfrm_l.c:685
  685   ../string/strxfrm_l.c: No such file or directory.
  (gdb) bt
  #0  __GI___wcsxfrm_l (dest=0x0, src=0x0, n=0, l=0x76fff5a0 
<_nl_global_locale>) at ../string/strxfrm_l.c:685
  #1  0x770c5a5e in g_utf8_collate_key () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x77f852ec in fuzzy_skip_prefix () at 
/lib/x86_64-linux-gnu/libgtkpod.so.1
  #3  0x7fffa80980ca in ??? () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #4  0x7fffa80997fd in normal_sort_tab_page_add_track () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #5  0x7fffa8099526 in normal_sort_tab_page_add_track () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #6  0x7fffa809f196 in sorttab_display_select_playlist_cb () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #7  0x7718d130 in g_closure_invoke () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #8  0x771ba4ac in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #9  0x771ab9b1 in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x771abbd6 in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x771abc93 in g_signal_emit () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #12 0x77f67e4b in gtkpod_set_current_playlist () at 
/lib/x86_64-linux-gnu/libgtkpod.so.1
  #13 0x7fffa807cce0 in ??? () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libplaylist_display.so
  #14 0x7708ba11 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #15 0x770e746f in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #16 0x7708c46f in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #17 0x777f61ed in gtk_main () at /lib/x86_64-linux-gnu/libgtk-3.so.0
  #18 0xea1f in main ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2044420/+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 2044420] Re: gtkpod segfaults when attempting to display songs

[Phil Wyett]

This is likely to see little attention for the following reasons:

* Not maintained/No viable upstream.
* Remove Request (RM) is active in Debian. [1]

This package is likely to be soon removed and I would advise looking for
an alternative to it.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018855

** Bug watch added: Debian Bug tracker #1018855
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018855

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

Title:
  gtkpod segfaults when attempting to display songs

Status in glib2.0 package in Ubuntu:
  New
Status in gtkpod package in Ubuntu:
  New
Status in glib2.0 source package in Mantic:
  New
Status in gtkpod source package in Mantic:
  New
Status in glib2.0 source package in Noble:
  New
Status in gtkpod source package in Noble:
  New

Bug description:
  Open gtkpod, and select your ipod from the list. If it has more than
  one screenfull of songs to display in the list, gtkpod will
  immediately segfault.

  I haven't found a workaround yet.

  Broken on Mantic, works on Lunar.

  Thread 1 "gtkpod" received signal SIGSEGV, Segmentation fault.
  __GI___wcsxfrm_l (dest=0x0, src=0x0, n=0, l=0x76fff5a0 
<_nl_global_locale>) at ../string/strxfrm_l.c:685
  685   ../string/strxfrm_l.c: No such file or directory.
  (gdb) bt
  #0  __GI___wcsxfrm_l (dest=0x0, src=0x0, n=0, l=0x76fff5a0 
<_nl_global_locale>) at ../string/strxfrm_l.c:685
  #1  0x770c5a5e in g_utf8_collate_key () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x77f852ec in fuzzy_skip_prefix () at 
/lib/x86_64-linux-gnu/libgtkpod.so.1
  #3  0x7fffa80980ca in ??? () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #4  0x7fffa80997fd in normal_sort_tab_page_add_track () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #5  0x7fffa8099526 in normal_sort_tab_page_add_track () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #6  0x7fffa809f196 in sorttab_display_select_playlist_cb () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #7  0x7718d130 in g_closure_invoke () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #8  0x771ba4ac in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #9  0x771ab9b1 in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x771abbd6 in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x771abc93 in g_signal_emit () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #12 0x77f67e4b in gtkpod_set_current_playlist () at 
/lib/x86_64-linux-gnu/libgtkpod.so.1
  #13 0x7fffa807cce0 in ??? () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libplaylist_display.so
  #14 0x7708ba11 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #15 0x770e746f in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #16 0x7708c46f in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #17 0x777f61ed in gtk_main () at /lib/x86_64-linux-gnu/libgtk-3.so.0
  #18 0xea1f in main ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2044420/+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 2044420] Re: gtkpod segfaults when attempting to display songs

[Matthew Ruffell]

** Also affects: glib2.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  gtkpod segfaults when attempting to display songs

Status in glib2.0 package in Ubuntu:
  New
Status in gtkpod package in Ubuntu:
  New
Status in glib2.0 source package in Mantic:
  New
Status in gtkpod source package in Mantic:
  New
Status in glib2.0 source package in Noble:
  New
Status in gtkpod source package in Noble:
  New

Bug description:
  Open gtkpod, and select your ipod from the list. If it has more than
  one screenfull of songs to display in the list, gtkpod will
  immediately segfault.

  I haven't found a workaround yet.

  Broken on Mantic, works on Lunar.

  Thread 1 "gtkpod" received signal SIGSEGV, Segmentation fault.
  __GI___wcsxfrm_l (dest=0x0, src=0x0, n=0, l=0x76fff5a0 
<_nl_global_locale>) at ../string/strxfrm_l.c:685
  685   ../string/strxfrm_l.c: No such file or directory.
  (gdb) bt
  #0  __GI___wcsxfrm_l (dest=0x0, src=0x0, n=0, l=0x76fff5a0 
<_nl_global_locale>) at ../string/strxfrm_l.c:685
  #1  0x770c5a5e in g_utf8_collate_key () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x77f852ec in fuzzy_skip_prefix () at 
/lib/x86_64-linux-gnu/libgtkpod.so.1
  #3  0x7fffa80980ca in ??? () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #4  0x7fffa80997fd in normal_sort_tab_page_add_track () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #5  0x7fffa8099526 in normal_sort_tab_page_add_track () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #6  0x7fffa809f196 in sorttab_display_select_playlist_cb () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #7  0x7718d130 in g_closure_invoke () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #8  0x771ba4ac in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #9  0x771ab9b1 in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x771abbd6 in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x771abc93 in g_signal_emit () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #12 0x77f67e4b in gtkpod_set_current_playlist () at 
/lib/x86_64-linux-gnu/libgtkpod.so.1
  #13 0x7fffa807cce0 in ??? () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libplaylist_display.so
  #14 0x7708ba11 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #15 0x770e746f in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #16 0x7708c46f in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #17 0x777f61ed in gtk_main () at /lib/x86_64-linux-gnu/libgtk-3.so.0
  #18 0xea1f in main ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2044420/+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 2044411] Re: retroeclairage ecran

[Daniel van Vugt]

Thanks for the bug report. Unfortunately we are unable to support this
system because your graphics packages are from the unsupported "oibaf"
PPA, which is known to cause bugs. Please remove that PPA from the
system and continue to report new bugs for any issues you find.


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

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

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

Title:
  retroeclairage ecran

Status in Ubuntu:
  Invalid

Bug description:
  retroeclairage ecran

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Nov 23 20:35:19 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:020e]
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:020e]
  InstallationDate: Installed on 2023-11-23 (0 days ago)
  InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  MachineType: Packard Bell EasyNote LJ65
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=UUID=243ada55-1961-402d-b934-b5f45e2edfa4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2009
  dmi.bios.vendor: Packard Bell
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: EasyNote LJ65
  dmi.board.vendor: Packard Bell
  dmi.board.version: V2.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnPackardBell:bvrV2.07:bd09/29/2009:svnPackardBell:pnEasyNoteLJ65:pvrV2.07:rvnPackardBell:rnEasyNoteLJ65:rvrV2.07:cvnPackardBell:ct10:cvrV2.07:skuMontevina_Fab:
  dmi.product.family: Intel_Mobile
  dmi.product.name: EasyNote LJ65
  dmi.product.sku: Montevina_Fab
  dmi.product.version: V2.07
  dmi.sys.vendor: Packard Bell
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.118+git2311210500.02a41c~oibaf~j
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0~git2311230600.9528d0~oibaf~j
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  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/+bug/2044411/+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 2044395] Re: System Freeze

[Daniel van Vugt]

What was the last working kernel version that didn't freeze?

Does the freeze also affect other desktop environments?

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

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

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

Title:
  System Freeze

Status in Ubuntu:
  Incomplete

Bug description:
  my ubuntu freeze when I update my kernel version, I hope this log can
  help me find the cause

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: sway
  Date: Fri Nov 24 00:36:04 2023
  DistUpgraded: 2023-11-23 22:23:58,950 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback/0.12.7, 6.2.0-33-generic, x86_64: installed
   v4l2loopback/0.12.7, 6.5.0-10-generic, x86_64: installed
   v4l2loopback/0.12.7, 6.5.0-12-generic, x86_64: installed
   v4l2loopback/0.12.7, 6.5.0-13-generic, x86_64: built
   v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation GeminiLake [UHD Graphics 600] [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation GeminiLake [UHD Graphics 600] [8086:2212]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-kitty
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=e81e591a-f843-455e-9125-867ecc3ab1d2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to mantic on 2023-11-23 (0 days ago)
  dmi.bios.date: 07/26/2022
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FW-BI-14.1-S8_G_116R100A-E60A-014-A
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: ITo be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.ec.firmware.release: 0.23
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFW-BI-14.1-S8_G_116R100A-E60A-014-A:bd07/26/2022:br5.13:efr0.23:svnSHENZHENYOUDISIE-COMMERCECO.LTD:pnXBOOK-2:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnITobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XBOOK-2
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: SHENZHEN YOUDISI E-COMMERCE CO. LTD
  version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu4
  version.libdrm2: libdrm2 2.4.117-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.8-1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2044395/+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 2003042] Re: gnome-shell crashed with SIGSEGV in meta_kms_connector_read_state(drm_connector=NULL) from meta_kms_connector_update_state()

[Daniel van Vugt]

** Tags removed: rls-kk-incoming

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_kms_connector_read_state(drm_connector=NULL) from
  meta_kms_connector_update_state()

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter package in Fedora:
  Unknown

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
43.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/8158e20e6ac0a16fd196b1b06a27678cf87f2029 
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/mutter/+bug/2003042/+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 2044382] Re: Quassel opens "another" icon under Gnome

[Daniel van Vugt]

Sounds like https://github.com/micheleg/dash-to-dock/issues/651

** Bug watch added: github.com/micheleg/dash-to-dock/issues #651
   https://github.com/micheleg/dash-to-dock/issues/651

** Tags added: mantic

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

Title:
  Quassel opens "another" icon under Gnome

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New
Status in quassel package in Ubuntu:
  New

Bug description:
  I'm unsure if this is a bug in quassel, or in the gnome dock itself.
  Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the
  left bar results in the pinned icon appearing "idle" (not running),
  and a second icon appearing below those that are pinned which
  apparently represents the running quassel instance.

  Pressing the idle quassel icon (or pressing the Super+4 shortcut for
  it) runs *another* instance of quassel rather than switching to the
  running instance. The "extra" icon also cannot be pinned (and
  occasionally strange "copies" of it are left lying around if one tries
  to drag it to the pinned icon locations).

  This may be because quassel is a Qt based application, but I also run
  KeepassXC (another Qt application) without such issues (other than
  unusual window borders and icons which appear on both applications),
  hence why I'm unsure this is an issue in quassel or in the gnome dock.
  I'll attach a screenshot demonstrating the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2044382/+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 2043538] Re: gnome-shell takes too much ram

[Daniel van Vugt]

Yep that's a leak.

Please start by disabling AppIndicators:

  gnome-extensions disable ubuntu-appindicat...@ubuntu.com

and then log in again. Does the bug still occur?

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

Title:
  gnome-shell takes too much ram

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I had no memory problems with Ubuntu 20.04.
  After upgrading to Ubuntu 22.04, my 16GB laptop suffered from lack of memory.
  I upgraded to 48GB (!), and the memory still continues to fill.
  After a few days, with no program started, 12GB is taken. Gnome-shell alone 
is taking 17.4% of my 48GB.
  I guess it is suffering from a memory leak. 

  Description:Ubuntu 22.04.3 LTS

  gnome-shell:
Installé : 42.9-0ubuntu2
Candidat : 42.9-0ubuntu2
   Table de version :
   *** 42.9-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.0-2ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 07:04:21 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-31 (75 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  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/2043538/+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

[Mauricio Faria de Oliveira]

Verification (synthetic) of the XDG_SESSION_TYPE fix in Mantic:

$ lsb_release -cs
No LSB modules are available.
mantic

The packages are downloaded from Launchpad librarian
since previous versions are not available in archive.

Before the fix (reverted) // 1:23.10.12
---

The XDG_CURRENT_DESKTOP variable IS NOT passed in `pkexec ... --env=`.

$ wget https://launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/1:23.10.12/+build/26929436/+files/{ubuntu-release-
upgrader-{core,gtk},python3-distupgrade}_23.10.12_all.deb

$ sudo apt install -y ./ubuntu-release-upgrader-
core_23.10.12_all.deb ./ubuntu-release-upgrader-gtk_23.10.12_all.deb
./python3-distupgrade_23.10.12_all.deb

$ dpkg -s ubuntu-release-upgrader-core | grep Version:
Version: 1:23.10.12

$ export XDG_CURRENT_DESKTOP=just:testing

$ strace -s 128 do-release-upgrade -d -f DistUpgradeViewGtk3 2>&1 | 
grep '^execve("/usr/bin/pkexec"' | grep -o -- '--env=[^"]\+'

--env=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus,XDG_SESSION_TYPE=tty

After the fix (reapplied) // 1:23.10.13
---

The XDG_CURRENT_DESKTOP variable IS passed in `pkexec ... --env=`.

$ wget https://launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/1:23.10.13/+build/26932072/+files/{ubuntu-release-
upgrader-{core,gtk},python3-distupgrade}_23.10.13_all.deb

$ sudo apt install -y ./ubuntu-release-upgrader-
core_23.10.13_all.deb ./ubuntu-release-upgrader-gtk_23.10.13_all.deb
./python3-distupgrade_23.10.13_all.deb

$ dpkg -s ubuntu-release-upgrader-core | grep Version:
Version: 1:23.10.13

$ export XDG_CURRENT_DESKTOP=just:testing

$ strace -s 128 do-release-upgrade -d -f DistUpgradeViewGtk3 2>&1 | 
grep '^execve("/usr/bin/pkexec"' | grep -o -- '--env=[^"]\+'

--env=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus,XDG_SESSION_TYPE=tty,XDG_CURRENT_DESKTOP=just:testing

Latest version (mantic-proposed) // 1:23.10.14
---

The XDG_CURRENT_DESKTOP variable IS passed in `pkexec ... --env=`.

$ sudo add-apt-repository -yp proposed

$ sudo apt install -y -t mantic-proposed ubuntu-release-
upgrader-core

$ dpkg -s ubuntu-release-upgrader-core | grep Version:
Version: 1:23.10.14

$ strace -s 128 do-release-upgrade -d -f DistUpgradeViewGtk3 2>&1 | 
grep '^execve("/usr/bin/pkexec"' | grep -o -- '--env=[^"]\+'

--env=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus,XDG_SESSION_TYPE=tty,XDG_CURRENT_DESKTOP=just:testing

-- 
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 Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release 

[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Mauricio Faria de Oliveira]

Summary for Mantic SRUs.

There are 3 LP bugs combined in mantic-proposed
(list sorted by package version so it's helpful).

1) Bug 2034986, used twice,

1A) First for 1:23.10.9, for 'fix v1':
* Temporary font for Ubuntu MATE (LP: #2034986)

It's released to mantic-updates with 1:23.10.10 (fix for
autopkgtests).

1B) Later for 1:23.10.11, for XDG_CURRENT_DESKTOP:
* do-release-upgrade: pass XDG_CURRENT_DESKTOP env var (LP: #2034986) 

It's reverted in 1:23.10.12:
* Temporarily revert "do-release-upgrade: pass XDG_CURRENT_DESKTOP env var"

and reapplied in 1:23.10.13:
* do-release-upgrade: pass XDG_CURRENT_DESKTOP env var (LP: #2034986)

2) Bug 2039356, used for 'fix v2' in 1:23:10.12:
* Adjustments of unreadable text workaround (LP: #2039356)

3) Bug 2039172, used for an unrelated quirk:
* DistUpgradeQuirks: prevent upgrades on BIOS systems with XFS /boot (LP: 
#2039172)

...

So, for verification, we have to consider 1:23.10.11 up to .14.

.11 doesn't need verification, as it's reverted in .12
.12 is verified (comment #65 / bug 2039356 comment #3)
.13 is not yet verified (comment #65, #66)
.14 is verified, but pending questions (bug 2039172 comment #9)

Thus, it seems what is pending for releasing mantic-proposed
is verification for .13 (that I'm happy to do synthetically),
plus a question for .14 (I'd be be happy to help, if needed).

-- 
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 Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original 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" - 

[Desktop-packages] [Bug 2043538] Re: gnome-shell takes too much ram

[Vincent Jaubert]

Here is what you asked for.
I have taken the recording with all GUI programms closed. 

** Attachment added: "ps-gs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043538/+attachment/5722841/+files/ps-gs.txt

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

Title:
  gnome-shell takes too much ram

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I had no memory problems with Ubuntu 20.04.
  After upgrading to Ubuntu 22.04, my 16GB laptop suffered from lack of memory.
  I upgraded to 48GB (!), and the memory still continues to fill.
  After a few days, with no program started, 12GB is taken. Gnome-shell alone 
is taking 17.4% of my 48GB.
  I guess it is suffering from a memory leak. 

  Description:Ubuntu 22.04.3 LTS

  gnome-shell:
Installé : 42.9-0ubuntu2
Candidat : 42.9-0ubuntu2
   Table de version :
   *** 42.9-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.0-2ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 07:04:21 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-31 (75 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  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/2043538/+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 2003042] Re: gnome-shell crashed with SIGSEGV in meta_kms_connector_read_state(drm_connector=NULL) from meta_kms_connector_update_state()

[Bug Watch Updater]

Launchpad has imported 17 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=2131269.

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 2022-09-30T13:42:15+00:00 kxra wrote:

Version-Release number of selected component:
gnome-shell-43.0-2.fc37

Additional info:
reporter:   libreport-2.17.4
backtrace_rating: 4
cgroup: 
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service
cmdline:/usr/bin/gnome-shell
crash_function: meta_kms_connector_read_state
dso_list:   /usr/bin/gnome-shell gnome-shell-43.0-2.fc37.x86_64 (Fedora 
Project) 1664437312
executable: /usr/bin/gnome-shell
journald_cursor: 
s=077a7e261b994b6c8c3b7bfb61d4808f;i=39d95;b=d18c6b9efc764bab9556a3f27efc7431;m=5d7ae831e;t=5e9e4dae5c13a;x=b0ef9ac64bae4473
kernel: 5.19.11-300.fc37.x86_64
rootdir:/
runlevel:   N 5
type:   CCpp
uid:1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 meta_kms_connector_read_state at 
../src/backends/native/meta-kms-connector.c:684
 #1 meta_kms_connector_update_state at 
../src/backends/native/meta-kms-connector.c:767
 #2 meta_kms_impl_device_update_states at 
../src/backends/native/meta-kms-impl-device.c:916
 #3 meta_kms_device_update_states_in_impl at 
../src/backends/native/meta-kms-device.c:267
 #4 meta_kms_update_states_in_impl at ../src/backends/native/meta-kms.c:604
 #5 update_states_in_impl at ../src/backends/native/meta-kms.c:620
 #6 meta_kms_run_impl_task_sync at ../src/backends/native/meta-kms.c:435
 #7 meta_kms_update_states_sync at ../src/backends/native/meta-kms.c:641
 #8 handle_hotplug_event at ../src/backends/native/meta-kms.c:651
 #9 on_udev_hotplug at ../src/backends/native/meta-kms.c:668

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/comments/0


On 2022-09-30T13:42:18+00:00 kxra wrote:

Created attachment 1915271
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/comments/1


On 2022-09-30T13:42:19+00:00 kxra wrote:

Created attachment 1915272
File: core_backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/comments/2


On 2022-09-30T13:42:20+00:00 kxra wrote:

Created attachment 1915273
File: cpuinfo

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/comments/3


On 2022-09-30T13:42:22+00:00 kxra wrote:

Created attachment 1915274
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/comments/4


On 2022-09-30T13:42:23+00:00 kxra wrote:

Created attachment 1915275
File: exploitable

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/comments/5


On 2022-09-30T13:42:24+00:00 kxra wrote:

Created attachment 1915276
File: limits

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/comments/6


On 2022-09-30T13:42:25+00:00 kxra wrote:

Created attachment 1915277
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/comments/7


On 2022-09-30T13:42:26+00:00 kxra wrote:

Created attachment 1915278
File: mountinfo

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/comments/8


On 2022-09-30T13:42:27+00:00 kxra wrote:

Created attachment 1915279
File: open_fds

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/comments/9


On 2022-09-30T13:42:28+00:00 kxra wrote:

Created attachment 1915280
File: proc_pid_status

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/comments/10


On 2022-09-30T13:42:29+00:00 kxra wrote:

Created attachment 1915281
File: var_log_messages

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/comments/11


On 2022-11-22T09:15:37+00:00 MIKHAIL.NIKITIN1 wrote:

Similar problem has been detected:

This caused by laptop going to sleep mode and returning back

[Desktop-packages] [Bug 2043027] Re: Wacom Intuos S stop working after upgrading to Ubuntu 23.10

[Valentin Svilenov Stoyanov]

Hello,

Might I add, I experience the same issue. My machine is a Lenovo Yoga 7 14ARP8, 
which is a 2-in-1 convertible. Issue was not present before I upgraded to 23.10 
from 22.04.03. If I may augment the "handy details" above:
- I've no dedicated graphics card - AMD Radeon 680M integrated into the CPU;
- The issue persists on tablet mode (fully-folded backwards), laptop mode and 
when wired to 1 or 2 monitors.

Even if it's an GNOME issue, I would really like to use it for the out-
of-the-box touchscreen gestures it offers right away.

Best,
Valentin

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

Title:
  Wacom Intuos S stop working after upgrading to Ubuntu 23.10

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Tablet seems to work until I open Krita (as I could read on Internet,
  it may be related with Qt Apps).

  When Krita is open, mouse movement works ok with the tablet, but when
  it comes to click action it doesn't work and any further action with
  mouse is not captured (even outside Krita!).

  To regain control of the mouse I have to Alt+Tab and then I can click
  again.

  Some details that may be handy:
  - I've got two monitors
  - Maybe Qt apps related
  - My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535

  Thanks for your effort. I love Ubuntu!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-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..06.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.129.03  Thu Oct 19 
18:56:32 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 17:20:34 2023
  DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
   nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
   virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] 
[19da:1438]
  InstallationDate: Installed on 2022-04-09 (578 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=9dd904a0-11bb-40fa-9fe8-2f10449a416c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-11-07 (1 days ago)
  dmi.bios.date: 06/15/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0608
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING B550-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0608:bd06/15/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB550-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: 

[Desktop-packages] [Bug 2044411] [NEW] retroeclairage ecran

[Alocci]

Public bug reported:

retroeclairage ecran

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Nov 23 20:35:19 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:020e]
   Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:020e]
InstallationDate: Installed on 2023-11-23 (0 days ago)
InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
MachineType: Packard Bell EasyNote LJ65
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=UUID=243ada55-1961-402d-b934-b5f45e2edfa4 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/29/2009
dmi.bios.vendor: Packard Bell
dmi.bios.version: V2.07
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: EasyNote LJ65
dmi.board.vendor: Packard Bell
dmi.board.version: V2.07
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell
dmi.chassis.version: V2.07
dmi.modalias: 
dmi:bvnPackardBell:bvrV2.07:bd09/29/2009:svnPackardBell:pnEasyNoteLJ65:pvrV2.07:rvnPackardBell:rnEasyNoteLJ65:rvrV2.07:cvnPackardBell:ct10:cvrV2.07:skuMontevina_Fab:
dmi.product.family: Intel_Mobile
dmi.product.name: EasyNote LJ65
dmi.product.sku: Montevina_Fab
dmi.product.version: V2.07
dmi.sys.vendor: Packard Bell
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.118+git2311210500.02a41c~oibaf~j
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0~git2311230600.9528d0~oibaf~j
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
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 third-party-packages 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/2044411

Title:
  retroeclairage ecran

Status in xorg package in Ubuntu:
  New

Bug description:
  retroeclairage ecran

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Nov 23 20:35:19 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:020e]
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:020e]
  InstallationDate: Installed on 2023-11-23 (0 days ago)
  InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  MachineType: Packard Bell EasyNote LJ65
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=UUID=243ada55-1961-402d-b934-b5f45e2edfa4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2009
  dmi.bios.vendor: Packard Bell
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: EasyNote LJ65
  dmi.board.vendor: Packard Bell
  dmi.board.version: V2.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnPackardBell:bvrV2.07:bd09/29/2009:svnPackardBell:pnEasyNoteLJ65:pvrV2.07:rvnPackardBell:rnEasyNoteLJ65:rvrV2.07:cvnPackardBell:ct10:cvrV2.07:skuMontevina_Fab:
  dmi.product.family: Intel_Mobile
  dmi.product.name: EasyNote LJ65
  dmi.product.sku: Montevina_Fab
  dmi.product.version: V2.07
  dmi.sys.vendor: Packard Bell
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.118+git2311210500.02a41c~oibaf~j
  version.libgl1-mesa-dri: libgl1-mesa-dri 

[Desktop-packages] [Bug 2042811] Re: [BPO] libreoffice 7.5.8 for jammy

[Rico Tzschichholz]

The corresponding SRU for lunar went through. Please accept this
backport upload from the jammy queue.

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

Title:
  [BPO] libreoffice 7.5.8 for jammy

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Jammy:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.5.8 is in its eighth and last bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.8_release

   * This source packages matches the proposed SRU for lunar handled at
   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2041716

  [Scope]

   * Backport of
  https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.8-0ubuntu0.23.04.1

   * Backport target is Jammy/22.04 LTS releases to provide an official
  build of a more recent upstream version of LibreOffice

  [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/1762/

    * 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.

     Jammy/22.04 build at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/15363218/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20231104_215443_4f9d7@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/arm64/libr/libreoffice/20231105_003318_b15a5@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/armhf/libr/libreoffice/20231106_141135_bbe65@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/ppc64el/libr/libreoffice/20231104_222356_65e77@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/s390x/libr/libreoffice/20231104_234922_f066c@/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 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/2042811/+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 2041716] Re: [SRU] libreoffice 7.5.8 for lunar

[Launchpad Bug Tracker]

This bug was fixed in the package libreoffice - 4:7.5.8-0ubuntu0.23.04.1

---
libreoffice (4:7.5.8-0ubuntu0.23.04.1) lunar; urgency=medium

  * New upstream release (LP: #2041716)

  [ Rico Tzschichholz ]
  * debian/patches/fix-arm64-tests.diff:
- Dropped while it got fixed upsteam
  * debian/rules:
- Remove potentially harmful replacement in control

  [ Rene Engelhard ]
  * debian/rules:
- Update officebean so install comment to reflect reality;
  libreoffice-officebean is long gone
- Fix typo, s/disble/disable/

 -- Rico Tzschichholz   Wed, 01 Nov 2023 21:57:34
+0100

** Changed in: libreoffice (Ubuntu Lunar)
   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/2041716

Title:
  [SRU] libreoffice 7.5.8 for lunar

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

Bug description:
  [Impact]

   * LibreOffice 7.5.8 is in its eighth and last bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.8_release

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

   7.5.8 RC2 is identical to the 7.5.8 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/1762/

    * 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/~ricotz/+archive/ubuntu/ppa/+sourcepub/15348703/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20231029_113409_73daf@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20231029_195903_c198a@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/armhf/libr/libreoffice/20231029_204848_b6986@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20231029_113020_49f1b@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20231029_131951_9ac3d@/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 21 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/2041716/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

[Tom Mason]

I'm not the original bug reporter, but thought the extra diagnostics may
assist.

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

[Tom Mason]

apport information

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

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

[Tom Mason]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/2011385/+attachment/5722765/+files/PaInfo.txt

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

[Tom Mason]

apport information

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

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

[Tom Mason]

apport information

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

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

[Tom Mason]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2011385/+attachment/5722763/+files/CurrentDmesg.txt

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

[Tom Mason]

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/2011385/+attachment/5722762/+files/AudioDevicesInUse.txt

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

[Tom Mason]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/2011385/+attachment/5722761/+files/AlsaInfo.txt

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

[Tom Mason]

ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-04-04 (233 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
NonfreeKernelModules: nvidia_modeset nvidia
Package: alsa-base 1.0.25+dfsg-0ubuntu7
PackageArchitecture: all
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-24 (30 days ago)
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/18/2023
dmi.bios.release: 1.6
dmi.bios.vendor: Razer
dmi.bios.version: 1.06
dmi.board.name: SO690
dmi.board.vendor: Razer
dmi.board.version: 4
dmi.chassis.type: 10
dmi.chassis.vendor: Razer
dmi.ec.firmware.release: 1.8
dmi.modalias: 
dmi:bvnRazer:bvr1.06:bd01/18/2023:br1.6:efr1.8:svnRazer:pnBlade16-RZ09-0483:pvr9.04:rvnRazer:rnSO690:rvr4:cvnRazer:ct10:cvr:skuRZ09-0483UWJ4:
dmi.product.family: 1A583006 Razer Blade
dmi.product.name: Blade 16 - RZ09-0483
dmi.product.sku: RZ09-0483UWJ4
dmi.product.version: 9.04
dmi.sys.vendor: Razer


** Tags added: apport-collected mantic

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2041716] Re: [SRU] libreoffice 7.5.8 for lunar

[Andreas Hasenack]

I'm OK with releasing this one day short of the 7-day aging period. I
don't think there is any gain in waiting an extra day for this update.

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

Title:
  [SRU] libreoffice 7.5.8 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.8 is in its eighth and last bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.8_release

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

   7.5.8 RC2 is identical to the 7.5.8 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/1762/

    * 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/~ricotz/+archive/ubuntu/ppa/+sourcepub/15348703/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20231029_113409_73daf@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20231029_195903_c198a@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/armhf/libr/libreoffice/20231029_204848_b6986@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20231029_113020_49f1b@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20231029_131951_9ac3d@/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 21 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/2041716/+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 2041716] Update Released

[Andreas Hasenack]

The verification of the Stable Release Update for libreoffice 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 libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/2041716

Title:
  [SRU] libreoffice 7.5.8 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.8 is in its eighth and last bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.8_release

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

   7.5.8 RC2 is identical to the 7.5.8 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/1762/

    * 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/~ricotz/+archive/ubuntu/ppa/+sourcepub/15348703/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20231029_113409_73daf@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20231029_195903_c198a@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/armhf/libr/libreoffice/20231029_204848_b6986@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20231029_113020_49f1b@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20231029_131951_9ac3d@/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 21 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/2041716/+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 2044395] [NEW] System Freeze

[John Paul Caigas]

Public bug reported:

my ubuntu freeze when I update my kernel version, I hope this log can
help me find the cause

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: sway
Date: Fri Nov 24 00:36:04 2023
DistUpgraded: 2023-11-23 22:23:58,950 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
 v4l2loopback/0.12.7, 6.2.0-33-generic, x86_64: installed
 v4l2loopback/0.12.7, 6.5.0-10-generic, x86_64: installed
 v4l2loopback/0.12.7, 6.5.0-12-generic, x86_64: installed
 v4l2loopback/0.12.7, 6.5.0-13-generic, x86_64: built
 v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff between 
built and installed module!)
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation GeminiLake [UHD Graphics 600] [8086:3185] (rev 03) (prog-if 
00 [VGA controller])
   Subsystem: Intel Corporation GeminiLake [UHD Graphics 600] [8086:2212]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/zsh
 TERM=xterm-kitty
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=e81e591a-f843-455e-9125-867ecc3ab1d2 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2023-11-23 (0 days ago)
dmi.bios.date: 07/26/2022
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FW-BI-14.1-S8_G_116R100A-E60A-014-A
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: ITo be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: To be filled by O.E.M.
dmi.chassis.version: To be filled by O.E.M.
dmi.ec.firmware.release: 0.23
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFW-BI-14.1-S8_G_116R100A-E60A-014-A:bd07/26/2022:br5.13:efr0.23:svnSHENZHENYOUDISIE-COMMERCECO.LTD:pnXBOOK-2:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnITobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: XBOOK-2
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: SHENZHEN YOUDISI E-COMMERCE CO. LTD
version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu4
version.libdrm2: libdrm2 2.4.117-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu4
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.8-1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug mantic third-party-packages ubuntu wayland-session

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

Title:
  System Freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  my ubuntu freeze when I update my kernel version, I hope this log can
  help me find the cause

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: sway
  Date: Fri Nov 24 00:36:04 2023
  DistUpgraded: 2023-11-23 22:23:58,950 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback/0.12.7, 6.2.0-33-generic, x86_64: installed
   v4l2loopback/0.12.7, 6.5.0-10-generic, x86_64: installed
   v4l2loopback/0.12.7, 6.5.0-12-generic, x86_64: installed
   v4l2loopback/0.12.7, 6.5.0-13-generic, x86_64: built
   v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation GeminiLake [UHD Graphics 600] [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation GeminiLake [UHD Graphics 600] [8086:2212]
  

[Desktop-packages] [Bug 2041831] Re: /usr/bin/update-manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup

[Julian Andres Klode]

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

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

Title:
  /usr/bin/update-
  
manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup

Status in pygobject package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
update-manager.  This problem was most recently seen with package version 
1:23.10.1, the problem page at 
https://errors.ubuntu.com/problem/dff72cd5c27c916b2d887a56311ba08ef15b0dff 
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/pygobject/+bug/2041831/+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 2037004] Re: warnings in terminal with software-properties-gtk

[Julian Andres Klode]

This is from ubuntu-drivers-common:

UbuntuDrivers/detect.py
452:out = subprocess.check_output(['udevadm', 'hwdb', '--test=' + 
alias],
455:logging.debug('_get_db_name(%s, %s): udevadm hwdb failed: %s', 
syspath, alias, str(e))


** Package changed: software-properties (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/2037004

Title:
  warnings in terminal with software-properties-gtk

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

Bug description:
  When running software-properties-gtk and switching to the "Additional
  Drivers" tab I saw the following warnings in my terminal:

   $ software-properties-gtk 
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: software-properties-gtk 0.99.39
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 11:49:24 2023
  InstallationDate: Installed on 2018-08-10 (1868 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2037004/+subscriptions


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

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

[Lukas Märdian]

** Tags removed: rls-nn-incoming

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

Title:
  Provide an option to avoid the yaml NM backend

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

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

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

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

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 2044019] Re: [SRU] libreoffice 7.6.3 for mantic

[Rico Tzschichholz]

** Description changed:

  [Impact]
  
   * LibreOffice 7.6.3 is in its third bugfix release of the 7.6 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.3_release
  
   * Version 7.6.2 is currently released in mantic. For a list of fixed bugs 
compared to 7.6.2 see the list of bugs fixed in the release candidates of 7.6.3 
(that's a total of 116 bugs):
   https://wiki.documentfoundation.org/Releases/7.6.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.6.3/RC2#List_of_fixed_bugs
  
   7.6.3 RC2 is identical to the 7.6.3 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_76/1459/
  
    * 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/15393176/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/amd64/libr/libreoffice/20231123_103407_283ac@/log.gz
  * [arm64] ...
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/armhf/libr/libreoffice/20231123_114914_bf535@/log.gz
- * [ppc64el] ...
+ * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/ppc64el/libr/libreoffice/20231123_150619_c4055@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/s390x/libr/libreoffice/20231123_122430_41ff2@/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 116 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.

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

Title:
  [SRU] libreoffice 7.6.3 for mantic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Mantic:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.6.3 is in its third bugfix release of the 7.6 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.3_release

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

   7.6.3 RC2 is identical to the 7.6.3 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_76/1459/

    * 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
    

[Desktop-packages] [Bug 2044019] Re: [SRU] libreoffice 7.6.3 for mantic

[Rico Tzschichholz]

** Description changed:

  [Impact]
  
   * LibreOffice 7.6.3 is in its third bugfix release of the 7.6 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.3_release
  
-  * Version 7.6.2 is currently released in mantic. For a list of fixed bugs 
compared to 7.6.2 see the list of bugs fixed in the release candidates of 7.6.3 
(that's a total of 115+ bugs):
+  * Version 7.6.2 is currently released in mantic. For a list of fixed bugs 
compared to 7.6.2 see the list of bugs fixed in the release candidates of 7.6.3 
(that's a total of 116 bugs):
   https://wiki.documentfoundation.org/Releases/7.6.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.6.3/RC2#List_of_fixed_bugs
  
   7.6.3 RC2 is identical to the 7.6.3 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_76/1459/
  
    * 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/15389862/+listing-archive-extra
- * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/amd64/libr/libreoffice/20231122_055508_b6ab7@/log.gz
- * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/arm64/libr/libreoffice/20231122_065528_077f4@/log.gz
- * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/armhf/libr/libreoffice/20231122_045051_d78ff@/log.gz
- * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/ppc64el/libr/libreoffice/20231122_033828_5af8c@/log.gz
+ Tested build can be found at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15393176/+listing-archive-extra
+ * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/amd64/libr/libreoffice/20231123_103407_283ac@/log.gz
+ * [arm64] ...
+ * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/armhf/libr/libreoffice/20231123_114914_bf535@/log.gz
+ * [ppc64el] ...
  * [riscv64] not available
- * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/s390x/libr/libreoffice/20231122_124339_d7006@/log.gz
+ * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/s390x/libr/libreoffice/20231123_122430_41ff2@/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 115+ bug fixes always carries the
+  * A minor release with a total of 116 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.

** Changed in: libreoffice (Ubuntu)
   Status: New => 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/2044019

Title:
  [SRU] libreoffice 7.6.3 for mantic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Mantic:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.6.3 is in its third bugfix release of the 7.6 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.3_release

   * Version 7.6.2 is currently released in mantic. For a list of fixed bugs 

[Desktop-packages] [Bug 2043015] Update Released

[Andreas Hasenack]

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

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

Title:
  Update gnome-shell to 45.1

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Mantic:
  Fix Released

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 45 series.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/45.1/NEWS

  Test Case
  -
  Complete all the non-optional test cases at 
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  gnome-shell provides the GNOME version number for the Settings app About 
page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by 
gnome-desktop/gnome-desktop3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043015/+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 2043015] Re: Update gnome-shell to 45.1

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 45.1-0ubuntu1

---
gnome-shell (45.1-0ubuntu1) mantic; urgency=medium

  * New upstream release (LP: #2043015)
  * Drop 2 patches applied in new release

 -- Jeremy Bícha   Wed, 08 Nov 2023 18:33:02 +0200

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

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

Title:
  Update gnome-shell to 45.1

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Mantic:
  Fix Released

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 45 series.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/45.1/NEWS

  Test Case
  -
  Complete all the non-optional test cases at 
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  gnome-shell provides the GNOME version number for the Settings app About 
page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by 
gnome-desktop/gnome-desktop3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043015/+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 2012954] Re: drag and drop files via hot corner Activities Overview don't work anymore

[Launchpad Bug Tracker]

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

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

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

Title:
  drag and drop files via hot corner Activities Overview  don't work
  anymore

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  With gnome 42, you can drag and drop a file (for example from nautilus
  to firefox) via hot corner to move from one maximized window to
  another maximized window.

  to do this we click on the file, while maintaining the click we move
  it to the upper corner to switch to another application and deposit it
  (drop a file drop a file on a website for example)

  on gnome 43 (ubuntu 22.10) it doesn't work anymore. Moving file to hot
  corner does not open the Activities Overview

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012954/+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 2007702] Re: [SRU] Deb version numbering is misleading

[Nathan Teodosio]

That scheme already made its way into Noble. Will we then [1] submit a
new package with that native package scheme for Noble, [2] do the native
package scheme only for the SRUs or [3] do the SRUs with the non-native
scheme for consistency?

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

Title:
  [SRU] Deb version numbering is misleading

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  New
Status in chromium-browser source package in Jammy:
  New
Status in chromium-browser source package in Lunar:
  New
Status in chromium-browser source package in Mantic:
  New

Bug description:
  [Impact]
  For Ubuntu >= Focal the transitional debs are frozen at the version number 
1:85...

  This might make one think[1][2] that it will install a critically
  outdated Chromium while it does not, because it installs the snap.

  [Test plan]

  Install the package and confirm the version change with e.g.

    dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1'

  [Regression potential]

  If the version were incorrectly constructed the deb build could fail.

  [1] 
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591
  [2] https://askubuntu.com/q/1420925

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+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 2044382] [NEW] Quassel opens "another" icon under Gnome

[Dave Jones]

Public bug reported:

I'm unsure if this is a bug in quassel, or in the gnome dock itself.
Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the
left bar results in the pinned icon appearing "idle" (not running), and
a second icon appearing below those that are pinned which apparently
represents the running quassel instance.

Pressing the idle quassel icon (or pressing the Super+4 shortcut for it)
runs *another* instance of quassel rather than switching to the running
instance. The "extra" icon also cannot be pinned (and occasionally
strange "copies" of it are left lying around if one tries to drag it to
the pinned icon locations).

This may be because quassel is a Qt based application, but I also run
KeepassXC (another Qt application) without such issues (other than
unusual window borders and icons which appear on both applications),
hence why I'm unsure this is an issue in quassel or in the gnome dock.
I'll attach a screenshot demonstrating the issue.

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

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

** Attachment added: "Screenshot from 2023-11-23 13-42-51.png"
   
https://bugs.launchpad.net/bugs/2044382/+attachment/5722734/+files/Screenshot%20from%202023-11-23%2013-42-51.png

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

- I'm unsure if this is a bug in quassel, or in gnome itself. Under Ubuntu
- 23.10 (mantic), running Quassel from a pinned icon on the left bar
- results in the pinned icon appearing "idle" (not running), and a second
- icon appearing below those that are pinned which apparently represents
- the running quassel instance.
+ I'm unsure if this is a bug in quassel, or in the gnome dock itself.
+ Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the
+ left bar results in the pinned icon appearing "idle" (not running), and
+ a second icon appearing below those that are pinned which apparently
+ represents the running quassel instance.
  
  Pressing the idle quassel icon (or pressing the Super+4 shortcut for it)
  runs *another* instance of quassel rather than switching to the running
  instance. The "extra" icon also cannot be pinned (and occasionally
  strange "copies" of it are left lying around if one tries to drag it to
  the pinned icon locations).
  
  This may be because quassel is a Qt based application, but I also run
  KeepassXC (another Qt application) without such issues (other than
  unusual window borders and icons which appear on both applications),
- hence why I'm unsure this is an issue in quassel or in gnome. I'll
- attach a screenshot demonstrating the issue.
+ hence why I'm unsure this is an issue in quassel or in the gnome dock.
+ I'll attach a screenshot demonstrating the issue.

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

Title:
  Quassel opens "another" icon under Gnome

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New
Status in quassel package in Ubuntu:
  New

Bug description:
  I'm unsure if this is a bug in quassel, or in the gnome dock itself.
  Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the
  left bar results in the pinned icon appearing "idle" (not running),
  and a second icon appearing below those that are pinned which
  apparently represents the running quassel instance.

  Pressing the idle quassel icon (or pressing the Super+4 shortcut for
  it) runs *another* instance of quassel rather than switching to the
  running instance. The "extra" icon also cannot be pinned (and
  occasionally strange "copies" of it are left lying around if one tries
  to drag it to the pinned icon locations).

  This may be because quassel is a Qt based application, but I also run
  KeepassXC (another Qt application) without such issues (other than
  unusual window borders and icons which appear on both applications),
  hence why I'm unsure this is an issue in quassel or in the gnome dock.
  I'll attach a screenshot demonstrating the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2044382/+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 2034664] Update Released

[Andreas Hasenack]

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

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

Title:
  Meta.Rectangle is deprecated, use Mtk.Rectangle instead

Status in gnome-shell-extension-tiling-assistant package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-tiling-assistant source package in Mantic:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  The gnome-shell 45.rc log fills with:

  Meta.Rectangle is deprecated, use Mtk.Rectangle instead

  [ Test case ]

  Run ubuntu with ubuntu extensions enabled (only).
  journalctl /usr/bin/gnome-shell should not contain any reference to 
Meta.Rectangle deprecation

  [ Regression potential ]

  Introspected types are not defined and so extensions may try to use
  undefined code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
87ubuntu2

---
gnome-shell-extension-ubuntu-dock (87ubuntu2) mantic; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * locationsWorker: Exit with the main script exit code (LP: #2038783)

  [ Stuart Hayhurst ]
  * appIcons: Use Mtk.Rectangle instead of Meta.Rectangle (LP: #2034664)

 -- Marco Trevisan (Treviño)   Mon, 09 Oct 2023
03:04:54 +0200

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

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

Title:
  Meta.Rectangle is deprecated, use Mtk.Rectangle instead

Status in gnome-shell-extension-tiling-assistant package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-tiling-assistant source package in Mantic:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  The gnome-shell 45.rc log fills with:

  Meta.Rectangle is deprecated, use Mtk.Rectangle instead

  [ Test case ]

  Run ubuntu with ubuntu extensions enabled (only).
  journalctl /usr/bin/gnome-shell should not contain any reference to 
Meta.Rectangle deprecation

  [ Regression potential ]

  Introspected types are not defined and so extensions may try to use
  undefined code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2038783] Re: Exit code of locations mount script is not respecting error

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
87ubuntu2

---
gnome-shell-extension-ubuntu-dock (87ubuntu2) mantic; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * locationsWorker: Exit with the main script exit code (LP: #2038783)

  [ Stuart Hayhurst ]
  * appIcons: Use Mtk.Rectangle instead of Meta.Rectangle (LP: #2034664)

 -- Marco Trevisan (Treviño)   Mon, 09 Oct 2023
03:04:54 +0200

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

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

Title:
  Exit code of locations mount script is not respecting error

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  When mounting an external location a script is used to get the current
  default app for a type, its return error is parsed by the dock to
  provide users a feedback, but the returned code is not valid in case
  of error.

  [ Test case ]

  Run:
    gjs -m 
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js 
handler file:///foo/bar/baz
    echo $?

  An error should be shown and the return code should be 1

  Doing instead

    gjs -m 
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js 
handler file://$HOME
    echo $?

  The file manager desktop-id should be printed and the script should
  return 0.

  [ Regression Potential ]

  Some locations may not have a default handler and so not being
  launched

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2038783/+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 2038783] Update Released

[Andreas Hasenack]

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

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

Title:
  Exit code of locations mount script is not respecting error

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  When mounting an external location a script is used to get the current
  default app for a type, its return error is parsed by the dock to
  provide users a feedback, but the returned code is not valid in case
  of error.

  [ Test case ]

  Run:
    gjs -m 
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js 
handler file:///foo/bar/baz
    echo $?

  An error should be shown and the return code should be 1

  Doing instead

    gjs -m 
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js 
handler file://$HOME
    echo $?

  The file manager desktop-id should be printed and the script should
  return 0.

  [ Regression Potential ]

  Some locations may not have a default handler and so not being
  launched

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2038783/+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 2044369] [NEW] [SRU] libreoffice 7.5.9 for lunar

[Rico Tzschichholz]

Public bug reported:

[Impact]

 * LibreOffice 7.5.9 is in its ninth and last bugfix release of the 7.5 line:
 https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.9_release

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

 7.5.9 RC1 is identical to the 7.5.9 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/1776/

  * 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/~ricotz/+archive/ubuntu/ppa/+sourcepub/15393334/+listing-archive-extra
* [amd64] ...
* [arm64] ...
* [armhf] ...
* [ppc64el] ...
* [riscv64] not available
* [s390x] ...
 * 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 ? 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.

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: libreoffice (Ubuntu Lunar)
 Importance: Medium
 Assignee: Rico Tzschichholz (ricotz)
 Status: In Progress

** Also affects: libreoffice (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Changed in: libreoffice (Ubuntu Lunar)
   Status: New => In Progress

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

** Changed in: libreoffice (Ubuntu Lunar)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

** Changed in: libreoffice (Ubuntu)
   Status: New => 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/2044369

Title:
  [SRU] libreoffice 7.5.9 for lunar

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Lunar:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.5.9 is in its ninth and last bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.9_release

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

   7.5.9 RC1 is identical to the 7.5.9 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/1776/

    * 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 

[Desktop-packages] [Bug 2007702] Re: [SRU] Deb version numbering is misleading

[Julian Andres Klode]

2:1snap1-0ubuntu1.22.04.1 is a non-native version number but of course
there is no upstream version, it would be a lot better to do this
correctly as a native package, like 2:1snap0ubuntu1.22.04.1

** Description changed:

- For Ubuntu >= Focal the transitional debs are frozen at the version
- number 1:85...
+ [Impact]
+ For Ubuntu >= Focal the transitional debs are frozen at the version number 
1:85...
  
  This might make one think[1][2] that it will install a critically
  outdated Chromium while it does not, because it installs the snap.
  
  [Test plan]
  
  Install the package and confirm the version change with e.g.
  
-   dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1'
+   dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1'
  
  [Regression potential]
  
  If the version were incorrectly constructed the deb build could fail.
  
  [1] 
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591
  [2] https://askubuntu.com/q/1420925

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

Title:
  [SRU] Deb version numbering is misleading

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  New
Status in chromium-browser source package in Jammy:
  New
Status in chromium-browser source package in Lunar:
  New
Status in chromium-browser source package in Mantic:
  New

Bug description:
  [Impact]
  For Ubuntu >= Focal the transitional debs are frozen at the version number 
1:85...

  This might make one think[1][2] that it will install a critically
  outdated Chromium while it does not, because it installs the snap.

  [Test plan]

  Install the package and confirm the version change with e.g.

    dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1'

  [Regression potential]

  If the version were incorrectly constructed the deb build could fail.

  [1] 
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591
  [2] https://askubuntu.com/q/1420925

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+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 2041716] Re: [SRU] libreoffice 7.5.8 for lunar

[Rico Tzschichholz]

Upgraded libreoffice from 4:7.5.7-0ubuntu0.23.04.1 to
4:7.5.8-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/2041716

Title:
  [SRU] libreoffice 7.5.8 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.8 is in its eighth and last bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.8_release

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

   7.5.8 RC2 is identical to the 7.5.8 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/1762/

    * 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/~ricotz/+archive/ubuntu/ppa/+sourcepub/15348703/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20231029_113409_73daf@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20231029_195903_c198a@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/armhf/libr/libreoffice/20231029_204848_b6986@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20231029_113020_49f1b@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20231029_131951_9ac3d@/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 21 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/2041716/+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 2043838] Re: "Welcome" App hangs

[Olivier Gayot]

Hello,

I'm adding gnome-initial-setup and for now I'm marking invalid for
subiquity, since it happens on first boot.

Thanks,
Olivier

** Also affects: gnome-initial-setup (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: subiquity
   Status: New => Invalid

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

Title:
  "Welcome" App hangs

Status in subiquity:
  Invalid
Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  RE: Noble Daily ISO image=2023116

  After a new install, on first boot, during the "Welcome" app progress
  through the panels, it throws an error, saying the Welcome app is
  unresponsive, asking the user if they want to kill it or wait...
  Choosing wait, it recovers and goes on.

  To reproduce, install with any (working) script option. Happens during
  the first boot.

  This is a left-over from Mantic, as many Mantic users report that this
  is happening to them, after installing Mantic, on the first boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 17 10:48:24 2023
  InstallationDate: Installed on 2023-11-17 (1 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231116)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: subiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Nathan Teodosio]

Hi Athos, thanks for having a look.

 > Would you mind filing the SRU paperwork as per the template at 
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ?

I think I have already done that. It is admittedly very short but so is 
the proposed change. Should I extend any section?

 > Could you please fix the version numbers for each release?

I'm attaching those, thanks.

** Patch added: "jammy.diff"
   https://bugs.launchpad.net/bugs/2007702/+attachment/5722648/+files/jammy.diff

** Patch added: "focal.diff"
   https://bugs.launchpad.net/bugs/2007702/+attachment/5722649/+files/focal.diff

** Patch added: "lunar.diff"
   https://bugs.launchpad.net/bugs/2007702/+attachment/5722650/+files/lunar.diff

** Patch added: "mantic.diff"
   
https://bugs.launchpad.net/bugs/2007702/+attachment/5722651/+files/mantic.diff

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

Title:
  [SRU] Deb version numbering is misleading

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  New
Status in chromium-browser source package in Jammy:
  New
Status in chromium-browser source package in Lunar:
  New
Status in chromium-browser source package in Mantic:
  New

Bug description:
  For Ubuntu >= Focal the transitional debs are frozen at the version
  number 1:85...

  This might make one think[1][2] that it will install a critically
  outdated Chromium while it does not, because it installs the snap.

  [Test plan]

  Install the package and confirm the version change with e.g.

dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1'

  [Regression potential]

  If the version were incorrectly constructed the deb build could fail.

  [1] 
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591
  [2] https://askubuntu.com/q/1420925

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+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 1875717] Re: Opening file from Samba share results in Document in Use

[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/1875717

Title:
  Opening file from Samba share results in Document in Use

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  This bug is related to bug # 1430531.

  I am running Lubuntu version 20.04 with all updates installed
  The Libre Office version :
  Version: 6.4.2.2
  Build ID: 1:6.4.2-0ubuntu3
  CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5;
  Locale: en-GB (en_GB.UTF-8); UI-Language: en-US
  Calc: threaded

  1. connect to share on local network with PCManFM-Qt File Manager
  2. click on file TEST_Samba.odt
  3. The Libre Office splash/Logo screen appears for a split second and the 
nothing happens and the file is not opened.
  4. I then right-click on file and select "open with Libre Office Writer
  5. Document in Use" window appears with text:

     Document file 'TEST_Samba.odt' is locked for editing by:

     Unknown User

     Open document read-only or open a copy of the document for editing.

     Open Read-Only Open Copy Cancel

  Screen shot attached..

  Expected results:
     The "TEST_Samba.odt" files is opened in read-write mode, user can edit it.

  Actual results:
     User can't edit original document (see 3-5 above)

  I have tested this on several boxes running Lubuntu 20.04 with the exact same 
results.
  I have also tested this on SparkyLinux LxQT version 5.11 with the same 
results.
  Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing 
and/or saving this file back to the Samba share.

  
  Global Samba config is "default"
   Usershare config is:

  $ cat /var/lib/samba/usershares/sameign2
  #VERSION 2
  path=/home/kbeins/Sameign2
  comment=
  usershare_acl=S-1-1-0:F
  guest_ok=n
  sharename=Sameign2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Tue Apr 28 17:51:14 2020
  InstallationDate: Installed on 2020-04-28 (0 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+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 2042909] Re: keyboard backlight slider and automatic brightness causes gnome-shell to freeze (mostly on MacBooks)

[Daniel van Vugt]

** Summary changed:

- keyboard backlight slider and automatic brightness causes gnome-shell to 
freeze
+ keyboard backlight slider and automatic brightness causes gnome-shell to 
freeze (mostly on MacBooks)

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

Title:
  keyboard backlight slider and automatic brightness causes gnome-shell
  to freeze (mostly on MacBooks)

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

Bug description:
  Ubuntu 23.10
  Gnome Shell 45.0
  I expect gdm and the shell to be responsive but they freeze forcing me to 
reboot. Sometimes I'm able to use them but it takes some time to load.

  After taking a look at the journal, I see lots of messages like this:
  #0   564c4df768c8 i   resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 
@ 48)
  nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to run a JS callback 
during garbage collection. This is most likely caused by destroying a Clutter 
actor or GTK widget with ::destroy signal connected, or using the destroy(), 
dispose(), or remove() vfuncs. Because it would crash the application, it has 
been blocked.
 The offending callback was 
AsyncReadyCallback().
 == Stack trace for context 
0x564c4deaab90 ==
 #0   564c4df768c8 i   
resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 @ 48)
  nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
 The offending signal was 
g-properties-changed on GDBusProxy 0x564c4fec8670.
 == Stack trace for context 
0x564c4deaab90 ==

  On successful boots this seems to auto resolve, being followed by this 
message:
  nov 07 09:21:56 perseus dbus-daemon[1758]: [session uid=1000 pid=1758] 
Successfully activated service 'org.freedesktop.impl.portal.desktop.gnome'
  nov 07 09:21:56 perseus systemd[1722]: Started 
xdg-desktop-portal-gnome.service - Portal service (GNOME implementation).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2042909/+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 2042909] Re: keyboard backlight slider and automatic brightness causes gnome-shell to freeze

[Pierrick]

I'm having a similar issue, mentioned as duplicate of this bug report.

Whenever I go beyond 50% brightness it freezes with:

The offending signal was notify on Gjs_status_backlight_SliderItem
0x5566a1978a70.

Same happens when booting if the value is above 50%.

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

Title:
  keyboard backlight slider and automatic brightness causes gnome-shell
  to freeze

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

Bug description:
  Ubuntu 23.10
  Gnome Shell 45.0
  I expect gdm and the shell to be responsive but they freeze forcing me to 
reboot. Sometimes I'm able to use them but it takes some time to load.

  After taking a look at the journal, I see lots of messages like this:
  #0   564c4df768c8 i   resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 
@ 48)
  nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to run a JS callback 
during garbage collection. This is most likely caused by destroying a Clutter 
actor or GTK widget with ::destroy signal connected, or using the destroy(), 
dispose(), or remove() vfuncs. Because it would crash the application, it has 
been blocked.
 The offending callback was 
AsyncReadyCallback().
 == Stack trace for context 
0x564c4deaab90 ==
 #0   564c4df768c8 i   
resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 @ 48)
  nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
 The offending signal was 
g-properties-changed on GDBusProxy 0x564c4fec8670.
 == Stack trace for context 
0x564c4deaab90 ==

  On successful boots this seems to auto resolve, being followed by this 
message:
  nov 07 09:21:56 perseus dbus-daemon[1758]: [session uid=1000 pid=1758] 
Successfully activated service 'org.freedesktop.impl.portal.desktop.gnome'
  nov 07 09:21:56 perseus systemd[1722]: Started 
xdg-desktop-portal-gnome.service - Portal service (GNOME implementation).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2042909/+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 2044336] Re: gnome-shell freezes while flooding the log with: Attempting to call back into JSAPI during the sweeping phase of GC. ... The offending signal was g-properties-chan

[Daniel van Vugt]

*** This bug is a duplicate of bug 2042909 ***
https://bugs.launchpad.net/bugs/2042909

Nice find. We're already tracking it in bug 2042909.

** This bug has been marked a duplicate of bug 2042909
   keyboard backlight slider and automatic brightness causes gnome-shell to 
freeze

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

Title:
  gnome-shell freezes while flooding the log with: Attempting to call
  back into JSAPI during the sweeping phase of GC. ... The offending
  signal was g-properties-changed on GDBusProxy ...

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Since I upgraded to Ubuntu 23.10 the GUI is unresponsive during, maybe 30 
seconds, then it works perfectly fine.
  I connected via SSH to see what was happening in the logs when that happens 
and it may be the logs collected, e.g.:

  2023-11-23T08:01:07.113135+01:00 enfants-ecole gnome-shell[1234]: Attempting 
to call back into JSAPI during the sweepin
  g phase of GC. This is most likely caused by not destroying a Clutter actor 
or Gtk+ widget with ::destroy signals conne
  cted, but can also be caused by using the destroy(), dispose(), or remove() 
vfuncs. Because it would crash the applicat
  ion, it has been blocked and the JS callback not invoked.#012The offending 
signal was notify on Gjs_ubuntu-dock_ubuntu_
  com_docking_DashToDock 0x55a9a71d3fb0.#012== Stack trace for context 
0x55a9a45f9d40 ==#012#0   55a9a46bc888 i   resourc
  e:///org/gnome/shell/ui/init.js:21 (6ea76470ba0 @ 48)
  2023-11-23T08:01:07.113227+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0x55a9a738ab20] is on because it 
needs an allocation.
  2023-11-23T08:01:07.113319+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0x55a9a738b8f0] is on because it needs an allocation.
  2023-11-23T08:01:07.113407+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0x55a9a71d58d0] is on because it needs an 
allocation.
  2023-11-23T08:01:07.113495+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0
  x55a9a7385880] is on because it needs an allocation.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
  Uname: Linux 6.5.0-13-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 08:06:45 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-11-22 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2044336/+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 2044336] Re: gnome-shell freezes while flooding the log with: Attempting to call back into JSAPI during the sweeping phase of GC. ... The offending signal was g-properties-chan

[Pierrick]

OK got it, when I go beyond 50% brightness it freezes with:

The offending signal was notify on Gjs_status_backlight_SliderItem
0x5566a1978a70.

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

Title:
  gnome-shell freezes while flooding the log with: Attempting to call
  back into JSAPI during the sweeping phase of GC. ... The offending
  signal was g-properties-changed on GDBusProxy ...

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Since I upgraded to Ubuntu 23.10 the GUI is unresponsive during, maybe 30 
seconds, then it works perfectly fine.
  I connected via SSH to see what was happening in the logs when that happens 
and it may be the logs collected, e.g.:

  2023-11-23T08:01:07.113135+01:00 enfants-ecole gnome-shell[1234]: Attempting 
to call back into JSAPI during the sweepin
  g phase of GC. This is most likely caused by not destroying a Clutter actor 
or Gtk+ widget with ::destroy signals conne
  cted, but can also be caused by using the destroy(), dispose(), or remove() 
vfuncs. Because it would crash the applicat
  ion, it has been blocked and the JS callback not invoked.#012The offending 
signal was notify on Gjs_ubuntu-dock_ubuntu_
  com_docking_DashToDock 0x55a9a71d3fb0.#012== Stack trace for context 
0x55a9a45f9d40 ==#012#0   55a9a46bc888 i   resourc
  e:///org/gnome/shell/ui/init.js:21 (6ea76470ba0 @ 48)
  2023-11-23T08:01:07.113227+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0x55a9a738ab20] is on because it 
needs an allocation.
  2023-11-23T08:01:07.113319+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0x55a9a738b8f0] is on because it needs an allocation.
  2023-11-23T08:01:07.113407+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0x55a9a71d58d0] is on because it needs an 
allocation.
  2023-11-23T08:01:07.113495+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0
  x55a9a7385880] is on because it needs an allocation.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
  Uname: Linux 6.5.0-13-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 08:06:45 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-11-22 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2044336/+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 2044336] Re: gnome-shell freezes while flooding the log with: Attempting to call back into JSAPI during the sweeping phase of GC. ... The offending signal was g-properties-chan

[Pierrick]

I found this: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7001

And it looks like when I play with keyboard backlight (it's a MacBook
Pro) the GUI freezes.

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

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

Title:
  gnome-shell freezes while flooding the log with: Attempting to call
  back into JSAPI during the sweeping phase of GC. ... The offending
  signal was g-properties-changed on GDBusProxy ...

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Since I upgraded to Ubuntu 23.10 the GUI is unresponsive during, maybe 30 
seconds, then it works perfectly fine.
  I connected via SSH to see what was happening in the logs when that happens 
and it may be the logs collected, e.g.:

  2023-11-23T08:01:07.113135+01:00 enfants-ecole gnome-shell[1234]: Attempting 
to call back into JSAPI during the sweepin
  g phase of GC. This is most likely caused by not destroying a Clutter actor 
or Gtk+ widget with ::destroy signals conne
  cted, but can also be caused by using the destroy(), dispose(), or remove() 
vfuncs. Because it would crash the applicat
  ion, it has been blocked and the JS callback not invoked.#012The offending 
signal was notify on Gjs_ubuntu-dock_ubuntu_
  com_docking_DashToDock 0x55a9a71d3fb0.#012== Stack trace for context 
0x55a9a45f9d40 ==#012#0   55a9a46bc888 i   resourc
  e:///org/gnome/shell/ui/init.js:21 (6ea76470ba0 @ 48)
  2023-11-23T08:01:07.113227+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0x55a9a738ab20] is on because it 
needs an allocation.
  2023-11-23T08:01:07.113319+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0x55a9a738b8f0] is on because it needs an allocation.
  2023-11-23T08:01:07.113407+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0x55a9a71d58d0] is on because it needs an 
allocation.
  2023-11-23T08:01:07.113495+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0
  x55a9a7385880] is on because it needs an allocation.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
  Uname: Linux 6.5.0-13-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 08:06:45 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-11-22 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2044336/+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 2044336] Re: gnome-shell freezes while flooding the log with: Attempting to call back into JSAPI during the sweeping phase of GC. ... The offending signal was g-properties-chan

[Daniel van Vugt]

I think the next step is to monitor dbus to find out what is causing:

  g-properties-changed on GDBusProxy

because it looks like the volume of events is the issue.

** Summary changed:

- Lots of error message filling disk
+ gnome-shell freezes while flooding the log with: Attempting to call back into 
JSAPI during the sweeping phase of GC. ... The offending signal was 
g-properties-changed on GDBusProxy ...

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

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

Title:
  gnome-shell freezes while flooding the log with: Attempting to call
  back into JSAPI during the sweeping phase of GC. ... The offending
  signal was g-properties-changed on GDBusProxy ...

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Since I upgraded to Ubuntu 23.10 the GUI is unresponsive during, maybe 30 
seconds, then it works perfectly fine.
  I connected via SSH to see what was happening in the logs when that happens 
and it may be the logs collected, e.g.:

  2023-11-23T08:01:07.113135+01:00 enfants-ecole gnome-shell[1234]: Attempting 
to call back into JSAPI during the sweepin
  g phase of GC. This is most likely caused by not destroying a Clutter actor 
or Gtk+ widget with ::destroy signals conne
  cted, but can also be caused by using the destroy(), dispose(), or remove() 
vfuncs. Because it would crash the applicat
  ion, it has been blocked and the JS callback not invoked.#012The offending 
signal was notify on Gjs_ubuntu-dock_ubuntu_
  com_docking_DashToDock 0x55a9a71d3fb0.#012== Stack trace for context 
0x55a9a45f9d40 ==#012#0   55a9a46bc888 i   resourc
  e:///org/gnome/shell/ui/init.js:21 (6ea76470ba0 @ 48)
  2023-11-23T08:01:07.113227+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0x55a9a738ab20] is on because it 
needs an allocation.
  2023-11-23T08:01:07.113319+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0x55a9a738b8f0] is on because it needs an allocation.
  2023-11-23T08:01:07.113407+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0x55a9a71d58d0] is on because it needs an 
allocation.
  2023-11-23T08:01:07.113495+01:00 enfants-ecole gnome-shell[1234]: Can't 
update stage views actor [:0
  x55a9a7385880] is on because it needs an allocation.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
  Uname: Linux 6.5.0-13-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 08:06:45 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-11-22 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-11-22 (0 days ago)

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