date:20220913

** Tags added: limerick

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

Title:
  Xwayland fails to start on Xilinx: symbol lookup error:
  /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane

Status in xwayland package in Ubuntu:
  Fix Released
Status in xwayland source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Xwayland fails to start on Xilinx:

  /usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined
  symbol: gbm_bo_get_fd_for_plane

  Without Xwayland you cannot run X11 apps in Wayland sessions (or even
  log into a gnome-shell Wayland session).

  [Test Plan]

  Run: Xwayland -h

  Expected: Command line options to be displayed.

  Observed: symbol lookup error: /usr/bin/Xwayland: undefined symbol:
  gbm_bo_get_fd_for_plane

  [Where problems could occur]

  Since this changes Xwayland initialization for all platforms, risk of
  bugs and regressions reaches all platforms. At best an Xwayland
  failure would prevent X11 apps from working properly, or at worst
  prevent gnome-shell Wayland sessions from starting (this bug).

  [Other Info]

  Fixing this for jammy is a prerequisite to resolve bug 1961563.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1987628/+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 1987628] Re: Xwayland fails to start on Xilinx: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane

Verified fixed in version 2:22.1.1-1ubuntu0.2 on jammy (arm64 Xilinx
Kria board).


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

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

Title:
  Xwayland fails to start on Xilinx: symbol lookup error:
  /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane

Status in xwayland package in Ubuntu:
  Fix Released
Status in xwayland source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Xwayland fails to start on Xilinx:

  /usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined
  symbol: gbm_bo_get_fd_for_plane

  Without Xwayland you cannot run X11 apps in Wayland sessions (or even
  log into a gnome-shell Wayland session).

  [Test Plan]

  Run: Xwayland -h

  Expected: Command line options to be displayed.

  Observed: symbol lookup error: /usr/bin/Xwayland: undefined symbol:
  gbm_bo_get_fd_for_plane

  [Where problems could occur]

  Since this changes Xwayland initialization for all platforms, risk of
  bugs and regressions reaches all platforms. At best an Xwayland
  failure would prevent X11 apps from working properly, or at worst
  prevent gnome-shell Wayland sessions from starting (this bug).

  [Other Info]

  Fixing this for jammy is a prerequisite to resolve bug 1961563.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1987628/+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 1931685] Re: Ubuntu 21.04: ubuntu dock causes windows in Activities view get cutt off at the bottom

Ubuntu 21.04 and 20.10 are no longer supported. If you continue to
experience problems in a supported Ubuntu release then please open new
bugs for them.

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => Won't Fix

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

Title:
Ubuntu 21.04: ubuntu dock causes windows in Activities view get cutt
off at the bottom

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Won't Fix

Bug description:
On ubuntu 21.04 and on 20.10. When I open the activities view with a
few windows open the bottom edge of the windows (with the window
names) get cut off, the bottom of the workspaces bar on the right side
also gets cut off.

When the workspaces bar is fully extended, the windows can be seen
fully. So when I hover over the workspaces bar, or there are multiple
workspaces with windows in them, or with an extension to always keep
the workspaces open, this issue doesn't impact anything. However, the
issue still exists because you can see the bottom of the workspaces
bar being cut off.

When I connect a second monitor, and arrange the monitors one above
the other (with the top one as the permanent), I can see the cut off
UI elements on the bottom monitor.

With the ubuntu dock extension disabled, none of these issues are
present.

Here are a few screenshots that show the bug in action:
https://ibb.co/album/4whv2c

I could NOT spot this issue on a clean install of ubuntu 20.04. But I
could see it on clean installs of both on 20.10 and on 21.04. This
exists both on Wayland and Xorg.

This might be related to this prior issue:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-
ubuntu-dock/+bug/1834967 . Maybe this issue was fixed in 20.04 but not
on the later versions.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell-extension-ubuntu-dock 69ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 11 13:05:40 2021
InstallationDate: Installed on 2021-06-11 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1931685/+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 1966054] Re: Dock gets confused in dual monitor setup with different scaling

** Tags added: multimonitor

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

Title:
  Dock gets confused in dual monitor setup with different scaling

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

Bug description:
  I have two monitors: the inbuilt laptop one, 1920x1080 at 125% scaling
  shifted slightly down to match the relative heights on my desk, and an
  external one, 1920x1080 at 100% scaling, primary. I have the dock set
  to autohide.

  When I open the dock by mousing to the side of the primary monitor it
  will appear, usually with the icons correct. Then, I think as a result
  of pushing the mouse slightly more to the left but not off the monitor
  (as the edge is slightly sticky), the icons will expand (see
  screenshot) I suspect as though they're picking up the scaling from
  the wrong monitor. Typically mousing over them will cause them to go
  back to their proper size again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 10:43:34 2022
  InstallationDate: Installed on 2022-03-17 (5 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1966054/+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 1989360] Re: gnome-session-binary crashed with SIGSEGV in GSM_IS_DBUS_CLIENT() from _disconnect_dbus_client() from foreach_remove_wrapper()

Ignore comment #3.

Also tracking in:
https://errors.ubuntu.com/problem/aa1e7373ce23aa7acbef3e8072bef2d8633118e7

** Summary changed:

- gnome-session-binary crashed with SIGSEGV
+ gnome-session-binary crashed with SIGSEGV in GSM_IS_DBUS_CLIENT() from 
_disconnect_dbus_client() from foreach_remove_wrapper()

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

** Information type changed from Private to Public

** Tags added: jammy

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

** Description changed:

+ https://errors.ubuntu.com/problem/aa1e7373ce23aa7acbef3e8072bef2d8633118e7
+ 
+ ---
+ 
  After upgrading open-vm-tools, system not upgrading, deleted open-vm-
  tools and set nomodeset in grub.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-session-bin 42.0-1ubuntu4
  Uname: Linux 5.19.3-051903-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Sep 12 17:25:17 2022
  ExecutablePath: /usr/libexec/gnome-session-binary
  InstallationDate: Installed on 2022-05-13 (121 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220513)
  ProcCmdline: /usr/libexec/gnome-session-binary --autostart 
/usr/share/gdm/greeter/autostart
  SegvAnalysis:
-  Segfault happened at: 0x56242209360d:mov(%rbx),%rax
-  PC (0x56242209360d) ok
-  source "(%rbx)" (0x0030) not located in a known VMA region (needed 
readable region)!
-  destination "%rax" ok
-  Stack memory exhausted (SP below stack segment)
+  Segfault happened at: 0x56242209360d:mov(%rbx),%rax
+  PC (0x56242209360d) ok
+  source "(%rbx)" (0x0030) not located in a known VMA region (needed 
readable region)!
+  destination "%rax" ok
+  Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-session
  StacktraceTop:
-  ()
-  ()
-  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  ()
-  ()
+  ()
+  ()
+  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  ()
+  ()
  Title: gnome-session-binary crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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

Title:
  gnome-session-binary crashed with SIGSEGV in GSM_IS_DBUS_CLIENT() from
  _disconnect_dbus_client() from foreach_remove_wrapper()

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/aa1e7373ce23aa7acbef3e8072bef2d8633118e7

  ---

  After upgrading open-vm-tools, system not upgrading, deleted open-vm-
  tools and set nomodeset in grub.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-session-bin 42.0-1ubuntu4
  Uname: Linux 5.19.3-051903-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Sep 12 17:25:17 2022
  ExecutablePath: /usr/libexec/gnome-session-binary
  InstallationDate: Installed on 2022-05-13 (121 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220513)
  ProcCmdline: /usr/libexec/gnome-session-binary --autostart 
/usr/share/gdm/greeter/autostart
  SegvAnalysis:
   Segfault happened at: 0x56242209360d:mov(%rbx),%rax
   PC (0x56242209360d) ok
   source "(%rbx)" (0x0030) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-session
  StacktraceTop:
   ()
   ()
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ()
   ()
  Title: gnome-session-binary crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1989360/+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 1989503] Re: Wrong change of dock zoom on multiple screens

Are you using auto-hide? If so then this sounds like bug 1966054.

** Tags added: jammy multimonitor

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

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

Title:
  Wrong change of dock zoom on multiple screens

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 22.04 LTS, I have two screens, one 4k and one 1080p, when
  I set the zoom to 200% on the 4k screen and 100% for the 1080p screen
  the dock increases in size on both screens, on the 1080p it looks
  huge, it is not able to detect the zoom value separately between
  different screens when set to show on all screens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1989503/+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 1989304] Re: gnome-shell 43.rc SIGSEGV in g_str_hash() via on_directory_profile_ready() [meta-color-store.c:94]

A potential fix is on the way:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2622

but upstream would also like to know what exists in
~gdm/.local/share/icc, ~/.local/share/icc and /usr/share/color/icc

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

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

Title:
  gnome-shell 43.rc SIGSEGV in g_str_hash() via
  on_directory_profile_ready() [meta-color-store.c:94]

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Unable to login to gnome session(bug#1989240).

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7
  Uname: Linux 5.19.0-16-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 12 10:51:32 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1662686872
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/thelastline
  RelatedPackageVersions: mutter-common 43~rc-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_steal () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: Upgraded to kinetic on 2022-09-07 (5 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1989304/+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 1989515] [NEW] "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic

2022-09-13 Thread Yaobin Wen

Public bug reported:

Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu
Bionic but "goo/gmem.h" still has the statement `#include
"GooCheckedOps.h"`. As a result, a compile error will happen when
compiling code that uses poppler:

/usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h: No
such file or directory

I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the
previous version) installed. I confirmed that "goo/gmem.h" doesn't have
the `#include "GooCheckedOps.h"` statement.

I found this issue when I was compiling gdal on my Docker container. The
Docker container was installed the problematic version
0.62.0-2ubuntu2.13 and I ran into the "No such file or directory" error.

I compiled on both Amd64 and AArch64 and I ran into the same error on
both platforms.

By reading the diff between 2.12 and 2.13
(https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz),
the patch looks quite right. But when I examined the contents of the
built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h".

Kind of weird, because the problem seems to be caused by applying
"CVE-2022-38784-pre.patch" in half: the first part that creates
"goo/GooCheckedOps.h" was not applied during the build process and the
second part that modifies "goo/gmem.h" was applied.

Any thoughts? Ideas?

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

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

Title:
"goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu
Bionic

Status in poppler package in Ubuntu:
New

Bug description:
Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on
Ubuntu Bionic but "goo/gmem.h" still has the statement `#include
"GooCheckedOps.h"`. As a result, a compile error will happen when
compiling code that uses poppler:

/usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h:
No such file or directory

I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the
previous version) installed. I confirmed that "goo/gmem.h" doesn't
have the `#include "GooCheckedOps.h"` statement.

I found this issue when I was compiling gdal on my Docker container.
The Docker container was installed the problematic version
0.62.0-2ubuntu2.13 and I ran into the "No such file or directory"
error.

I compiled on both Amd64 and AArch64 and I ran into the same error on
both platforms.

By reading the diff between 2.12 and 2.13

(https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz),
the patch looks quite right. But when I examined the contents of the
built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h".

Any thoughts? Ideas?

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

[Desktop-packages] [Bug 1974438] Re: Info segfaults on open when LANG=pt-BR

** Changed in: texinfo (Debian)
   Status: Unknown => Fix Released

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

Title:
  Info segfaults on open when LANG=pt-BR

Status in texinfo package in Ubuntu:
  Fix Released
Status in texinfo source package in Jammy:
  Triaged
Status in texinfo package in Debian:
  Fix Released

Bug description:
  Impact
  ---
  The common CLI help utility info doesn't work for systems where the language 
is set to Brazilian

  Test Case
  
  Open a terminal and run these 2 commands:

  sudo apt install language-pack-pt
  LANGUAGE=pt_BR info

  The commands should complete without error. You can press q to exit
  info.

  What Could Go Wrong
  
  This is a double fix. First we fix the broken Brazilian translation. That 
actually won't fix the bug because we use language packs and those are 
generally only updated just before the LTS point releases (months from now).

  Next we cherry pick a fix from upstream to not crash when there is an
  error in the translations like this.

  https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=04f7ed5ce647050

  
  Original Bug Report
  
  When using my default locale info segfaults on open:

  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `info'.
  Program terminated with signal SIGABRT, Aborted.
  #0  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140004652754752) at ./nptl/pthread_kill.c:44
  44./nptl/pthread_kill.c: Arquivo ou diretório inexistente.
  (gdb) bt
  #0  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140004652754752) at ./nptl/pthread_kill.c:44
  #1  __pthread_kill_internal (signo=6, threadid=140004652754752) at 
./nptl/pthread_kill.c:78
  #2  __GI___pthread_kill (threadid=140004652754752, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
  #3  0x7f555f9c7476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #4  0x7f555f9ad7f3 in __GI_abort () at ./stdlib/abort.c:79
  #5  0x55e7b9c13546 in replace_in_documentation (
  string=0x7f555fbf61ed "Bem vindo à versão Info %s. Digite 
\\[get-help-window] p/ ajuda,\\[get-inffo-help-node] p/ tutorial.", 
help_is_only_window_p=help_is_only_window_p@entry=0) at ./info/infodoc.c:722
  #6  0x55e7b9c068c8 in display_startup_message () at ./info/session.c:187
  #7  info_session (error=, user_filename=0x0, 
ref_list=0x55e7ba92b050) at ./info/session.c:208
  #8  main (argc=, argv=) at ./info/info.c:1079

  if I do LC_ALL=C info then it opens normally. It seems the translation
  string is not matching some positional parameter in the original
  string, but I didn't check that far.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: info 6.8-4build1
  ProcVersionSignature: Ubuntu 5.15.0-32.33-lowlatency 5.15.35
  Uname: Linux 5.15.0-32-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 20 09:13:44 2022
  InstallationDate: Installed on 2019-05-30 (1085 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: texinfo
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1974438/+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 1974438] Re: Info segfaults on open when LANG=pt-BR

** Description changed:

  Impact
  ---
  The common CLI help utility info doesn't work for systems where the language 
is set to Brazilian
  
  Test Case
  
  Open a terminal and run these 2 commands:
  
  sudo apt install language-pack-pt
  LANGUAGE=pt_BR info
  
  The commands should complete without error. You can press q to exit
  info.
  
  What Could Go Wrong
  
- 
- Other Info
- --
- This is a double fix. First we fix the broken Brazilian translation.
+ This is a double fix. First we fix the broken Brazilian translation. That 
actually won't fix the bug because we use language packs and those are 
generally only updated just before the LTS point releases (months from now).
  
  Next we cherry pick a fix from upstream to not crash when there is an
  error in the translations like this.
  
  https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=04f7ed5ce647050
+ 
  
  Original Bug Report
  
  When using my default locale info segfaults on open:
  
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `info'.
  Program terminated with signal SIGABRT, Aborted.
  #0  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140004652754752) at ./nptl/pthread_kill.c:44
  44./nptl/pthread_kill.c: Arquivo ou diretório inexistente.
  (gdb) bt
  #0  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140004652754752) at ./nptl/pthread_kill.c:44
  #1  __pthread_kill_internal (signo=6, threadid=140004652754752) at 
./nptl/pthread_kill.c:78
  #2  __GI___pthread_kill (threadid=140004652754752, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
  #3  0x7f555f9c7476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #4  0x7f555f9ad7f3 in __GI_abort () at ./stdlib/abort.c:79
  #5  0x55e7b9c13546 in replace_in_documentation (
  string=0x7f555fbf61ed "Bem vindo à versão Info %s. Digite 
\\[get-help-window] p/ ajuda,\\[get-inffo-help-node] p/ tutorial.", 
help_is_only_window_p=help_is_only_window_p@entry=0) at ./info/infodoc.c:722
  #6  0x55e7b9c068c8 in display_startup_message () at ./info/session.c:187
  #7  info_session (error=, user_filename=0x0, 
ref_list=0x55e7ba92b050) at ./info/session.c:208
  #8  main (argc=, argv=) at ./info/info.c:1079
  
  if I do LC_ALL=C info then it opens normally. It seems the translation
  string is not matching some positional parameter in the original string,
  but I didn't check that far.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: info 6.8-4build1
  ProcVersionSignature: Ubuntu 5.15.0-32.33-lowlatency 5.15.35
  Uname: Linux 5.15.0-32-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 20 09:13:44 2022
  InstallationDate: Installed on 2019-05-30 (1085 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: texinfo
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (19 days ago)

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

Title:
  Info segfaults on open when LANG=pt-BR

Status in texinfo package in Ubuntu:
  Fix Released
Status in texinfo source package in Jammy:
  Triaged
Status in texinfo package in Debian:
  Fix Released

Bug description:
  Impact
  ---
  The common CLI help utility info doesn't work for systems where the language 
is set to Brazilian

  Test Case
  
  Open a terminal and run these 2 commands:

  sudo apt install language-pack-pt
  LANGUAGE=pt_BR info

  The commands should complete without error. You can press q to exit
  info.

  What Could Go Wrong
  
  This is a double fix. First we fix the broken Brazilian translation. That 
actually won't fix the bug because we use language packs and those are 
generally only updated just before the LTS point releases (months from now).

  Next we cherry pick a fix from upstream to not crash when there is an
  error in the translations like this.

  https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=04f7ed5ce647050

  
  Original Bug Report
  
  When using my default locale info segfaults on open:

  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `info'.
  Program terminated with signal SIGABRT, Aborted.
  #0  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140004652754752) at ./nptl/pthread_kill.c:44
  44./nptl/pthread_kill.c: Arquivo ou diretório inexistente.
  (gdb) bt
  #0  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140004652754752) at ./nptl/pthr

[Desktop-packages] [Bug 1974438] Re: Info segfaults on open when LANG=pt-BR

** Description changed:

+ Impact
+ ---
+ The common CLI help utility info doesn't work for systems where the language 
is set to Brazilian
+ 
+ Test Case
+ 
+ Open a terminal and run these 2 commands:
+ 
+ sudo apt install language-pack-pt
+ LANGUAGE=pt_BR info
+ 
+ The commands should complete without error. You can press q to exit
+ info.
+ 
+ What Could Go Wrong
+ 
+ 
+ Other Info
+ --
+ This is a double fix. First we fix the broken Brazilian translation.
+ 
+ Next we cherry pick a fix from upstream to not crash when there is an
+ error in the translations like this.
+ 
+ https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=04f7ed5ce647050
+ 
+ Original Bug Report
+ 
  When using my default locale info segfaults on open:
  
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `info'.
  Program terminated with signal SIGABRT, Aborted.
  #0  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140004652754752) at ./nptl/pthread_kill.c:44
  44./nptl/pthread_kill.c: Arquivo ou diretório inexistente.
  (gdb) bt
  #0  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140004652754752) at ./nptl/pthread_kill.c:44
  #1  __pthread_kill_internal (signo=6, threadid=140004652754752) at 
./nptl/pthread_kill.c:78
  #2  __GI___pthread_kill (threadid=140004652754752, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
  #3  0x7f555f9c7476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #4  0x7f555f9ad7f3 in __GI_abort () at ./stdlib/abort.c:79
  #5  0x55e7b9c13546 in replace_in_documentation (
- string=0x7f555fbf61ed "Bem vindo à versão Info %s. Digite 
\\[get-help-window] p/ ajuda,\\[get-inffo-help-node] p/ tutorial.", 
help_is_only_window_p=help_is_only_window_p@entry=0) at ./info/infodoc.c:722
+ string=0x7f555fbf61ed "Bem vindo à versão Info %s. Digite 
\\[get-help-window] p/ ajuda,\\[get-inffo-help-node] p/ tutorial.", 
help_is_only_window_p=help_is_only_window_p@entry=0) at ./info/infodoc.c:722
  #6  0x55e7b9c068c8 in display_startup_message () at ./info/session.c:187
  #7  info_session (error=, user_filename=0x0, 
ref_list=0x55e7ba92b050) at ./info/session.c:208
  #8  main (argc=, argv=) at ./info/info.c:1079
  
- 
- if I do LC_ALL=C info then it opens normally. It seems the translation string 
is not matching some positional parameter in the original string, but I didn't 
check that far.
+ if I do LC_ALL=C info then it opens normally. It seems the translation
+ string is not matching some positional parameter in the original string,
+ but I didn't check that far.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: info 6.8-4build1
  ProcVersionSignature: Ubuntu 5.15.0-32.33-lowlatency 5.15.35
  Uname: Linux 5.15.0-32-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 20 09:13:44 2022
  InstallationDate: Installed on 2019-05-30 (1085 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
-  LANGUAGE=pt_BR:pt:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=pt_BR.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=pt_BR:pt:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=pt_BR.UTF-8
+  SHELL=/bin/bash
  SourcePackage: texinfo
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (19 days ago)

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

** Also affects: texinfo (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013283
   Importance: Unknown
   Status: Unknown

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

Title:
  Info segfaults on open when LANG=pt-BR

Status in texinfo package in Ubuntu:
  Fix Released
Status in texinfo source package in Jammy:
  Triaged
Status in texinfo package in Debian:
  Unknown

Bug description:
  Impact
  ---
  The common CLI help utility info doesn't work for systems where the language 
is set to Brazilian

  Test Case
  
  Open a terminal and run these 2 commands:

  sudo apt install language-pack-pt
  LANGUAGE=pt_BR info

  The commands should complete without error. You can press q to exit
  info.

  What Could Go Wrong
  

  Other Info
  --
  This is a double fix. First we fix the broken Brazilian translation.

  Next we cherry pick a fix from upstream to not crash when there is an
  error in the translations like this.

  https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=04f7ed5ce647050

  Original Bug Report
  
  When using my default locale info segfaults on open:

  Using host libthread_db library "/lib/x86_64-linux-

[Desktop-packages] [Bug 1974438] Re: Info segfaults on open when LANG=pt-BR

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

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

** Also affects: texinfo (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: texinfo (Ubuntu)
   Status: Triaged => Fix Released

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

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

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

Title:
  Info segfaults on open when LANG=pt-BR

Status in texinfo package in Ubuntu:
  Fix Released
Status in texinfo source package in Jammy:
  Triaged

Bug description:
  Impact
  ---
  The common CLI help utility info doesn't work for systems where the language 
is set to Brazilian

  Test Case
  
  Open a terminal and run these 2 commands:

  sudo apt install language-pack-pt
  LANGUAGE=pt_BR info

  The commands should complete without error. You can press q to exit
  info.

  What Could Go Wrong
  

  Other Info
  --
  This is a double fix. First we fix the broken Brazilian translation.

  Next we cherry pick a fix from upstream to not crash when there is an
  error in the translations like this.

  https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=04f7ed5ce647050

  Original Bug Report
  
  When using my default locale info segfaults on open:

  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `info'.
  Program terminated with signal SIGABRT, Aborted.
  #0  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140004652754752) at ./nptl/pthread_kill.c:44
  44./nptl/pthread_kill.c: Arquivo ou diretório inexistente.
  (gdb) bt
  #0  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140004652754752) at ./nptl/pthread_kill.c:44
  #1  __pthread_kill_internal (signo=6, threadid=140004652754752) at 
./nptl/pthread_kill.c:78
  #2  __GI___pthread_kill (threadid=140004652754752, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
  #3  0x7f555f9c7476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #4  0x7f555f9ad7f3 in __GI_abort () at ./stdlib/abort.c:79
  #5  0x55e7b9c13546 in replace_in_documentation (
  string=0x7f555fbf61ed "Bem vindo à versão Info %s. Digite 
\\[get-help-window] p/ ajuda,\\[get-inffo-help-node] p/ tutorial.", 
help_is_only_window_p=help_is_only_window_p@entry=0) at ./info/infodoc.c:722
  #6  0x55e7b9c068c8 in display_startup_message () at ./info/session.c:187
  #7  info_session (error=, user_filename=0x0, 
ref_list=0x55e7ba92b050) at ./info/session.c:208
  #8  main (argc=, argv=) at ./info/info.c:1079

  if I do LC_ALL=C info then it opens normally. It seems the translation
  string is not matching some positional parameter in the original
  string, but I didn't check that far.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: info 6.8-4build1
  ProcVersionSignature: Ubuntu 5.15.0-32.33-lowlatency 5.15.35
  Uname: Linux 5.15.0-32-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 20 09:13:44 2022
  InstallationDate: Installed on 2019-05-30 (1085 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: texinfo
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1974438/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies

and I've uploaded a focal SRU candidate to the review queue now

** Changed in: iputils (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: iputils (Ubuntu Focal)
   Status: New => Fix Committed

** Description changed:

+ = Impact =
+ 
+ the ping statistics are incorrect when dealing with truncated packets
+ 
+ = Test case =
+ 
+ $ ping -c 1 -s 1200 8.8.8.8
+ 
+ should list truncated replies and received packets
+ 
+ = Regression potential =
+ 
+ the changes are limited to the ping source any regression would impact
+ that utility, check that responses are correctly handled and statistics
+ reflecting what is expected
+ 
+ --
+ 
  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.
  
  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722
  
  Could this patch be added for a Focal update please?
  
  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)
  
  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  
  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms
  
  4)
  
  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)
  
  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Focal:
  Fix Committed

Bug description:
  = Impact =

  the ping statistics are incorrect when dealing with truncated packets

  = Test case =

  $ ping -c 1 -s 1200 8.8.8.8

  should list truncated replies and received packets

  = Regression potential =

  the changes are limited to the ping source any regression would impact
  that utility, check that responses are correctly handled and
  statistics reflecting what is expected

  --

  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1977564] Re: wireplumber conflicts with pipewire-media-session & needs fixing

** Changed in: pipewire-media-session (Debian)
   Status: Confirmed => Fix Released

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

Title:
  wireplumber conflicts with pipewire-media-session & needs fixing

Status in pipewire-media-session package in Ubuntu:
  Fix Released
Status in wireplumber package in Ubuntu:
  Fix Released
Status in pipewire-media-session source package in Jammy:
  Incomplete
Status in wireplumber source package in Jammy:
  Incomplete
Status in pipewire-media-session package in Debian:
  Fix Released

Bug description:
  Impact
  --
  Ubuntu 22.04 LTS installs pipewire-media-session by default. If a user 
attempts to install wireplumber, it will break the pipewire-session-manager 
systemd user service used by gnome-remote-desktop

  Failed to preset unit, file 
/etc/systemd/user/pipewire-session-manager.service already exists and is a 
symlink to /usr/lib/systemd/user/pipewire-media-session.service.
  Created symlink /etc/systemd/user/pipewire.service.wants/wireplumber.service 
\u2192 /usr/lib/systemd/user/wireplumber.service.
  /usr/bin/deb-systemd-helper: error: systemctl preset failed on 
wireplumber.service: No such file or directory

  More details are needed for whether the broken symlink causes any
  issues since pipewire appears to still work.

  Test Case
  -

  What Could Go Wrong
  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1977564/+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 1989503] [NEW] Wrong change of dock zoom on multiple screens

2022-09-13 Thread WHK

Public bug reported:

I use Ubuntu 22.04 LTS, I have two screens, one 4k and one 1080p, when I
set the zoom to 200% on the 4k screen and 100% for the 1080p screen the
dock increases in size on both screens, on the 1080p it looks huge, it
is not able to detect the zoom value separately between different
screens when set to show on all screens.

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

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

Title:
  Wrong change of dock zoom on multiple screens

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

Bug description:
  I use Ubuntu 22.04 LTS, I have two screens, one 4k and one 1080p, when
  I set the zoom to 200% on the 4k screen and 100% for the 1080p screen
  the dock increases in size on both screens, on the 1080p it looks
  huge, it is not able to detect the zoom value separately between
  different screens when set to show on all screens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1989503/+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 1987628] Re: Xwayland fails to start on Xilinx: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane

Hello Daniel, or anyone else affected,

Accepted xwayland into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/xwayland/2:22.1.1-1ubuntu0.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: xwayland (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  Xwayland fails to start on Xilinx: symbol lookup error:
  /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane

Status in xwayland package in Ubuntu:
  Fix Released
Status in xwayland source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Xwayland fails to start on Xilinx:

  /usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined
  symbol: gbm_bo_get_fd_for_plane

  Without Xwayland you cannot run X11 apps in Wayland sessions (or even
  log into a gnome-shell Wayland session).

  [Test Plan]

  Run: Xwayland -h

  Expected: Command line options to be displayed.

  Observed: symbol lookup error: /usr/bin/Xwayland: undefined symbol:
  gbm_bo_get_fd_for_plane

  [Where problems could occur]

  Since this changes Xwayland initialization for all platforms, risk of
  bugs and regressions reaches all platforms. At best an Xwayland
  failure would prevent X11 apps from working properly, or at worst
  prevent gnome-shell Wayland sessions from starting (this bug).

  [Other Info]

  Fixing this for jammy is a prerequisite to resolve bug 1961563.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1987628/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies

The issue is fixed in the version available in the current Ubuntu serie

** Changed in: iputils (Ubuntu)
   Importance: Undecided => Low

** Changed in: iputils (Ubuntu)
   Status: New => Fix Released

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Focal:
  New

Bug description:
  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container

** Changed in: livecd-rootfs (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: livecd-rootfs (Ubuntu Jammy)
   Importance: Medium => High

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

Title:
  server image pulls in ModemManager via fwupd, consumes 25MiB RAM in
  every container

Status in fwupd package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  New
Status in fwupd source package in Jammy:
  Invalid
Status in livecd-rootfs source package in Jammy:
  Triaged
Status in modemmanager source package in Jammy:
  New
Status in ubuntu-meta source package in Jammy:
  New

Bug description:
  Looking at memory utilization in a pristine Ubuntu lxd container (top
  -o RES), I see that ModemManager is running, which I was surprised to
  see is present at all in the stock image.

  Tracking this I find that fwupd depends on libmm-glib0, which in turn
  Recommends: modemmanager.

  Libraries in general should not recommend daemons, so it's possible
  this should be fixed by libmm-glib0 dropping this Recommends.  It
  certainly doesn't seem to be a deliberate decision by the Server Team
  to have modemmanager installed and running by default on all systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

2022-09-13 Thread Rigoberto Sanchez

This is a problem for snap versions of Chromium and Firefox, they are
unable to access the kerberos ticket and also (not sure why)
/etc/gss/mech.d/

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1849346/+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 1989352] Re: [WSL] Prepare kinetic for common snap use cases

2022-09-13 Thread Carlos Nihelton

Upgrading a Jammy instance with `do-release-upgrade -d` worked as
expected.

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

Title:
  [WSL] Prepare kinetic for common snap use cases

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Users of Ubuntu WSL might be surprised by unexpected dependencies when
  dealing with snaps. The Ubuntu WSL development team is looking for
  ways to let early adopters to experiment some snapd support in
  Kinetic, while still providing the most seamless experience for them.
  Tests done in WSL instances showed surprises that we should mitigate
  soon.

  Some examples are:

  * Sublime Text and Sublime Merge apps silently depend on libgl1. This
  seems a bug which we didn't yet figure out how to fix in the snaps
  themselves. Being such hidden dependencies, we'd expect to soon find
  similar cases as those.

  * Flutter snap provides all dependencies and runs without issues, but
  apps compiled by Flutter requires libgl1, libegl1 and libgtk-3-0
  present in the system during development. Attempting to just run any
  app compiled with Flutter during development will result in crash due
  those libs not being found. Most likely, once package as snaps, those
  apps will behave as expected, if the packager lists dependencies
  properly. The issue reported here affects the app developer
  experience.

  One solution for those problems is seeding for Ubuntu WSL
  specifically:

  - libgl1
  - libegl1
  - libgtk-3-0

  Experienced Ubuntu users would figure out how to overcome those issues
  very quickly, but we should expect that most of Ubuntu WSL userbase
  won't fit in that persona.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989352/+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 1989352] Re: [WSL] Prepare kinetic for common snap use cases

Given that these seed changes are happening for Kinetic and the work
done in ubuntu-release-upgrader to support WSL upgrades have upgrades
from Jammy to Kinetic been considered?

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

Title:
  [WSL] Prepare kinetic for common snap use cases

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Users of Ubuntu WSL might be surprised by unexpected dependencies when
  dealing with snaps. The Ubuntu WSL development team is looking for
  ways to let early adopters to experiment some snapd support in
  Kinetic, while still providing the most seamless experience for them.
  Tests done in WSL instances showed surprises that we should mitigate
  soon.

  Some examples are:

  * Sublime Text and Sublime Merge apps silently depend on libgl1. This
  seems a bug which we didn't yet figure out how to fix in the snaps
  themselves. Being such hidden dependencies, we'd expect to soon find
  similar cases as those.

  * Flutter snap provides all dependencies and runs without issues, but
  apps compiled by Flutter requires libgl1, libegl1 and libgtk-3-0
  present in the system during development. Attempting to just run any
  app compiled with Flutter during development will result in crash due
  those libs not being found. Most likely, once package as snaps, those
  apps will behave as expected, if the packager lists dependencies
  properly. The issue reported here affects the app developer
  experience.

  One solution for those problems is seeding for Ubuntu WSL
  specifically:

  - libgl1
  - libegl1
  - libgtk-3-0

  Experienced Ubuntu users would figure out how to overcome those issues
  very quickly, but we should expect that most of Ubuntu WSL userbase
  won't fit in that persona.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989352/+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 1989490] [NEW] Translatable release notes

2022-09-13 Thread Sabri Ünal

Public bug reported:

Hi,

I'm a member of Turkish translation team of GNOME also Turkish
translation team of Ubuntu (https://launchpad.net/~ubuntu-l10n-tr).

GNOME team actually does not mark release notes as translatable* for any
GNOME application but Ubuntu keeps them translatable.

Could we exclude release notes ( everything in *
tag) from translation process?

* https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1903

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

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

Title:
  Translatable release notes

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Hi,

  I'm a member of Turkish translation team of GNOME also Turkish
  translation team of Ubuntu (https://launchpad.net/~ubuntu-l10n-tr).

  GNOME team actually does not mark release notes as translatable* for
  any GNOME application but Ubuntu keeps them translatable.

  Could we exclude release notes ( everything in *
  tag) from translation process?

  * https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1903

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1989490/+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 1959507] Re: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)

2022-09-13 Thread Yi

Apologies for #13. Added below in case anyone else ends up here for the
same thing...

I had multiple monitors configured using ARandR, I'm working around the
random crashes by disabling my second monitor via Settings>Screen
Display>Single Display. Only one display, but better than crashing when
one of the displays times out.

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

Title:
  gnome-shell crashed in clutter_actor_get_real_resource_scale() with
  assertion failed: (guessed_scale >= 1.f)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  I'm starting a VM Ubuntu 22.04 on QEMU/KVM and this alert appears.
  It seems to myself there is an issue between Wayland and spice-vdagent.
  Regards,
  Michel

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 29 09:52:12 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-01-28 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 41.3-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __pthread_kill_implementation (no_tid=0, signo=6, threadid=140083783699840) 
at pthread_kill.c:44
   __pthread_kill_internal (signo=6, threadid=140083783699840) at 
pthread_kill.c:80
   __GI___pthread_kill (threadid=140083783699840, signo=signo@entry=6) at 
pthread_kill.c:91
   __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
   __GI_abort () at abort.c:79
  Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507/+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 1979891] Re: Firefox becomes unusable when adjusting window size

2022-09-13 Thread Olivier Tilloy

Thanks!

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1790527
   Importance: Unknown
   Status: Unknown

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

Title:
  Firefox becomes unusable when adjusting window size

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

Bug description:
  OS version: Ubuntu 22.04 LTS
  Firefox version: 1:1snap1-0ubuntu2 - 101.0.1 (64-bit)

  Sometimes when I adjust the size of a Firefox window, that window
  becomes messed up: the contents don't fill the window, not all the
  controls are visible, and clicks are offset, so if I click on one
  spot, the window behaves as if I clicked on a different spot (so it's
  impossible to use Firefox in that window anymore). I seem to remember
  being able to fix this by dragging and dropping the window onto a
  different monitor or workspace in the GNOME Activities view, but I'm
  currently experiencing the problem and that is not helping. I took a
  screenshot of what's currently going on (attached) which happened when
  I tried to maximize the window. This is on a laptop with an external
  monitor that I'm using in portrait mode, via a USB-C connection that's
  converted to HDMI. I had plugged in to the external monitor a few
  minutes before this happens, and plugging in or possibly unplugging
  seems to make this bug more likely. This is a relatively new problem,
  starting within the last few weeks. (Maybe after I switched to the
  snap version of Firefox? I guess that was when I upgraded from the
  previous LTS version of Ubuntu.)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 25 15:23:13 2022
  DistUpgraded: 2022-05-27 14:03:05,108 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.32, 5.15.0-39-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:07e6]
  InstallationDate: Installed on 2018-11-23 (1309 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-05-27 (29 days ago)
  dmi.bios.date: 03/22/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0H0VG3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd03/22/2022:br1.19:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:sku07E6:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1
  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/firefox/+bug/1979891/+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 1989376] Re: [snap] firefox webauthn not working with flipper zero u2f

2022-09-13 Thread Olivier Tilloy

There's a snapd PR to address this:
https://github.com/snapcore/snapd/pull/12003.

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

** Changed in: firefox (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
   [snap] firefox webauthn not working with flipper zero u2f

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Similar to
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956865/ using
  webauthn with my flipper device did not work out of the box.

  The device id does not seem to be registered. The upstream community
  recommends[1] the following udev rules:

  ```
  # u2f-devices
  # STMicroelectronics U2F Token
  KERNEL=="hidraw*", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="5741", 
MODE="0660", GROUP="plugdev", TAG+="uaccess", TAG+="udev-acl", 
TAG+="snap_firefox_firefox"
  ```

  1: https://forum.flipperzero.one/t/u2f-not-working/4490/11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1989376/+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 1956865] Re: [snap] firefox webauthn not working with tomu u2f

2022-09-13 Thread Olivier Tilloy

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

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

Title:
  [snap] firefox webauthn not working with tomu u2f

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Similar to
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947746/ using
  webauthn with my tomu device did not work out of the box.

  The device id does not seem to be registered. Adding 
/etc/udev/rules.d/10-tomu.rules with
  ```
  ACTION=="add|change", KERNEL=="hidraw*", SUBSYSTEM=="hidraw", 
ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="0e90", TAG+="uaccess" 
TAG+="snap_firefox_firefox"
  ACTION=="add|change", SUBSYSTEM=="usb", ATTRS{idVendor}=="16d0", 
ATTRS{idProduct}=="0e90", TAG+="uaccess"
  ```
  fixed this.

  It used to work fine following the instructions from
  https://github.com/gl-sergei/u2f-token with the .deb package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956865/+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 259698] Re: pptp vpn service stops unexpectedly

2022-09-13 Thread Sturmkater

@Igor Yozhikov (iyozhikov)
Your solution works, but how do I make it persistent? I would like my system to 
auto-connect to the vpn again.

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

Title:
  pptp vpn service stops unexpectedly

Status in pptp-linux package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pptp-linux

  Using ubuntu 8.10 x86.

  pptp-linux version 1.7.2-1

  When I select the vpn option, I can create the VPN configuration, but
  after trying to connect for around ~1 second, I get the popup error:

  "The VPN connection 'Warwick' failed because the VPN service stopped
  unexpectedly."

  Im not entirely sure how to execute the connection via command line,
  so I cant work out how to get any more info on what is going on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pptp-linux/+bug/259698/+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 1989403] Re: g-c-c translation handling broken due to missing dh_translations override

2022-09-13 Thread Gunnar Hjalmarsson

Right, Jeremy, I realized that a "remaining changes" list might have
made a difference. OTOH, even with such a list I suppose it's desirable
to minimize the delta. Hence my suggestion to 'upstream' those lines to
Debian's d/rules, which Sebastien also committed.

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

Title:
  g-c-c translation handling broken due to missing dh_translations
  override

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

Bug description:
  From the latest kinetic buildlog:

 dh_translations
  dh_translations: warning: more than one meson translation domain found 
(gnome-control-center-2.0,gnome-control-center-2.0-timezones), don't know which 
one to use

  Previously d/rules included this override:

  override_dh_translations:
dh_translations --domain=gnome-control-center-2.0

  Somehow it seems to have been dropped, though. Maybe, to reduce the
  risk it gets unintentionally dropped again, it should be added to the
  debian/master branch instead of the ubuntu/master ditto?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1989403/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies

** Also affects: iputils (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  New
Status in iputils source package in Focal:
  New

Bug description:
  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1989477] Re: Switching to dark mode in settings does not change shell theme.

** Tags added: rls-kk-incoming

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

Title:
Switching to dark mode in settings does not change shell theme.

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

Bug description:
Changing the "Style" in the "Appearance" section of "Settings" (gnome-
control-center), does not update the shell theme. When I select dark
mode from settings, Libadwaita apps respond to the changes, but the
shell theme and GTK3 applications do not. This has been observed on
both Wayland and X11.

Ubuntu Version: Ubuntu Kinetic Kudu (development branch) | 22.10

Package Version: 1:43~rc-1ubuntu2

What I Expected: Changing the style in settings will affect all the
apps that support changing light/dark mode. The shell theme will also
respond to the change.

What happened instead: Only libadwaita apps are affected by changing
the style in Settings. GTK3 apps and the shell theme do not change.
When changing to dark mode via the quick settings menu, all the apps
change their color scheme appropriately. However, there is not a
smooth transition when switching the style from quick settings.

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

[Desktop-packages] [Bug 1989477] Re: Switching to dark mode in settings does not change shell theme.

2022-09-13 Thread Launchpad Bug Tracker

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

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

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

Title:
Switching to dark mode in settings does not change shell theme.

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

Ubuntu Version: Ubuntu Kinetic Kudu (development branch) | 22.10

Package Version: 1:43~rc-1ubuntu2

What I Expected: Changing the style in settings will affect all the
apps that support changing light/dark mode. The shell theme will also
respond to the change.

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

[Desktop-packages] [Bug 1309781] Re: Chromium browser does not respect defined input method

I cannot verify this in the current Bionic .deb package. I can verify it
on all (not only Chromium) snaps though,  see
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1989475.

Please only bump this bug report if you can still verify it on the .deb.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Chromium browser does not respect defined input method

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  = Steps to reproduce
  

  1. Use “im-config” to select “xim” as input method. It will change
  your “~/.xinputrc” file to define “xim” as selected method.

  = Expected behavior
  ===

  1. You should be able to use your “~/.XCompose” sequences in any
  program inside Ubuntu.

  = Current behavior
  ==

  1. Your “XCompose” sequences won't work anywhere inside the Chromium
  window, and any input in Chromium will behave sometimes as the
  standard input (“ibus”, if I recall correctly), other times it will
  ignore dead keys completely (apostrophe, quotes and grave have no
  effect).

  1.1. I say “sometimes” because I couldn't figure out what makes/when
  it behave in any of the two ways. But both are wrong anyway, so it
  does not really matter. Other programs I've tried so far (gedit,
  firefox and others) work correctly all the time, i.e., I can normally
  use my XCompose escape sequencies as expected.

  = Rationale
  ===

  As of now, I need “XCompose” sequences in order to type special
  characters and diacritics easily and correctly, for portuguese. As it
  happens, the standard input does not provide an easy way to type
  c-cedilla (ç), as the input sequence (apostrophe-c) ends with a
  c-acute (ć) instead.

  Therefore, I'd like Chromium to behave as the other programs do, i.e.,
  using “xim” as the input method.

  = lsb_release -rd
  =

  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  = apt-cache policy pkgname
  ==

  chromium-browser:
    Installed: 34.0.1847.116-0ubuntu2
    Candidate: 34.0.1847.116-0ubuntu2
    Version table:
   *** 34.0.1847.116-0ubuntu2 0
  500 http://br.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 18 18:54:32 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DetectedPlugins:

  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1309781/+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 1989477] [NEW] Switching to dark mode in settings does not change shell theme.

2022-09-13 Thread Joshua T

Public bug reported:

Changing the "Style" in the "Appearance" section of "Settings" (gnome-
control-center), does not update the shell theme. When I select dark
mode from settings, Libadwaita apps respond to the changes, but the
shell theme and GTK3 applications do not. This has been observed on both
Wayland and X11.

Ubuntu Version: Ubuntu Kinetic Kudu (development branch) | 22.10

Package Version: 1:43~rc-1ubuntu2

What I Expected: Changing the style in settings will affect all the apps
that support changing light/dark mode. The shell theme will also respond
to the change.

What happened instead: Only libadwaita apps are affected by changing the
style in Settings. GTK3 apps and the shell theme do not change. When
changing to dark mode via the quick settings menu, all the apps change
their color scheme appropriately. However, there is not a smooth
transition when switching the style from quick settings.

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

** Tags: kinetic

** Attachment added: "A video of the bug."

https://bugs.launchpad.net/bugs/1989477/+attachment/5615565/+files/simplescreenrecorder-2022-09-13_09.34.16.mkv

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

Title:
Switching to dark mode in settings does not change shell theme.

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

Ubuntu Version: Ubuntu Kinetic Kudu (development branch) | 22.10

Package Version: 1:43~rc-1ubuntu2

What I Expected: Changing the style in settings will affect all the
apps that support changing light/dark mode. The shell theme will also
respond to the change.

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

[Desktop-packages] [Bug 1989403] Re: g-c-c translation handling broken due to missing dh_translations override

Our best practice is to have a long list of "remaining changes" when we
merge from Debian which can act as a checklist of changes, but this list
doesn't currently exist for gnome-control-center.

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

Title:
  g-c-c translation handling broken due to missing dh_translations
  override

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

Bug description:
  From the latest kinetic buildlog:

 dh_translations
  dh_translations: warning: more than one meson translation domain found 
(gnome-control-center-2.0,gnome-control-center-2.0-timezones), don't know which 
one to use

  Previously d/rules included this override:

  override_dh_translations:
dh_translations --domain=gnome-control-center-2.0

  Somehow it seems to have been dropped, though. Maybe, to reduce the
  risk it gets unintentionally dropped again, it should be added to the
  debian/master branch instead of the ubuntu/master ditto?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1989403/+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 1195338] Re: cr build ugliness: shlibdeps

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  cr build ugliness: shlibdeps

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  dh_shlibdeps -pchromium-browser
  dpkg-shlibdeps: warning: couldn't find library libbase.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libffmpeg.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libwebkit.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libTestRunner.so (ELF 
format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libskia.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libsurface.so (ELF 
format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libui.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libsurface.so (ELF 
format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libbase.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libdbus.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libprotobuf_lite.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libdbus.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libbase.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libbase_i18n.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libgoogleurl.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libcrcrypto.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libnet.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libsql.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libprotobuf_lite.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libcrssl.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libbase.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libwebkit_base.so (ELF 
format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libgoogleurl.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libwebkit_base.so (ELF 
format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libwebkit.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libwebkit_base.so (ELF 
format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libbase_i18n.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libglue.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libgoogleurl.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libglue.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libmedia.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libglue.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libgoogleurl.so needed by 
debian/chromium-browser/usr/lib/chromium-browser/libs/libnet.so (ELF format: 
'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
  dpkg-shlibdeps: warning: couldn't find library libcrcrypto.so needed by 
debian/chromiu

[Desktop-packages] [Bug 1308250] Re: chromium window creeps upward under unity bar

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  chromium window creeps upward under unity bar

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  In chromium 34, the window can be initially placed so the window bar
  is obscured by the top unity bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1308250/+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 1989366] Re: Weird form for current app in gnome

2022-09-13 Thread Jonas Knauber

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

Ok, thanks

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

Title:
  Weird form for current app in gnome

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Sometimes, the grey surface around the application being used in gnome
  have not the expected round-square form but a weird squared form, as
  if 4 squares had merged together. I use Xorg and the NVIDIA
  proprietary driver (515.65.01).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_15_0_43_46_generic_89 nvidia_modeset 
nvidia zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 12 18:01:59 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-09-05 (6 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989366/+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 124406] Re: Keyboard keys get stuck and repeat

2022-09-13 Thread Timo Denissen

Still happens on Ubuntu 20.04 with a Lenovo ThinkPad L14 Gen 2 (and the
proposed OEM kernel). Workaround/fix for the issue is plugging in a USB
keyboard. After that the issue is gone and the external keyboard can be
unplugged again,

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

Title:
  Keyboard keys get stuck and repeat

Status in GNU Emacs:
  Invalid
Status in Linux:
  Confirmed
Status in X.Org X server:
  In Progress
Status in linux package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  Won't Fix
Status in linux source package in Jaunty:
  Won't Fix
Status in xorg-server source package in Jaunty:
  Invalid
Status in Gentoo Linux:
  New

Bug description:
  Keyboard keys such as the arrows, Alt-F4, PageUp/PageDown, etc. often
  get 'stuck' and continue being 'clicked' even after they are
  physically released. For example when clicking Alt-F4, sometimes it
  gets stuck so all the windows are closed instead of just one.

  My configuration is Feisty + Xgl + Compiz Fusion. My previous
  configuration was Edgy + Xgl + Beryl, where this didn't happen. Others
  have reported the same problem without using either Xgl or Compiz.

  The keyboard itself isn't the problem. When dual-booting to Windows,
  everything works fine. Also, the problem happens with two different
  keyboards (internal laptop, external USB).

  My best guess is that the problem occurs at time of high system load.
  Somehow during these times the key-release signal gets lost and the
  key-press is repeated indefinitely. This happens more often with
  Compiz configurations because Compiz tends to increase system load. It
  also happens more often with power-hungry apps like Firefox and
  Acrobat Reader for similar reasons.

  PS: When the keys would repeat all input devices would be locked up.
  ie. mouse won't move, clicks don't do anything, keyboard presses don't
  register. Then when it becomes unstuck, the mouse moves around and
  everything. Hope this helps.

  See also this forum thread for other people with the same problem:
  http://ubuntuforums.org/showthread.php?t=432057

To manage notifications about this bug go to:
https://bugs.launchpad.net/emacs/+bug/124406/+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 1989403] Re: g-c-c translation handling broken due to missing dh_translations override

2022-09-13 Thread Gunnar Hjalmarsson

** Changed in: ubuntu-translations
   Status: New => Fix Released

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

Title:
  g-c-c translation handling broken due to missing dh_translations
  override

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

Bug description:
  From the latest kinetic buildlog:

 dh_translations
  dh_translations: warning: more than one meson translation domain found 
(gnome-control-center-2.0,gnome-control-center-2.0-timezones), don't know which 
one to use

  Previously d/rules included this override:

  override_dh_translations:
dh_translations --domain=gnome-control-center-2.0

  Somehow it seems to have been dropped, though. Maybe, to reduce the
  risk it gets unintentionally dropped again, it should be added to the
  debian/master branch instead of the ubuntu/master ditto?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1989403/+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 1989403] Re: g-c-c translation handling broken due to missing dh_translations override

2022-09-13 Thread Launchpad Bug Tracker

This bug was fixed in the package gnome-control-center -
1:43~rc-1ubuntu2

---
gnome-control-center (1:43~rc-1ubuntu2) kinetic; urgency=medium

  * debian/rules:
- restore the dh_translations override which was forgotten during one
  of the recent merge, it's still needed (lp: #1989403)

 -- Sebastien Bacher   Tue, 13 Sep 2022 12:10:16
+0200

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  g-c-c translation handling broken due to missing dh_translations
  override

Status in Ubuntu Translations:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  From the latest kinetic buildlog:

 dh_translations
  dh_translations: warning: more than one meson translation domain found 
(gnome-control-center-2.0,gnome-control-center-2.0-timezones), don't know which 
one to use

  Previously d/rules included this override:

  override_dh_translations:
dh_translations --domain=gnome-control-center-2.0

  Somehow it seems to have been dropped, though. Maybe, to reduce the
  risk it gets unintentionally dropped again, it should be added to the
  debian/master branch instead of the ubuntu/master ditto?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1989403/+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 1989455] [NEW] [snap] No keyring for Chromium in Seahorse

Public bug reported:

The password storage test[1] says

> Open seahorse (the default system keyring application), and under the
Connexion keyring verify that there's an entry called "Chromium Safe
Storage".

I reproduce it in the .deb package, but fail to be reproduce it in the
snap, even though password storage still works.

[1]: https://wiki.ubuntu.com/Process/Merges/TestPlans/chromium

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: Triaged


** Tags: snap

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

Title:
  [snap] No keyring for Chromium in Seahorse

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  The password storage test[1] says

  > Open seahorse (the default system keyring application), and under
  the Connexion keyring verify that there's an entry called "Chromium
  Safe Storage".

  I reproduce it in the .deb package, but fail to be reproduce it in the
  snap, even though password storage still works.

  [1]: https://wiki.ubuntu.com/Process/Merges/TestPlans/chromium

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989455/+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 1965123] Re: Active launchers area pixels (corners) missing

2022-09-13 Thread Ivan Wolf

The problem also occurs for me on laptop with Intel Graphics. I use the
dark theme.


** Attachment added: "BdSZUtI.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965123/+attachment/5615491/+files/BdSZUtI.png

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

Title:
  Active launchers area pixels (corners) missing

Status in Dash to dock:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 development branch @ 16/03/2022

  after yesterdays updates to gnome 42 beta

  the docks area around the active launcher is missing 4 pixels in the corners
  when hovering mouse over them

  switching to another active launchers can be reproduced

  non-active area around launchers does not suffer this bug

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 16 12:55:20 2022
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1965123/+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 1989403] Re: g-c-c translation handling broken due to missing dh_translations override

and I've also added it to the Debian git branch now

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

Title:
  g-c-c translation handling broken due to missing dh_translations
  override

Status in Ubuntu Translations:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  From the latest kinetic buildlog:

 dh_translations
  dh_translations: warning: more than one meson translation domain found 
(gnome-control-center-2.0,gnome-control-center-2.0-timezones), don't know which 
one to use

  Previously d/rules included this override:

  override_dh_translations:
dh_translations --domain=gnome-control-center-2.0

  Somehow it seems to have been dropped, though. Maybe, to reduce the
  risk it gets unintentionally dropped again, it should be added to the
  debian/master branch instead of the ubuntu/master ditto?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1989403/+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 1989403] Re: g-c-c translation handling broken due to missing dh_translations override

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

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

Title:
  g-c-c translation handling broken due to missing dh_translations
  override

Status in Ubuntu Translations:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  From the latest kinetic buildlog:

 dh_translations
  dh_translations: warning: more than one meson translation domain found 
(gnome-control-center-2.0,gnome-control-center-2.0-timezones), don't know which 
one to use

  Previously d/rules included this override:

  override_dh_translations:
dh_translations --domain=gnome-control-center-2.0

  Somehow it seems to have been dropped, though. Maybe, to reduce the
  risk it gets unintentionally dropped again, it should be added to the
  debian/master branch instead of the ubuntu/master ditto?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1989403/+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 1738774] Re: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display

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

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

Title:
  Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display

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

Bug description:
  LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled
  icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360.

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

2022-09-13 Thread Quikee

(In reply to V Stuart Foote from comment #50)
> (In reply to bugzilla2 from comment #49)
> 
> So guess we would add additional bracketing for a 25% increment in scale
> factoring.  Like this maybe:
> 
>  nDPI > 264
>  300 (so 3.0x)
>  nDPI > 240
>  275 (so 2.75x)
>  nDPI > 216
>  250 (so 2.5x)
>  nDPI > 192
>  225 (so 2.25x)
>  nDPI > 168
>  200 (so 2.0x)
>  nDPI > 144
>  175 (so 1.75x)
>  nDPI > 120
>  150 (so 1.5x)
> otherwise 
>  100 (or unscaled and using the prebuilt PNG)
> 
> @Tomaž -- what do you think. Looks easy hackable, but will the current SVG
> to PNG resampling suffice to generate usable icon themes at the 25%
> increments? And any other places in the UI that 25% increments would cause
> problems?

SVG icons shouldn't be a problem - if they are rendered properly.

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

Title:
  Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display

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

Bug description:
  LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled
  icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360.

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

2022-09-13 Thread Renato S. Yamane

Just to remember this bug was happening also at 100% scale as you can
see on the Ckmment below with an screenshot:

https://bugs.documentfoundation.org/show_bug.cgi?id=117158#c4

I cannot test anymore, because I switched back to MS Office.

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

Title:
  Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display

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

Bug description:
  LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled
  icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360.

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

2022-09-13 Thread Vstuart-foote

(In reply to bugzilla2 from comment #49)

So guess we would add additional bracketing for a 25% increment in scale
factoring.  Like this maybe:

 nDPI > 264
 300 (so 3.0x)
 nDPI > 240
 275 (so 2.75x)
 nDPI > 216
 250 (so 2.5x)
 nDPI > 192
 225 (so 2.25x)
 nDPI > 168
 200 (so 2.0x)
 nDPI > 144
 175 (so 1.75x)
 nDPI > 120
 150 (so 1.5x)
otherwise 
 100 (or unscaled and using the prebuilt PNG)

@Tomaž -- what do you think. Looks easy hackable, but will the current
SVG to PNG resampling suffice to generate usable icon themes at the 25%
increments? And any other places in the UI that 25% increments would
cause problems?

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

Title:
  Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display

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

Bug description:
  LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled
  icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360.

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

2022-09-13 Thread Vstuart-foote

(In reply to Renato S. Yamane from comment #51)
> Just to remember this bug was happening also at 100% scale as you can see on
> the Ckmment below with an screenshot:
> 
> https://bugs.documentfoundation.org/show_bug.cgi?id=117158#c4
> 
> I cannot test anymore, because I switched back to MS Office.

That was never confirmed and in the screen clips provided the LO icons
are clearly not 100% or 150% of the native FHD mode--they've been scaled
poorly.

The Yoga L380 in use does have a native screen DPI of ~165dpi, so
believe it does scale the PNG icons to a higher scale--look in
%APPDATA%\LibreOffice\4\cache\Colibre and if 150 shows the PNG rasters
were scaled larger (with the pixilation noted).

To avoid similar on HiDPI displays close to this resolution, *simply*
make a selection of an SVG based icon theme. Do not use the default PNG
based icon theme.

Anyhow, the set of pre-installed non-SVG icon themes render cleanly from
100 to 150 pct scaling, starting to pixelate above 150 pct. If on a
HiDPI display, or working at higher scaling 150 - 300% first use Tools
-> Options -> View and switch to the bundled SVG icon sets which will
then be resampled into clean PNG sized as needed.

A useful enhancement at this point might be to detect and switch from
the PNG icon themes to SVG theme when at a higher scaling factor is in
use--i.e. avoid scaling the PNG.

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

Title:
  Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display

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

Bug description:
  LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled
  icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360.

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

2022-09-13 Thread Bugzilla2-r

Thanks for the explanation :)

That sounds not so bad, but LibO really should offer the same "steps" as
the Host-OS (in my case Windows) does, that means 25% steps, not only
50% steps on Windows. Otherwise the Icons look to small or to big on
175% Scale for example. And not only the Icons itself, also the spaces
between them (other bugs show that problem).

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

Title:
  Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display

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

Bug description:
  LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled
  icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+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 1970459] Re: import of ca-certificate in browser does not work

2022-09-13 Thread Edward Karavakis

How is this not a bug? A crippled version of firefox is being offered by
default without the xdg-desktop-portal-gnome package... I too had to
install in a fresh ubuntu 22.04 installation my institute's Root
Certification Authority Certificate (CERN) and my grid certificate.

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

Title:
  import of ca-certificate in browser does not work

Status in chromium-browser package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  I tried to import a CA root certificate into both Firefox and Chrome.
  In Firefox, the import button just didn't do anything, in Chrome
  pressing "import" hangs up the browser. This means I can't reach the
  intranet of the company I work for.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ca-certificates 20211016
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:16:12 2022
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ca-certificates
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970459/+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 1989434] [NEW] poppler 0.62.0-2ubuntu2.13 breaks GDAL compilation

2022-09-13 Thread Even Rouault

Public bug reported:

The security update poppler 0.62.0-2ubuntu2.13 that fixes CVE-2022-38784 adds a 
new header file goo/GooCheckedOps.h that is included by goo/gmem.h
goo/gmem.h is a file installed in the libpoppler-private-dev package, which is 
used by GDAL, but the patches added in the 0.62.0-2ubuntu2.13 update omit 
installing goo/GooCheckedOps.h, consequently any external code including 
goo/gmem.h breaks at compilation

The following extra patch should fix this:
```
$ diff -u CMakeLists.txt.ori CMakeLists.txt
--- CMakeLists.txt.ori  2022-09-13 10:58:42.282712260 +0200
+++ CMakeLists.txt  2022-09-13 10:58:44.198709344 +0200
@@ -578,6 +578,7 @@
 goo/GooString.h
 goo/gtypes.h
 goo/gmem.h
+goo/GooCheckedOps.h
 goo/gfile.h
 goo/FixedPoint.h
 goo/ImgWriter.h
```

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

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

Title:
  poppler 0.62.0-2ubuntu2.13  breaks GDAL compilation

Status in poppler package in Ubuntu:
  New

Bug description:
  The security update poppler 0.62.0-2ubuntu2.13 that fixes CVE-2022-38784 adds 
a new header file goo/GooCheckedOps.h that is included by goo/gmem.h
  goo/gmem.h is a file installed in the libpoppler-private-dev package, which 
is used by GDAL, but the patches added in the 0.62.0-2ubuntu2.13 update omit 
installing goo/GooCheckedOps.h, consequently any external code including 
goo/gmem.h breaks at compilation

  The following extra patch should fix this:
  ```
  $ diff -u CMakeLists.txt.ori CMakeLists.txt
  --- CMakeLists.txt.ori2022-09-13 10:58:42.282712260 +0200
  +++ CMakeLists.txt2022-09-13 10:58:44.198709344 +0200
  @@ -578,6 +578,7 @@
   goo/GooString.h
   goo/gtypes.h
   goo/gmem.h
  +goo/GooCheckedOps.h
   goo/gfile.h
   goo/FixedPoint.h
   goo/ImgWriter.h
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989434/+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 1892559] Re: [MIR] ccid opensc pcsc-lite

2022-09-13 Thread Steve Beattie

** Changed in: ccid (Ubuntu)
 Assignee: Ray Veldkamp (rayveldkamp) => Ubuntu Security Team 
(ubuntu-security)

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

Title:
  [MIR] ccid opensc pcsc-lite

Status in ccid package in Ubuntu:
  In Progress
Status in opensc package in Ubuntu:
  Incomplete
Status in pam-pkcs11 package in Ubuntu:
  Invalid
Status in pcsc-lite package in Ubuntu:
  New
Status in pcsc-perl package in Ubuntu:
  Invalid
Status in pcsc-tools package in Ubuntu:
  Invalid

Bug description:
  ==> ccid <==
  [Availability]
  ccid is in universe, and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs for ccid are listed in our database.
  Doesn't appear to bind to a socket.
  No privileged executables, but does have udev rules.
  Probably needs a security review.

  [Quality assurance]
  No test suite.
  Does require odd hardware that we'll probably need to buy.
  I don't see debconf questions.
  ccid is well maintained in Debian by upstream author.
  One open wishlist bug in BTS, harmless.

  One open bug in launchpad, not security, but looks very frustrating
  for the users. The upstream author was engaged but it never reached
  resolution.  https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465

  Has a debian/watch file.
  Quilt packaging.

  P: ccid source: no-dep5-copyright
  P: ccid source: package-uses-experimental-debhelper-compat-version 13

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  ccid provides drivers to interact with usb-connected smart card readers.

  ==> libpam-pkcs11 <==
  [Availability]
  Source package pam-pkcs11 is in universe and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs in our database.
  Doesn't appear to bind to sockets.
  No privileged executables (but is a PAM module).
  As a PAM module this will require a security review.

  [Quality assurance]
  The package does not call pam-auth-update in its postinst #1650366
  Does not ask questions during install.
  One Ubuntu bug claims very poor behaviour if a card isn't plugged in.
  No Debian bugs.
  Occasional updates in Debian by long-term maintainer.
  Does require odd hardware that we'll probably need to buy.
  Does not appear to run tests during build.
  Has scary warnings in the build logs.
  Has a debian/watch file.

  Ancient standards version; other smaller lintian messages, mostly
  documentation problems.

  Quilt packaging.

  [Dependencies]
  Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1
  All are in main.

  [Standards compliance]
  The package does not call pam-auth-update in its postinst #1650366
  Otherwise looks to conform to FHS and Debian policies

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  This PAM module can use CRLs and full-chain verification of certificates.
  It can also do LDAP, AD, and Kerberos username mapping.

  ==> libpcsc-perl <==
  [Availability]
  Source package pcsc-perl is in universe, builds for all architectures,
  plus i386

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  There are no cves for pcsc-perl in our database.
  No privileged executables.
  Doesn't appear to bind to sockets.
  Probably needs a security review.

  [Quality assurance]
  Library package not intended to be used directly.
  No debconf questions.
  No bugs in Debian.
  No bugs in Ubuntu.
  Does require odd hardware that we'll probably need to buy.
  Tests exist, not run during the build; probably can't run during the build.
  Includes debian/watch file.
  A handful of lintian issues
  Quilt packaging.

  [Dependencies]
  libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0.
  All are in main.

  [Standards compliance]
  One oddity, Card.pod is stored in 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/
  Many other perl packages have .pod files in these directory trees so maybe
  it's fine, but it seems funny all the same.

  Otherwise appears to satisfy FHS and Debian policy.

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  D

[Desktop-packages] [Bug 1868332] Re: Scrolling jumps after switching windows

2022-09-13 Thread Alon Diamant

I am in the exact same situation as Gedvan.

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

Title:
  Scrolling jumps after switching windows

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The bug has to do with mouse scrolling and switching windows; I do not
  know which package it is part of.

  The problem arises when I have two windows of two different
  applications open, such as Google Chrome and a text editor. To
  reproduce the error, I have Google Chrome open initially, then I
  switch tabs (using the shortcut Alt-Tab) to the text editor, then
  scroll around on the text editor. When I Alt-Tab back to Google
  Chrome, my first scroll leads to the page jumping by a large amount
  either up or down before resuming regular mouse scrolling. It is only
  this initial scroll after switching tabs that jumps like this. It also
  happens regardless of whether I use a mouse or the touch pad.

  I also notice, given the same scenario, if I scroll up on the text
  editor, the Google Chrome initial scroll jump will be upward. If I
  scroll down on the text editor, the Chrome jump will be downward. If I
  scroll a lot in the text editor, the Chrome jump will be large. If I
  scroll a small amount in the text editor, the Chrome jump will be
  small.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 17:17:39 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b9]
  InstallationDate: Installed on 2020-01-26 (54 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=7cfa547e-7b38-4467-9a1c-5f581ce738c1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.24:bd01/07/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 1WU65AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1868332/+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 1989418] Re: [BPO] libreoffice 7.3.6 for focal

2022-09-13 Thread Rico Tzschichholz

** Attachment added: "libreoffice_7.3.6-0ubuntu0.22.04.1_bpo20.04.1"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1989418/+attachment/5615444/+files/libreoffice_7.3.6-0ubuntu0.22.04.1_bpo20.04.1

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

Title:
   [BPO] libreoffice 7.3.6 for focal

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

Bug description:
  [Impact]

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

   * This source packages matches the proposed SRU for jammy handled at
   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744
     and its backport is currently provided by the LibreOffice Fresh PPA at
   https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages

   * Previous backport of 7.3.5 handled at
   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987045

   * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in 
focal.
   * LibreOffice 7.3.5 is currently released in focal-backports.

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

  [Scope]

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

   * Backport target is Focal/20.04 LTS only to provide an official
  build of a more recent upstream version of LibreOffice

  [Testing]

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

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

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

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/amd64/libr/libreoffice/20220904_103401_f46f5@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/arm64/libr/libreoffice/20220904_144020_84b5b@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/armhf/libr/libreoffice/20220904_113245_95845@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/ppc64el/libr/libreoffice/20220904_100953_3af7d@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/s390x/libr/libreoffice/20220904_095636_d0c69@/log.gz

   * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented
  by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1989418/+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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)

2022-09-13 Thread Alberto Mardegan

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

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

Title:
  libreoffice help doesn't open in firefox (404 error on
  file:///tmp/lu417531j7po.tmp/NewHelp0.html)

Status in libreoffice package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Committed
Status in libreoffice source package in Jammy:
  Fix Released
Status in snapd source package in Jammy:
  Confirmed

Bug description:
  Ubuntu jammy live QA-test on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  Opened LibreOffice Writer as random apps in QA-test.
  Hit F1 to call help, and all I get is an error

  URL:  file:///tmp/lu417531j7po.tmp/NewHelp0.html

  ---
  File not found

  Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html.

  Check the file name for capitalization or other typing errors.
  Check to see if the file was moved, renamed or deleted.
  ---

  Firefox opens as a snap; but it isn't accessing the data from
  LibreOffice.

  Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks-
  libreoffice-deb/27537

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465+canary3.3
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 17 04:46:33 2021
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+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 1989325] Re: gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1

2022-09-13 Thread maarten

I'm sorry, but have spend lots of time working around this bug and need
to focus on this weird phenomenon called work first, but will try to
reproduce as soon as I have time

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

Title:
  gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I upgrade to Ubuntu 22.04 recently, and while upgrading and updating I
  also got a new bios version (1.69) for my Lenovo Thinkpad P50 laptop.
  Since then gnome-shell has been very unstable, crashing regularly on
  minor changes, like plugging in a monitor or going to suspend mode.

  Update: I just found out that the bug is not reproducable when logged
  in with Xorg instead of Wayland
  (https://askubuntu.com/questions/1428898/lenovo-p50-crashes-gnome-
  shell-regularly-after-upgrade-to-ubuntu-22-04-1-using)

  So we got a workaround and a culprit: Wayland ... in conjunction with
  something quite typical for my hardware maybe(?), Lenovo Thinkpad P50
  (20ENCTO1WW) with Quadro M2000M discrete graphics ...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 12 09:49:57 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-09-09 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-09-09 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989325/+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 1989418] [NEW] [BPO] libreoffice 7.3.6 for focal

2022-09-13 Thread Rico Tzschichholz

Public bug reported:

[Impact]

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

 * This source packages matches the proposed SRU for jammy handled at
 https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744
   and its backport is currently provided by the LibreOffice Fresh PPA at
 https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages

 * Previous backport of 7.3.5 handled at
 https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987045

 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in 
focal.
 * LibreOffice 7.3.5 is currently released in focal-backports.

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

[Scope]

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

 * Backport target is Focal/20.04 LTS only to provide an official build
of a more recent upstream version of LibreOffice

[Testing]

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

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

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

 * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
* [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/amd64/libr/libreoffice/20220904_103401_f46f5@/log.gz
* [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/arm64/libr/libreoffice/20220904_144020_84b5b@/log.gz
* [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/armhf/libr/libreoffice/20220904_113245_95845@/log.gz
* [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/ppc64el/libr/libreoffice/20220904_100953_3af7d@/log.gz
* [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/s390x/libr/libreoffice/20220904_095636_d0c69@/log.gz

 * General smoke testing of all the applications in the office suite
were carried out by going through the manual testplan as documented by:
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

[Regression Potential]

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

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

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

** Affects: libreoffice (Ubuntu Focal)
 Importance: High
 Assignee: Rico Tzschichholz (ricotz)
 Status: In Progress

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

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

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

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

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

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

Title:
   [BPO] libreoffice 7.3.6 for focal

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

Bug description:
  [Impact]

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

   * This source packages matches the proposed SRU for jammy handled at
   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744
     and its backport is currently provided by the LibreOffice Fresh PPA at
   https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages

   * Previous backport of 7.3.5 handled at
   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987045

[Desktop-packages] [Bug 1988230] Re: glib 2.73 breaks modemmanager