Re: [Desktop-packages] [Bug 2045478] Re: [snap] Chromium-Browser starts with unmaximized window

[Nathan Teodosio]

What is 'type -a chromium' and 'lsb_release -a'? Do you use Gnome Shell 
extensions? If you try some other window manager (e.g. icewm), does the 
problem persist?

Am 05/12/2023 um 01:54 schrieb Mickael Reis:
> After I read your message, I tried to remove and purge chromium snap package 
> and install it again but I have the same problem.
> I use default Gnome desktop environment in Ubuntu and "snap info chromium" 
> give me that :
> name:  chromium
> summary:   Chromium web browser, open-source version of Chrome
> publisher: Canonical✓
> store-url: https://snapcraft.io/chromium
> contact:   
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
> license:   unset
> description: |
>An open-source browser project that aims to build a safer, faster, and more
>stable way for all Internet users to experience the web.
> commands:
>- chromium.chromedriver
>- chromium
> snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
> tracking: latest/stable
> refresh-date: aujourd'hui à 01h50, heure des Rocheuses
> channels:
>latest/stable:119.0.6045.199 2023-12-04 (2704) 165MB -
>latest/candidate: 119.0.6045.199 2023-11-29 (2704) 165MB -
>latest/beta:  120.0.6099.56  2023-11-30 (2707) 166MB -
>latest/edge:  121.0.6129.0   2023-11-17 (2699) 167MB -
> 
>

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

Title:
  [snap] Chromium-Browser starts with unmaximized window

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium browser by default start with an unmaximized window in my Ubuntu 
system and I've to manually do maximize.
  I have try to edit all desktop file I can edit to add --start-maximized 
option but it doesn't work ...
  And i can't edit desktop file in /snap/chromium directory

  Is it possible to modify desktop file with another way or snap package
  must be updated with this option ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2045478/+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 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep

[Wojciech Semik]

I have the same issue. Kubuntu 22.04, after sleep/screen lock my usb-c
-> display port connected monitor goes from 5120x1440 down to 3840x2160.

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

Title:
  [amdgpu] Wrong external screen resolution after wake up from sleep

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04,
  running KDE) I started experiencing a problem with external screen
  resolution after the wake up from sleep. The monitor resolution is
  small (1280x768) and doesn't respect the setting prior the sleep
  (1920x1200).

  After the wake up from sleep:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1280x768  59.94* 
 # a list of lower resolutions
  ```

  There is an error when trying to change the setting to the highest
  resolution supported by the monitor (which is not included in the
  above list).

  ```
  > xrandr --output DisplayPort-1 --mode 1920x1200
  xrandr: cannot find mode 1920x1200
  ```

  After the turn off and turn on of the external monitor, the resolution
  is somehow added to the xrandr list:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1920x1200 59.95 +
 # a list of resolutions
 1280x768  59.94* 
 # a list of lower resolutions
  ```

  Now it is possible to change the resolution:

  ```
  > xrandr --output DisplayPort-1 --mode 1920x1200
  # no output, the resolution was successfully changed
  ```   

  After the change, the resolution is successfully changed and xrandr
  gives proper output:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1920x1200 59.95*+
 # a list of lower resolutions
  ```

  The problem is not present on fresh start. However, it is consistently
  present after the wake up from sleep.

  What can cause the problem and how may I fix it?

  Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the
  external monitor is connected via USB-C. There are no problems with
  laptop screen resolution, only external monitor is affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Jun 16 18:12:05 2022
  DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2019-08-21 (1030 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20NE000BMC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic 
root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft 
vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago)
  dmi.bios.date: 01/26/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET44W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NE000BMC
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET44W(1.24):bd01/26/2022:br1.24:efr1.24:svnLENOVO:pn20NE000BMC:pvrThinkPadE495:rvnLENOVO:rn20NE000BMC:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NE000BMC
  dmi.product.sku: 

[Desktop-packages] [Bug 2045478] Re: [snap] Chromium-Browser starts with unmaximized window

[Mickael Reis]

After I read your message, I tried to remove and purge chromium snap package 
and install it again but I have the same problem.
I use default Gnome desktop environment in Ubuntu and "snap info chromium" give 
me that :
name:  chromium
summary:   Chromium web browser, open-source version of Chrome
publisher: Canonical✓
store-url: https://snapcraft.io/chromium
contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license:   unset
description: |
  An open-source browser project that aims to build a safer, faster, and more
  stable way for all Internet users to experience the web.
commands:
  - chromium.chromedriver
  - chromium
snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/stable
refresh-date: aujourd'hui à 01h50, heure des Rocheuses
channels:
  latest/stable:119.0.6045.199 2023-12-04 (2704) 165MB -
  latest/candidate: 119.0.6045.199 2023-11-29 (2704) 165MB -
  latest/beta:  120.0.6099.56  2023-11-30 (2707) 166MB -
  latest/edge:  121.0.6129.0   2023-11-17 (2699) 167MB -


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

Title:
  [snap] Chromium-Browser starts with unmaximized window

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium browser by default start with an unmaximized window in my Ubuntu 
system and I've to manually do maximize.
  I have try to edit all desktop file I can edit to add --start-maximized 
option but it doesn't work ...
  And i can't edit desktop file in /snap/chromium directory

  Is it possible to modify desktop file with another way or snap package
  must be updated with this option ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2045478/+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 253670]

[Qa-admin-q]

Dear Christopher M. Penalver,

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

Title:
  [upstream] Draw exporting .odg to .eps removes inserted image

Status in LibreOffice:
  Confirmed
Status in OpenOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Triaged
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-draw
  libreoffice-draw:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  apt-cache policy unoconv
  unoconv:
Installed: 0.3-6
Candidate: 0.3-6
Version table:
   *** 0.3-6 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in LibreOffice Draw via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/253670/+attachment/364486/+files/EPS.odg
  && unoconv --listener && unoconv -f eps EPS.odg && lodraw -nologo
  EPS.odg EPS.eps

  the two files look the same.

  4) What happens instead is the image at the bottom right of EPS.eps
  disappears.

  Original Reporter Comments: Ubuntu 7.10 Gutsy, Oo Draw 2.3 (package
  version 1:2.3.0-1ubuntu5.4)

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

[Qa-admin-q]

Dear Christopher M. Penalver,

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

Title:
  [Upstream] Writer Formula horizontal Spacing not honored

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

Bug description:
  Binary package hint: libreoffice

  1) lsb_release -rd
  Description: Ubuntu 11.04
  Release: 11.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386
  Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/778979/+attachment/2119391/+files/test.odt
  && lowriter -nologo test.odt

  double click third icon down (theta with a superscript) -> click
  Format -> Spacing... -> change the Spacing combo box to 200% -> OK
  button and the spacing between the theta and the superscript should
  change.

  4) What happens instead is it does not budge.

  WORKAROUND: Add a space in the formula.

  %itheta^{{" "}a}

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libreoffice-core 1:3.3.2-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sat May  7 13:40:08 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to natty on 2011-04-28 (8 days ago)

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

[Qa-admin-q]

Dear Alexander Kallenbach,

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

Title:
  [Upstream] Libreoffice-wiki-publisher: Translation of charts into
  wikitext is incorrect

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

Bug description:
  I've generated a chart in which I merged some cells. The wiki-
  publisher didn't translate the merging (it should in my case add a
  "rowspan: "3""). I'll attach an exemplary document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice-wiki-publisher 1.1.1+LibO3.4.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Thu Feb  2 18:13:24 2012
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE:en
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   LC_MESSAGES=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to oneiric on 2011-10-02 (123 days ago)

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

[Qa-admin-q]

Dear Sandra Farnedi,

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

Title:
  [Upstream] field length inherited

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

Bug description:
  When I define a table field in LbreOfficeBase I notice that the
  following field types NUMERIC, DECIMAL, FLOAT, VARCHAR,
  VARCHAR_IGNORECASE, inherit the latest set length, that is: when I add
  a field it is set to VARCHAR (100), if I change it to FLOAT its length
  is automatically set to 17, if I come back to VARCHAR, the field
  length is not set back to 100, but still remains 17.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-core 1:3.5.2-2ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
  Uname: Linux 3.2.0-23-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: i386
  CasperVersion: 1.315
  Date: Sun Apr 22 13:13:28 2012
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  LiveMediaBuild: Edubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120420)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/986880/+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 2035076] Re: Wayland - Capital accented letters not recognized

[Jeremy Bícha]

** Description changed:

+ Impact
+ --
+ Capital accented letters can't be entered using CAPS LOCK
+ 
+ Test Case
+ -
+ Open a terminal and install basic French support:
+ sudo apt install language-pack-gnome-fr
+ 
+ Open the Settings app. In the sidebar, click Keyboard
+ Click +, choose French (France), then choose the French (AZERTY) keyboard
+ Close the Settings app
+ In the top right of the screen, click en and switch the keyboard layout to 
French (AZERTY)
+ In the text editor, type é (this is the number 2 key on a US English 
keyboard).
+ Now, press the Caps Lock key to enable Caps Lock.
+ Press the same key. You should get É
+ 
+ What Could Go Wrong
+ ---
+ This fix is included in mutter 45.2 so see the master bug for this upstream 
update: LP: #2043000
+ 
+ Original bug report
+ ---
  Most programs don't recognize Italian accented capital letters.
  When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some 
reasons they are not capitalized.
  I've noticed that everything works fine using the Live session which still 
uses X11 session.
  
  It looks there's no problem with programs that use xwayland like Gimp
  and MarkText.
- 
  
  WORKAROUND
  ===
  In "Settings -> Keyboard" it's possible to set a "compose key".
  For example I've selected the [Super left] key. If I want to compose È I 
press and immediately release each key:
  [Super left] + [E] + [Alt Gr] + [']
  
  If you want É:
  [Super left] + [E] + [']
  
  Do the same for the other vowels.
  ===
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-text-editor 45~beta-1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 11 11:48:41 2023
  InstallationDate: Installed on 2023-09-07 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3)
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-text-editor
  UpgradeStatus: No upgrade log present (probably fresh install)

** Also affects: mutter (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

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

** Changed in: mutter (Ubuntu Mantic)
 Assignee: (unassigned) => Jeremy Bícha (jbicha)

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Jeremy Bícha (jbicha)

** Summary changed:

- Wayland - Capital accented letters not recognized
+ Can't enter capital accented letters with Caps Lock on Wayland

** Description changed:

  Impact
  --
- Capital accented letters can't be entered using CAPS LOCK
+ Capital accented letters can't be entered using CAPS LOCK in the Wayland 
session
  
  Test Case
  -
  Open a terminal and install basic French support:
  sudo apt install language-pack-gnome-fr
  
  Open the Settings app. In the sidebar, click Keyboard
  Click +, choose French (France), then choose the French (AZERTY) keyboard
  Close the Settings app
  In the top right of the screen, click en and switch the keyboard layout to 
French (AZERTY)
  In the text editor, type é (this is the number 2 key on a US English 
keyboard).
  Now, press the Caps Lock key to enable Caps Lock.
  Press the same key. You should get É
  
  What Could Go Wrong
  ---
  This fix is included in mutter 45.2 so see the master bug for this upstream 
update: LP: #2043000
  
  Original bug report
  ---
  Most programs don't recognize Italian accented capital letters.
  When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some 
reasons they are not capitalized.
  I've noticed that everything works fine using the Live session which still 
uses X11 session.
  
  It looks there's no problem with programs that use xwayland like Gimp
  and MarkText.
  
  WORKAROUND
  ===
  In "Settings -> Keyboard" it's possible to set a "compose key".
  For example I've selected the [Super left] key. If I want to compose È I 
press and immediately release each key:
  [Super left] + [E] + [Alt Gr] + [']
  
  If you want É:
  [Super left] + [E] + [']
  
  Do the same for the other vowels.
  ===
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-text-editor 45~beta-1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 11 11:48:41 2023
  InstallationDate: Installed on 2023-09-07 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3)
  ProcEnviron:
   

[Desktop-packages] [Bug 1759591] Re: [printer] segfault when printing a test page

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: New => Fix Released

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

Title:
  [printer] segfault when printing a test page

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  was setting the printer

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu4
  Uname: Linux 4.16.0-041600rc7-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AssertionMessage: corrupted size vs. prev_size
  CurrentDesktop: GNOME
  Date: Wed Mar 28 16:23:37 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-02-06 (49 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: gnome-control-center printers
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa0d6dcdb9a 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7fa0d6dcbc9d "corrupted size vs. 
prev_size") at malloc.c:5350
   _int_realloc (av=av@entry=0x7fa0d7002c40 , 
oldp=oldp@entry=0x55f7d56c5400, oldsize=oldsize@entry=912, nb=nb@entry=928) at 
malloc.c:4564
   __GI___libc_realloc (oldmem=0x55f7d56c5410, bytes=912) at malloc.c:3230
   g_realloc () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center assert failure: corrupted size vs. prev_size
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1759591/+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 1973084] Re: transmission-daemon high RAM usage

[Chuck H]

Sure here is the output:

root@gw:~# apt-cache policy transmission-daemon
transmission-daemon:
  Installed: 3.00-2ubuntu2.1
  Candidate: 3.00-2ubuntu2.1
  Version table:
 *** 3.00-2ubuntu2.1 100
100 /var/lib/dpkg/status
 3.00-2ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages

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

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  Fix Released
Status in transmission source package in Jammy:
  Fix Committed
Status in transmission source package in Lunar:
  Fix Committed
Status in transmission package in Debian:
  New

Bug description:
  [ Impact ]

  There is a memory leak in transmission-daemon that was introduced by a
  faulty openssl3 patch. It has been reported that it's noticeable after
  a few hours of seeding/downloading torrent files, less than a day.

  [ Test Plan ]

  Being a memory leak, there is no immediate/quick test that can be
  performed, other than letting it run for a few hours and measure
  memory consumption "before" and "after". comment #5 mentions about 1Gb
  of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not
  for how long it was running.

  comment #20 says that after 24h using the patched version from a PPA
  build, the memory consumption was steady at 300Mb.

  I'd suggest a 24h test and that it should stay under 1Gb of RAM.

  [ Where problems could occur ]

  The patch loads the default and legacy openssl3 providers. This will
  potentially change the set of algorithms available to the application,
  compared to what was there before. That being said, the legacy
  provider is a conservative approach, and the likely result is that
  *more* algorithms will become available, and not less. This is also
  the approach I have seen in other applications that were rebuilt using
  openssl3 instead of openssl1.1.

  It does seem safer than the original patch, which was manually
  handling ciphers, in particular RC4, and, well, introduced the memory
  leak.

  [ Other Info ]

  Patch came from gentoo.

  [ Original Description ]
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a 
Raspberry Pi 4.

  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.

  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.

  Description:Ubuntu 22.04 LTS
  Release:22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 2028082] Re: Update glib to 2.76.4

[Jeremy Bícha]

I installed glib 2.76.4-0ubuntu1 on Ubuntu 23.10 and verified that the
file browser, terminal, and epiphany-browser work as expected.

The build tests and autopkgtests completed successfully also.

** 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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2028082

Title:
  Update glib to 2.76.4

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Lunar:
  Fix Committed

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

  The current release in Ubuntu 23.04 is 2.76.1

  https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS

  Test Case 1
  ---
  glib has an extensive test suite.

  Failing tests will fail the build.
  This update will also trigger a lot of autopkgtests.

  Ensure that there aren't autopkgtest regressions triggered by this
  update and that the builds complete successfully

  Test Case 2
  ---
  Pretty much all parts of GNOME use GLib, so test anything in the desktop that 
you can. If you reboot the machine and can get to the desktop, that's already 
tested GLib extensively. But also run applications like the terminal, the file 
browser and epiphany-browser

  What Could Go Wrong
  ---
  This update contains fixes in multiple places so multiple apps could be 
affected. The consequences of a broken GLib can range from some functions 
returning bad results sometimes, which have minimal runtime implications, up to 
the system simply crashing all the time.

  Other Info
  --
  The upstream gnome-remote-desktop maintainer requested that we do this update 
to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+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 2043000] Re: Update mutter to 45.2

[Jeremy Bícha]

** Description changed:

  Impact
  --
  There is a new bugfix release in the stable 45 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS
  
  Test Case
  -
  Complete the test case from
  
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter
  
  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.
  
  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.
  
  Smaller bugs could interrupt people's workflows.
  
  mutter is part of GNOME Core and is included in the GNOME micro release
  exception
  
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
  
  Other Info
  --
+ Ubuntu 24.04 "Noble" has mutter 45.1 with all the non translation commits 
cherry-picked. It will get updated to 45.2 (and eventually to 46) after a mesa 
regression is handled.

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

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

Title:
  Update mutter to 45.2

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Mantic:
  In Progress

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 45 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

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

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

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

  Other Info
  --
  Ubuntu 24.04 "Noble" has mutter 45.1 with all the non translation commits 
cherry-picked. It will get updated to 45.2 (and eventually to 46) after a mesa 
regression is handled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000/+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 2043027] Re: Wacom Intuos S stop working after upgrading to Ubuntu 23.10

[Jeremy Bícha]

** Also affects: mutter (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

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

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

** Description changed:

- Tablet seems to work until I open Krita (as I could read on Internet, it
- may be related with Qt Apps).
+ Impact
+ --
+ Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11 
sessions
+ 
+ Test Case
+ -
+ One of the people affected by this issue will verify whether their Wacom 
tablet is working noticably better with the upgraded Mutter packages
+ 
+ What Could Go Wrong
+ ---
+ The fix for this issue is included in upstream's mutter 45.2 release so 
please see bug 2043000 as the master bug for this upgrade
+ 
+ Original Bug Report
+ ---
+ 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:
+  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
+  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]
+  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:
-  

[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage

[Andreas Hasenack]

Hello Chuck,

thanks for the verification. Can you please confirm the package version?
The output of the command below is enough:

apt-cache policy transmission-daemon

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

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  Fix Released
Status in transmission source package in Jammy:
  Fix Committed
Status in transmission source package in Lunar:
  Fix Committed
Status in transmission package in Debian:
  New

Bug description:
  [ Impact ]

  There is a memory leak in transmission-daemon that was introduced by a
  faulty openssl3 patch. It has been reported that it's noticeable after
  a few hours of seeding/downloading torrent files, less than a day.

  [ Test Plan ]

  Being a memory leak, there is no immediate/quick test that can be
  performed, other than letting it run for a few hours and measure
  memory consumption "before" and "after". comment #5 mentions about 1Gb
  of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not
  for how long it was running.

  comment #20 says that after 24h using the patched version from a PPA
  build, the memory consumption was steady at 300Mb.

  I'd suggest a 24h test and that it should stay under 1Gb of RAM.

  [ Where problems could occur ]

  The patch loads the default and legacy openssl3 providers. This will
  potentially change the set of algorithms available to the application,
  compared to what was there before. That being said, the legacy
  provider is a conservative approach, and the likely result is that
  *more* algorithms will become available, and not less. This is also
  the approach I have seen in other applications that were rebuilt using
  openssl3 instead of openssl1.1.

  It does seem safer than the original patch, which was manually
  handling ciphers, in particular RC4, and, well, introduced the memory
  leak.

  [ Other Info ]

  Patch came from gentoo.

  [ Original Description ]
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a 
Raspberry Pi 4.

  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.

  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.

  Description:Ubuntu 22.04 LTS
  Release:22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 1973084] Re: transmission-daemon high RAM usage

[Chuck H]

I was also experiencing the memory leak / crash issue and the proposed
package appears to have corrected it along with running stable for over
72 hours now.  I've performed a variety of actions such as verifying
files and downloading large torrents (>300GB) with many peers. I'm on
latest jammy.  I think it's okay to push to release.

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

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  Fix Released
Status in transmission source package in Jammy:
  Fix Committed
Status in transmission source package in Lunar:
  Fix Committed
Status in transmission package in Debian:
  New

Bug description:
  [ Impact ]

  There is a memory leak in transmission-daemon that was introduced by a
  faulty openssl3 patch. It has been reported that it's noticeable after
  a few hours of seeding/downloading torrent files, less than a day.

  [ Test Plan ]

  Being a memory leak, there is no immediate/quick test that can be
  performed, other than letting it run for a few hours and measure
  memory consumption "before" and "after". comment #5 mentions about 1Gb
  of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not
  for how long it was running.

  comment #20 says that after 24h using the patched version from a PPA
  build, the memory consumption was steady at 300Mb.

  I'd suggest a 24h test and that it should stay under 1Gb of RAM.

  [ Where problems could occur ]

  The patch loads the default and legacy openssl3 providers. This will
  potentially change the set of algorithms available to the application,
  compared to what was there before. That being said, the legacy
  provider is a conservative approach, and the likely result is that
  *more* algorithms will become available, and not less. This is also
  the approach I have seen in other applications that were rebuilt using
  openssl3 instead of openssl1.1.

  It does seem safer than the original patch, which was manually
  handling ciphers, in particular RC4, and, well, introduced the memory
  leak.

  [ Other Info ]

  Patch came from gentoo.

  [ Original Description ]
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a 
Raspberry Pi 4.

  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.

  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.

  Description:Ubuntu 22.04 LTS
  Release:22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 1588443] Re: package fonts-sil-abyssinica 1.500-1 failed to install/upgrade: el paquete fonts-sil-abyssinica no está listo para configurarse no se puede configurar (estado act

[Bobby de Vos]

I don't know why the error occurred. A newer version (2.201-1) of the
package has been uploaded to Debian sid that hopefully does not cause
the same errors.

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

Title:
  package fonts-sil-abyssinica 1.500-1 failed to install/upgrade: el
  paquete fonts-sil-abyssinica no está listo para configurarse  no se
  puede configurar (estado actual `half-installed')

Status in fonts-sil-abyssinica package in Ubuntu:
  New

Bug description:
  Error al instalar e iniciar SO

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fonts-sil-abyssinica 1.500-1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   fonts-sil-abyssinica: Configure
   libkf5xmlgui-bin: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Jun  1 12:37:22 2016
  DpkgTerminalLog:
   dpkg: error al procesar el paquete fonts-sil-abyssinica (--configure):
el paquete fonts-sil-abyssinica no está listo para configurarse
no se puede configurar (estado actual `half-installed')
  ErrorMessage: el paquete fonts-sil-abyssinica no está listo para configurarse 
 no se puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2016-05-23 (10 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fonts-sil-abyssinica
  Title: package fonts-sil-abyssinica 1.500-1 failed to install/upgrade: el 
paquete fonts-sil-abyssinica no está listo para configurarse  no se puede 
configurar (estado actual `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-sil-abyssinica/+bug/1588443/+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 2045563] Re: gnome-control-panel crashes on start with SIGABRT

[Sebastien Bacher]

Which panel did you use last? (if you don't remember 'gsettings get
org.gnome.Settings last-panel' should tell you)

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

Title:
  gnome-control-panel crashes on start with SIGABRT

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  bus[20360]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2760.
  This is normally a bug in some application using the D-Bus library.

D-Bus not built with -rdynamic so unable to print a backtrace
  Neúspěšně ukončen (SIGABRT) (core dumped [obraz paměti uložen])

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.7
  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
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  4 15:16:29 2023
  InstallationDate: Installed on 2022-12-12 (357 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2045563/+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 2045563] Re: gnome-control-panel crashes on start with SIGABRT

[Lubor]

From GUI:

```
pro 04 17:08:56 lubor-kemza-work-hp systemd[5099]: Started Application launched 
by gnome-shell.
pro 04 17:08:56 lubor-kemza-work-hp /usr/libexec/gdm-x-session[5727]: (II) 
AMDGPU(0): EDID vendor "CSO", prod id 5129
pro 04 17:08:56 lubor-kemza-work-hp /usr/libexec/gdm-x-session[5727]: (II) 
AMDGPU(0): Printing DDC gathered Modelines:
pro 04 17:08:56 lubor-kemza-work-hp /usr/libexec/gdm-x-session[5727]: (II) 
AMDGPU(0): Modeline "1920x1080"x0.0  138.66  1920 1968 2000 2080  1080 1083 
1088  -hsync -vsync (66.7 kHz eP)
pro 04 17:08:56 lubor-kemza-work-hp /usr/libexec/gdm-x-session[5727]: (II) 
AMDGPU(0): Modeline "1920x1080"x0.0   92.44  1920 1968 2000 2080  1080 1083 
1088  -hsync -vsync (44.4 kHz e)
pro 04 17:08:56 lubor-kemza-work-hp gnome-control-center.desktop[36955]: 
dbus[36955]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2760.
pro 04 17:08:56 lubor-kemza-work-hp gnome-control-center.desktop[36955]: This 
is normally a bug in some application using the D-Bus library.
pro 04 17:08:56 lubor-kemza-work-hp gnome-control-center.desktop[36955]:   
D-Bus not built with -rdynamic so unable to print a backtrace

```

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

Title:
  gnome-control-panel crashes on start with SIGABRT

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  bus[20360]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2760.
  This is normally a bug in some application using the D-Bus library.

D-Bus not built with -rdynamic so unable to print a backtrace
  Neúspěšně ukončen (SIGABRT) (core dumped [obraz paměti uložen])

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.7
  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
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  4 15:16:29 2023
  InstallationDate: Installed on 2022-12-12 (357 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2045563/+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 2045563] Re: gnome-control-panel crashes on start with SIGABRT

[Lubor]

From terminal
```
pro 04 17:06:09 lubor-kemza-work-hp systemd[5099]: Started Application launched 
by gnome-shell.
pro 04 17:06:09 lubor-kemza-work-hp /usr/libexec/gdm-x-session[5727]: (II) 
AMDGPU(0): EDID vendor "CSO", prod id 5129
pro 04 17:06:09 lubor-kemza-work-hp /usr/libexec/gdm-x-session[5727]: (II) 
AMDGPU(0): Printing DDC gathered Modelines:
pro 04 17:06:09 lubor-kemza-work-hp /usr/libexec/gdm-x-session[5727]: (II) 
AMDGPU(0): Modeline "1920x1080"x0.0  138.66  1920 1968 2000 2080  1080 1083 
1088  -hsync -vsync (66.7 kHz eP)
pro 04 17:06:09 lubor-kemza-work-hp /usr/libexec/gdm-x-session[5727]: (II) 
AMDGPU(0): Modeline "1920x1080"x0.0   92.44  1920 1968 2000 2080  1080 1083 
1088  -hsync -vsync (44.4 kHz e)
pro 04 17:06:09 lubor-kemza-work-hp gnome-control-center.desktop[36241]: 
dbus[36241]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2760.
pro 04 17:06:09 lubor-kemza-work-hp gnome-control-center.desktop[36241]: This 
is normally a bug in some application using the D-Bus library.
pro 04 17:06:09 lubor-kemza-work-hp gnome-control-center.desktop[36241]:   
D-Bus not built with -rdynamic so unable to print a backtrace
```

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

Title:
  gnome-control-panel crashes on start with SIGABRT

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  bus[20360]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2760.
  This is normally a bug in some application using the D-Bus library.

D-Bus not built with -rdynamic so unable to print a backtrace
  Neúspěšně ukončen (SIGABRT) (core dumped [obraz paměti uložen])

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.7
  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
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  4 15:16:29 2023
  InstallationDate: Installed on 2022-12-12 (357 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2045563/+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 2040488] Re: loading lvm2 module crashes: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed

[Martin Pitt]

Interesting! when I check out the source package, and build with the
above patch and like this:

  ./configure CFLAGS="-g -O0" --disable-gtk-docs --enable-lvm2
  make -j4
  sudo src/udisksd -rd --force-load-modules

then it loads the module just fine:

(udisksd:17050): udisks-WARNING **: 14:52:41.121: Can't load configuration file 
/usr/local/etc/udisks2/udisks2.conf
udisks-Message: 14:52:41.122: Loading module lvm2 ...
udisks-Message: 14:52:41.131: Acquired the name org.freedesktop.UDisks2 on the 
system message bus

Curiously, when I run the exact same ./configure invocation that the
Debian packaging does, and run it out of the build tree, it works.

It does seem to be *something* about the built module, though -- with
the patch above (running modules from build tree) it works, but without
the patch it loads them from /usr and fails.

Back trace:

#0  0x779a8a5d in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x779a8cf3 in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x77ac2ead in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3  0x77aca18f in g_type_register_static () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#4  0x77aca3e8 in g_type_register_static_simple () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5  0x746da71d in udisks_daemon_get_type_once () at udisksdaemon.c:115
g_define_type_id = 0x1
#6  0x746da69c in udisks_daemon_get_type () at udisksdaemon.c:115
g_define_type_id = Python Exception : Variable 
'static_fundamental_type_nodes' not found.

static_g_define_type_id = 0
#7  0x746cb784 in udisks_module_lvm2_new (daemon=0x55615340, 
cancellable=0x0, error=0x7fffe210)
at udiskslinuxmodulelvm2.c:133
__inst = 0x55615340
__t = Python Exception : No type named TypeNode.

__r = 32767
initable = 0x556131b0
__func__ = "udisks_module_lvm2_new"
#8  0x555d21a3 in load_single_module_unlocked
(manager=0x55624950, sopath=0x55637090 
"/usr/lib/x86_64-linux-gnu/udisks2/modules/libudisks2_lvm2.so", 
do_notify=0x7fffe208, error=0x7fffe210) at udisksmodulemanager.c:344
state = 0x555eb6b5
handle = 0x556a2450
module_id = 0x55692ea0 "lvm2"
module_new_func_name = 0x55613ae0 "\2602v\364\377\177"
module_id_func = 0x746cb73a 
module_new_func = 0x746cb75f 
module = 0x556a3693
__func__ = "load_single_module_unlocked"
#9  0x555d2505 in udisks_module_manager_load_modules 
(manager=0x55624950) at udisksmodulemanager.c:448
modules_to_load = 0x556a2150 = {0x55637090}
modules_to_load_tmp = 0x556a2150 = {0x55637090}
error = 0x0
do_notify = 0
__func__ = "udisks_module_manager_load_modules"
#10 0x55578002 in load_modules_in_idle_cb (user_data=0x55615340) at 
udisksdaemon.c:277
daemon = 0x55615340
#11 0x779a0a61 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x779fc4ff in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x779a14bf in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x555776e8 in main (argc=1, argv=0x7fffe4d8) at main.c:184
error = 0x0
opt_context = 0x55607f60
ret = 1
name_owner_id = 1
sigint_id = 1
__func__ = "main"


This keeps mystifying and evading me. More debugging tomorrow, but it's quickly 
nearing the point where I run out of time to debug this.

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

Title:
  loading lvm2 module crashes: udisks_module_lvm2_new: assertion
  'UDISKS_IS_DAEMON (daemon)' failed

Status in udisks2 package in Ubuntu:
  New
Status in udisks2 source package in Mantic:
  New

Bug description:
  I tried to do this with `apport-cli
  /var/crash/_usr_libexec_udisks2_udisksd.0.crash`, but 's'ending
  doesn't do anything obvious. I run this from a cloud image over ssh, I
  really don't have any GUI. So filing this manually.

  Trying to load the lvm2 module crashes udisks immediately:

 busctl call org.freedesktop.UDisks2
  /org/freedesktop/UDisks2/Manager org.freedesktop.UDisks2.Manager
  EnableModule sb lvm2 true

  
  udisksd[5709]: cannot register existing type 'UDisksDaemon'
  udisksd[5709]: g_once_init_leave: assertion 'result != 0' failed
  udisksd[5709]: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' 
failed
  systemd[1]: Started systemd-coredump@2-5767-0.service - Process Core Dump 
(PID 5767/UID 0).

Module libudev.so.1 from deb 
systemd-253.5-1ubuntu6.amd64
 Module libsystemd.so.0 from 
deb systemd-253.5-1ubuntu6.amd64
 

[Desktop-packages] [Bug 2045563] Re: gnome-control-panel crashes on start with SIGABRT

[Sebastien Bacher]

Thank you for your bug report. Could you do

$ journalctl -f

trigger the issue and share the log from the previous command?

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

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

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

Title:
  gnome-control-panel crashes on start with SIGABRT

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  bus[20360]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2760.
  This is normally a bug in some application using the D-Bus library.

D-Bus not built with -rdynamic so unable to print a backtrace
  Neúspěšně ukončen (SIGABRT) (core dumped [obraz paměti uložen])

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.7
  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
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  4 15:16:29 2023
  InstallationDate: Installed on 2022-12-12 (357 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

I have prepared another build which drops the dependency change to
"libcurl4-openssl-dev" and keeps "libcurl4-gnutls-dev".

I have updated the description accordingly.

** 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] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/arm64/libr/libreoffice/20231124_182414_cb6a2@/log.gz
- * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/armhf/libr/libreoffice/20231123_114914_bf535@/log.gz
- * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/ppc64el/libr/libreoffice/20231123_150619_c4055@/log.gz
+ Tested build can be found at 
https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15409029/+listing-archive-extra
+ * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20231204_140350_e86f9@/log.gz
+ * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20231204_121007_4cf76@/log.gz
+ * [armhf] ... (autopkgtests infra problems on this arch)
+ * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20231204_113322_18e7a@/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
+ * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20231204_115147_339ff@/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:
  Incomplete

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 

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

[Rico Tzschichholz]

** Patch added: "libreoffice_7.6.3-0ubuntu0.23.10.1.diff"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2044019/+attachment/5726245/+files/libreoffice_7.6.3-0ubuntu0.23.10.1.diff

-- 
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:
  Incomplete

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
    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/15409029/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20231204_140350_e86f9@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20231204_121007_4cf76@/log.gz
  * [armhf] ... (autopkgtests infra problems on this arch)
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20231204_113322_18e7a@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20231204_115147_339ff@/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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2044019/+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 2045563] [NEW] gnome-control-panel crashes on start with SIGABRT

[Lubor]

Public bug reported:

bus[20360]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2760.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace
Neúspěšně ukončen (SIGABRT) (core dumped [obraz paměti uložen])

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.7-0ubuntu0.22.04.7
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
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec  4 15:16:29 2023
InstallationDate: Installed on 2022-12-12 (357 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  gnome-control-panel crashes on start with SIGABRT

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  bus[20360]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2760.
  This is normally a bug in some application using the D-Bus library.

D-Bus not built with -rdynamic so unable to print a backtrace
  Neúspěšně ukončen (SIGABRT) (core dumped [obraz paměti uložen])

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.7
  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
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  4 15:16:29 2023
  InstallationDate: Installed on 2022-12-12 (357 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2045563/+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 2045096] Re: Error in network definition: Invalid MAC address 'random'

[Lukas Märdian]

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: fr-6121

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

Title:
  Error in network definition: Invalid MAC address 'random'

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

Bug description:
  netplan dose not understand the 'random' key word in 'Cloned MAC address' set 
by networkmanager.
  ```
  /etc/netplan/90-NM-X.yaml:9:19: Error in network definition: Invalid MAC 
address 'random', must be XX:XX:XX:XX:XX:XX or 
XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
macaddress: "random"
^
  ```

  netplan Version 0.107-5ubuntu2
  network-manager Version 1.44.2-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2045096/+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 2045096] Re: Error in network definition: Invalid MAC address 'random'

[Lukas Märdian]

** Tags added: netplan-everywhere

** Changed in: netplan
   Status: New => Triaged

** Changed in: netplan
   Importance: Undecided => High

** Tags added: foundations-todo

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

Title:
  Error in network definition: Invalid MAC address 'random'

Status in netplan:
  Triaged
Status in network-manager package in Ubuntu:
  New

Bug description:
  netplan dose not understand the 'random' key word in 'Cloned MAC address' set 
by networkmanager.
  ```
  /etc/netplan/90-NM-X.yaml:9:19: Error in network definition: Invalid MAC 
address 'random', must be XX:XX:XX:XX:XX:XX or 
XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
macaddress: "random"
^
  ```

  netplan Version 0.107-5ubuntu2
  network-manager Version 1.44.2-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2045096/+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 2043000] Re: Update mutter to 45.2

[Jeremy Bícha]

** Summary changed:

- Update mutter to 45.1
+ Update mutter to 45.2

** Description changed:

  Impact
  --
  There is a new bugfix release in the stable 45 series.
- https://gitlab.gnome.org/GNOME/mutter/-/blob/45.1/NEWS
+ https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS
  
  Test Case
  -
  Complete the test case from
  
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter
  
  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.
  
  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.
  
  Smaller bugs could interrupt people's workflows.
  
  mutter is part of GNOME Core and is included in the GNOME micro release
  exception
  
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
  
  Other Info
  --

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

Title:
  Update mutter to 45.2

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Mantic:
  Triaged

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 45 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

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

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

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

  Other Info
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000/+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 2045290] Re: cracklib2 FTBFS against python 3.12

[Olivier Gayot]

** Tags added: proposed-migration

** Tags removed: proposed-migration
** Tags added: update-excuse

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

Title:
  cracklib2 FTBFS against python 3.12

Status in cracklib2 package in Ubuntu:
  New
Status in cracklib2 package in Debian:
  New

Bug description:
  Build against Python 3.12 is red. The build-time test-suite uses the
  obsolete function unittest.TestCase.assertEquals - which was dropped
  from Python 3.12.

  ...E
  ==
  ERROR: test_simple_combinations 
(test_cracklib.TestModuleFunctions.test_simple_combinations)
  --
  Traceback (most recent call last):
File 
"/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py",
 line 122, in test_simple_combinations
  self.assertEquals(
  ^
  AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. 
Did you mean: 'assertEqual'?

  ==
  ERROR: test_simple_digit (test_cracklib.TestModuleFunctions.test_simple_digit)
  --
  Traceback (most recent call last):
File 
"/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py",
 line 99, in test_simple_digit
  self.assertEquals(
  ^
  AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. 
Did you mean: 'assertEqual'?

  ==
  ERROR: test_simple_lower (test_cracklib.TestModuleFunctions.test_simple_lower)
  --
  Traceback (most recent call last):
File 
"/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py",
 line 79, in test_simple_lower
  self.assertEquals(
  ^
  AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. 
Did you mean: 'assertEqual'?

  ==
  ERROR: test_simple_other (test_cracklib.TestModuleFunctions.test_simple_other)
  --
  Traceback (most recent call last):
File 
"/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py",
 line 109, in test_simple_other
  self.assertEquals(
  ^
  AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. 
Did you mean: 'assertEqual'?

  ==
  ERROR: test_simple_upper (test_cracklib.TestModuleFunctions.test_simple_upper)
  --
  Traceback (most recent call last):
File 
"/<>/debian/buildtmp/python3.12/python/build/lib.linux-x86_64-cpython-312/test_cracklib.py",
 line 89, in test_simple_upper
  self.assertEquals(
  ^
  AttributeError: 'TestModuleFunctions' object has no attribute 'assertEquals'. 
Did you mean: 'assertEqual'?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/2045290/+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 2033949] Re: Does not work with Ubuntu sources in deb822 format

[Julian Andres Klode]

Setting the mantic tasks to Won't Fix as the changes to python-apt to
enable deb822 ubuntu.sources were larger than anticipated.

** Also affects: python-apt (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: software-properties (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: python-apt (Ubuntu)
   Status: New => Fix Committed

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

** Changed in: python-apt (Ubuntu Mantic)
   Status: New => Won't Fix

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

Title:
  Does not work with Ubuntu sources in deb822 format

Status in python-apt package in Ubuntu:
  Fix Committed
Status in software-properties package in Ubuntu:
  Fix Committed
Status in python-apt source package in Mantic:
  Won't Fix
Status in software-properties source package in Mantic:
  Won't Fix

Bug description:
  On my Mantic I have sources in new deb822 format.
  Starting software-properties-gtk seems my server is Main server, but from 
/etc/apt/sources.list.d/ubuntu.sources I see server from Italy and I 
software-properties-gtk seems unable to change.

  corrado@corrado-n16-mm-0901:~$ cat /etc/apt/sources.list.d/ubuntu.sources
  Types: deb
  URIs: http://it.archive.ubuntu.com/ubuntu
  Suites: mantic mantic-updates mantic-backports
  Components: main restricted universe multiverse
  Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

  Types: deb
  URIs: http://it.archive.ubuntu.com/ubuntu
  Suites: mantic-security
  Components: main restricted universe multiverse
  Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

  corrado@corrado-n16-mm-0901:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: software-properties-gtk 0.99.39
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  2 10:33:12 2023
  InstallationDate: Installed on 2023-09-01 (1 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[jmharris]

Also get this problem of no sound output from speakers on a Razer laptop
(headphones work fine). Using firmware-sof-signed 2.2.6-1ubuntu1.2.

-- 
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:
  Confirmed

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

[jmharris]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2011385/+attachment/5726205/+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:
  Confirmed

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

[jmharris]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/2011385/+attachment/5726206/+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:
  Confirmed

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

[jmharris]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/2011385/+attachment/5726204/+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:
  Confirmed

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

[jmharris]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2011385/+attachment/5726203/+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:
  Confirmed

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

[jmharris]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/2011385/+attachment/5726202/+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:
  Confirmed

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] apport information

[jmharris]

ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  john   3528 F pipewire
  john   3533 F wireplumber
 /dev/snd/controlC0:  john   3533 F wireplumber
 /dev/snd/seq:john   3528 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2021-11-15 (749 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-hwe-5.19
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Tags: mantic
Uname: Linux 6.5.0-13-generic x86_64
UpgradeStatus: Upgraded to mantic on 2022-10-31 (399 days ago)
UserGroups: adm audio cdrom dip docker libvirt lpadmin lxd plugdev sambashare 
sudo video
_MarkForUpload: True
dmi.bios.date: 04/14/2023
dmi.bios.release: 2.0
dmi.bios.vendor: Razer
dmi.bios.version: 2.00
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.9
dmi.modalias: 
dmi:bvnRazer:bvr2.00:bd04/14/2023:br2.0:efr1.9:svnRazer:pnBlade16-RZ09-0483:pvr9.04:rvnRazer:rnSO690:rvr4:cvnRazer:ct10:cvr:skuRZ09-0483TWH3:
dmi.product.family: 1A583006 Razer Blade
dmi.product.name: Blade 16 - RZ09-0483
dmi.product.sku: RZ09-0483TWH3
dmi.product.version: 9.04
dmi.sys.vendor: Razer

-- 
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:
  Confirmed

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

[Launchpad Bug Tracker]

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

** Changed in: linux-hwe-5.19 (Ubuntu)
   Status: New => Confirmed

-- 
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:
  Confirmed

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 2040488] Re: loading lvm2 module crashes: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed

[Martin Pitt]

Comparing with Debian testing: Running

# /usr/libexec/udisks2/udisksd --debug --force-load-modules
udisks-Message: 10:34:44.696: udisks daemon version 2.10.1 starting
udisks-Message: 10:34:44.724: Acquired the name org.freedesktop.UDisks2 on the 
system message bus
udisks-Message: 10:34:44.729: Loading module lvm2 ...

there works, and doesn't show any of the three assertions that fail on
noble:

(udisksd:57782): GLib-GObject-CRITICAL **: 10:33:06.459: cannot register
existing type 'UDisksDaemon'

(udisksd:57782): GLib-CRITICAL **: 10:33:06.460: g_once_init_leave:
assertion 'result != 0' failed

(udisksd:57782): libudisks2-lvm2-CRITICAL **: 10:33:06.460:
udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed

glib2.0 and libblockdev have identical versions.

Installing debian-testing's glib debs:

  apt install --reinstall libglib2.0-{0,bin,data,dev,dev-bin,doc}

and/or the libblockdev debs:

  dpkg -l | grep 3.0.4-1 | awk '{print $2}' | xargs apt install -y
--reinstall

makes no difference. What the heck?

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

Title:
  loading lvm2 module crashes: udisks_module_lvm2_new: assertion
  'UDISKS_IS_DAEMON (daemon)' failed

Status in udisks2 package in Ubuntu:
  New
Status in udisks2 source package in Mantic:
  New

Bug description:
  I tried to do this with `apport-cli
  /var/crash/_usr_libexec_udisks2_udisksd.0.crash`, but 's'ending
  doesn't do anything obvious. I run this from a cloud image over ssh, I
  really don't have any GUI. So filing this manually.

  Trying to load the lvm2 module crashes udisks immediately:

 busctl call org.freedesktop.UDisks2
  /org/freedesktop/UDisks2/Manager org.freedesktop.UDisks2.Manager
  EnableModule sb lvm2 true

  
  udisksd[5709]: cannot register existing type 'UDisksDaemon'
  udisksd[5709]: g_once_init_leave: assertion 'result != 0' failed
  udisksd[5709]: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' 
failed
  systemd[1]: Started systemd-coredump@2-5767-0.service - Process Core Dump 
(PID 5767/UID 0).

Module libudev.so.1 from deb 
systemd-253.5-1ubuntu6.amd64
 Module libsystemd.so.0 from 
deb systemd-253.5-1ubuntu6.amd64
 Stack trace of thread 5709:
 #0  0x56079be701ad 
udisks_module_manager_load_modules (udisksd + 0x601ad)
 #1  0x56079be5fdf5 n/a 
(udisksd + 0x4fdf5)
 #2  0x7f7d5f122a11 n/a 
(libglib-2.0.so.0 + 0x5aa11)
 #3  0x7f7d5f17e46f n/a 
(libglib-2.0.so.0 + 0xb646f)
 #4  0x7f7d5f12346f 
g_main_loop_run (libglib-2.0.so.0 + 0x5b46f)
 #5  0x56079be323d2 main 
(udisksd + 0x223d2)
 #6  0x7f7d5ee280d0 
__libc_start_call_main (libc.so.6 + 0x280d0)
 #7  0x7f7d5ee28189 
__libc_start_main_impl (libc.so.6 + 0x28189)
 #8  0x56079be324f5 _start 
(udisksd + 0x224f5)

  ProblemType: Crash
  Architecture: amd64
  Date: Wed Oct 25 12:13:14 2023
  DistroRelease: Ubuntu 23.10
  ExecutablePath: /usr/libexec/udisks2/udisksd
  Package: udisks2 2.10.1-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2040488/+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 2040488] Re: loading lvm2 module crashes: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed

[Martin Pitt]

It's a bit easier to investigate with

/usr/libexec/udisks2/udisksd --debug --force-load-modules

There I've1 also seen it fail on the btrfs module, so it's not specific
to the LVM one.

It also happens with rebuilding the udisks source package (so not just
changed ABI)

I tried building upstream git, but it fails due to some missing API,
like

udiskslinuxmodulelvm2.c:438:29: error: implicit declaration of function
'udisks_logical_volume_get_uuid' [-Werror=implicit-function-declaration]

presumably libblockdev or some other build dep which moved along?

Anyway, this doesn't happen on Debian, and it's certainly not related to
the current Ubuntu delta. So something in the stack must be different.
glib2.0 would be the obvious candidate, but both Debian sid and Ubuntu
noble have 2.78.1-4.

For investigating it is helpful to load the modules from the source
tree:

--- src/udisksmodulemanager.c.orig  2023-12-04 10:20:54.571542454 +
+++ src/udisksmodulemanager.c   2023-12-04 10:21:01.047569622 +
@@ -637,7 +637,7 @@
 udisks_module_manager_new (UDisksDaemon *daemon)
 {
   return UDISKS_MODULE_MANAGER (g_object_new (UDISKS_TYPE_MODULE_MANAGER,
-  "daemon", daemon, NULL));
+  "daemon", daemon, "uninstalled", 
TRUE, NULL));
 }
 
 /**


and then 

  sudo ./src/udisksd --debug --force-load-modules

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

Title:
  loading lvm2 module crashes: udisks_module_lvm2_new: assertion
  'UDISKS_IS_DAEMON (daemon)' failed

Status in udisks2 package in Ubuntu:
  New
Status in udisks2 source package in Mantic:
  New

Bug description:
  I tried to do this with `apport-cli
  /var/crash/_usr_libexec_udisks2_udisksd.0.crash`, but 's'ending
  doesn't do anything obvious. I run this from a cloud image over ssh, I
  really don't have any GUI. So filing this manually.

  Trying to load the lvm2 module crashes udisks immediately:

 busctl call org.freedesktop.UDisks2
  /org/freedesktop/UDisks2/Manager org.freedesktop.UDisks2.Manager
  EnableModule sb lvm2 true

  
  udisksd[5709]: cannot register existing type 'UDisksDaemon'
  udisksd[5709]: g_once_init_leave: assertion 'result != 0' failed
  udisksd[5709]: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' 
failed
  systemd[1]: Started systemd-coredump@2-5767-0.service - Process Core Dump 
(PID 5767/UID 0).

Module libudev.so.1 from deb 
systemd-253.5-1ubuntu6.amd64
 Module libsystemd.so.0 from 
deb systemd-253.5-1ubuntu6.amd64
 Stack trace of thread 5709:
 #0  0x56079be701ad 
udisks_module_manager_load_modules (udisksd + 0x601ad)
 #1  0x56079be5fdf5 n/a 
(udisksd + 0x4fdf5)
 #2  0x7f7d5f122a11 n/a 
(libglib-2.0.so.0 + 0x5aa11)
 #3  0x7f7d5f17e46f n/a 
(libglib-2.0.so.0 + 0xb646f)
 #4  0x7f7d5f12346f 
g_main_loop_run (libglib-2.0.so.0 + 0x5b46f)
 #5  0x56079be323d2 main 
(udisksd + 0x223d2)
 #6  0x7f7d5ee280d0 
__libc_start_call_main (libc.so.6 + 0x280d0)
 #7  0x7f7d5ee28189 
__libc_start_main_impl (libc.so.6 + 0x28189)
 #8  0x56079be324f5 _start 
(udisksd + 0x224f5)

  ProblemType: Crash
  Architecture: amd64
  Date: Wed Oct 25 12:13:14 2023
  DistroRelease: Ubuntu 23.10
  ExecutablePath: /usr/libexec/udisks2/udisksd
  Package: udisks2 2.10.1-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2040488/+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 2044718] Re: mantic on raspberry5: x and/or lightdm problems

[Juerg Haefliger]

Ok. Thanks for the clarification regarding X support. In that case we
need to understand what gldriver_test is doing that fixes things.

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

Title:
  mantic on raspberry5: x and/or lightdm problems

Status in linux-raspi package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  New

Bug description:
  running mantic on raspberry5, graphical sessions doesn't start unless on 
gdm3; while performing installation, Ubuntu Budgie graphical session goes on 
without problems but at reboot DE doesn't start.
  Tried installing "classical" ubuntu and DE came on w/o problems; installed 
budgie-desktop and lightdm side by side and budgie didn't start; installed sddm 
with same results. Only gdm3 works
  See attached logs collection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2044718/+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 2040488] Re: loading lvm2 module crashes: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed

[Martin Pitt]

Confirmed on current noble, same udisks2 version.

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

Title:
  loading lvm2 module crashes: udisks_module_lvm2_new: assertion
  'UDISKS_IS_DAEMON (daemon)' failed

Status in udisks2 package in Ubuntu:
  New
Status in udisks2 source package in Mantic:
  New

Bug description:
  I tried to do this with `apport-cli
  /var/crash/_usr_libexec_udisks2_udisksd.0.crash`, but 's'ending
  doesn't do anything obvious. I run this from a cloud image over ssh, I
  really don't have any GUI. So filing this manually.

  Trying to load the lvm2 module crashes udisks immediately:

 busctl call org.freedesktop.UDisks2
  /org/freedesktop/UDisks2/Manager org.freedesktop.UDisks2.Manager
  EnableModule sb lvm2 true

  
  udisksd[5709]: cannot register existing type 'UDisksDaemon'
  udisksd[5709]: g_once_init_leave: assertion 'result != 0' failed
  udisksd[5709]: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' 
failed
  systemd[1]: Started systemd-coredump@2-5767-0.service - Process Core Dump 
(PID 5767/UID 0).

Module libudev.so.1 from deb 
systemd-253.5-1ubuntu6.amd64
 Module libsystemd.so.0 from 
deb systemd-253.5-1ubuntu6.amd64
 Stack trace of thread 5709:
 #0  0x56079be701ad 
udisks_module_manager_load_modules (udisksd + 0x601ad)
 #1  0x56079be5fdf5 n/a 
(udisksd + 0x4fdf5)
 #2  0x7f7d5f122a11 n/a 
(libglib-2.0.so.0 + 0x5aa11)
 #3  0x7f7d5f17e46f n/a 
(libglib-2.0.so.0 + 0xb646f)
 #4  0x7f7d5f12346f 
g_main_loop_run (libglib-2.0.so.0 + 0x5b46f)
 #5  0x56079be323d2 main 
(udisksd + 0x223d2)
 #6  0x7f7d5ee280d0 
__libc_start_call_main (libc.so.6 + 0x280d0)
 #7  0x7f7d5ee28189 
__libc_start_main_impl (libc.so.6 + 0x28189)
 #8  0x56079be324f5 _start 
(udisksd + 0x224f5)

  ProblemType: Crash
  Architecture: amd64
  Date: Wed Oct 25 12:13:14 2023
  DistroRelease: Ubuntu 23.10
  ExecutablePath: /usr/libexec/udisks2/udisksd
  Package: udisks2 2.10.1-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2040488/+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 2038998] Re: [amdgpu] Screen corruption, distorted geometry and misplaced triangles

[Alexander Michler]

I've tried the kernel parameter and those artifacts are still happening.
But just on my FHD screen; not on my other screens (1440p).

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

Title:
  [amdgpu] Screen corruption, distorted geometry and misplaced triangles

Status in GNOME Shell:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A00068US
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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

Re: [Desktop-packages] [Bug 2045478] [NEW] [snap] Chromium-Browser starts with unmaximized window

[Nathan Teodosio]

Gnome Shell is supposed the last window state, either maximized or not, 
and opens it accordingly. At least that is what I see when I

1. Open Chromium.
2. Make it {maximized, not maximized}.
3. Close it.
4. Open Chromium.
5. Verify that it is {maximized, not maximized}.

It also respects --start-maximized for the case that the window would 
otherwise not be maximized.

Do you use the default Gnome desktop environment in Ubuntu? And what is 
'snap info chromium' for you?

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

Title:
  [snap] Chromium-Browser starts with unmaximized window

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium browser by default start with an unmaximized window in my Ubuntu 
system and I've to manually do maximize.
  I have try to edit all desktop file I can edit to add --start-maximized 
option but it doesn't work ...
  And i can't edit desktop file in /snap/chromium directory

  Is it possible to modify desktop file with another way or snap package
  must be updated with this option ?

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


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

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

[Daniel van Vugt]

** Description changed:

  [ Impact ]
  
- Touchscreen touches at the left or bottom edges (less than 20px) of the
+ Touchscreen touches at the left or bottom edges (within 20px) of the
  screen are not treated as mouse clicks. Icons only get highlighted, not
  launched.
  
  [ Test Plan ]
  
  0. Find a touchscreen.
  1. Set Ubuntu Dock in Panel mode (the default mode) if not already.
  2. Touch as close to the edge of the screen as possible. Aim for the gap 
between the icon and the edge of the screen.
  
  Expect: The app launch animation occurs for each touch. Icons aren't
  just highlighted.
  
  [ Where problems could occur ]
  
  Anywhere in touchscreen gesture tracking or even regular touchscreen
  usage. As this bug demonstrates, the former is able to interfere with
  even simple touchscreen actions.
  
  [ Workaround ]
  
  Size the Ubuntu Dock adequately large so it is unlikely the user will
  touch less than 20 pixels from the edge of the screen.
  
  [ Original description ]
  
  On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance,
  adjust the dock icon-size to 24. It is hard to launch corner app like
  firefox, or trigger the launcher. The app icon gets focus but not
  clicked.
  
  1. Ubuntu version 20.04.6
  2. gnome-shell 3.36.9-0ubuntu0.20.04.2
  3. The app or launcher is launched after a click
  4. Only see focus but no app launched

** Description changed:

  [ Impact ]
  
  Touchscreen touches at the left or bottom edges (within 20px) of the
  screen are not treated as mouse clicks. Icons only get highlighted, not
  launched.
  
  [ Test Plan ]
  
  0. Find a touchscreen.
  1. Set Ubuntu Dock in Panel mode (the default mode) if not already.
  2. Touch as close to the edge of the screen as possible. Aim for the gap 
between the icon and the edge of the screen.
  
- Expect: The app launch animation occurs for each touch. Icons aren't
- just highlighted.
+ Expect: The app launch animation occurs for each tap. Icons aren't just
+ highlighted.
  
  [ Where problems could occur ]
  
  Anywhere in touchscreen gesture tracking or even regular touchscreen
  usage. As this bug demonstrates, the former is able to interfere with
  even simple touchscreen actions.
  
  [ Workaround ]
  
  Size the Ubuntu Dock adequately large so it is unlikely the user will
  touch less than 20 pixels from the edge of the screen.
  
  [ Original description ]
  
  On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance,
  adjust the dock icon-size to 24. It is hard to launch corner app like
  firefox, or trigger the launcher. The app icon gets focus but not
  clicked.
  
  1. Ubuntu version 20.04.6
  2. gnome-shell 3.36.9-0ubuntu0.20.04.2
  3. The app or launcher is launched after a click
  4. Only see focus but no app launched

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

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

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

Bug description:
  [ Impact ]

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

  [ Test Plan ]

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

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

  [ Where problems could occur ]

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

  [ Workaround ]

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

  [ Original description ]

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

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

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


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

[Desktop-packages] [Bug 2044369] Re: [SRU] libreoffice 7.5.9 for lunar

[Rico Tzschichholz]

** Description changed:

  [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
   https://wiki.documentfoundation.org/Releases/7.5.9/RC2#List_of_fixed_bugs
  
   7.5.9 RC2 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/15402714/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20231130_032215_7d344@/log.gz
- * [arm64] ...
+ * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20231130_110658_1779c@/log.gz
  * [armhf] ...
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20231129_180258_07169@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20231130_024056_ac67e@/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 ? 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/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
   https://wiki.documentfoundation.org/Releases/7.5.9/RC2#List_of_fixed_bugs

   7.5.9 RC2 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