date:20231023

[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  NetworkManager does not complete DHCP negotiation

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  I run into a problem today where NetworkManager suddenly stopped
  configuring network interfaces - it would ask DHCP server for an IP
  address, the say negotiation failed and then do this again in a loop.

  This happened on a built-in wired interface, and also on a USB
  ethernet dongle that I plugged in.

  Turns out the cause was that I run "dhclient -v" to try to force DHCP
  client to renew the lease. Apparently, dhclient creates directory
  "/run/network" and if this directory is present the NetworkManager
  refuses to accept DHCP server proposals.

  This happens even after server restart, and with no dhclient running -
  just the presence of /run/network is enough to cause the problem.

  Removing the directory "/run/network" fixes the issue.

  I imagine quite a few people run into this, because using dhclient to
  manually bring up an address is fairly common practice.

  I am using Ubuntu 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2032991/+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 1970800] Re: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch

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

** Tags added: fixed-in-gnome-shell-46 fixed-upstream

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

Title:
  Clicking a calendar date in the bottom row of the panel calendar
  causes a graphical glitch

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  If you click a calendar date in the bottom row of the top panel
  calendar, the backdrop shrinks and the dates overflow out of the
  backdrop boundaries.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 28 16:25:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-U GT2 [UHD 
Graphics] [1462:129c]
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU117M [GeForce GTX 
1650 Mobile / Max-Q] [1462:129c]
  InstallationDate: Installed on 2022-04-22 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16S3.1:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1970800/+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 2040197] [NEW] El disco dió un error y luego se apagó la aplicación.

2023-10-23 Thread antonio

Public bug reported:

===
 Info  
===
   PID: 15709 (gnome-disks)
   UID: 1000 (antonio)
   GID: 1000 (antonio)
Signal: 6 (ABRT)
 Timestamp: Tue 2023-10-24 01:31:30 CEST (56min ago)
  Command Line: /usr/bin/gnome-disks --gapplication-service
Executable: /usr/bin/gnome-disks
 Control Group: 
/user.slice/user-1000.slice/user@1000.service/app.slice/dbus.service
  Unit: user@1000.service
 User Unit: dbus.service
 Slice: user-1000.slice
 Owner UID: 1000 (antonio)
   Boot ID: 78ad763b966149188bdb1bcaba66c22f
Machine ID: 939972095cf1459c8b22cc608eff85da
  Hostname: antonio-P35-DS3L
   Storage: 
/var/lib/systemd/coredump/core.gnome-disks.1000.78ad763b966149188bdb1bcaba66c22f.15709.169810389000.zst
 (present)
 Disk Size: 2.0M
   Message: Process 15709 (gnome-disks) of user 1000 dumped core.

Found module linux-vdso.so.1 with build-id: 
9458bc6e35938878c83d05a1f7de11ffe02c8e76
Found module libnss_systemd.so.2 with build-id: 
9efcd2bc218dcf61b4e13ca2512f7e0e4953cf0c
Found module librsvg-2.so.2 with build-id: 
e29ac4267b59a7fa0226e2db1475d480a295b615
Found module libpixbufloader-svg.so with build-id: 
cc0bb6bc80c180edd1a2f7b5deff6e3dda24b16f
Found module libgvfscommon.so with build-id: 
e7fa580fb91bb21aac9fc69229e0961dc743f2b1
Found module libgvfsdbus.so with build-id: 
28abe694dac468552cc1d23d6f643e7989de85e8
Found module libgcc_s.so.1 with build-id: 
e3a44e0da9c6e835d293ed8fd2882b4c4a87130c
Found module libstdc++.so.6 with build-id: 
e37fe1a879783838de78cbc8c80621fa685d58a2
Found module libicudata.so.70 with build-id: 
b1c2496dd0543023c7a19c961bb7f3abc818f465
Found module libicuuc.so.70 with build-id: 
bef3ff1d70aadd68aab07d858a759360c8b919ae
Found module libxkbfile.so.1 with build-id: 
b585f533dd10bd8c043f887705d4e45828baf206
Found module libxml2.so.2 with build-id: 
1cf4a22fbe15a77baca28e9c824592b8b5d852ff
Found module libxklavier.so.16 with build-id: 
a581072418d786fb4a1d160ee7143bbd977025e7
Found module libgnomekbd.so.8 with build-id: 
636c4ae86d1bff2aa2cb92b39b42e41ff714ec7c
Found module libgnomekbdui.so.8 with build-id: 
e01ea8bdf45e3995a2449f1cb4bd8e6bd886efa5
Found module libxapp.so.1 with build-id: 
47c504a90a10f5703881afee628c5cbb8b285da0
Found module libxapp-gtk3-module.so with build-id: 
52e54b458e8327bdea03c65d79e37ec3b68ffe55
Found module libmd.so.0 with build-id: 
cd2d2f71b3967ebde30e2aa43b8eb63339020c06
Found module libbsd.so.0 with build-id: 
9a6c72469251e2feb63e175ef5cb944ce6e00df3
Found module libbrotlicommon.so.1 with build-id: 
43a72967cf84155914c8b3e915926733d1e57c11
Found module libogg.so.0 with build-id: 
842412496daf280ca5491dfb6581df5a378b72f0
Found module libvorbis.so.0 with build-id: 
fc9c832676aac541183d1b4774746bec48b66051
Found module libgpg-error.so.0 with build-id: 
3fbec71c67bee60d8aef00697ee187079b0fb307
Found module libXdmcp.so.6 with build-id: 
6b60f99504aa1d3999ea02a14366d1a39d6c5dcf
Found module libXau.so.6 with build-id: 
7089b383cacbfc1760634a3be19a923e51fe3315
Found module libbrotlidec.so.1 with build-id: 
4b1f390dd6e24d49684db8b2443d082379e8e977
Found module libdatrie.so.1 with build-id: 
128b6874a47f2b783d9e9060d3caaee4110bfd3d
Found module libuuid.so.1 with build-id: 
64c0d0cb22fa2bdeca075a0c0418ba5ff314b220
Found module libexpat.so.1 with build-id: 
d212d1f61d04a1e60fccad1a8c118428cfd9be42
Found module libgraphite2.so.3 with build-id: 
5ffbc76fc948f6b88d766a7210c2e6a329a6c278
Found module libatspi.so.0 with build-id: 
2843c68233d5ba81da3d6bc31422e49472873dba
Found module libdbus-1.so.3 with build-id: 
63e8b99215502138cb63afd6d65851a5e837ed49
Found module libltdl.so.7 with build-id: 
be74205d7325609af44c23c4b469c222a7faaecf
Found module libtdb.so.1 with build-id: 
add802f354e46a856c5729b2c917ff1d43ba1550
Found module libvorbisfile.so.3 with build-id: 
02874bbb32f5adc492b1cb2f72038522bcd7e181
Found module libpcre2-8.so.0 with build-id: 
184a841c55fb7fe5e3873fcda8368c71016cd54c
Found module libblkid.so.1 with build-id: 
cdf95a964e3302bb356fefc4b801fae8c4340b31
Found module libcap.so.2 with build-id: 
b4bf900abf14aabe12d90988ceb30888acb2bcb0
Found module liblz4.so.1 with

[Desktop-packages] [Bug 2039804] Re: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2

2023-10-23 Thread Jay Berkenbilt

The tests include binary files. Unless something has changed, I can't
create a quilt patch that modifies a binary file. The qpdf test suite is
full of PDF files, and PDF files are binary files, even when they are
hand-created, as many of mine are. This makes including tests in patches
challenging. There are a few unit tests that we could include, but they
will likely not backport cleanly, which adds additional risk, and I
don't think including them in the patch will add any value since the
tests are specifically crafted to prove that this bug is fixed, and we
have already done that through current releases and the manual tests.
The bug affects a very specific pattern in the data. This part of the
code that was affected is not actively modified, and the bug involved
changing an infrequently-traversed section of code. The tokenizer is
very low level and stable, and I did an audit of the code again after
this bug was found.

qpdf has been an open source project since 2008 and has been in debian
since the beginning. I am the author and debian maintainer. It is
excessively unlikely that there will a "next" SRU that will come from
other than the version control system, and unless I am hit by the
proverbial bus, I will probably be the originator of it. While qpdf has
a wide following, if I were not there to fix problems like this and push
them through, it is not likely that problems like this would even be
entered into an SRU process. It's been quite a long time since there's
been any divergence between the debian and Ubuntu versions of the
package.

While I agree that more testing is better, I wonder if the benefit we
will get is actually worth the effort. The new tests exercise specific
case related to this fix. If there is still a bug of this type, adding
the new tests will not help us find them. I don't think it would be
worth the hassle to tweak the test system or jump through some hoops to
allow the binary files involved in the tests to get into the patch --
that is more likely to cause a problem than to prevent one. The same is
true of trying to backport the unit tests. qpdf processes millions of
pages a day across a wide range of free and commercial systems. My
employer processes over a million pages a day all by itself.

In qpdf's 21 year history, 15 of which have been open source, this is
only the second data-loss bug, and it has the potential to cause silent
corruption of data in rare corner cases. I appreciate the diligence
here, but I really think the level of testing that has already gone into
this, the inclusion of new patches in the latest release, is adequate,
and now that the bug is known, our priority should be getting a well-
reviewed, well-tested patch in front of users to minimize the risk of
data loss.

Please let me know what else I need to do to get this through. I will
cooperate, of course. My intention here is not to argue, but rather to
try to assure you that the testing is already quite thorough, most
likely exceeding the standard that would be applied to most packages by
their authors. We are passing a point of diminishing return. Thanks for
considering my argument.

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

Title:
  SRU request: qpdf: data loss bug affecting versions 11.0.0 through
  11.6.2

Status in Qpdf:
  Fix Released
Status in qpdf package in Ubuntu:
  New
Status in qpdf source package in Lunar:
  New
Status in qpdf source package in Mantic:
  New

Bug description:
  Notes:

  * I am the upstream author and debian maintainer for qpdf.
  * This bug has been fixed in debian unstable and testing with version 11.6.3, 
but because 24.04 is not yet open, it has not synced. This should not block 
fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: 
https://launchpad.net/~qpdf/+archive/ubuntu/qpdf
  * I am attaching debdiffs for lunar and mantic

  Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug
  in qpdf's lexical layer that would cause qpdf to discard the character
  in a binary string following an octal quoted character with 1 or 2
  digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and
  allows the first two forms if the next character is other than an
  octal digit. Most PDF writers never use the \d or \dd forms, but some
  do. With default options, qpdf does not parse or alter strings inside
  content streams, so this bug is not likely to affect page content.
  However, binary strings of this sort are common in the document /ID
  and may also appear in metadata for encrypted files. In some cases,
  such as the file in #1050, this bug can cause error, in this case,
  because the discarded character was the string end delimiter. In most
  case, this bug results in silent data loss. The fix is very small and
  locally contained. The upstream fix includes several new test cases,
  but the patch I will include to fix the

[Desktop-packages] [Bug 2039804] Re: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2

2023-10-23 Thread Robie Basak

> The patch doesn't include the new test cases, but it does include all
the old ones, which should demonstrate that there is no regression.

OK, but doesn't that just leave a problem behind for the next person who
tries to do an SRU to this package? Can't we just include the tests?

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

Title:
  SRU request: qpdf: data loss bug affecting versions 11.0.0 through
  11.6.2

Status in Qpdf:
  Fix Released
Status in qpdf package in Ubuntu:
  New
Status in qpdf source package in Lunar:
  New
Status in qpdf source package in Mantic:
  New

Bug description:
  Notes:

  * I am the upstream author and debian maintainer for qpdf.
  * This bug has been fixed in debian unstable and testing with version 11.6.3, 
but because 24.04 is not yet open, it has not synced. This should not block 
fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: 
https://launchpad.net/~qpdf/+archive/ubuntu/qpdf
  * I am attaching debdiffs for lunar and mantic

  Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug
  in qpdf's lexical layer that would cause qpdf to discard the character
  in a binary string following an octal quoted character with 1 or 2
  digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and
  allows the first two forms if the next character is other than an
  octal digit. Most PDF writers never use the \d or \dd forms, but some
  do. With default options, qpdf does not parse or alter strings inside
  content streams, so this bug is not likely to affect page content.
  However, binary strings of this sort are common in the document /ID
  and may also appear in metadata for encrypted files. In some cases,
  such as the file in #1050, this bug can cause error, in this case,
  because the discarded character was the string end delimiter. In most
  case, this bug results in silent data loss. The fix is very small and
  locally contained. The upstream fix includes several new test cases,
  but the patch I will include to fix the issue only includes the
  relevant code change.

  I also reported this as a debian bug: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1054158

  It was approved as a stable update by debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119

  [ Impact ]

  The bug could result in silent corruption of binary strings in PDF
  metadata. It could also result in failure of qpdf to process a valid
  file. Data loss justifies a stable update.

  [ Test Plan ]

  The test file in https://github.com/qpdf/qpdf/issues/1050 can be used
  to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and
  that the bug is fixed in 11.6.3.

  The upstream fix includes several additional automated test cases.
  These are not included in the patch, but they are included in the
  upstream commit that fixes the bug:
  https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4

  How to test the SRU package on Ubuntu manually (copied from Jay's
  comment #6 below):

  Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to
  the upstream bug will reproduce the issue. With the current version in
  22.04 and 23.04, you will see something like this:

  ```
  WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while 
reading token
  WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected 
EOF
  WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse 
error while reading object
  WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected 
endobj
  WARNING: /tmp/z/018.pdf: file is damaged
  WARNING: /tmp/z/018.pdf (offset 110267): xref not found
  WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table
  qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering 
damaged file
  ```

  After the fix, you will see
  ```
  checking /home/ejb/Downloads/018.pdf
  PDF Version: 1.7
  File is not encrypted
  File is not linearized
  No syntax or stream encoding errors found; the file may still contain
  errors that qpdf cannot detect
  ```
  (obviously with the full paths based on whatever you call the file).

  [ Where problems could occur ]

  This fix has a very low risk of causing a regression. The fix is very
  localized to qpdf's lexical layer and is in a code path that only
  occurs when a 1-digit or 2-digit octal quoted character is terminated
  by other than an octal digit. This is the first bug in qpdf's lexical
  layer in many years. It was introduced by a pull request from a
  reliable and consistent contributor who has made may improvements to
  qpdf's performance. The fix follows the established pattern of how to
  handle instances in which a character triggers a state change and has
  to be reprocessed in the new state.

  qpdf has a rigorous test suite and an extremely

[Desktop-packages] [Bug 2039804] Re: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2

2023-10-23 Thread Till Kamppeter

Thanks Jay, for elaborating on the test procedures and also for
providing instructions for manual testing so that users can easily
verify the fix. I have copied your instructions to the "[ Test Plan ]"
section of the initial description of the bug so that they get easily
found.

** Description changed:

  Notes:
  
  * I am the upstream author and debian maintainer for qpdf.
  * This bug has been fixed in debian unstable and testing with version 11.6.3, 
but because 24.04 is not yet open, it has not synced. This should not block 
fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: 
https://launchpad.net/~qpdf/+archive/ubuntu/qpdf
  * I am attaching debdiffs for lunar and mantic
  
  Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in
  qpdf's lexical layer that would cause qpdf to discard the character in a
  binary string following an octal quoted character with 1 or 2 digits.
  The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the
  first two forms if the next character is other than an octal digit. Most
  PDF writers never use the \d or \dd forms, but some do. With default
  options, qpdf does not parse or alter strings inside content streams, so
  this bug is not likely to affect page content. However, binary strings
  of this sort are common in the document /ID and may also appear in
  metadata for encrypted files. In some cases, such as the file in #1050,
  this bug can cause error, in this case, because the discarded character
  was the string end delimiter. In most case, this bug results in silent
  data loss. The fix is very small and locally contained. The upstream fix
  includes several new test cases, but the patch I will include to fix the
  issue only includes the relevant code change.
  
  I also reported this as a debian bug: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1054158
  
  It was approved as a stable update by debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119
  
  [ Impact ]
  
  The bug could result in silent corruption of binary strings in PDF
  metadata. It could also result in failure of qpdf to process a valid
  file. Data loss justifies a stable update.
  
  [ Test Plan ]
  
  The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to
  prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that
  the bug is fixed in 11.6.3.
  
  The upstream fix includes several additional automated test cases. These
  are not included in the patch, but they are included in the upstream
  commit that fixes the bug:
  https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4
  
+ How to test the SRU package on Ubuntu manually (copied from Jay's
+ comment #6 below):
+ 
+ Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to
+ the upstream bug will reproduce the issue. With the current version in
+ 22.04 and 23.04, you will see something like this:
+ 
+ ```
+ WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while 
reading token
+ WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected 
EOF
+ WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse 
error while reading object
+ WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected 
endobj
+ WARNING: /tmp/z/018.pdf: file is damaged
+ WARNING: /tmp/z/018.pdf (offset 110267): xref not found
+ WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table
+ qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering 
damaged file
+ ```
+ 
+ After the fix, you will see
+ ```
+ checking /home/ejb/Downloads/018.pdf
+ PDF Version: 1.7
+ File is not encrypted
+ File is not linearized
+ No syntax or stream encoding errors found; the file may still contain
+ errors that qpdf cannot detect
+ ```
+ (obviously with the full paths based on whatever you call the file).
+ 
  [ Where problems could occur ]
  
  This fix has a very low risk of causing a regression. The fix is very
  localized to qpdf's lexical layer and is in a code path that only occurs
  when a 1-digit or 2-digit octal quoted character is terminated by other
  than an octal digit. This is the first bug in qpdf's lexical layer in
  many years. It was introduced by a pull request from a reliable and
  consistent contributor who has made may improvements to qpdf's
  performance. The fix follows the established pattern of how to handle
  instances in which a character triggers a state change and has to be
  reprocessed in the new state.
  
  qpdf has a rigorous test suite and an extremely good quality record. It
  processes millions of documents daily by many commercial entities. My
  current employer runs millions of pages a day through qpdf.
  
  [ Other Info ]
  
  See also
  
  Upstream bug report: https://github.com/qpdf/qpdf/issues/1050
  Corresponding debian bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054158
  Debian stable release

[Desktop-packages] [Bug 2039868]

2023-10-23 Thread mario.limonciello

#98

The amdgpu.mcbp=0  will only help GFX9 products.  For GFX10 this is a
different problem, please open at AMD Gitlab.

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

Title:
  amdgpu reset during usage of firefox

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  Running nightly on 23.10 (since monday), I have been experiencing a
  few amdgpu resets in the past hours

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  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
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 18:26:43 2023
  HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
  InstallationDate: Installed on 2022-07-04 (472 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash 
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
  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: 21A0CTO1WW
  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:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland

2023-10-23 Thread Mario Limonciello

The fixes are identified, I don't think this should wait until GNOME 45.1 
release.
This issue is totally breaking suspend on several of my test systems.  

I've backported the fixes from the GNOME 45 branch onto this PPA build:
https://launchpad.net/~superm1/+archive/ubuntu/lp2034619/+packages

I've also uploaded the mutter package into the proposed queue for SRU
team to look at.

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

** Changed in: mutter (Ubuntu Mantic)
 Assignee: (unassigned) => Mario Limonciello (superm1)

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

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

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Committed
Status in linux source package in Mantic:
  Triaged
Status in mutter source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

  gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems,
  sometimes when the screen locks, sometimes when launching particular
  apps.

  [ Workaround ]

  Add this to /etc/environment:

    MUTTER_DEBUG_KMS_THREAD_TYPE=user

  and then reboot.

  [ Test Plan ]

  Not all Ryzen systems (including one I just purchased) are able to
  reproduce the bug. We have no choice but to leave final verification
  to the community. Anyone affected should try locking their screen and
  verify they are not instantly returned to the login screen.

  [ Where problems could occur ]

  Anywhere in frame scheduling and particularly for mouse cursor
  movement since that's what the real-time thread exists to optimize.

  [ Original Description ]

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

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

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


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

[Desktop-packages] [Bug 2037179] Re: transmission-daemon memory leak

2023-10-23 Thread Marius Gedminas

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

** This bug has been marked a duplicate of bug 1973084
   transmission-daemon high RAM usage

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

Title:
  transmission-daemon memory leak

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  Since deploying transmission-daemon on Ubuntu 22.04 I've noticed a
  regular memory leak

  
  I'm not sure where or when, but it does appear the bug has been fixed 
upstream:
  https://github.com/transmission/transmission/issues/3077

  Required Information:

  1)
  # lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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

  3/4)
  Application behavior is normal, and working as expected, with the exception 
of the memory leak. I've been using scheduled restarts to get around it. See 
pmap output below, it shows the process currently using nearly 2GB of memory 
while running no torrents & being alive for 1 days, 16 hours.

  # pmap $(pgrep -u debian-transmission) | sort -hk 2
  170:   /usr/bin/transmission-daemon -f --log-error
  55e93cf7  4K rw--- transmission-daemon
  55e93cf71000  4K rw---   [ anon ]
  7fe36bfff000  4K -   [ anon ]
  7fe3c5bf9000  4K -   [ anon ]
  7fe3c63fa000  4K -   [ anon ]
  7fe3c6c1  4K - legacy.so
  7fe3c6c15000  4K rw--- legacy.so
  7fe3c6c16000  4K -   [ anon ]
  7fe3c7417000  4K -   [ anon ]
  7fe3c7c18000  4K -   [ anon ]
  7fe3c8428000  4K r libffi.so.8.1.0
  7fe3c8429000  4K - libffi.so.8.1.0
  7fe3c842a000  4K r libffi.so.8.1.0
  7fe3c842b000  4K rw--- libffi.so.8.1.0
  7fe3c843e000  4K r libresolv.so.2
  7fe3c843f000  4K rw--- libresolv.so.2
  7fe3c8446000  4K r libkeyutils.so.1.9
  7fe3c8447000  4K r libkeyutils.so.1.9
  7fe3c8448000  4K rw--- libkeyutils.so.1.9
  7fe3c845e000  4K - libtasn1.so.6.6.2
  7fe3c845f000  4K r libtasn1.so.6.6.2
  7fe3c846  4K rw--- libtasn1.so.6.6.2
  7fe3c85c  4K r libgpg-error.so.0.32.1
  7fe3c85c1000  4K rw--- libgpg-error.so.0.32.1
  7fe3c85c4000  4K r libbrotlicommon.so.1.0.9
  7fe3c85c5000  4K r-x-- libbrotlicommon.so.1.0.9
  7fe3c85e5000  4K r libbrotlicommon.so.1.0.9
  7fe3c85e6000  4K rw--- libbrotlicommon.so.1.0.9
  7fe3c860  4K r libsasl2.so.2.0.25
  7fe3c8601000  4K rw--- libsasl2.so.2.0.25
  7fe3c860d000  4K - libkrb5support.so.0.1
  7fe3c860e000  4K r libkrb5support.so.0.1
  7fe3c860f000  4K rw--- libkrb5support.so.0.1
  7fe3c8612000  4K r-x-- libcom_err.so.2.1
  7fe3c8613000  4K r libcom_err.so.2.1
  7fe3c8614000  4K r libcom_err.so.2.1
  7fe3c8615000  4K rw--- libcom_err.so.2.1
  7fe3c8641000  4K - libk5crypto.so.3.1
  7fe3c8642000  4K r libk5crypto.so.3.1
  7fe3c8643000  4K rw--- libk5crypto.so.3.1
  7fe3c8644000  4K rw---   [ anon ]
  7fe3c870  4K - libkrb5.so.3.3
  7fe3c8792000  4K r libgmp.so.10.4.1
  7fe3c8793000  4K rw--- libgmp.so.10.4.1
  7fe3c87d9000  4K rw--- libnettle.so.8.4
  7fe3c881f000  4K - libhogweed.so.6.4
  7fe3c882  4K r libhogweed.so.6.4
  7fe3c8821000  4K rw--- libhogweed.so.6.4
  7fe3c8bb6000  4K rw--- libunistring.so.2.2.0
  7fe3c8cec000  4K - libgcrypt.so.20.3.4
  7fe3c8cf6000  4K rw---   [ anon ]
  7fe3c8d0  4K r libcap.so.2.44
  7fe3c8d01000  4K rw--- libcap.so.2.44
  7fe3c8d1f000  4K - liblz4.so.1.9.3
  7fe3c8d2  4K r liblz4.so.1.9.3
  7fe3c8d21000  4K rw--- liblz4.so.1.9.3
  7fe3c8d4b000  4K r liblzma.so.5.2.5
  7fe3c8d4c000  4K rw--- liblzma.so.5.2.5
  7fe3c8d4d000  4K r libbrotlidec.so.1.0.9
  7fe3c8d59000  4K r libbrotlidec.so.1.0.9
  7fe3c8d5a000  4K rw--- libbrotlidec.so.1.0.9
  7fe3c8e2a000  4K r libzstd.so.1.4.8
  7fe3c8e2b000  4K rw--- libzstd.so.1.4.8
  7fe3c8e3a000  4K - liblber-2.5.so.0.1.11
  7fe3c8e3b000  4K r liblber-2.5.so.0.1.11
  7fe3c8e3c000  4K rw--- liblber-2.5.so.0.1.11
  7fe3c8e96000  4K - libldap-2.5.so.0.1.11
  7fe3c8e99000  4K rw--- libldap-2.5.so.0.1.11
  7fe3c8eeb000  4K -

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

2023-10-23 Thread Marius Gedminas

The memory leak makes transmission unusable, so this bug should qualify
for a SRU.  All we need is for someone to prepare a debdiff and request
sponsorship for the upload, as described in
https://wiki.ubuntu.com/StableReleaseUpdates

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

Bug 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 1775434] Re: Wrong ExecStop in systemd service unit

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

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

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

Title:
  Wrong ExecStop in systemd service unit

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  ExecStop in /lib/systemd/system/transmission-daemon.service is:

  ExecStop=/bin/kill -s STOP $MAINPID

  when it should be:

  ExecStop=/bin/kill -s TERM $MAINPID

  since SIGSTOP will just suspend the daemon until it received a
  SIGCONT.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: transmission-daemon (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jun  6 13:47:25 2018
  InstallationDate: Installed on 2018-04-28 (39 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: transmission
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1775434/+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 2037179] Re: transmission-daemon memory leak

2023-10-23 Thread Marius Gedminas

I'm also seeing memory leaks in transmission-gtk after upgrading to
22.04 LTS.  In 48 hours it eats up all the RAM and Swap and gets killed
by systemd-oomd.

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

Title:
  transmission-daemon memory leak

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  Since deploying transmission-daemon on Ubuntu 22.04 I've noticed a
  regular memory leak

  
  I'm not sure where or when, but it does appear the bug has been fixed 
upstream:
  https://github.com/transmission/transmission/issues/3077

  Required Information:

  1)
  # lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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

  3/4)
  Application behavior is normal, and working as expected, with the exception 
of the memory leak. I've been using scheduled restarts to get around it. See 
pmap output below, it shows the process currently using nearly 2GB of memory 
while running no torrents & being alive for 1 days, 16 hours.

  # pmap $(pgrep -u debian-transmission) | sort -hk 2
  170:   /usr/bin/transmission-daemon -f --log-error
  55e93cf7  4K rw--- transmission-daemon
  55e93cf71000  4K rw---   [ anon ]
  7fe36bfff000  4K -   [ anon ]
  7fe3c5bf9000  4K -   [ anon ]
  7fe3c63fa000  4K -   [ anon ]
  7fe3c6c1  4K - legacy.so
  7fe3c6c15000  4K rw--- legacy.so
  7fe3c6c16000  4K -   [ anon ]
  7fe3c7417000  4K -   [ anon ]
  7fe3c7c18000  4K -   [ anon ]
  7fe3c8428000  4K r libffi.so.8.1.0
  7fe3c8429000  4K - libffi.so.8.1.0
  7fe3c842a000  4K r libffi.so.8.1.0
  7fe3c842b000  4K rw--- libffi.so.8.1.0
  7fe3c843e000  4K r libresolv.so.2
  7fe3c843f000  4K rw--- libresolv.so.2
  7fe3c8446000  4K r libkeyutils.so.1.9
  7fe3c8447000  4K r libkeyutils.so.1.9
  7fe3c8448000  4K rw--- libkeyutils.so.1.9
  7fe3c845e000  4K - libtasn1.so.6.6.2
  7fe3c845f000  4K r libtasn1.so.6.6.2
  7fe3c846  4K rw--- libtasn1.so.6.6.2
  7fe3c85c  4K r libgpg-error.so.0.32.1
  7fe3c85c1000  4K rw--- libgpg-error.so.0.32.1
  7fe3c85c4000  4K r libbrotlicommon.so.1.0.9
  7fe3c85c5000  4K r-x-- libbrotlicommon.so.1.0.9
  7fe3c85e5000  4K r libbrotlicommon.so.1.0.9
  7fe3c85e6000  4K rw--- libbrotlicommon.so.1.0.9
  7fe3c860  4K r libsasl2.so.2.0.25
  7fe3c8601000  4K rw--- libsasl2.so.2.0.25
  7fe3c860d000  4K - libkrb5support.so.0.1
  7fe3c860e000  4K r libkrb5support.so.0.1
  7fe3c860f000  4K rw--- libkrb5support.so.0.1
  7fe3c8612000  4K r-x-- libcom_err.so.2.1
  7fe3c8613000  4K r libcom_err.so.2.1
  7fe3c8614000  4K r libcom_err.so.2.1
  7fe3c8615000  4K rw--- libcom_err.so.2.1
  7fe3c8641000  4K - libk5crypto.so.3.1
  7fe3c8642000  4K r libk5crypto.so.3.1
  7fe3c8643000  4K rw--- libk5crypto.so.3.1
  7fe3c8644000  4K rw---   [ anon ]
  7fe3c870  4K - libkrb5.so.3.3
  7fe3c8792000  4K r libgmp.so.10.4.1
  7fe3c8793000  4K rw--- libgmp.so.10.4.1
  7fe3c87d9000  4K rw--- libnettle.so.8.4
  7fe3c881f000  4K - libhogweed.so.6.4
  7fe3c882  4K r libhogweed.so.6.4
  7fe3c8821000  4K rw--- libhogweed.so.6.4
  7fe3c8bb6000  4K rw--- libunistring.so.2.2.0
  7fe3c8cec000  4K - libgcrypt.so.20.3.4
  7fe3c8cf6000  4K rw---   [ anon ]
  7fe3c8d0  4K r libcap.so.2.44
  7fe3c8d01000  4K rw--- libcap.so.2.44
  7fe3c8d1f000  4K - liblz4.so.1.9.3
  7fe3c8d2  4K r liblz4.so.1.9.3
  7fe3c8d21000  4K rw--- liblz4.so.1.9.3
  7fe3c8d4b000  4K r liblzma.so.5.2.5
  7fe3c8d4c000  4K rw--- liblzma.so.5.2.5
  7fe3c8d4d000  4K r libbrotlidec.so.1.0.9
  7fe3c8d59000  4K r libbrotlidec.so.1.0.9
  7fe3c8d5a000  4K rw--- libbrotlidec.so.1.0.9
  7fe3c8e2a000  4K r libzstd.so.1.4.8
  7fe3c8e2b000  4K rw--- libzstd.so.1.4.8
  7fe3c8e3a000  4K - liblber-2.5.so.0.1.11
  7fe3c8e3b000  4K r liblber-2.5.so.0.1.11
  7fe3c8e3c000  4K rw--- liblber-2.5.so.0.1.11
  7fe3c8e96000  4K - libldap-2.5.so.0.1.11
  7fe3c8e99000  4K rw--- libldap-2.5.so.0.1.11
  7fe3c8eeb000  4K - libgssapi_krb5.so.2.2

[Desktop-packages] [Bug 2037179] Re: transmission-daemon memory leak

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

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

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

Title:
  transmission-daemon memory leak

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  Since deploying transmission-daemon on Ubuntu 22.04 I've noticed a
  regular memory leak

  
  I'm not sure where or when, but it does appear the bug has been fixed 
upstream:
  https://github.com/transmission/transmission/issues/3077

  Required Information:

  1)
  # lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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

  3/4)
  Application behavior is normal, and working as expected, with the exception 
of the memory leak. I've been using scheduled restarts to get around it. See 
pmap output below, it shows the process currently using nearly 2GB of memory 
while running no torrents & being alive for 1 days, 16 hours.

  # pmap $(pgrep -u debian-transmission) | sort -hk 2
  170:   /usr/bin/transmission-daemon -f --log-error
  55e93cf7  4K rw--- transmission-daemon
  55e93cf71000  4K rw---   [ anon ]
  7fe36bfff000  4K -   [ anon ]
  7fe3c5bf9000  4K -   [ anon ]
  7fe3c63fa000  4K -   [ anon ]
  7fe3c6c1  4K - legacy.so
  7fe3c6c15000  4K rw--- legacy.so
  7fe3c6c16000  4K -   [ anon ]
  7fe3c7417000  4K -   [ anon ]
  7fe3c7c18000  4K -   [ anon ]
  7fe3c8428000  4K r libffi.so.8.1.0
  7fe3c8429000  4K - libffi.so.8.1.0
  7fe3c842a000  4K r libffi.so.8.1.0
  7fe3c842b000  4K rw--- libffi.so.8.1.0
  7fe3c843e000  4K r libresolv.so.2
  7fe3c843f000  4K rw--- libresolv.so.2
  7fe3c8446000  4K r libkeyutils.so.1.9
  7fe3c8447000  4K r libkeyutils.so.1.9
  7fe3c8448000  4K rw--- libkeyutils.so.1.9
  7fe3c845e000  4K - libtasn1.so.6.6.2
  7fe3c845f000  4K r libtasn1.so.6.6.2
  7fe3c846  4K rw--- libtasn1.so.6.6.2
  7fe3c85c  4K r libgpg-error.so.0.32.1
  7fe3c85c1000  4K rw--- libgpg-error.so.0.32.1
  7fe3c85c4000  4K r libbrotlicommon.so.1.0.9
  7fe3c85c5000  4K r-x-- libbrotlicommon.so.1.0.9
  7fe3c85e5000  4K r libbrotlicommon.so.1.0.9
  7fe3c85e6000  4K rw--- libbrotlicommon.so.1.0.9
  7fe3c860  4K r libsasl2.so.2.0.25
  7fe3c8601000  4K rw--- libsasl2.so.2.0.25
  7fe3c860d000  4K - libkrb5support.so.0.1
  7fe3c860e000  4K r libkrb5support.so.0.1
  7fe3c860f000  4K rw--- libkrb5support.so.0.1
  7fe3c8612000  4K r-x-- libcom_err.so.2.1
  7fe3c8613000  4K r libcom_err.so.2.1
  7fe3c8614000  4K r libcom_err.so.2.1
  7fe3c8615000  4K rw--- libcom_err.so.2.1
  7fe3c8641000  4K - libk5crypto.so.3.1
  7fe3c8642000  4K r libk5crypto.so.3.1
  7fe3c8643000  4K rw--- libk5crypto.so.3.1
  7fe3c8644000  4K rw---   [ anon ]
  7fe3c870  4K - libkrb5.so.3.3
  7fe3c8792000  4K r libgmp.so.10.4.1
  7fe3c8793000  4K rw--- libgmp.so.10.4.1
  7fe3c87d9000  4K rw--- libnettle.so.8.4
  7fe3c881f000  4K - libhogweed.so.6.4
  7fe3c882  4K r libhogweed.so.6.4
  7fe3c8821000  4K rw--- libhogweed.so.6.4
  7fe3c8bb6000  4K rw--- libunistring.so.2.2.0
  7fe3c8cec000  4K - libgcrypt.so.20.3.4
  7fe3c8cf6000  4K rw---   [ anon ]
  7fe3c8d0  4K r libcap.so.2.44
  7fe3c8d01000  4K rw--- libcap.so.2.44
  7fe3c8d1f000  4K - liblz4.so.1.9.3
  7fe3c8d2  4K r liblz4.so.1.9.3
  7fe3c8d21000  4K rw--- liblz4.so.1.9.3
  7fe3c8d4b000  4K r liblzma.so.5.2.5
  7fe3c8d4c000  4K rw--- liblzma.so.5.2.5
  7fe3c8d4d000  4K r libbrotlidec.so.1.0.9
  7fe3c8d59000  4K r libbrotlidec.so.1.0.9
  7fe3c8d5a000  4K rw--- libbrotlidec.so.1.0.9
  7fe3c8e2a000  4K r libzstd.so.1.4.8
  7fe3c8e2b000  4K rw--- libzstd.so.1.4.8
  7fe3c8e3a000  4K - liblber-2.5.so.0.1.11
  7fe3c8e3b000  4K r liblber-2.5.so.0.1.11
  7fe3c8e3c000  4K rw--- liblber-2.5.so.0.1.11
  7fe3c8e96000  4K - libldap-2.5.so.0.1.11
  7fe3c8e99000  4K rw--- libldap-2.5.so.0.1.11
  7fe3c8eeb000  4K - libgssapi_krb5.so.2.2
  7fe3c8f02000

[Desktop-packages] [Bug 2040153] Re: Network Manager will not remove Netplan YAMLs when connections are deleted

** Merge proposal linked:
   
https://code.launchpad.net/~danilogondolfo/network-manager/+git/network-manager/+merge/454296

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

Title:
  Network Manager will not remove Netplan YAMLs when connections are
  deleted

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

Bug description:
  When a connection is deleted using any NM facility, libnetplan is
  failing to delete the YAML file. Because of that, the connection will
  be recreated when "netplan generate" runs again.

  This is probably being caused by a combination of two things. First,
  the NM's systemd unit has this setting "ProtectSystem=true", which
  will mount /usr as read-only for NM. Second, we migrated the default
  "00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1].
  When libnetplan tries to open this file for writing, the open system
  fails with EROFS:

  ---
  22517 openat(AT_FDCWD, "/lib/netplan/00-network-manager-all.yaml", 
O_WRONLY|O_CREAT|O_TRUNC, 0600) = -1 EROFS (Read-only file system)
  22517 write(2, "netplan_delete_connection: Canno"..., 76) = 76
  ---

  
  [1] - https://launchpad.net/ubuntu/+source/ubuntu-settings/23.10.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2040153/+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 2039804] Re: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2

2023-10-23 Thread Jay Berkenbilt

> This is great, but is this test suite run as part of the package build
and publication process in Ubuntu? If not, how could we arrange to run
the test suite against the Ubuntu build of the package that includes
this patch to ensure that we aren't regressing unaffected users in
providing this update?

The test suite is run as part of the Ubuntu build. The patch doesn't
include the new test cases, but it does include all the old ones, which
should demonstrate that there is no regression. When 24.04 opens for
business and the packages sync, the new tests will run as they are in
11.6.3. You can also see it in my PPA:
https://launchpad.net/~qpdf/+archive/ubuntu/qpdf. In any case, I believe
the fact that test suite is run during the existing builds should be
sufficient to ensure that there is no regression. qpdf also has
meaningful autopkgtests. You can also check the debian build output.
Debian stable proposed updates has 11.3.0 with the same patch.

For manual testing:

Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to
the upstream bug will reproduce the issue. With the current version in
22.04 and 23.04, you will see something like this:

```
WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while 
reading token
WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected 
EOF
WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error 
while reading object
WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected 
endobj
WARNING: /tmp/z/018.pdf: file is damaged
WARNING: /tmp/z/018.pdf (offset 110267): xref not found
WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table
qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering 
damaged file
```

After the fix, you will see
```
checking /home/ejb/Downloads/018.pdf
PDF Version: 1.7
File is not encrypted
File is not linearized
No syntax or stream encoding errors found; the file may still contain
errors that qpdf cannot detect
```
(obviously with the full paths based on whatever you call the file).

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

Title:
  SRU request: qpdf: data loss bug affecting versions 11.0.0 through
  11.6.2

Status in Qpdf:
  Fix Released
Status in qpdf package in Ubuntu:
  New
Status in qpdf source package in Lunar:
  New
Status in qpdf source package in Mantic:
  New

Bug description:
  Notes:

  * I am the upstream author and debian maintainer for qpdf.
  * This bug has been fixed in debian unstable and testing with version 11.6.3, 
but because 24.04 is not yet open, it has not synced. This should not block 
fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: 
https://launchpad.net/~qpdf/+archive/ubuntu/qpdf
  * I am attaching debdiffs for lunar and mantic

  Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug
  in qpdf's lexical layer that would cause qpdf to discard the character
  in a binary string following an octal quoted character with 1 or 2
  digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and
  allows the first two forms if the next character is other than an
  octal digit. Most PDF writers never use the \d or \dd forms, but some
  do. With default options, qpdf does not parse or alter strings inside
  content streams, so this bug is not likely to affect page content.
  However, binary strings of this sort are common in the document /ID
  and may also appear in metadata for encrypted files. In some cases,
  such as the file in #1050, this bug can cause error, in this case,
  because the discarded character was the string end delimiter. In most
  case, this bug results in silent data loss. The fix is very small and
  locally contained. The upstream fix includes several new test cases,
  but the patch I will include to fix the issue only includes the
  relevant code change.

  I also reported this as a debian bug: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1054158

  It was approved as a stable update by debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119

  [ Impact ]

  The bug could result in silent corruption of binary strings in PDF
  metadata. It could also result in failure of qpdf to process a valid
  file. Data loss justifies a stable update.

  [ Test Plan ]

  The test file in https://github.com/qpdf/qpdf/issues/1050 can be used
  to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and
  that the bug is fixed in 11.6.3.

  The upstream fix includes several additional automated test cases.
  These are not included in the patch, but they are included in the
  upstream commit that fixes the bug:
  https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4

  [ Where problems could occur ]

  This fix has a very low risk of causing a regression. The fix is very
  localized to qpdf's

[Desktop-packages] [Bug 1738251]

2023-10-23 Thread Qa-admin-q

Dear bugcatcher1,

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

Title:
[upstream] Missing Data when Copying from Clipboard to Writer

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

Bug description:
I have copied and pasted the webpage
'https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1607535' into
LibreOffice, so as to be able to print and read it. The resulting page is
incomplete. Thus, for example, at [Workaround 1], where the the following
command line is specified:
$ wget http://downloads.sourceforge.net/corefonts/
{andale32.exe,arial32.exe,arialb32.exe,comic32.exe,courie32.exe,
georgi32.exe,impact32.exe,times32.exe,trebuc32.exe,verdan32.exe,
webdin32.exe}
only the following text appears:
$ wget http://
{
georgi32.
webdin32.exe}
The HTML code for that text is:
$ wget http://downloads.sourceforge.net/corefonts/;>http://downloads.sourceforge.net/corefonts/
{andale32.exe,arial32.exe,arialb32.exe,comic32.exe,courie32.exe,
georgi32.exe,impact32.exe,times32.exe,trebuc32.exe,verdan32.exe,
webdin32.exe}
The problem is triggered by the tag. Where one of these occurs in the
HTML, all subsequent text is omitted until either a or a tag is
reached (and of course there may be others).
As there are 956 tags in this document, much of the text is missing
after pasting. If the all the tags are removed from the page, copying
and pasting works fine.
I shall be grateful for help with the problem, as it means that that with
LibreOffice copying and pasting is unreliable.

Ubuntu Mate 16.04.3
lsb-release: 9.20160110ubuntu0.2
LibreOffice Writer: libreoffice-writer 1:5.1.6-rc20ubuntu1-xenial2

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

[Desktop-packages] [Bug 2039804] Re: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2

2023-10-23 Thread Robie Basak

Thank you for contributing this fix!

Could you please expand on the Test Plan?

For manual testing, what are the exact steps that a user would perform,
what results would indicate that the bug is present, and what results
would indicate that the bug is fixed? For example, I don't see a command
to run in https://github.com/qpdf/qpdf/issues/1050, or the expected
results if the bug is fixed.

For automated testing, you said the tests aren't included in the patch.
Why not? Could we include them instead, and therefore increase
confidence in the correctness of the fix?

> qpdf has a rigorous test suite

This is great, but is this test suite run as part of the package build
and publication process in Ubuntu? If not, how could we arrange to run
the test suite against the Ubuntu build of the package that includes
this patch to ensure that we aren't regressing unaffected users in
providing this update?

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

Title:
  SRU request: qpdf: data loss bug affecting versions 11.0.0 through
  11.6.2

Status in Qpdf:
  Fix Released
Status in qpdf package in Ubuntu:
  New
Status in qpdf source package in Lunar:
  New
Status in qpdf source package in Mantic:
  New

Bug description:
  Notes:

  * I am the upstream author and debian maintainer for qpdf.
  * This bug has been fixed in debian unstable and testing with version 11.6.3, 
but because 24.04 is not yet open, it has not synced. This should not block 
fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: 
https://launchpad.net/~qpdf/+archive/ubuntu/qpdf
  * I am attaching debdiffs for lunar and mantic

  Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug
  in qpdf's lexical layer that would cause qpdf to discard the character
  in a binary string following an octal quoted character with 1 or 2
  digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and
  allows the first two forms if the next character is other than an
  octal digit. Most PDF writers never use the \d or \dd forms, but some
  do. With default options, qpdf does not parse or alter strings inside
  content streams, so this bug is not likely to affect page content.
  However, binary strings of this sort are common in the document /ID
  and may also appear in metadata for encrypted files. In some cases,
  such as the file in #1050, this bug can cause error, in this case,
  because the discarded character was the string end delimiter. In most
  case, this bug results in silent data loss. The fix is very small and
  locally contained. The upstream fix includes several new test cases,
  but the patch I will include to fix the issue only includes the
  relevant code change.

  I also reported this as a debian bug: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1054158

  It was approved as a stable update by debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119

  [ Impact ]

  The bug could result in silent corruption of binary strings in PDF
  metadata. It could also result in failure of qpdf to process a valid
  file. Data loss justifies a stable update.

  [ Test Plan ]

  The test file in https://github.com/qpdf/qpdf/issues/1050 can be used
  to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and
  that the bug is fixed in 11.6.3.

  The upstream fix includes several additional automated test cases.
  These are not included in the patch, but they are included in the
  upstream commit that fixes the bug:
  https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4

  [ Where problems could occur ]

  This fix has a very low risk of causing a regression. The fix is very
  localized to qpdf's lexical layer and is in a code path that only
  occurs when a 1-digit or 2-digit octal quoted character is terminated
  by other than an octal digit. This is the first bug in qpdf's lexical
  layer in many years. It was introduced by a pull request from a
  reliable and consistent contributor who has made may improvements to
  qpdf's performance. The fix follows the established pattern of how to
  handle instances in which a character triggers a state change and has
  to be reprocessed in the new state.

  qpdf has a rigorous test suite and an extremely good quality record.
  It processes millions of documents daily by many commercial entities.
  My current employer runs millions of pages a day through qpdf.

  [ Other Info ]

  See also

  Upstream bug report: https://github.com/qpdf/qpdf/issues/1050
  Corresponding debian bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054158
  Debian stable release approval: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to :

[Desktop-packages] [Bug 2040169] Re: GTK4 app glitches on AMD GPU

2023-10-23 Thread Readable Author

libgtk-4-1:
  Installed: 4.6.9+ds-0ubuntu0.22.04.1
  Candidate: 4.6.9+ds-0ubuntu0.22.04.1
  Version table:
 *** 4.6.9+ds-0ubuntu0.22.04.1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
 4.6.2+ds-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

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

Title:
  GTK4 app glitches on AMD GPU

Status in gtk4 package in Ubuntu:
  New

Bug description:
  Works fine on internal intel GPU, GTK4 apps glitch when using "Launch
  using Discrete Graphics Card".

  
  Ubuntu 22.04.3, Xorg

  Graphics:
Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel
Device-2: AMD Topaz PRO [Radeon R5 M255] driver: amdgpu v: kernel
Display: x11 server: X.Org v: 1.21.1.4 driver: X:
  loaded: amdgpu,ati,modesetting unloaded: fbdev,radeon,vesa gpu: i915
  resolution: 1366x768~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 4400 (HSW GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2040169/+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 2040169] Re: GTK4 app glitches on AMD GPU

2023-10-23 Thread Readable Author

Video recording

** Attachment added: "gtk4-amd-glitches.webm"
   
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2040169/+attachment/5712665/+files/gtk4-amd-glitches.webm

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

Title:
  GTK4 app glitches on AMD GPU

Status in gtk4 package in Ubuntu:
  New

Bug description:
  Works fine on internal intel GPU, GTK4 apps glitch when using "Launch
  using Discrete Graphics Card".

  
  Ubuntu 22.04.3, Xorg

  Graphics:
Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel
Device-2: AMD Topaz PRO [Radeon R5 M255] driver: amdgpu v: kernel
Display: x11 server: X.Org v: 1.21.1.4 driver: X:
  loaded: amdgpu,ati,modesetting unloaded: fbdev,radeon,vesa gpu: i915
  resolution: 1366x768~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 4400 (HSW GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2040169/+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 2040169] [NEW] GTK4 app glitches on AMD GPU

2023-10-23 Thread Readable Author

Public bug reported:

Works fine on internal intel GPU, GTK4 apps glitch when using "Launch
using Discrete Graphics Card".


Ubuntu 22.04.3, Xorg

Graphics:
  Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel
  Device-2: AMD Topaz PRO [Radeon R5 M255] driver: amdgpu v: kernel
  Display: x11 server: X.Org v: 1.21.1.4 driver: X:
loaded: amdgpu,ati,modesetting unloaded: fbdev,radeon,vesa gpu: i915
resolution: 1366x768~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 4400 (HSW GT2)
v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1

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

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

Title:
  GTK4 app glitches on AMD GPU

Status in gtk4 package in Ubuntu:
  New

Bug description:
  Works fine on internal intel GPU, GTK4 apps glitch when using "Launch
  using Discrete Graphics Card".

  
  Ubuntu 22.04.3, Xorg

  Graphics:
Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel
Device-2: AMD Topaz PRO [Radeon R5 M255] driver: amdgpu v: kernel
Display: x11 server: X.Org v: 1.21.1.4 driver: X:
  loaded: amdgpu,ati,modesetting unloaded: fbdev,radeon,vesa gpu: i915
  resolution: 1366x768~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 4400 (HSW GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2040169/+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 2040167] [NEW] Panel Indicator Icon can't show, but it can interact and give feedback window tiling style chooser dialog

2023-10-23 Thread Moh Anif Yuliansyah

Public bug reported:

I try to enable Panel Indicator option, but it can't show it icon in
panel, but if I click in it area, it give response to showing window
tiling style dialog. My screenshot can explain I mean in this bug
report. I wish it can fixed soon as possible

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


** Tags: mantic

** Attachment added: "My description screenshot"
   
https://bugs.launchpad.net/bugs/2040167/+attachment/5712662/+files/Screenshot%20from%202023-10-23%2020-38-50.png

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

Title:
  Panel Indicator Icon can't show, but it can interact and give feedback
  window tiling style chooser dialog

Status in gnome-shell-extension-tiling-assistant package in Ubuntu:
  New

Bug description:
  I try to enable Panel Indicator option, but it can't show it icon in
  panel, but if I click in it area, it give response to showing window
  tiling style dialog. My screenshot can explain I mean in this bug
  report. I wish it can fixed soon as possible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2040167/+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 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar

More information dump:

* It's easier to see the error Andreas mentioned with --enable-
logging=stderr:

--->
[246126:246235:1023/123348.818876:WARNING:obfuscated_file_util.cc(1323)] Failed 
to get origin+type directory: { uri: 
filesystem:https://docs.google.com/persistent/docs/fonts/4iCv6KVjbNBYlgoCxCvTsg.woff2,
 storage key: { origin: https://docs.google.com, top-level site: 
https://google.com, nonce: , ancestor chain bit: Same-Site } } error:-4
[246126:246235:1023/123348.818941:WARNING:obfuscated_file_util.cc(1323)] Failed 
to get origin+type directory: { uri: 
filesystem:https://docs.google.com/persistent/docs/fonts/4iCp6KVjbNBYlgoKejZPsmyN.woff2,
 storage key: { origin: https://docs.google.com, top-level site: 
https://google.com, nonce: , ancestor chain bit: Same-Site } } error:-4
<---

I don't quite understand the process there, an uneducated guess: It is
trying to fetch a font and then storing it using the filesystem API —
which would save it in snap/chromium/common/chromium/Default/File\
Systems but that directory doesn't even exist. Maybe Firefox's
implementation differs from Chromium's critically enough to hit this
bug. Disabling that with --disable-file-system has no effect.

* Docs uses a remote font instead of a system font because --disable-
remote-fonts prevents the Ubuntu font from loading despite it still
being listed (the 't' character is a giveaway). This is in line with the
error message.

* Since we don't get the problem in Firefox, I tried switching the user
agent to Firefox just to see if behavior changed; it didn't.

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

Title:
  [snap] New Ubuntu font with normal weight displayed as bold in Google
  Docs in Chromium after upgrading to Lunar

Status in chromium-browser package in Ubuntu:
  Triaged
Status in fonts-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  I am experiencing a rendering regression after upgrading from Kinetic to 
Lunar.
  Google Docs using the Ubuntu font family are displayed incorrectly in 
Chromium: the normal weight font is rendered identically to the bold weight 
one, instead of being thicker than light and thinner than medium.

  Printing is also affected, unless I use Google Docs' download to PDF
  function, although that probably triggers a server-side rendering.

  This issue does not occur in Firefox or Google Chrome.

  One thing that may be relevant: if I force-refresh my test Google Doc
  I see all four Ubuntu font lines initially being rendered as bold. The
  light and medium lines are then re-rendered with the correct weight.
  It's as if bold was the default weight and the normal variant
  disappeared.

  As far as I can tell I was already running Chromium 112.0.5615.49 in
  Kinetic, and with Chromium being a snap I don't quite understand why
  the Ubuntu series would matter.

  I have also tried version 114.0.5735.16 (in latest/beta at the
  moment); the symptoms are identical.

  The attachments show the rendering error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+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 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar

2023-10-23 Thread Andreas Hasenack

I installed ubuntu-fonts-classic from mantic on my lunar desktop (it's
not available for lunar). It removed ubuntu-fonts, but the fonts look ok
now in google docs. Got some differences in my desktop too, but still
looks ok.

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

Title:
  [snap] New Ubuntu font with normal weight displayed as bold in Google
  Docs in Chromium after upgrading to Lunar

Status in chromium-browser package in Ubuntu:
  Triaged
Status in fonts-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  I am experiencing a rendering regression after upgrading from Kinetic to 
Lunar.
  Google Docs using the Ubuntu font family are displayed incorrectly in 
Chromium: the normal weight font is rendered identically to the bold weight 
one, instead of being thicker than light and thinner than medium.

  Printing is also affected, unless I use Google Docs' download to PDF
  function, although that probably triggers a server-side rendering.

  This issue does not occur in Firefox or Google Chrome.

  One thing that may be relevant: if I force-refresh my test Google Doc
  I see all four Ubuntu font lines initially being rendered as bold. The
  light and medium lines are then re-rendered with the correct weight.
  It's as if bold was the default weight and the normal variant
  disappeared.

  As far as I can tell I was already running Chromium 112.0.5615.49 in
  Kinetic, and with Chromium being a snap I don't quite understand why
  the Ubuntu series would matter.

  I have also tried version 114.0.5735.16 (in latest/beta at the
  moment); the symptoms are identical.

  The attachments show the rendering error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+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 2036651] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("LANGUAGE") from guess_category_value() from __dcigettext()

2023-10-23 Thread Bug Watch Updater

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  gnome-shell crashed with SIGSEGV in __GI_getenv("LANGUAGE") from
  guess_category_value() from __dcigettext()

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

Bug description:
  Crash on startup

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Sep 19 22:38:53 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-09-12 (7 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f706ee45e6d <__GI_getenv+77>:   cmp
(%rbx),%r12b
   PC (0x7f706ee45e6d) ok
   source "(%rbx)" (0x55fd90525) not located in a known VMA region (needed 
readable region)!
   destination "%r12b" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_getenv (name=name@entry=0x7f706efc0257 "LANGUAGE") at 
./stdlib/getenv.c:31
   guess_category_value (categoryname=0x7f706efa5493 <_nl_category_names+51> 
"LC_MESSAGES", category=5) at ./intl/dcigettext.c:1569
   __dcigettext (domainname=0x7f706f79e126 "glib20", msgid1=0x7f706f985c68 "The 
sockets address family to use for socket construction", msgid2=0x0, plural=0, 
n=0, category=5) at ./intl/dcigettext.c:647
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_type_class_ref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
  UpgradeStatus: Upgraded to mantic on 2023-09-18 (1 days ago)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2036651/+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 2040153] Re: Network Manager will not remove Netplan YAMLs when connections are deleted

2023-10-23 Thread Lukas Märdian

** Tags added: foundations-todo

** Changed in: netplan.io (Ubuntu Mantic)
   Status: New => Triaged

** Changed in: network-manager (Ubuntu Mantic)
   Status: New => Triaged

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

Title:
  Network Manager will not remove Netplan YAMLs when connections are
  deleted

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

Bug description:
  When a connection is deleted using any NM facility, libnetplan is
  failing to delete the YAML file. Because of that, the connection will
  be recreated when "netplan generate" runs again.

  This is probably being caused by a combination of two things. First,
  the NM's systemd unit has this setting "ProtectSystem=true", which
  will mount /usr as read-only for NM. Second, we migrated the default
  "00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1].
  When libnetplan tries to open this file for writing, the open system
  fails with EROFS:

  ---
  22517 openat(AT_FDCWD, "/lib/netplan/00-network-manager-all.yaml", 
O_WRONLY|O_CREAT|O_TRUNC, 0600) = -1 EROFS (Read-only file system)
  22517 write(2, "netplan_delete_connection: Canno"..., 76) = 76
  ---

  
  [1] - https://launchpad.net/ubuntu/+source/ubuntu-settings/23.10.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2040153/+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 2040153] [NEW] Network Manager will not remove Netplan YAMLs when connections are deleted

2023-10-23 Thread Danilo Egea Gondolfo

Public bug reported:

When a connection is deleted using any NM facility, libnetplan is
failing to delete the YAML file. Because of that, the connection will be
recreated when "netplan generate" runs again.

This is probably being caused by a combination of two things. First, the
NM's systemd unit has this setting "ProtectSystem=true", which will
mount /usr as read-only for NM. Second, we migrated the default
"00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1].
When libnetplan tries to open this file for writing, the open system
fails with EROFS:

---
22517 openat(AT_FDCWD, "/lib/netplan/00-network-manager-all.yaml", 
O_WRONLY|O_CREAT|O_TRUNC, 0600) = -1 EROFS (Read-only file system)
22517 write(2, "netplan_delete_connection: Canno"..., 76) = 76
---


[1] - https://launchpad.net/ubuntu/+source/ubuntu-settings/23.10.1

** Affects: netplan.io (Ubuntu)
 Importance: Critical
 Status: Triaged

** Affects: network-manager (Ubuntu)
 Importance: Critical
 Status: Triaged

** Affects: netplan.io (Ubuntu Mantic)
 Importance: Critical
 Status: Triaged

** Affects: network-manager (Ubuntu Mantic)
 Importance: Critical
 Status: Triaged


** Tags: foundations-todo

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

** Also affects: network-manager (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

** Changed in: netplan.io (Ubuntu Mantic)
   Importance: Undecided => Critical

** Changed in: network-manager (Ubuntu Mantic)
   Importance: Undecided => Critical

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

Title:
  Network Manager will not remove Netplan YAMLs when connections are
  deleted

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

Bug description:
  When a connection is deleted using any NM facility, libnetplan is
  failing to delete the YAML file. Because of that, the connection will
  be recreated when "netplan generate" runs again.

  This is probably being caused by a combination of two things. First,
  the NM's systemd unit has this setting "ProtectSystem=true", which
  will mount /usr as read-only for NM. Second, we migrated the default
  "00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1].
  When libnetplan tries to open this file for writing, the open system
  fails with EROFS:

  ---
  22517 openat(AT_FDCWD, "/lib/netplan/00-network-manager-all.yaml", 
O_WRONLY|O_CREAT|O_TRUNC, 0600) = -1 EROFS (Read-only file system)
  22517 write(2, "netplan_delete_connection: Canno"..., 76) = 76
  ---

  
  [1] - https://launchpad.net/ubuntu/+source/ubuntu-settings/23.10.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2040153/+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 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar

Bold renders fine given simple CSS:

Ubuntu.
Ubuntu bold.

This looks specific to Google Docs.

** Attachment added: "fonts.png"

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+attachment/5712423/+files/fonts.png

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

Title:
[snap] New Ubuntu font with normal weight displayed as bold in Google
Docs in Chromium after upgrading to Lunar

Status in chromium-browser package in Ubuntu:
Triaged
Status in fonts-ubuntu package in Ubuntu:
Confirmed

Bug description:
I am experiencing a rendering regression after upgrading from Kinetic to
Lunar.
Google Docs using the Ubuntu font family are displayed incorrectly in
Chromium: the normal weight font is rendered identically to the bold weight
one, instead of being thicker than light and thinner than medium.

Printing is also affected, unless I use Google Docs' download to PDF
function, although that probably triggers a server-side rendering.

This issue does not occur in Firefox or Google Chrome.

One thing that may be relevant: if I force-refresh my test Google Doc
I see all four Ubuntu font lines initially being rendered as bold. The
light and medium lines are then re-rendered with the correct weight.
It's as if bold was the default weight and the normal variant
disappeared.

As far as I can tell I was already running Chromium 112.0.5615.49 in
Kinetic, and with Chromium being a snap I don't quite understand why
the Ubuntu series would matter.

I have also tried version 114.0.5735.16 (in latest/beta at the
moment); the symptoms are identical.

The attachments show the rendering error.

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

[Desktop-packages] [Bug 2038811] Re: NetworkManager crashes when updating wpa-eap connections

2023-10-23 Thread Danilo Egea Gondolfo

I'm working on the SRU of a couple of fixes for Netplan. This ticket is
being user for the SRU
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039825

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

Title:
  NetworkManager crashes when updating wpa-eap connections

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2038811/+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 2039801] Re: Locate pointer not working when animations are disabled

Yes a new bug please. It might be reported elsewhere already.

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

Title:
  Locate pointer not working when animations are disabled

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2019-10-17 (1464 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 45.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

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

2023-10-23 Thread nairboon

I had the same issue with a NEC display on Debian stable and AMD gpu.
Interestingly, *enabling* DDC/CI seems to solve it, at least so far.

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

[Desktop-packages] [Bug 2039801] Re: Locate pointer not working when animations are disabled

2023-10-23 Thread J Chapman

Thanks Daniel, 
Should I start a new thread regarding the 'show pointer' in the screencast 
function that is launched via ctrl+shift+alt+r or prntSc?

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

Title:
  Locate pointer not working when animations are disabled

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2019-10-17 (1464 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 45.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039801/+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 2039801] Re: Locate pointer not working when animations are disabled

Fix proposed: https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/2986

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Locate pointer not working when animations are disabled

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2019-10-17 (1464 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 45.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039801/+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 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar

The new font relies on some different mechanism to determine the style
of a given typeface, as each different style points to a same file. The
old font doesn't do that. Maybe that could be tripping the resolution.

--->
# ubuntu-fonts
lrwxrwxrwx 1 root root   20 jun 21 10:35  UbuntuMono-B.ttf -> 
'UbuntuMono[wght].ttf'
lrwxrwxrwx 1 root root   27 jun 21 10:35  UbuntuMono-BI.ttf -> 
'UbuntuMono-Italic[wght].ttf'
-rw-r--r-- 1 root root 169K mar 24  2023 'UbuntuMono-Italic[wght].ttf'
lrwxrwxrwx 1 root root   20 jun 21 10:35  UbuntuMono-R.ttf -> 
'UbuntuMono[wght].ttf'
lrwxrwxrwx 1 root root   27 jun 21 10:35  UbuntuMono-RI.ttf -> 
'UbuntuMono-Italic[wght].ttf'
-rw-r--r-- 1 root root 169K mar 24  2023 'UbuntuMono[wght].ttf'
lrwxrwxrwx 1 root root   21 jun 21 10:35  Ubuntu-B.ttf -> 
'Ubuntu[wdth,wght].ttf'
lrwxrwxrwx 1 root root   28 jun 21 10:35  Ubuntu-BI.ttf -> 
'Ubuntu-Italic[wdth,wght].ttf'
lrwxrwxrwx 1 root root   21 jun 21 10:35  Ubuntu-C.ttf -> 
'Ubuntu[wdth,wght].ttf'
-rw-r--r-- 1 root root 664K jun 21 10:34 'Ubuntu-Italic[wdth,wght].ttf'
lrwxrwxrwx 1 root root   21 jun 21 10:35  Ubuntu-L.ttf -> 
'Ubuntu[wdth,wght].ttf'
lrwxrwxrwx 1 root root   28 jun 21 10:35  Ubuntu-LI.ttf -> 
'Ubuntu-Italic[wdth,wght].ttf'
lrwxrwxrwx 1 root root   21 jun 21 10:35  Ubuntu-M.ttf -> 
'Ubuntu[wdth,wght].ttf'
lrwxrwxrwx 1 root root   28 jun 21 10:35  Ubuntu-MI.ttf -> 
'Ubuntu-Italic[wdth,wght].ttf'
lrwxrwxrwx 1 root root   21 jun 21 10:35  Ubuntu-R.ttf -> 
'Ubuntu[wdth,wght].ttf'
lrwxrwxrwx 1 root root   28 jun 21 10:35  Ubuntu-RI.ttf -> 
'Ubuntu-Italic[wdth,wght].ttf'
lrwxrwxrwx 1 root root   21 jun 21 10:35  Ubuntu-Th.ttf -> 
'Ubuntu[wdth,wght].ttf'
-rw-r--r-- 1 root root 1,1M jun 21 10:34 'Ubuntu[wdth,wght].ttf'


# ubuntu-fonts-classic
-rw-r--r-- 1 root root 187K set 26  2011 UbuntuMono-B.ttf
-rw-r--r-- 1 root root 212K set 26  2011 UbuntuMono-BI.ttf
-rw-r--r-- 1 root root 201K set 26  2011 UbuntuMono-R.ttf
-rw-r--r-- 1 root root 206K set 26  2011 UbuntuMono-RI.ttf
-rw-r--r-- 1 root root 326K jul 10  2015 Ubuntu-B.ttf
-rw-r--r-- 1 root root 349K jul 10  2015 Ubuntu-BI.ttf
-rw-r--r-- 1 root root 343K jul 10  2015 Ubuntu-C.ttf
-rw-r--r-- 1 root root 406K jul 10  2015 Ubuntu-L.ttf
-rw-r--r-- 1 root root 401K jul 10  2015 Ubuntu-LI.ttf
-rw-r--r-- 1 root root 334K jul 10  2015 Ubuntu-M.ttf
-rw-r--r-- 1 root root 359K jul 10  2015 Ubuntu-MI.ttf
-rw-r--r-- 1 root root 346K jul 10  2015 Ubuntu-R.ttf
-rw-r--r-- 1 root root 378K jul 10  2015 Ubuntu-RI.ttf
-rw-r--r-- 1 root root 235K fev 18  2022 Ubuntu-Th.ttf
<---

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

Title:
  [snap] New Ubuntu font with normal weight displayed as bold in Google
  Docs in Chromium after upgrading to Lunar

Status in chromium-browser package in Ubuntu:
  Triaged
Status in fonts-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  I am experiencing a rendering regression after upgrading from Kinetic to 
Lunar.
  Google Docs using the Ubuntu font family are displayed incorrectly in 
Chromium: the normal weight font is rendered identically to the bold weight 
one, instead of being thicker than light and thinner than medium.

  Printing is also affected, unless I use Google Docs' download to PDF
  function, although that probably triggers a server-side rendering.

  This issue does not occur in Firefox or Google Chrome.

  One thing that may be relevant: if I force-refresh my test Google Doc
  I see all four Ubuntu font lines initially being rendered as bold. The
  light and medium lines are then re-rendered with the correct weight.
  It's as if bold was the default weight and the normal variant
  disappeared.

  As far as I can tell I was already running Chromium 112.0.5615.49 in
  Kinetic, and with Chromium being a snap I don't quite understand why
  the Ubuntu series would matter.

  I have also tried version 114.0.5735.16 (in latest/beta at the
  moment); the symptoms are identical.

  The attachments show the rendering error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+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 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar

Workaround:

  apt install fonts-ubuntu- fonts-ubuntu-classic

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

Title:
  [snap] New Ubuntu font with normal weight displayed as bold in Google
  Docs in Chromium after upgrading to Lunar

Status in chromium-browser package in Ubuntu:
  Triaged
Status in fonts-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  I am experiencing a rendering regression after upgrading from Kinetic to 
Lunar.
  Google Docs using the Ubuntu font family are displayed incorrectly in 
Chromium: the normal weight font is rendered identically to the bold weight 
one, instead of being thicker than light and thinner than medium.

  Printing is also affected, unless I use Google Docs' download to PDF
  function, although that probably triggers a server-side rendering.

  This issue does not occur in Firefox or Google Chrome.

  One thing that may be relevant: if I force-refresh my test Google Doc
  I see all four Ubuntu font lines initially being rendered as bold. The
  light and medium lines are then re-rendered with the correct weight.
  It's as if bold was the default weight and the normal variant
  disappeared.

  As far as I can tell I was already running Chromium 112.0.5615.49 in
  Kinetic, and with Chromium being a snap I don't quite understand why
  the Ubuntu series would matter.

  I have also tried version 114.0.5735.16 (in latest/beta at the
  moment); the symptoms are identical.

  The attachments show the rendering error.

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


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

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

I see the bug is addressed, but for what it's worth, one more data
point.

I just run into the issue today when doing

  apt remove fonts-ubuntu*

What I didn't notice was that a replacement instead of a removal was
carried out

  fonts-ubuntu (0.83-6ubuntu1 => 0.869-0ubuntu1)

After a while I turned back to Firefox — which I had set up to use
Ubuntu font as default — and it had corrupted font.

That was not during installation, it was my normal several months old
Mantic environment. Restarting Firefox solved the problem. I can
reproduce it with

  apt install fonts-ubuntu fonts-ubuntu-classic-

** Attachment added: "zalgo:firefox-right:chromium-left.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2034986/+attachment/5712410/+files/zalgo%3Afirefox-right%3Achromium-left.png

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

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

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

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

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

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

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

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

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

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

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

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

  [ Other Info ]

   * TBD

  ---

  Original description:

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

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

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1998111] Re: Quectel EM05-G not being unlocked

2023-10-23 Thread Julian Andres Klode

Yes, correct, I no longer see the issue in mantic.

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

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

Title:
  Quectel EM05-G not being unlocked

Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  Despite support being in fcc-unlock.d

  Bus 001 Device 003: ID 2c7c:030a Quectel Wireless Solutions Co., Ltd.
  Quectel EM05-G

  the modem remains locked and enabling it fails:

  jak@jak-t14-g3:~:master$ mmcli -m any -e
  error: couldn't enable the modem: 
'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Retry: Invalid transition'

  
  Doing something like

  # modprobe -r cdc_mbim
  # modprobe cdc_mbim
  # mbimcli --device-open-proxy --device="/dev/wwan0mbim0" 
--quectel-set-radio-state=on 
  # systemctl RestartModemManager
  # mmcli -m any -e

  makes it work.

  Peculiar it seems that the mbim-proxy process that ModemManager
  started is hanging and causing the mbimcli command to time out (if I
  just run it manually).

  
  Further investigation warranted, tips welcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: modemmanager 1.20.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Mon Nov 28 13:54:07 2022
  InstallationDate: Installed on 2022-11-26 (1 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  SourcePackage: modemmanager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1998111/+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 2038901] Re: Ubuntu default/minimal installation is only ~11% smaller than full installation

** Summary changed:

- Ubuntu default/minimal installation should be smaller
+ Ubuntu default/minimal installation is only ~11% smaller than full 
installation

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

Title:
  Ubuntu default/minimal installation is only ~11% smaller than full
  installation

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu default/minimal installation should be made smaller in future.
  It's a little too close to the full install size right now. As of
  mantic 2023-10-10, the default/minimal install ends up 8.4 GB whereas
  the full install is 9.4 GB.

  
https://docs.google.com/spreadsheets/d/e/2PACX-1vSmQLXuDO0E-tKnWcgjL3Ua2bWDeUg4ICZIfuMrrZndBrYjbVLKAWlKuiZLZ9EOrj4N1WV37DRg8GyW/pubchart?oid=2040836911=interactive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2038901/+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 1857191] Re: Dark themes don't work well with highlighted current line in gedit

2023-10-23 Thread Daniel Tang

I "fixed" this problem by switching from gedit to gnome-text-editor.
People say it's the successor to gedit and is recommended as the
default.

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

Title:
  Dark themes don't work well with highlighted current line in gedit

Status in GtkSourceView:
  Fix Released
Status in Yaru Theme:
  New
Status in gtksourceview4 package in Ubuntu:
  Triaged
Status in yaru-theme package in Ubuntu:
  Confirmed
Status in gtksourceview4 source package in Jammy:
  Confirmed
Status in yaru-theme source package in Jammy:
  Confirmed

Bug description:
  In order to checkout out an old bug report I started gedit, enabled
  "Highlight current line" and changed the application theme to "Yaru-
  dark" The current line is highlighted correctly but the text is
  unreadable because it is too light. The text needs to be much darker.

  This is not a theme that I would normally use so I'm not too bothered
  about how the problem is fixed but this configuration makes gedit very
  difficult to use as you can't actually see the text that you're
  adding, changing or deleting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: yaru-theme-gtk 19.10.4
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 21 16:33:03 2019
  InstallationDate: Installed on 2019-05-17 (218 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  PackageArchitecture: all
  SourcePackage: yaru-theme
  UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtksourceview/+bug/1857191/+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 2039801] Re: Locate pointer not working when animations are disabled

** Summary changed:

- Ubuntu 23.10, locate pointer not working when animations are disabled
+ Locate pointer not working when animations are disabled

** Tags added: jammy

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

Title:
  Locate pointer not working when animations are disabled

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2019-10-17 (1464 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 45.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039801/+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 2039340] Re: gnome-shell (login screen) crashes with SIGSEGV in __GI_getenv("EXPAT_ACCOUNTING_DEBUG")