date:20220518

** No longer affects: mutter (Ubuntu)

** Changed in: mesa-demos (Ubuntu)
   Status: Confirmed => Fix Committed

** Tags added: fixed-in-8.5.0 fixed-upstream

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

Title:
  es2gears_wayland on mutter sticks to 119 FPS on a 59.95Hz display

Status in Mesa:
  Fix Released
Status in mesa-demos package in Ubuntu:
  Fix Committed

Bug description:
  es2gears_wayland sticks to 119 FPS on a 59.95Hz display

  $ es2gears_wayland
  EGL_VERSION = 1.4 (DRI2)
  vertex shader info:
  fragment shader info:
  info:
  597 frames in 5.0 seconds = 119.138 FPS
  600 frames in 5.0 seconds = 119.880 FPS
  598 frames in 5.0 seconds = 119.481 FPS
  600 frames in 5.0 seconds = 119.952 FPS
  600 frames in 5.0 seconds = 119.880 FPS
  600 frames in 5.0 seconds = 119.880 FPS
  596 frames in 5.0 seconds = 119.105 FPS

  $ es2gears_x11
  EGL_VERSION = 1.4 (DRI2)
  vertex shader info:
  fragment shader info:
  info:
  315 frames in 5.0 seconds = 62.837 FPS
  300 frames in 5.0 seconds = 60.000 FPS
  300 frames in 5.0 seconds = 60.000 FPS
  300 frames in 5.0 seconds = 60.000 FPS
  300 frames in 5.0 seconds = 60.000 FPS
  301 frames in 5.0 seconds = 60.008 FPS

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mesa-utils-extra 8.4.0-1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Mar  6 16:39:18 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3 Processor Integrated Graphics Controller 
[8086:041a] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Xeon E3-1200 v3 Processor Integrated Graphics Controller 
[17aa:30a1]
  InstallationDate: Installed on 2017-12-12 (84 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  MachineType: LENOVO 30AJS05700
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=f9fe7460-9c41-4d4a-8376-e5ceb57bbec8 ro quiet splash vt.handoff=1
  SourcePackage: mesa-demos
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTB6AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50519 PRO
  dmi.chassis.type: 7
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 30AJS05700
  dmi.product.version: ThinkStation P300
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1753677/+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 1947836] Re: nvidia-340 cannot be installed on F-Intel-5.13

2022-05-18 Thread Po-Hsu Lin

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  nvidia-340 cannot be installed on F-Intel-5.13

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix

Bug description:
  Issue found on 5.13.0-1007-intel with ADT testing.

  It looks like this package installation will fail with kernel version parsing:
  Setting up gir1.2-geoclue-2.0:amd64 (2.5.6-0ubuntu1) ...
  Setting up xserver-xorg-video-vesa (1:2.4.0-2) ...
  Setting up nvidia-340 (340.108-0ubuntu5.20.04.2) ...
  dpkg: error: version '-' has bad syntax: revision number is empty
  dpkg: error: version '-' has bad syntax: revision number is empty
  update-initramfs: deferring update (trigger activated)
  Adding system user `nvidia-persistenced' (UID 121) ...

  nvidia-390 and newer drivers can be installed without any problem.

  Not sure if we ever care about this old driver on this kernel for IoT
  devices, filed a bug here in case we forgot about this.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu5.20.04.2
  ProcVersionSignature: User Name 5.13.0-1007.7-intel 5.13.14
  Uname: Linux 5.13.0-1007-intel x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Oct 20 06:37:26 2021
  SourcePackage: nvidia-graphics-drivers-340
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1947836/+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 1973226] Re: UI doesn't allow setting Left Ctrl as Compose

2022-05-18 Thread Kevin Bullock

Thanks for the reply! Reported upstream here:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1860

And patch submitted here: https://gitlab.gnome.org/GNOME/gnome-control-
center/-/merge_requests/1328

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1860
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1860

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

Title:
  UI doesn't allow setting Left Ctrl as Compose

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

Bug description:
  In Ubuntu 20.04, I was able to set Left Ctrl as my Compose key using
  gnome-tweaks. I just upgraded to 22.04, where the Compose key settings
  have been removed from gnome-tweaks and moved into control-center, but
  Left Ctrl is not in the list of options for Compose.

  I was able to restore Left Ctrl as my Compose key using:

  $ gsettings set org.gnome.desktop.input-sources xkb-options ...

  adding 'compose:lctrl' to that list, but it would be nice to expose it
  in the GUI.

  For context, my modifier settings are:

  * Caps Lock is Ctrl ('ctrl:nocaps')
  * Left Ctrl is Compose ('compose:lctrl')
  * Both Shift keys enable/disable Caps Lock ('shift:both_capslock')

  which gives me both a Ctrl key on both sides of the keyboard and an
  easily-accessible Compose key.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1973226/+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 1973802] Re: Gnome Shell crashes when disconnecting external monitor

Sounds like you forgot to pass the crash file as a parameter to 'apport-
cli'?

As mentioned in the instructions, please don't attach crash files to bug 
reports:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

Title:
  Gnome Shell crashes when disconnecting external monitor

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04, gnome-shell 42.0-2ubuntu1

  When unplugging an external monitor connected via USB-C to my Thinkpad
  P14s, the entire UI session crashes. While the external monitor is
  plugged in, it is configured as the primary display. Here are the
  gnome-shell logs of the latest incident, I suppose the relevant part
  is `assertion 'window->stack_position >= 0' failed`.

  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212959: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212959 does not exist.
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212963: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212963 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212964: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212964 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212965: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212965 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212966: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212966 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212967: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212967 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 31 with keysym 31 (keycode a).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 32 with keysym 32 (keycode b).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 33 with keysym 33 (keycode c).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 38 with keysym 38 (keycode 11).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting

[Desktop-packages] [Bug 1974103] Re: dock alters the alignment of date and time on top gnome bar as well as the desktop icons positions

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1884392, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1884392
Clock does not remain in center when auto-hide the dock setting is disabled
from gnome settings

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

Title:
dock alters the alignment of date and time on top gnome bar as well as
the desktop icons positions

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

Bug description:
the alignment becomes correct under following circumstances

1. the dock is turned off
2. its set to autohide
3. its set in the bottom

also alters alignment when icon size is changed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1974103/+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 1974018] Re: UBSAN: invalid-load in /build/linux-WD899k/linux-5.15.0/net/mac80211/status.c:1164:21

** Summary changed:

- dmesg
+ UBSAN: invalid-load in 
/build/linux-WD899k/linux-5.15.0/net/mac80211/status.c:1164:21

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

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

Title:
  UBSAN: invalid-load in /build/linux-
  WD899k/linux-5.15.0/net/mac80211/status.c:1164:21

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:Ubuntu 22.04 LTS
  Release:22.04

  [   29.170087] 

  [   29.170097] UBSAN: invalid-load in 
/build/linux-WD899k/linux-5.15.0/net/mac80211/status.c:1164:21
  [   29.170102] load of value 255 is not a valid value for type '_Bool'
  [   29.170105] CPU: 3 PID: 549 Comm: in:imuxsock Tainted: P   OE 
5.15.0-30-generic #31-Ubuntu
  [   29.170110] Hardware name: ASUSTeK COMPUTER INC. X550CL/X550CL, BIOS 
X550CL.204 10/17/2013
  [   29.170113] Call Trace:
  [   29.170116]  
  [   29.170119]  show_stack+0x52/0x58
  [   29.170128]  dump_stack_lvl+0x4a/0x5f
  [   29.170136]  dump_stack+0x10/0x12
  [   29.170140]  ubsan_epilogue+0x9/0x45
  [   29.170144]  __ubsan_handle_load_invalid_value.cold+0x44/0x49
  [   29.170149]  ieee80211_tx_status_ext.cold+0x4e/0x5f [mac80211]
  [   29.170251]  ieee80211_tx_status+0x72/0xa0 [mac80211]
  [   29.170320]  ath_txq_unlock_complete+0x12d/0x160 [ath9k]
  [   29.170336]  ath_tx_edma_tasklet+0xef/0x4c0 [ath9k]
  [   29.170349]  ? del_timer_sync+0x6c/0xb0
  [   29.170355]  ath9k_tasklet+0x14e/0x290 [ath9k]
  [   29.170367]  tasklet_action_common.constprop.0+0xc0/0xf0
  [   29.170373]  tasklet_action+0x22/0x30
  [   29.170378]  __do_softirq+0xd9/0x2e3
  [   29.170385]  irq_exit_rcu+0x8c/0xb0
  [   29.170389]  common_interrupt+0x8a/0xa0
  [   29.170396]  
  [   29.170398]  
  [   29.170400]  asm_common_interrupt+0x1e/0x40
  [   29.170404] RIP: 0010:copy_user_generic_unrolled+0x89/0xc0
  [   29.170411] Code: 38 4c 89 47 20 4c 89 4f 28 4c 89 57 30 4c 89 5f 38 48 8d 
76 40 48 8d 7f 40 ff c9 75 b6 89 d1 83 e2 07 c1 e9 03 74 12 4c 8b 06 <4c> 89 07 
48 8d 76 08 48 8d 7f 08 ff c9 75 ee 21 d2 74 10 89 d1 8a
  [   29.170414] RSP: 0018:ae00c0b83c10 EFLAGS: 0202
  [   29.170419] RAX: 7f4885d52298 RBX: ae00c0b83c40 RCX: 
0007
  [   29.170422] RDX:  RSI: 7f4885d52260 RDI: 
ae00c0b83c40
  [   29.170424] RBP: ae00c0b83c30 R08:  R09: 
9a32e177e418
  [   29.170427] R10:  R11:  R12: 
0038
  [   29.170429] R13: ae00c0b83cd8 R14: ae00c0b83ce0 R15: 
0040
  [   29.170434]  ? _copy_from_user+0x2e/0x60
  [   29.170440]  __copy_msghdr_from_user+0x3d/0x130
  [   29.170446]  ___sys_recvmsg+0x68/0x110
  [   29.170450]  ? check_preempt_curr+0x5d/0x70
  [   29.170455]  ? ttwu_do_wakeup+0x1c/0x160
  [   29.170460]  ? rseq_get_rseq_cs.isra.0+0x1b/0x220
  [   29.170466]  ? ttwu_do_activate+0x72/0xf0
  [   29.170470]  ? __fget_files+0x86/0xc0
  [   29.170476]  ? __fget_light+0x32/0x80
  [   29.170481]  __sys_recvmsg+0x5f/0xb0
  [   29.170485]  ? switch_fpu_return+0x4e/0xc0
  [   29.170491]  ? exit_to_user_mode_prepare+0x92/0xb0
  [   29.170496]  ? syscall_exit_to_user_mode+0x27/0x50
  [   29.170501]  __x64_sys_recvmsg+0x1d/0x20
  [   29.170505]  do_syscall_64+0x5c/0xc0
  [   29.170510]  ? __x64_sys_futex+0x78/0x1e0
  [   29.170515]  ? exit_to_user_mode_prepare+0x37/0xb0
  [   29.170520]  ? syscall_exit_to_user_mode+0x27/0x50
  [   29.170524]  ? do_syscall_64+0x69/0xc0
  [   29.170528]  ? do_syscall_64+0x69/0xc0
  [   29.170533]  ? do_syscall_64+0x69/0xc0
  [   29.170537]  ? do_syscall_64+0x69/0xc0
  [   29.170541]  ? asm_common_interrupt+0x8/0x40
  [   29.170546]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   29.170550] RIP: 0033:0x7f48864179ef
  [   29.170554] Code: 44 00 00 89 54 24 0c 48 89 34 24 89 7c 24 08 e8 97 90 f6 
ff 8b 54 24 0c 48 8b 34 24 41 89 c0 8b 7c 24 08 b8 2f 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 31 4c 63 e0 44 89 c7 e8 de 90 f6 ff 48 83 c4
  [   29.170557] RSP: 002b:7f4885d52140 EFLAGS: 0293 ORIG_RAX: 
002f
  [   29.170561] RAX: ffda RBX:  RCX: 
7f48864179ef
  [   29.170564] RDX: 0040 RSI: 7f4885d52260 RDI: 
0003
  [   29.170566] RBP:  R08:  R09: 
7f4878000bb0
  [   29.170568] R10: 7f4878002b50 R11: 0293 R12: 
55d6ce037580
  [   29.170570] R13: 55d6cc64e4cc R14: 1fa0 R15: 
7f4878000bb0
  [   29.170575]  
  [   29.170585] 


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64

[Desktop-packages] [Bug 1974074] Bug is not a security issue

2022-05-18 Thread Alex Murray

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

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

Title:
  missing symlink in /root/.config/libreoffice/4/user/config/

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  missing symlink in /root/.config/libreoffice/4/user/config/

  javasettings_Linux_*.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+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 1974054] Re: Without a reason gnome-shell CPU usage gets high

Thanks for the bug report. Please:

1. Open the Extensions app and ensure only the three Ubuntu extensions
are enabled. No others.

2. Remove any locally-installed extensions:

   cd ~/.local/share/gnome-shell/
   rm -rf extensions

   and log in again.

3. Check to see if you have anything constantly changing on the screen.
Make sure you don't have any performance indicators/graphs running, or
web browsers open, when the problem occurs.

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

** Tags added: performance

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

Title:
  Without a reason gnome-shell CPU usage gets high

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Without a reason, CPU usage for gnome-shell jumps from 4% to 22%.
  All I did this normal workflow, locking/unlocking multiple times over few 
hours and couple of suspends.

  The screenshot is showing 37% because of the screenshot tool, but idling at 
22%.
  And if I re-logged or reboot, it idles at 4% normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 18 17:24:38 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-02-03 (103 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+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 1958224] Re: brltty claiming cp210x devices on 22.04

2022-05-18 Thread Batwam

Hi Steve, would you he able to describe how the patch worked Vs current
behaviour?

If we can’t touch the package, can we remove it from standard install
(like in Debian) to minimise the number of people impacted and/or make
it incompatible with every other package which might be incompatible
with it (such as Arduino) so people get prompted to removed brltty if it
is installed - include special warning if you feel it’s needed)?

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

Title:
  brltty claiming cp210x devices on 22.04

Status in brltty package in Ubuntu:
  Fix Committed
Status in brltty source package in Jammy:
  Confirmed

Bug description:
  * Impact

  The brltty udev rules are claiming generic devices IDs which makes
  some other devices like Arduino cards not able to interact with the
  serial port anymore

  * Test Case

  Try to use an Arduino over a cp210x or FTDI serial port, it should be
  able to talk to the computer

  * Regression potential

  There are some braille devices on the market using generic IDs which
  are going to stop working out of the box. Those devices are uncommon
  and it's arguably an hardware bugs they are using those IDs.

  ---

  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy
  brltty:  Installed: 6.4-2ubuntu1

   brltty appears once again to be claiming cp210x devices with the
  vendor/product ID of:

  idVendor=10c4, idProduct=ea60

  Example dmesg output:
    999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00
  [  999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge
  [  999.215977] usb 3-6.3: Manufacturer: Silicon Labs
  [  999.215978] usb 3-6.3: SerialNumber: 0005
  [  999.234070] usbcore: registered new interface driver usbserial_generic
  [  999.234081] usbserial: USB Serial support registered for generic
  [  999.235262] usbcore: registered new interface driver cp210x
  [  999.235272] usbserial: USB Serial support registered for cp210x
  [  999.235298] cp210x 3-6.3:1.0: cp210x converter detected
  [  999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0
  [  999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41
  [  999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input42
  [  999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' 
sets config #1
  [  999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
  [  999.995066] cp210x 3-6.3:1.0: device disconnected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+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 1974103] [NEW] dock alters the alignment of date and time on top gnome bar as well as the desktop icons positions

2022-05-18 Thread TripleK

Public bug reported:

the alignment becomes correct under following circumstances

1. the dock is turned off
2. its set to autohide
3. its set in the bottom

also alters alignment when icon size is changed

** 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/1974103

Title:
  dock alters the alignment of date and time on top gnome bar as well as
  the desktop icons positions

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

Bug description:
  the alignment becomes correct under following circumstances

  1. the dock is turned off
  2. its set to autohide
  3. its set in the bottom

  also alters alignment when icon size is changed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1974103/+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 1971076] Re: webkitgtk 2.36 doesn't work with orca anymore

This bug was fixed in the package orca - 42.1-1ubuntu1

---
orca (42.1-1ubuntu1) kinetic; urgency=medium

  * Merge with Debian (LP: #1971076). Remaining changes:
+ debian/patches/unity-a11y.patch: add hacks to better work with Unity
+ Revert "control: Add xkbset dependency (Closes #972621)" This is in
  universe in Ubuntu so we can't depend on it. It's silently skipped if
  not available.

orca (42.1-1) unstable; urgency=medium

  [ Samuel Thibault ]
  * New upstream release.
  * control: Drop gnome-orca transition package, fixed since stretch.
- orca.install: drop etc and usr, already installed.

  [ Debian Janitor ]
  * Bump debhelper from old 12 to 13.
+ debian/rules: Drop --fail-missing argument to dh_missing, which is now the
  default.

 -- Jeremy Bicha   Wed, 18 May 2022 16:54:51 -0400

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

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

Title:
  webkitgtk 2.36 doesn't work with orca anymore

Status in gnome-orca:
  Unknown
Status in orca package in Ubuntu:
  Fix Released
Status in orca source package in Focal:
  Triaged
Status in orca source package in Impish:
  Triaged
Status in orca source package in Jammy:
  Triaged

Bug description:
  Since Ubuntu 22.04 I can not read the content of the yelp pages, le content 
of a mail from evolution or a web page from epiphany.
  This worked correctly for Ubuntu 21.10 or Ubuntu 20.04 LTS.
  This problem occurs if I migrate from a previous version, or if I reinstall 
from scrash.

  Is there a new setting that I don't aware of? 
  This also could be related to webkitgtk I suppose.

  A work arround is to select all the texte and to copy it to a place
  that I can read (gedit).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: orca 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Sun May  1 10:03:38 2022
  InstallationDate: Installed on 2022-04-03 (27 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: orca
  UpgradeStatus: Upgraded to jammy on 2022-04-12 (18 days ago)
  mtime.conffile..etc.xdg.autostart.orca-autostart.desktop: 
2022-04-17T10:13:33.207956

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-orca/+bug/1971076/+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 1973594] Re: [BPO] libreoffice 7.2.7 for focal

2022-05-18 Thread Rico Tzschichholz

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

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

Title:
   [BPO] libreoffice 7.2.7 for focal

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

Bug description:
  [Impact]

   * LibreOffice 7.2.7 is in its seventh (and last) bugfix release of the 7.2 
line:
   https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.7_release

   * This source packages matches the proposed SRU for impish handled at
   https://bugs.launchpad.net/ubuntu/impish/+source/libreoffice/+bug/1972155
     and its backport is currently provided by the LibreOffice Still PPA at
   
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages

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

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

   * 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.2.7-0ubuntu0.21.10.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_72/1617/

    * 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-experimental/focal/amd64/libr/libreoffice/20220518_095601_b5724@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/arm64/libr/libreoffice/20220518_133315_9e5cd@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/armhf/libr/libreoffice/20220518_135411_142bf@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/ppc64el/libr/libreoffice/20220518_143359_edb75@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/s390x/libr/libreoffice/20220518_095423_36802@/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 44+ 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/1973594/+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 1958224] Proposed package upload rejected

2022-05-18 Thread Steve Langasek

An upload of brltty to jammy-proposed has been rejected from the upload
queue for the following reason: "Would introduce a critical regression
for blind users of this hardware".

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

Title:
  brltty claiming cp210x devices on 22.04

Status in brltty package in Ubuntu:
  Fix Committed
Status in brltty source package in Jammy:
  Confirmed

Bug description:
  * Impact

  The brltty udev rules are claiming generic devices IDs which makes
  some other devices like Arduino cards not able to interact with the
  serial port anymore

  * Test Case

  Try to use an Arduino over a cp210x or FTDI serial port, it should be
  able to talk to the computer

  * Regression potential

  There are some braille devices on the market using generic IDs which
  are going to stop working out of the box. Those devices are uncommon
  and it's arguably an hardware bugs they are using those IDs.

  ---

  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy
  brltty:  Installed: 6.4-2ubuntu1

   brltty appears once again to be claiming cp210x devices with the
  vendor/product ID of:

  idVendor=10c4, idProduct=ea60

  Example dmesg output:
    999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00
  [  999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge
  [  999.215977] usb 3-6.3: Manufacturer: Silicon Labs
  [  999.215978] usb 3-6.3: SerialNumber: 0005
  [  999.234070] usbcore: registered new interface driver usbserial_generic
  [  999.234081] usbserial: USB Serial support registered for generic
  [  999.235262] usbcore: registered new interface driver cp210x
  [  999.235272] usbserial: USB Serial support registered for cp210x
  [  999.235298] cp210x 3-6.3:1.0: cp210x converter detected
  [  999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0
  [  999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41
  [  999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input42
  [  999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' 
sets config #1
  [  999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
  [  999.995066] cp210x 3-6.3:1.0: device disconnected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+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 1958224] Re: brltty claiming cp210x devices on 22.04

2022-05-18 Thread Steve Langasek

I understand the importance of fixing this conflict, and I agree it's
bad behavior on the part of the hardware manufacturer that retail
devices were shipped using these generic USB IDs, but the consequence of
the proposed SRU - disabling the use of brltty on the USB ids in
question - is that a blind user who uses one of these devices, who has
successfully installed Ubuntu and has a working system, will on the
installation of this SRU have their only accessible tty device rendered
inoperable.

That represents a CRITICAL regression for the users in question.  It
effectively bricks their machine and requires the user to rely on a
sighted person (who is also Ubuntu-knowledgeable) to get it working
again.

So I am rejecting this SRU.  It's unfortunate that this wasn't caught
before release, but now that support for this hardware is present in the
release, we can't be bricking blind users' systems to enable other
cp210x devices.  We'll need to find some other path forward.

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

Title:
  brltty claiming cp210x devices on 22.04

Status in brltty package in Ubuntu:
  Fix Committed
Status in brltty source package in Jammy:
  Confirmed

Bug description:
  * Impact

  The brltty udev rules are claiming generic devices IDs which makes
  some other devices like Arduino cards not able to interact with the
  serial port anymore

  * Test Case

  Try to use an Arduino over a cp210x or FTDI serial port, it should be
  able to talk to the computer

  * Regression potential

  There are some braille devices on the market using generic IDs which
  are going to stop working out of the box. Those devices are uncommon
  and it's arguably an hardware bugs they are using those IDs.

  ---

  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy
  brltty:  Installed: 6.4-2ubuntu1

   brltty appears once again to be claiming cp210x devices with the
  vendor/product ID of:

  idVendor=10c4, idProduct=ea60

  Example dmesg output:
    999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00
  [  999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge
  [  999.215977] usb 3-6.3: Manufacturer: Silicon Labs
  [  999.215978] usb 3-6.3: SerialNumber: 0005
  [  999.234070] usbcore: registered new interface driver usbserial_generic
  [  999.234081] usbserial: USB Serial support registered for generic
  [  999.235262] usbcore: registered new interface driver cp210x
  [  999.235272] usbserial: USB Serial support registered for cp210x
  [  999.235298] cp210x 3-6.3:1.0: cp210x converter detected
  [  999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0
  [  999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41
  [  999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input42
  [  999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' 
sets config #1
  [  999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
  [  999.995066] cp210x 3-6.3:1.0: device disconnected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+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 1958224] Re: brltty claiming cp210x devices on 22.04

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

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

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

Title:
  brltty claiming cp210x devices on 22.04

Status in brltty package in Ubuntu:
  Fix Committed
Status in brltty source package in Jammy:
  Confirmed

Bug description:
  * Impact

  The brltty udev rules are claiming generic devices IDs which makes
  some other devices like Arduino cards not able to interact with the
  serial port anymore

  * Test Case

  Try to use an Arduino over a cp210x or FTDI serial port, it should be
  able to talk to the computer

  * Regression potential

  There are some braille devices on the market using generic IDs which
  are going to stop working out of the box. Those devices are uncommon
  and it's arguably an hardware bugs they are using those IDs.

  ---

  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy
  brltty:  Installed: 6.4-2ubuntu1

   brltty appears once again to be claiming cp210x devices with the
  vendor/product ID of:

  idVendor=10c4, idProduct=ea60

  Example dmesg output:
    999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00
  [  999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge
  [  999.215977] usb 3-6.3: Manufacturer: Silicon Labs
  [  999.215978] usb 3-6.3: SerialNumber: 0005
  [  999.234070] usbcore: registered new interface driver usbserial_generic
  [  999.234081] usbserial: USB Serial support registered for generic
  [  999.235262] usbcore: registered new interface driver cp210x
  [  999.235272] usbserial: USB Serial support registered for cp210x
  [  999.235298] cp210x 3-6.3:1.0: cp210x converter detected
  [  999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0
  [  999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41
  [  999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input42
  [  999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' 
sets config #1
  [  999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
  [  999.995066] cp210x 3-6.3:1.0: device disconnected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+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 1970789] Re: Microsoft Code PlatformIO extension conflicts with brltty Ubuntu 22.04 LTS (USB ID 1a86:7523)

2022-05-18 Thread Steve Langasek

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

** This bug has been marked a duplicate of bug 1958224
   brltty claiming cp210x devices on 22.04

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

Title:
  Microsoft Code PlatformIO extension conflicts with brltty Ubuntu 22.04
  LTS (USB ID 1a86:7523)

Status in brltty package in Ubuntu:
  New

Bug description:
  When using the PlatformIO extension within Microsoft Visual Studio
  Code to upload firmware to a ESP32 based microcontroller attached via
  USB, the upload fails with the following repeated error messages in
  syslog:

  "brltty: Ignored Byte: xx" Where xx is a different hexadecimal value.

  The problem manifests itself with a timeout and a "Looking for upload port...
  Error: Please specify `upload_port` for environment or use global 
`--upload-port` option." message in PlatformIO.

  This error was not present in Ubuntu prior to upgrading to 22.04.

  Steps taken to resolve:

  1. Changed USB cable between powered hub and microcontroller
  2. Attempted upload with USB hub powered off
  3. Attempted upload from other USB ports
  4. Defined USB port microcontroller is connected to in platformio.ini by 
adding the parameter "upload_port = /dev/ttyUSB0"

  Current workaround:

  Uninstall the brltty package:

  "sudo apt remove brltty"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1970789/+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 1974071] Re: package firefox 100.0+build2-0ubuntu0.21.10.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-05-18 Thread Erich Eickmeyer 

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Thank you!

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

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

Title:
  package firefox 100.0+build2-0ubuntu0.21.10.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  virtualbox extension pack

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 100.0+build2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19
  Uname: Linux 5.13.0-41-generic x86_64
  NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3040 F pulseaudio
  BuildID: 20220428192727
  CasperMD5CheckResult: pass
  Channel: Unavailable
  Date: Wed May 18 10:24:40 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-01-07 (131 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.0.1 dev eno1 proto static 
   192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.120
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 100.0+build2-0ubuntu0.21.10.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-05-18 (0 days ago)
  dmi.bios.date: 06/30/2017
  dmi.bios.release: 0.6
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT99AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 219256
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT99AUS:bd06/30/2017:br0.6:svnLENOVO:pn3238C93:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_3238:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3238C93
  dmi.product.sku: LENOVO_MT_3238
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1974071/+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 1971076] Re: webkitgtk 2.36 doesn't work with orca anymore

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

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

Title:
  webkitgtk 2.36 doesn't work with orca anymore

Status in gnome-orca:
  Unknown
Status in orca package in Ubuntu:
  Fix Committed
Status in orca source package in Focal:
  Triaged
Status in orca source package in Impish:
  Triaged
Status in orca source package in Jammy:
  Triaged

Bug description:
  Since Ubuntu 22.04 I can not read the content of the yelp pages, le content 
of a mail from evolution or a web page from epiphany.
  This worked correctly for Ubuntu 21.10 or Ubuntu 20.04 LTS.
  This problem occurs if I migrate from a previous version, or if I reinstall 
from scrash.

  Is there a new setting that I don't aware of? 
  This also could be related to webkitgtk I suppose.

  A work arround is to select all the texte and to copy it to a place
  that I can read (gedit).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: orca 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Sun May  1 10:03:38 2022
  InstallationDate: Installed on 2022-04-03 (27 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: orca
  UpgradeStatus: Upgraded to jammy on 2022-04-12 (18 days ago)
  mtime.conffile..etc.xdg.autostart.orca-autostart.desktop: 
2022-04-17T10:13:33.207956

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-orca/+bug/1971076/+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 1971076] Re: 2.36 doesn't work with orca anymore

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

** Also affects: webkit2gtk (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Changed in: webkit2gtk (Ubuntu)
   Status: Incomplete => Fix Committed

** Package changed: webkit2gtk (Ubuntu) => orca (Ubuntu)

** Summary changed:

- 2.36 doesn't work with orca anymore
+ webkitgtk 2.36 doesn't work with orca anymore

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

Title:
  webkitgtk 2.36 doesn't work with orca anymore

Status in orca package in Ubuntu:
  Fix Committed
Status in orca source package in Focal:
  Triaged
Status in orca source package in Impish:
  Triaged
Status in orca source package in Jammy:
  Triaged

Bug description:
  Since Ubuntu 22.04 I can not read the content of the yelp pages, le content 
of a mail from evolution or a web page from epiphany.
  This worked correctly for Ubuntu 21.10 or Ubuntu 20.04 LTS.
  This problem occurs if I migrate from a previous version, or if I reinstall 
from scrash.

  Is there a new setting that I don't aware of? 
  This also could be related to webkitgtk I suppose.

  A work arround is to select all the texte and to copy it to a place
  that I can read (gedit).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: orca 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Sun May  1 10:03:38 2022
  InstallationDate: Installed on 2022-04-03 (27 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: orca
  UpgradeStatus: Upgraded to jammy on 2022-04-12 (18 days ago)
  mtime.conffile..etc.xdg.autostart.orca-autostart.desktop: 
2022-04-17T10:13:33.207956

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/orca/+bug/1971076/+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 1922548] Re: The admin backend is broken

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

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

Title:
  The admin backend is broken

Status in PolicyKit:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  On my PC I have some different users. If from one user I try to access the 
Home directory of a different user I enter the password and then I have a 
crash. Seen attached screenshot.
  Problem happens with both x11 and Wayland sessions.
  More: opening this bug I have the messages:
  corrado@corrado-n2-hh-0402:~$ ubuntu-bug -w
  ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 227, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info
  apport.hookutils.attach_casper_md5check(report,
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 945, in 
attach_casper_md5check
  with open(location) as json_file:
  PermissionError: [Errno 13] Permission denied: 
'/var/log/installer/casper-md5check.json'
  corrado@corrado-n2-hh-0402:~$ [GFX1-]: glxtest: Could not connect to wayland 
socket

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  5 12:05:27 2021
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1137, 
611)'
  InstallationDate: Installed on 2021-04-02 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince3.39.2-1
   file-roller   3.38.0-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit/+bug/1922548/+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 1960954] Re: Update gvfs to 1.50

** Changed in: gvfs (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Update gvfs to 1.50

Status in gvfs package in Ubuntu:
  Fix Committed

Bug description:
  gvfs 1.50 switched to libsoup3 which we will not be including in
  Ubuntu 22.04 LTS.2

  We should stay with the 1.48 series unless we want to revert this commit:
  https://gitlab.gnome.org/GNOME/gvfs/-/commit/beaaf78

  https://gitlab.gnome.org/GNOME/gvfs/-/blob/master/NEWS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1960954/+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 1974074] Re: missing symlink in /root/.config/libreoffice/4/user/config/

2022-05-18 Thread Ubuntu Foundations Team Bug Bot

The attachment "javasettings_Linux_*.xml" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  missing symlink in /root/.config/libreoffice/4/user/config/

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  missing symlink in /root/.config/libreoffice/4/user/config/

  javasettings_Linux_*.xml

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

2022-05-18 Thread Rahul-siddharthan

I do have gsfonts installed, version 1:8.11+urwcyr1.0.7~pre44-4.5 . As
noted, the font rendering is fine if I disable
"browser.display.use_document_fonts". So it is not a missing font
problem.

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

Title:
Firefox PDF font rendering is often messed up

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

Bug description:
I don't know whether it is an ubuntu bug or a firefox bug but since I
am running the mozilla-supported ubuntu snap of firefox 99.0.1 (on
22.04 jammy) (firefox 100 not yet available on snap), posting it here.

Many pdfs have messed-up fonts on this firefox. Following a reddit
thread, I tried disabling browser.display.use_document_fonts in
about:config. Then the pdfs render correctly, but html webpages have
messed-up fonts.

Reddit post with screenshots and sample URL here; previous reddit thread
linked therein.

https://www.reddit.com/r/firefox/comments/uhz6d1/continued_messedup_font_rendering_in_firefox_pdf/

Others (on this and previous thread) report it doesn't happen on other
platforms. On this thread, someone confirms it on a Ubuntu VM, and
someone else says it doesn't happen on Mint (based on Ubuntu but I
think doesn't use snaps).

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

[Desktop-packages] [Bug 1971608]

2022-05-18 Thread Rahul-siddharthan

Update: this problem does not occur with firefox-trunk (version
101.0a1), which is installed via apt. I strongly suspect it is a problem
with the snap packaging of firefox.

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

Title:
Firefox PDF font rendering is often messed up

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

Reddit post with screenshots and sample URL here; previous reddit thread
linked therein.

https://www.reddit.com/r/firefox/comments/uhz6d1/continued_messedup_font_rendering_in_firefox_pdf/

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

[Desktop-packages] [Bug 1971608]

2022-05-18 Thread Athaleaseem

Do you have `gsfonts` installed on your system? I had the same problem,
but I fixed it by installing gsfonts.

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

Title:
Firefox PDF font rendering is often messed up

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

Reddit post with screenshots and sample URL here; previous reddit thread
linked therein.

https://www.reddit.com/r/firefox/comments/uhz6d1/continued_messedup_font_rendering_in_firefox_pdf/

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

[Desktop-packages] [Bug 1974079] Re: Firefox and Thunderbird fail to open after recent updates

2022-05-18 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => firefox (Ubuntu)

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

Title:
  Firefox and Thunderbird fail to open after recent updates

Status in firefox package in Ubuntu:
  New

Bug description:
  System Info:
  Ubuntu 20.04 LTS
  Firefox 100.0 (64 bit)
  Thunderbird 91.8.1 (64 bit)

  Received various updates yesterday which required a reboot. After
  reboot, base system operates fine, but Thunderbird and Firefox fail to
  open. As far as I can tell, these are the only applications affected.

  Tried to file a ubuntu-bug report but Firefox was the default browser,
  so that failed as well. I switched to Chromium as default and the bug
  report succeeds.

  Launching either Firefox or Thunderbird in Safe Mode from the terminal
  succeeds.

  As a troubleshooting step, I attempted to Mark All Upgrades, only
  files available were:

  apt (2.0.6) to 2.0.8
  apt-utils (2.0.6) to 2.0.8
  libapt-pkg6.0 (2.0.6) to 2.0.8
  login (1:4.8.1-1ubuntu5.20.04.1) to 1:4.8.1-1ubuntu5.20.04.2
  passwd (1:4.8.1-1ubuntu5.20.04.1) to 1:4.8.1-1ubuntu5.20.04.2

  
  Of special note: yesterdays automatic updates do not appear in Synaptic 
History. The only updates which appear in recent History are the ones I 
manually applied. They do appear when using :

  find /var/lib/dpkg/info/ -name \*.list -mtime -3 | sed
  's#.list$##;s#.*/##'

  This produces this list:

  mesa-vulkan-drivers:amd64
  systemd-sysv
  gnome-control-center
  libc6-dbg:amd64
  mesa-va-drivers:amd64
  libpcre3:i386
  libpam-systemd:amd64
  libldap-2.4-2:amd64
  apport
  python3-apport
  libc6-i386
  libc6:amd64
  libpcre3:amd64
  systemd-timesyncd
  libdrm-common
  libxatracker2:amd64
  gnome-control-center-faces
  libegl-mesa0:amd64
  udev
  libdrm-intel1:amd64
  sbsigntool
  libc6-dev:amd64
  libc6:i386
  libglapi-mesa:amd64
  libldap-common
  login
  libdrm-nouveau2:amd64
  systemd
  ubuntu-advantage-tools
  gnome-control-center-data
  mesa-vdpau-drivers:amd64
  libdrm-amdgpu1:amd64
  openssh-client
  libtiff5:amd64
  apt-utils
  locales
  python3-problem-report
  libtiff5:i386
  apt
  libapt-pkg6.0:amd64
  apport-gtk
  libc-dev-bin
  libdrm-radeon1:amd64
  libgbm1:amd64
  libsystemd0:i386
  libsystemd0:amd64
  libdrm2:amd64
  libgl1-mesa-dri:amd64
  libc-bin
  libxml2:amd64
  passwd
  libudev1:i386
  libnss-systemd:amd64
  libudev1:amd64
  libglx-mesa0:amd64
  libxml2:i386

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.38
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 18 14:58:07 2022
  InstallationDate: Installed on 2020-08-05 (650 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2021-08-22 16:56:14.687667
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   None

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1974079/+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 1974079] [NEW] Firefox and Thunderbird fail to open after recent updates

You have been subscribed to a public bug:

System Info:
Ubuntu 20.04 LTS
Firefox 100.0 (64 bit)
Thunderbird 91.8.1 (64 bit)

Received various updates yesterday which required a reboot. After
reboot, base system operates fine, but Thunderbird and Firefox fail to
open. As far as I can tell, these are the only applications affected.

Tried to file a ubuntu-bug report but Firefox was the default browser,
so that failed as well. I switched to Chromium as default and the bug
report succeeds.

Launching either Firefox or Thunderbird in Safe Mode from the terminal
succeeds.

As a troubleshooting step, I attempted to Mark All Upgrades, only files
available were:

apt (2.0.6) to 2.0.8
apt-utils (2.0.6) to 2.0.8
libapt-pkg6.0 (2.0.6) to 2.0.8
login (1:4.8.1-1ubuntu5.20.04.1) to 1:4.8.1-1ubuntu5.20.04.2
passwd (1:4.8.1-1ubuntu5.20.04.1) to 1:4.8.1-1ubuntu5.20.04.2


Of special note: yesterdays automatic updates do not appear in Synaptic 
History. The only updates which appear in recent History are the ones I 
manually applied. They do appear when using :

find /var/lib/dpkg/info/ -name \*.list -mtime -3 | sed
's#.list$##;s#.*/##'

This produces this list:

mesa-vulkan-drivers:amd64
systemd-sysv
gnome-control-center
libc6-dbg:amd64
mesa-va-drivers:amd64
libpcre3:i386
libpam-systemd:amd64
libldap-2.4-2:amd64
apport
python3-apport
libc6-i386
libc6:amd64
libpcre3:amd64
systemd-timesyncd
libdrm-common
libxatracker2:amd64
gnome-control-center-faces
libegl-mesa0:amd64
udev
libdrm-intel1:amd64
sbsigntool
libc6-dev:amd64
libc6:i386
libglapi-mesa:amd64
libldap-common
login
libdrm-nouveau2:amd64
systemd
ubuntu-advantage-tools
gnome-control-center-data
mesa-vdpau-drivers:amd64
libdrm-amdgpu1:amd64
openssh-client
libtiff5:amd64
apt-utils
locales
python3-problem-report
libtiff5:i386
apt
libapt-pkg6.0:amd64
apport-gtk
libc-dev-bin
libdrm-radeon1:amd64
libgbm1:amd64
libsystemd0:i386
libsystemd0:amd64
libdrm2:amd64
libgl1-mesa-dri:amd64
libc-bin
libxml2:amd64
passwd
libudev1:i386
libnss-systemd:amd64
libudev1:amd64
libglx-mesa0:amd64
libxml2:i386

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.38
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Wed May 18 14:58:07 2022
InstallationDate: Installed on 2020-08-05 (650 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
 Log time: 2021-08-22 16:56:14.687667
 Starting pkgProblemResolver with broken count: 0
 Starting 2 pkgProblemResolver with broken count: 0
 Done
 None

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


** Tags: amd64 apport-bug dist-upgrade focal
-- 
Firefox and Thunderbird fail to open after recent updates
https://bugs.launchpad.net/bugs/1974079
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to firefox in Ubuntu.

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

[Desktop-packages] [Bug 1973594] Re: [BPO] libreoffice 7.2.7 for focal

2022-05-18 Thread Dan Streetman

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

Title:
   [BPO] libreoffice 7.2.7 for focal

Status in libreoffice package in Ubuntu:
  New
Status in libreoffice source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.2.7 is in its seventh (and last) bugfix release of the 7.2 
line:
   https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.7_release

   * This source packages matches the proposed SRU for impish handled at
   https://bugs.launchpad.net/ubuntu/impish/+source/libreoffice/+bug/1972155
     and its backport is currently provided by the LibreOffice Still PPA at
   
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages

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

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

   * 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.2.7-0ubuntu0.21.10.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_72/1617/

    * 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-experimental/focal/amd64/libr/libreoffice/20220518_095601_b5724@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/arm64/libr/libreoffice/20220518_133315_9e5cd@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/armhf/libr/libreoffice/20220518_135411_142bf@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/ppc64el/libr/libreoffice/20220518_143359_edb75@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/s390x/libr/libreoffice/20220518_095423_36802@/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 44+ 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/1973594/+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 1974074] Re: missing symlink in /root/.config/libreoffice/4/user/config/

libreoffice for ubuntu is missing an important symlink required for
libreoffice to run properly without crashing the required file must be
patched by creating a symlink in the directory for the missing symlink
in /root/.config/libreoffice/4/user/config/

when you do a fresh install of any ubuntu 18.04.5 LTS
do these commands then update/upgrade your system
for all the patches to take place.

run the commands to fix it yourself

ln -s /home/xubuntu/Desktop/libreoffice/javasettings_Linux_X86_64.xml
/home/xubuntu/Desktop/libreoffice/javasettings_Linux_*.xml

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

Title:
  missing symlink in /root/.config/libreoffice/4/user/config/

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  missing symlink in /root/.config/libreoffice/4/user/config/

  javasettings_Linux_*.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+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 1974074] Re: missing symlink in /root/.config/libreoffice/4/user/config/

** Attachment added: "javasettings_Linux_*.xml"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+attachment/5590981/+files/javasettings_Linux_%2A.xml

** Patch removed: "javasettings_Linux_X86_64.xml"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+attachment/5590980/+files/javasettings_Linux_X86_64.xml

** Changed in: libreoffice (Ubuntu)
 Assignee: (unassigned) => jake (adam21232323)

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

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

Title:
  missing symlink in /root/.config/libreoffice/4/user/config/

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  missing symlink in /root/.config/libreoffice/4/user/config/

  javasettings_Linux_*.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+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 1974074] Re: missing symlink in /root/.config/libreoffice/4/user/config/

** Attachment removed: 
"/root/.config/libreoffice/4/user/config/javasettings_Linux_*.xml"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+attachment/5590973/+files/ProcCpuinfoMinimal.txt

** Attachment added: "javasettings_Linux_X86_64.xml"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+attachment/5590980/+files/javasettings_Linux_X86_64.xml

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

Title:
  missing symlink in /root/.config/libreoffice/4/user/config/

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  missing symlink in /root/.config/libreoffice/4/user/config/

  javasettings_Linux_*.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+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 1859353] Re: software-properties-gtk not working

2022-05-18 Thread Christian Rauch

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

** This bug has been marked a duplicate of bug 1900098
   software-properties-gtk fails to open with error

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

Title:
  software-properties-gtk not working

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Additional Drivers /Software & Update not working

  Hello,

  I am running :-
  Description: Ubuntu 19.10
  Release: 19.10

  software-properties-gtk:
  Installed: 0.98.5
  Candidate: 0.98.5
  Version table:
  *** 0.98.5 500
  500 http://ca.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://ca.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status



  I am trying to run Additional Drivers /Software & Update . But it opened once 
and froze and never opened again.
  When I try running the command:-
  $ sudo software-properties-gtk

  Did a remove and reinstall of the same, but did not work.

  It returns:-

  
  ERROR:dbus.proxies:Introspect error on :1.2559:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
  Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 175, in __init__
  self.backend.Reload();
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
  return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 147, in __call__
  **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 653, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name :1.2559 was not provided by any .service files

  
  Also, the syslog says:-
  name='com.ubuntu.SoftwareProperties' requested by ':1.2455' (uid=1000 
pid=2267 comm="/usr/bin/python3 /usr/bin/software-properties-gtk " 
label="unconfined") (using servicehelper)
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Unable to init 
server: Could not connect: Connection refused
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Unable to init 
server: Could not connect: Connection refused
  Jan 12 11:58:55 gillZ dbus-daemon[2192]: [system] Successfully activated 
service 'com.ubuntu.SoftwareProperties'
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Traceback (most 
recent call last):
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File 
"/usr/lib/software-properties/software-properties-dbus", line 68, in 
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: server = 
SoftwarePropertiesDBus(bus, datadir=datadir)
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File 
"/lib/python3/dist-packages/softwareproperties/dbus/SoftwarePropertiesDBus.py", 
line 66, in __init__
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: 
self._livepatch_service = LivepatchService()
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File 
"/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line 93, 
in __init__
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: self._session = 
requests_unixsocket.Session()
  Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: NameError: name 
'requests_unixsocket' is not defined
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: 
ERROR:dbus.proxies:Introspect error on :1.2457:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: Traceback 
(most recent call last):
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File 
"/usr/bin/software-properties-gtk", line 100, in 
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: app = 
SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file)
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 175, in __init__
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: 
self.backend.Reload();
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: return 
self._proxy_method(*args, **keywords)
  Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 147, in

[Desktop-packages] [Bug 1974074] Re: libreoffice crashes because of a missing symlink

** Tags removed: amd64 bionic

** Description changed:

- libreoffice crashes if you dont add a symlink in
- /root/.config/libreoffice/4/user/config/ named  javasettings_Linux_*.xml
- by creating a symlink with ln -s javasettings_Linux_X86_64.xml
- javasettings_Linux_*.xml that fixes the problem please add a bug fix by
- automatically creating this symlink to prevent libreoffice from crashing
- in a future update or upgrade.
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
- Package: libreoffice (installed)
- ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
- Uname: Linux 5.4.0-42-generic x86_64
- ApportVersion: 2.20.9-0ubuntu7.16
- Architecture: amd64
- CasperVersion: 1.394.3
- CurrentDesktop: XFCE
- Date: Wed May 18 18:04:17 2022
- LiveMediaBuild: Xubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
- 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)
+ missing symlink in
+ /root/.config/libreoffice/4/user/config/javasettings_Linux_*.xml

** Description changed:

- missing symlink in
- /root/.config/libreoffice/4/user/config/javasettings_Linux_*.xml
+ missing symlink in /root/.config/libreoffice/4/user/config/
+ 
+ javasettings_Linux_*.xml

** Attachment added: "Screenshot_2022-05-18_18-40-29.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+attachment/5590976/+files/Screenshot_2022-05-18_18-40-29.png

** Information type changed from Private Security to Public

** Summary changed:

- libreoffice crashes because of a missing symlink
+ missing symlink in /root/.config/libreoffice/4/user/config/

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

Title:
  missing symlink in /root/.config/libreoffice/4/user/config/

Status in libreoffice package in Ubuntu:
  New

Bug description:
  missing symlink in /root/.config/libreoffice/4/user/config/

  javasettings_Linux_*.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974074/+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 1930974] Re: software-properties-gtk is broken again

2022-05-18 Thread Christian Rauch

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

The Qt (software-properties-qt) and KDE (software-properties-kde)
versions still work when launched as root via sudo.

** This bug has been marked a duplicate of bug 1900098
   software-properties-gtk fails to open with error

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

Title:
  software-properties-gtk is broken again

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  Hello,
  This issue is happening very often

  $ software-properties-gtk 
  ERROR:dbus.proxies:Introspect error on :1.127:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 211, in __init__
  self.backend.Reload();
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
  return self._proxy_method(*args, **keywords)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
  return self._connection.call_blocking(self._named_service,
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in 
call_blocking
  reply_message = self.send_message_with_reply_and_block(
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name :1.127 was not provided by any .service files

  
  I tried the usual solution I used before:

  $ sudo apt-get update && sudo apt-get install --reinstall python3-six
  python3-certifi

  However, the package is still broken and there is no way to open
  software and updates.

  
  =
  $ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  =
  $ apt-cache policy software-properties-gtk 
  software-properties-gtk:
Installed: 0.98.9.5
Candidate: 0.98.9.5
Version table:
   *** 0.98.9.5 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages
  100 /var/lib/dpkg/status
   0.98.9.2 500
  500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu focal-security/main i386 Packages
   0.98.9 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
  ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1930974/+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 1931902] Re: [AMD Ellesmere] Crackling sound on Pulseaudio

2022-05-18 Thread Cuppa-Chino

can confirm this also affects combination of 
Ryzen 5600X
Asus Strix B550-I motherboard
Sapphire 6600XT graphics card

monitor is connected via display port

"killall speech-dispatcher" fixes issue (had previously used "pulseaudio
-k" but that is more of a pain)

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

Title:
  [AMD Ellesmere] Crackling sound on Pulseaudio

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in speech-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  While playing back any sounds, a certain crackling sound (static) will
  play with a fixed delay of the sound being played. The amount and
  volume of the static will depend on the sound/music that is being
  played, and this only starts occurring after a somewhat long time (30
  minutes or more). What is interesting to see is that while playing
  back music from Spotify (Snap) the static will only start after a
  second or so, but when playing YouTube videos on Firefox, it will be
  immediate and output that static while the video is playing.

  I've added two sound recordings, one while playing back a song from
  Spotify and the other while playing a song from YouTube. This issue
  goes away when restarting the PulseAudio service, but it comes back
  after a random amount of time.

  1) Description:   Ubuntu 21.04
  Release:  21.04

  2) pulseaudio:
Installed: 1:14.2-1ubuntu1
Candidate: 1:14.2-1ubuntu1
Version table:
   1:14.2-1ubuntu1.1 1 (phased 10%)
  500 http://br.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
   *** 1:14.2-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  matheus   18662 F pulseaudio
   /dev/snd/controlC2:  matheus   18662 F pulseaudio
   /dev/snd/controlC0:  matheus   18662 F pulseaudio
   /dev/snd/pcmC0D8p:   matheus   18662 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 14 16:58:43 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-05-03 (41 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931902/+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 1931902] Re: [AMD Ellesmere] Crackling sound on Pulseaudio

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

** Changed in: speech-dispatcher (Ubuntu)
   Status: New => Confirmed

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

Title:
  [AMD Ellesmere] Crackling sound on Pulseaudio

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in speech-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  While playing back any sounds, a certain crackling sound (static) will
  play with a fixed delay of the sound being played. The amount and
  volume of the static will depend on the sound/music that is being
  played, and this only starts occurring after a somewhat long time (30
  minutes or more). What is interesting to see is that while playing
  back music from Spotify (Snap) the static will only start after a
  second or so, but when playing YouTube videos on Firefox, it will be
  immediate and output that static while the video is playing.

  I've added two sound recordings, one while playing back a song from
  Spotify and the other while playing a song from YouTube. This issue
  goes away when restarting the PulseAudio service, but it comes back
  after a random amount of time.

  1) Description:   Ubuntu 21.04
  Release:  21.04

  2) pulseaudio:
Installed: 1:14.2-1ubuntu1
Candidate: 1:14.2-1ubuntu1
Version table:
   1:14.2-1ubuntu1.1 1 (phased 10%)
  500 http://br.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
   *** 1:14.2-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  matheus   18662 F pulseaudio
   /dev/snd/controlC2:  matheus   18662 F pulseaudio
   /dev/snd/controlC0:  matheus   18662 F pulseaudio
   /dev/snd/pcmC0D8p:   matheus   18662 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 14 16:58:43 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-05-03 (41 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931902/+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 1974071] [NEW] package firefox 100.0+build2-0ubuntu0.21.10.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-05-18 Thread DA

Public bug reported:

virtualbox extension pack

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: firefox 100.0+build2-0ubuntu0.21.10.1
ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19
Uname: Linux 5.13.0-41-generic x86_64
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu71.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm3040 F pulseaudio
BuildID: 20220428192727
CasperMD5CheckResult: pass
Channel: Unavailable
Date: Wed May 18 10:24:40 2022
ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
ForcedLayersAccel: False
InstallationDate: Installed on 2022-01-07 (131 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
IpRoute:
 default via 192.168.0.1 dev eno1 proto static 
 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.120
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2
 apt  2.4.5
RunningIncompatibleAddons: False
SourcePackage: firefox
Title: package firefox 100.0+build2-0ubuntu0.21.10.1 failed to install/upgrade: 
new firefox package pre-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to jammy on 2022-05-18 (0 days ago)
dmi.bios.date: 06/30/2017
dmi.bios.release: 0.6
dmi.bios.vendor: LENOVO
dmi.bios.version: 9SKT99AUS
dmi.board.name: MAHOBAY
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: 219256
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT99AUS:bd06/30/2017:br0.6:svnLENOVO:pn3238C93:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_3238:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: 3238C93
dmi.product.sku: LENOVO_MT_3238
dmi.product.version: ThinkCentre M92p
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package jammy need-duplicate-check

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

Title:
  package firefox 100.0+build2-0ubuntu0.21.10.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  New

Bug description:
  virtualbox extension pack

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 100.0+build2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19
  Uname: Linux 5.13.0-41-generic x86_64
  NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3040 F pulseaudio
  BuildID: 20220428192727
  CasperMD5CheckResult: pass
  Channel: Unavailable
  Date: Wed May 18 10:24:40 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-01-07 (131 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.0.1 dev eno1 proto static 
   192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.120
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 100.0+build2-0ubuntu0.21.10.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-05-18 (0 days ago)
  dmi.bios.date: 06/30/2017
  dmi.bios.release: 0.6
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT99AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 219256
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT99AUS:bd06/30/2017:br0.6:svnLENOVO:pn3238C93:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_3238:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3238C93

[Desktop-packages] [Bug 1973802] Re: Gnome Shell crashes when disconnecting external monitor

2022-05-18 Thread Ralf Sternberg

So `ubuntu-bug ` fails and an error UI pops up, asking to
send an error report (which I did). After that, `apport-cli` tells me
that there are no pending crash reports.

Strangely, there are no recent items on
https://errors.ubuntu.com/user/, only some that are
several days, some several months old.

Trying to attach the crash log here failed again. I've opened
https://bugs.launchpad.net/launchpad/+bug/1974066 for that.

Seems I'm running out of options, sorry.

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

Title:
  Gnome Shell crashes when disconnecting external monitor

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04, gnome-shell 42.0-2ubuntu1

  When unplugging an external monitor connected via USB-C to my Thinkpad
  P14s, the entire UI session crashes. While the external monitor is
  plugged in, it is configured as the primary display. Here are the
  gnome-shell logs of the latest incident, I suppose the relevant part
  is `assertion 'window->stack_position >= 0' failed`.

  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212959: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212959 does not exist.
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212963: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212963 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212964: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212964 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212965: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212965 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212966: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212966 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212967: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212967 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 31 with keysym 31 (keycode a).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 32 with keysym 32 (keycode b).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 33 with keysym 33 (keycode c).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
  May 17

[Desktop-packages] [Bug 1974068] [NEW] Touchpad tapping not working after upgrade to Ubuntu 22.04

2022-05-18 Thread Sten-Ove Olsson

Public bug reported:

I have an Intel NUC pc with Ubuntu, recently upgraded to 22.04.

I use a Logitech wireless keyboard K830 with integrated touchpad.

After the Ubuntu upgrade the tapping function (emulating left mouse-
click) of the touchpad doesn't work anymore.

I can move the screen arrow around by using the touchpad, but for mouse
clicking I have to use the button below the touchpad, which is very
awkward.

Moving the screen arrow around by sweeping and clicking an object by
tapping, all on the touchpad is very much more convenient.

So please fix this!


My pc specs:

# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.2.1 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Intel(R) Client Systems
Product Name: NUC8i7BEH
Version: J72992-303
Serial Number: G6BE84300WZE
UUID: 41b41c36-9b51-47ea-e26e-94c691a692ec
Wake-up Type: Power Switch
SKU Number: BOXNUC8i7BEH
Family: Intel NUC

Distributor ID: Ubuntu
Description:Ubuntu 22.04 LTS
Release:22.04
Codename:   jammy
Linux SO-NUC-TV 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Touchpad tapping not working after upgrade to Ubuntu 22.04

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  I have an Intel NUC pc with Ubuntu, recently upgraded to 22.04.

  I use a Logitech wireless keyboard K830 with integrated touchpad.

  After the Ubuntu upgrade the tapping function (emulating left mouse-
  click) of the touchpad doesn't work anymore.

  I can move the screen arrow around by using the touchpad, but for
  mouse clicking I have to use the button below the touchpad, which is
  very awkward.

  Moving the screen arrow around by sweeping and clicking an object by
  tapping, all on the touchpad is very much more convenient.

  So please fix this!

  
  My pc specs:

  # dmidecode 3.3
  Getting SMBIOS data from sysfs.
  SMBIOS 3.2.1 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
Manufacturer: Intel(R) Client Systems
Product Name: NUC8i7BEH
Version: J72992-303
Serial Number: G6BE84300WZE
UUID: 41b41c36-9b51-47ea-e26e-94c691a692ec
Wake-up Type: Power Switch
SKU Number: BOXNUC8i7BEH
Family: Intel NUC

  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04 LTS
  Release:  22.04
  Codename: jammy
  Linux SO-NUC-TV 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1974068/+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 1974064] [NEW] gnome-calculator error: Gdk-Message: 13:57:03.713: Error flushing display: Erro de protocolo

2022-05-18 Thread Edson T. Marques

Public bug reported:

etm@ETM:~$ gnome-calculator

** (gnome-calculator:4273): WARNING **: 13:57:03.546: unit.vala:443:
Failed to convert value: π*x/180

** (gnome-calculator:4273): WARNING **: 13:57:03.558: unit.vala:443:
Failed to convert value: π*x/180

** (gnome-calculator:4273): WARNING **: 13:57:03.558: unit.vala:443:
Failed to convert value: π*x/180

** (gnome-calculator:4273): WARNING **: 13:57:03.560: unit.vala:443:
Failed to convert value: π*x/180

** (gnome-calculator:4273): WARNING **: 13:57:03.561: unit.vala:443:
Failed to convert value: π*x/180

** (gnome-calculator:4273): WARNING **: 13:57:03.561: unit.vala:443:
Failed to convert value: π*x/180

** (gnome-calculator:4273): WARNING **: 13:57:03.561: unit.vala:443:
Failed to convert value: π*x/180

** (gnome-calculator:4273): WARNING **: 13:57:03.562: unit.vala:443:
Failed to convert value: π*x/180

** (gnome-calculator:4273): WARNING **: 13:57:03.563: unit.vala:443: Failed to 
convert value: π*x/180
Gdk-Message: 13:57:03.713: Error flushing display: Erro de protocolo

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-calculator 1:42.0-3ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-28.29-generic 5.15.35
Uname: Linux 5.15.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Wed May 18 13:57:48 2022
InstallationDate: Installed on 2022-03-15 (63 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
SourcePackage: gnome-calculator
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kinetic package-from-proposed third-party-packages 
wayland-session

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

Title:
  gnome-calculator error: Gdk-Message: 13:57:03.713: Error flushing
  display: Erro de protocolo

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  etm@ETM:~$ gnome-calculator

  ** (gnome-calculator:4273): WARNING **: 13:57:03.546: unit.vala:443:
  Failed to convert value: π*x/180

  ** (gnome-calculator:4273): WARNING **: 13:57:03.558: unit.vala:443:
  Failed to convert value: π*x/180

  ** (gnome-calculator:4273): WARNING **: 13:57:03.558: unit.vala:443:
  Failed to convert value: π*x/180

  ** (gnome-calculator:4273): WARNING **: 13:57:03.560: unit.vala:443:
  Failed to convert value: π*x/180

  ** (gnome-calculator:4273): WARNING **: 13:57:03.561: unit.vala:443:
  Failed to convert value: π*x/180

  ** (gnome-calculator:4273): WARNING **: 13:57:03.561: unit.vala:443:
  Failed to convert value: π*x/180

  ** (gnome-calculator:4273): WARNING **: 13:57:03.561: unit.vala:443:
  Failed to convert value: π*x/180

  ** (gnome-calculator:4273): WARNING **: 13:57:03.562: unit.vala:443:
  Failed to convert value: π*x/180

  ** (gnome-calculator:4273): WARNING **: 13:57:03.563: unit.vala:443: Failed 
to convert value: π*x/180
  Gdk-Message: 13:57:03.713: Error flushing display: Erro de protocolo

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-calculator 1:42.0-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-28.29-generic 5.15.35
  Uname: Linux 5.15.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Wed May 18 13:57:48 2022
  InstallationDate: Installed on 2022-03-15 (63 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1974064/+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 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock

2022-05-18 Thread Timmy Braun

I applied the patch now and it seems to work great so far! Will let you
know if I find any issues. Thank you Daniel!

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

Title:
  Dock auto-hides when a right click context menu is opened while a
  window is under the dock

Status in Dash to dock:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  Triaged

Bug description:
  Currently testing a fresh install of the beta for 22.04.
  All packages are up to date.

  When having the dock auto-hide option enabled, a glitch occurs when opening 
the windows selector (when multiple instances of the same program are opened).
  The selector does open, but the dock will hide itself immediately instead of 
waiting for a selection. Selecting a window will then cause a glitch where the 
selector will align with the hidden dock in a non natural way before 
disappearing.

  A proposed fix would be to prevent the dock from auto-hiding when the
  miniatures selector opens and wait for a second input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1967121/+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 1958267] Re: wpa can't connect to servers using TLS 1.1 or older

2022-05-18 Thread Bug Watch Updater

** Changed in: wpa (Debian)
   Status: Unknown => New

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

Title:
  wpa can't connect to servers using TLS 1.1 or older

Status in wpa package in Ubuntu:
  Triaged
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  New

Bug description:
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using 
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1974029] Re: vram memory leak under Wayland

2022-05-18 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  vram memory leak under Wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  I use 3 monitors. When I turn two of then off and on, the "memory
  usage" shown by nvidia-smi grows by approximately 400 MB each cycle.
  When used video memory reaches maximum my card has (it ix GTX 970 with
  4GB) the graphical system sort of crashes (desktop is not shown, one
  of the monitor does not show image at all).

  This occurs only under Wayland.

  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset 
nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0c.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 18 14:50:11 2022
  DistUpgraded: 2022-03-19 09:03:59,252 INFO cache.commit()
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed
   nvidia/510.60.02, 5.15.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:367a]
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic 
root=UUID=ca73c670-cd82-4bb7-9d49-1e036cf94a1a ro usbcore.autosuspend=-1 
libata.force=1.00:noncq acpi_enforce_resources=lax libata.noacpi=1 amd_iommu=on 
iommu=pt
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (60 days ago)
  dmi.bios.date: 08/10/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5861
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5861:bd08/10/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1974029/+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 1974029] [NEW] vram memory leak under Wayland

You have been subscribed to a public bug:

I use 3 monitors. When I turn two of then off and on, the "memory usage"
shown by nvidia-smi grows by approximately 400 MB each cycle. When used
video memory reaches maximum my card has (it ix GTX 970 with 4GB) the
graphical system sort of crashes (desktop is not shown, one of the
monitor does not show image at all).

This occurs only under Wayland.

Description:Ubuntu 22.04 LTS
Release:22.04

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset 
nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..0c.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 11:24:05 
UTC 2022
 GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 18 14:50:11 2022
DistUpgraded: 2022-03-19 09:03:59,252 INFO cache.commit()
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed
 nvidia/510.60.02, 5.15.0-30-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:367a]
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic 
root=UUID=ca73c670-cd82-4bb7-9d49-1e036cf94a1a ro usbcore.autosuspend=-1 
libata.force=1.00:noncq acpi_enforce_resources=lax libata.noacpi=1 amd_iommu=on 
iommu=pt
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-03-19 (60 days ago)
dmi.bios.date: 08/10/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5861
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X470-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5861:bd08/10/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session
-- 
vram memory leak under Wayland
https://bugs.launchpad.net/bugs/1974029
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 1974040] Re: Cannot connect to PEAP wifi (eduroam)

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

thanks for your quick answer Sebastien. I tried to do as suggested in
#22 and then #36 but still not working. Can I provide and further
information to help track this problem down?

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

Title:
  Cannot connect to PEAP wifi (eduroam)

Status in wpa package in Ubuntu:
  New

Bug description:
  Connection to wifi fails with

  May 18 15:08:55 attila wpa_supplicant[9698]: OpenSSL:
  openssl_handshake - SSL_connect error:0A0C0103:SSL routines::internal
  error

  
  Description:Ubuntu 22.04 LTS
  Release:22.04


  wpasupplicant:
Installed: 2:2.10-6ubuntu1
Candidate: 2:2.10-6ubuntu1
Version table:
   *** 2:2.10-6ubuntu1 1 (phased 40%)
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:2.10-6 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed May 18 15:13:41 2022
  InstallationDate: Installed on 2019-10-22 (938 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1974040/+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 1958267] Re: wpa can't connect to servers using TLS 1.1 or older

Retitling this report to focus on the issue connecting to TLS <= 1.1
servers, which is reported upstream now on
http://lists.infradead.org/pipermail/hostap/2022-May/040563.html


** Summary changed:

- "Connection failed" for WPA Enterprise network (e.g. eduroam)
+ wpa can't connect to servers using TLS 1.1 or older

** Changed in: wpa (Ubuntu)
   Status: Confirmed => Triaged

** Description changed:

+ wpa built with in openssl3 fails to connect to TLS 1.1 or lower server
+ 
+ those uses MD5-SHA1 as digest in its signature algorithm which no longer
+ meets OpenSSL default level of security of 80 bits
+ 
+ http://lists.infradead.org/pipermail/hostap/2022-May/040563.html
+ 
+ Workaround are described in #22 and #36 by basically using 
+ CipherString = DEFAULT@SECLEVEL=0
+ 
+ which lowers the security level
+ 
+ ---
+ 
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a request
  to re-enter the password.
  
  - I've re-tried the credentials: no fix ;-)
  
  - Tried a 21.10 live session on the same machine: works fine!
  
  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.
  
  - Upgraded wpasupplicant to the latest version: fails to connect again.
- 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: wpa (Ubuntu Jammy)
Milestone: None => ubuntu-22.04.1

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

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

** Changed in: wpa (Debian)
 Remote watch: Debian Bug tracker #1010603 => Debian Bug tracker #1011121

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

Title:
  wpa can't connect to servers using TLS 1.1 or older

Status in wpa package in Ubuntu:
  Triaged
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  Unknown

Bug description:
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using 
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1974054] [NEW] Without a reason gnome-shell CPU usage gets high

2022-05-18 Thread Islam

Public bug reported:

Without a reason, CPU usage for gnome-shell jumps from 4% to 22%.
All I did this normal workflow, locking/unlocking multiple times over few hours 
and couple of suspends.

The screenshot is showing 37% because of the screenshot tool, but idling at 22%.
And if I re-logged or reboot, it idles at 4% normally.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 18 17:24:38 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 
InstallationDate: Installed on 2022-02-03 (103 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago)

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


** Tags: amd64 apport-bug jammy

** Attachment added: "Screenshot from 2022-05-18 17-24-19.png"
   
https://bugs.launchpad.net/bugs/1974054/+attachment/5590938/+files/Screenshot%20from%202022-05-18%2017-24-19.png

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

Title:
  Without a reason gnome-shell CPU usage gets high

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Without a reason, CPU usage for gnome-shell jumps from 4% to 22%.
  All I did this normal workflow, locking/unlocking multiple times over few 
hours and couple of suspends.

  The screenshot is showing 37% because of the screenshot tool, but idling at 
22%.
  And if I re-logged or reboot, it idles at 4% normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 18 17:24:38 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-02-03 (103 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974054/+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 1971415] Re: Remote desktop is automatically enabled after login

This bug was fixed in the package gnome-control-center -
1:41.4-1ubuntu13.2

---
gnome-control-center (1:41.4-1ubuntu13.2) jammy-security; urgency=medium

  * Add patches to turn off RDP & VNC gsettings keys when turning off
Remote Desktop Sharing (LP: #1971415)
- CVE-2022-1736

 -- Jeremy Bicha   Wed, 18 May 2022 08:52:00 -0400

** Changed in: gnome-control-center (Ubuntu Jammy)
   Status: Confirmed => 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/1971415

Title:
  Remote desktop is automatically enabled after login

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Jammy:
  Fix Released

Bug description:
  Details:
  Turning off RDP Remote Desktop Sharing with gnome-control-center would only 
turn off RDP sharing for the current session. Upon logging back in, RDP Sharing 
would be enabled again without any additional user interaction or notification.

  Other Info:
  As mentioned in the comments at 
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1825
  this issue could have been avoided if Ubuntu's gnome-remote-desktop didn't 
keep the systemd user service always running. I do intend to fix that issue 
also but it is a more complicated fix. I think it will require a maintainer 
script to remove the automatic conffiles added by dh. I will do the 
gnome-remote-desktop bugfix as a normal non-security SRU.

  Original Bug Report:
  If I disable sharing/remote desktop in GNOME Control Center, then log out and 
back in, it is automatically enabled again. I report this as a security 
vulnerability because remote desktop is enabled without the user's knowledge.

  Software versions:
  - Ubuntu 22.04
  - gnome-remote-desktop 42.0-4ubuntu1
  - gnome-control-center 1:41.4-1ubuntu13

  Steps to reproduce:
  1. Start with Remote Desktop enabled. "systemctl --user status 
gnome-remote-desktop.service" reports "active (running)".
  2. Disable Remote Desktop in Control Center. systemctl reports "inactive 
(dead)".
  3. Log out and back in.
  4. Open Control Center. Remote Desktop is enabled again. systemctl reports 
"active (running)".

  Expected behavior:
  Remote Desktop should stay disabled upon the new login.

  Actual behavior:
  Remote Desktop was automatically enabled again.

  Previous discussion: https://gitlab.gnome.org/GNOME/gnome-control-
  center/-/issues/1775#note_1443319

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1971415/+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 1973594] Re: [BPO] libreoffice 7.2.7 for focal

2022-05-18 Thread Rico Tzschichholz

** Patch added: "libreoffice_7.2.7-0ubuntu0.21.10.1_bpo20.04.1.diff"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1973594/+attachment/5590937/+files/libreoffice_7.2.7-0ubuntu0.21.10.1_bpo20.04.1.diff

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

Title:
   [BPO] libreoffice 7.2.7 for focal

Status in libreoffice package in Ubuntu:
  New
Status in libreoffice source package in Focal:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.2.7 is in its seventh (and last) bugfix release of the 7.2 
line:
   https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.7_release

   * This source packages matches the proposed SRU for impish handled at
   https://bugs.launchpad.net/ubuntu/impish/+source/libreoffice/+bug/1972155
     and its backport is currently provided by the LibreOffice Still PPA at
   
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages

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

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

   * 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.2.7-0ubuntu0.21.10.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_72/1617/

    * 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-experimental/focal/amd64/libr/libreoffice/20220518_095601_b5724@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/arm64/libr/libreoffice/20220518_133315_9e5cd@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/armhf/libr/libreoffice/20220518_135411_142bf@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/ppc64el/libr/libreoffice/20220518_143359_edb75@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/s390x/libr/libreoffice/20220518_095423_36802@/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 44+ 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/1973594/+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 1974040] Re: Cannot connect to PEAP wifi (eduroam)

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

Thanks, it sounds like the same as bug #1958267 which is detailed on
http://lists.infradead.org/pipermail/hostap/2022-May/040563.html but
basically an issue when trying to connect to servers using old TLS
versions

The workaround described on the other bug is to use DEFAULT@SECLEVEL=0 ,
#22 has details on how to create a configuration specific to wpa

** This bug has been marked a duplicate of bug 1958267
   wpa can't connect to servers using TLS 1.1 or older

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

Title:
  Cannot connect to PEAP wifi (eduroam)

Status in wpa package in Ubuntu:
  New

Bug description:
  Connection to wifi fails with

  May 18 15:08:55 attila wpa_supplicant[9698]: OpenSSL:
  openssl_handshake - SSL_connect error:0A0C0103:SSL routines::internal
  error

  
  Description:Ubuntu 22.04 LTS
  Release:22.04


  wpasupplicant:
Installed: 2:2.10-6ubuntu1
Candidate: 2:2.10-6ubuntu1
Version table:
   *** 2:2.10-6ubuntu1 1 (phased 40%)
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:2.10-6 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed May 18 15:13:41 2022
  InstallationDate: Installed on 2019-10-22 (938 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1974040/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

2022-05-18 Thread Ludovic Rousseau

I reinstalled Ubuntu 22.04 in another VM (still using VirtualBox) and I do NOT 
get the problem.
So it is not related to the hardware (I was expecting this result).

Strange.

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1965536] Re: Network icon disappeared in Unity

2022-05-18 Thread Alistair Cunningham

"apt install indicator-application" and a reboot solved the problem.
indicator-applet was already installed and the latest version. Thank you
Anton!

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

Title:
  Network icon disappeared in Unity

Status in network-manager-applet package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 22.04, the network icon at the top right of
  the screen in Unity has disappeared. The only way to change wireless
  network is now gear icon -> System Settings -> Network.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager-gnome 1.24.0-1ubuntu3
  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: Unity:Unity7:ubuntu
  Date: Fri Mar 18 14:07:50 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2020-07-14 (611 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 10.0.0.1 dev wlp0s20f3 proto dhcp metric 600 
   10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 
   10.0.0.0/19 dev wlp0s20f3 proto kernel scope link src 10.0.7.124 metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
  SourcePackage: network-manager-applet
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1965536/+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 1973594] Re: [BPO] libreoffice 7.2.7 for focal

2022-05-18 Thread Rico Tzschichholz

** Description changed:

  [Impact]
  
   * LibreOffice 7.2.7 is in its seventh (and last) bugfix release of the 7.2 
line:
   https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.7_release
  
   * This source packages matches the proposed SRU for impish handled at
   https://bugs.launchpad.net/ubuntu/impish/+source/libreoffice/+bug/1972155
     and its backport is currently provided by the LibreOffice Still PPA at
   
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages
  
   * Previous backport of 7.2.6 handled at
   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969808
  
   * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released
  in focal.
  
   * 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.2.7-0ubuntu0.21.10.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_72/1617/
  
    * 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] ...
- * [arm64] ...
- * [armhf] ...
- * [ppc64el] ...
- * [s390x] ...
+ * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/amd64/libr/libreoffice/20220518_095601_b5724@/log.gz
+ * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/arm64/libr/libreoffice/20220518_133315_9e5cd@/log.gz
+ * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/armhf/libr/libreoffice/20220518_135411_142bf@/log.gz
+ * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/ppc64el/libr/libreoffice/20220518_143359_edb75@/log.gz
+ * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-experimental/focal/s390x/libr/libreoffice/20220518_095423_36802@/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 44+ bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.
  
   * A combination of autopkgtests and careful smoke testing as described
  above should provide reasonable confidence that no regressions sneaked
  in.

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

Title:
   [BPO] libreoffice 7.2.7 for focal

Status in libreoffice package in Ubuntu:
  New
Status in libreoffice source package in Focal:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.2.7 is in its seventh (and last) bugfix release of the 7.2 
line:
   https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.7_release

   * This source packages matches the proposed SRU for impish handled at
   https://bugs.launchpad.net/ubuntu/impish/+source/libreoffice/+bug/1972155
     and its backport is currently provided by the LibreOffice Still PPA at
   
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages

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

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

   * 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.2.7-0ubuntu0.21.10.1

   * Backport target is Focal/20.04 LTS only to

[Desktop-packages] [Bug 1958019]

2022-05-18 Thread andreimiculita+kern

(In reply to Cameron Berkenpas from comment #600)
> Looking at the model number, there's a chance it's compatible with the 
> verbs of the 15IMHG05, or another model from around that time.
> 
> Do you know how to build and run your own kernel?
> 
> Also, please provide a URL to your alsa-info.
> 
> On 5/15/2022 12:12 PM, bugzilla-dae...@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=208555
> >
> > --- Comment #599 from Andrei Miculita (andreimiculita+k...@gmail.com) ---
> > Lenovo Legion S7 15IMH5
> >
> > Has anyone managed to get their sound working on it? Would appreciate a
> > tutorial or some tips (the more specific, the better, as this thread is
> full
> > of
> > other devices as well and it'd take a long time to try everything)
> >


I do, it might take me a while to get it done if I start now, but I've done it 
before for fun. 


My alsa-info:
http://alsa-project.org/db/?f=c1ba1098da13b2d7d6793fbce823e4feed2ac4ee

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

Same as @melser-anton
I installed 2:2.10-6ubuntu1 from ubuntu-updates but still no luck. I followed 
the instructions in #35 and submitted a new bug  #1974040

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Jammy:
  Fix Released

Bug description:
  * Impact

  Connecting to some PEAP wifi doesn't work anymore since the openssl3
  transition

  Details on the issue can be found on
  http://lists.infradead.org/pipermail/hostap/2022-May/040511.html

  * Test case

  Try using a PEAP wifi not implementing RFC5746, it should be able to
  connect

  * Regression potential

  The change allows to connect to less secure WiFis the same way that
  wpa allowed before openssl3, lower security enforcement isn't ideal
  but still better than non working hardware.

  

  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.release-upgrades:
  2022-02-27T21:07:16.553410

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1974040] Re: Cannot connect to PEAP wifi (eduroam)

This looks like the same as bug #1962541
Followed the instructions in comment #35 therein.


** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1974040/+attachment/5590933/+files/journalctl.log

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

Title:
  Cannot connect to PEAP wifi (eduroam)

Status in wpa package in Ubuntu:
  New

Bug description:
  Connection to wifi fails with

  May 18 15:08:55 attila wpa_supplicant[9698]: OpenSSL:
  openssl_handshake - SSL_connect error:0A0C0103:SSL routines::internal
  error

  
  Description:Ubuntu 22.04 LTS
  Release:22.04


  wpasupplicant:
Installed: 2:2.10-6ubuntu1
Candidate: 2:2.10-6ubuntu1
Version table:
   *** 2:2.10-6ubuntu1 1 (phased 40%)
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:2.10-6 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed May 18 15:13:41 2022
  InstallationDate: Installed on 2019-10-22 (938 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1974040/+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 1974040] [NEW] Cannot connect to PEAP wifi (eduroam)

Public bug reported:

Connection to wifi fails with

May 18 15:08:55 attila wpa_supplicant[9698]: OpenSSL: openssl_handshake
- SSL_connect error:0A0C0103:SSL routines::internal error


Description:Ubuntu 22.04 LTS
Release:22.04


wpasupplicant:
  Installed: 2:2.10-6ubuntu1
  Candidate: 2:2.10-6ubuntu1
  Version table:
 *** 2:2.10-6ubuntu1 1 (phased 40%)
500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2:2.10-6 500
500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: wpasupplicant 2:2.10-6ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed May 18 15:13:41 2022
InstallationDate: Installed on 2019-10-22 (938 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: wpa
UpgradeStatus: Upgraded to jammy on 2022-04-22 (26 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Cannot connect to PEAP wifi (eduroam)

Status in wpa package in Ubuntu:
  New

Bug description:
  Connection to wifi fails with

  May 18 15:08:55 attila wpa_supplicant[9698]: OpenSSL:
  openssl_handshake - SSL_connect error:0A0C0103:SSL routines::internal
  error

  
  Description:Ubuntu 22.04 LTS
  Release:22.04


  wpasupplicant:
Installed: 2:2.10-6ubuntu1
Candidate: 2:2.10-6ubuntu1
Version table:
   *** 2:2.10-6ubuntu1 1 (phased 40%)
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:2.10-6 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed May 18 15:13:41 2022
  InstallationDate: Installed on 2019-10-22 (938 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1974040/+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 1974034] [NEW] Printing from evince crashes

2022-05-18 Thread ts

Public bug reported:

$ apt-cache policy evince
evince:
  Installed: 42.1-3
  Candidate: 42.1-3
  Version table:
 *** 42.1-3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status

$ lsb_release -rd
Description:Ubuntu 22.04 LTS
Release:22.04


Opening a PDF from the file browser
Pressing 
Printing dialog opens
I would expect to be able to choose a printer and print

Printing dialog shows "Print to PDF" with all the parameters, also shows
all the possible printers, but freezes, requires "Isn't responding ..
force quit"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evince 42.1-3
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Wed May 18 15:31:30 2022
InstallationDate: Installed on 2022-03-07 (72 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Printing from evince crashes

Status in evince package in Ubuntu:
  New

Bug description:
  $ apt-cache policy evince
  evince:
Installed: 42.1-3
Candidate: 42.1-3
Version table:
   *** 42.1-3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  $ lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  
  Opening a PDF from the file browser
  Pressing 
  Printing dialog opens
  I would expect to be able to choose a printer and print

  Printing dialog shows "Print to PDF" with all the parameters, also
  shows all the possible printers, but freezes, requires "Isn't
  responding .. force quit"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evince 42.1-3
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Wed May 18 15:31:30 2022
  InstallationDate: Installed on 2022-03-07 (72 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1974034/+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 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04

Thanks Ted, I've added the bug reference to the changelog and uploaded
for you

** Changed in: xdg-desktop-portal (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: xdg-desktop-portal-gtk (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: xdg-desktop-portal (Ubuntu Focal)
 Assignee: (unassigned) => Ted Gould (ted)

** Changed in: xdg-desktop-portal-gtk (Ubuntu Focal)
 Assignee: (unassigned) => Ted Gould (ted)

** Description changed:

- The file dialog implementation doesn't return the current filter. It is
- in the spec and it is fixed in newer versions of the portals. But the
- 1.6.0 version doesn't return it.
+ * Impact
+ The file dialog implementation doesn't return the current filter. It is in 
the spec and it is fixed in newer versions of the portals. But the 1.6.0 
version doesn't return it.
  
  This is an issue for Inkscape which uses the filter to select which file
  format someone wishes to save as if they override the defaults. This
  works well on Ubuntu 22.04.
+ 
+ * Test case
+ 
+ $ snap install --candidate inkscape.
+ 
+ In Inkscape if you just draw on the canvas and hit save a save dialog
+ will appear. There is a selector at the bottom right that adjust which
+ files you see, but also which format you want to save in. So if you make
+ your file "test.pdf" and select "Portable Document Format (*.pdf)" in
+ the selector you should get a PDF file. Before these patches you will
+ get a file "test.pdf" which is actually an SVG file. After the patches
+ you'll get a "test.pdf" that is actually a PDF.
+ 
+ * Regression potential
+ 
+ That's a change to the fileselector portal so check that opening and
+ saving files in a few snaps and flatpaks still works as intended

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.04

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Focal:
  Fix Committed
Status in xdg-desktop-portal-gtk source package in Focal:
  Fix Committed

Bug description:
  * Impact
  The file dialog implementation doesn't return the current filter. It is in 
the spec and it is fixed in newer versions of the portals. But the 1.6.0 
version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

  * Test case

  $ snap install --candidate inkscape.

  In Inkscape if you just draw on the canvas and hit save a save dialog
  will appear. There is a selector at the bottom right that adjust which
  files you see, but also which format you want to save in. So if you
  make your file "test.pdf" and select "Portable Document Format
  (*.pdf)" in the selector you should get a PDF file. Before these
  patches you will get a file "test.pdf" which is actually an SVG file.
  After the patches you'll get a "test.pdf" that is actually a PDF.

  * Regression potential

  That's a change to the fileselector portal so check that opening and
  saving files in a few snaps and flatpaks still works as intended

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+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 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04

** Changed in: xdg-desktop-portal (Ubuntu)
   Status: New => Fix Released

** Changed in: xdg-desktop-portal (Ubuntu)
   Importance: Undecided => Low

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
   Importance: Undecided => Low

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
   Status: New => Fix Committed

** Changed in: xdg-desktop-portal-gtk (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: xdg-desktop-portal (Ubuntu Focal)
   Importance: Undecided => Low

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.04

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Committed
Status in xdg-desktop-portal source package in Focal:
  New
Status in xdg-desktop-portal-gtk source package in Focal:
  New

Bug description:
  The file dialog implementation doesn't return the current filter. It
  is in the spec and it is fixed in newer versions of the portals. But
  the 1.6.0 version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+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 1974028] Re: Cheese doesn't start in Wyaland

2022-05-18 Thread Islam

apport-collect and ubuntu-bug are looking for package "linux" however I
provided "cheese".

** Package changed: linux (Ubuntu) => cheese (Ubuntu)

** Changed in: cheese (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Cheese doesn't start in Wyaland

Status in cheese package in Ubuntu:
  Confirmed

Bug description:
  $ WAYLAND_DEBUG=1 cheese 
  [2642509.975]  -> wl_display@1.get_registry(new id wl_registry@2)
  [2642509.993]  -> wl_disp...@1.sync(new id wl_callback@3)
  [2642510.089] wl_display@1.delete_id(3)
  [2642510.101] wl_registry@2.global(1, "wl_compositor", 5)
  [2642510.110]  -> wl_regis...@2.bind(1, "wl_compositor", 3, new id 
[unknown]@4)
  [2642510.122] wl_registry@2.global(2, "wl_drm", 2)
  [2642510.131] wl_registry@2.global(3, "wl_shm", 1)
  [2642510.138]  -> wl_regis...@2.bind(3, "wl_shm", 1, new id [unknown]@5)
  [2642510.147] wl_registry@2.global(5, "wl_output", 2)
  [2642510.154]  -> wl_regis...@2.bind(5, "wl_output", 2, new id [unknown]@6)
  [2642510.217]  -> wl_disp...@1.sync(new id wl_callback@7)
  [2642510.223] wl_registry@2.global(6, "zxdg_output_manager_v1", 3)
  [2642510.233]  -> wl_regis...@2.bind(6, "zxdg_output_manager_v1", 3, new id 
[unknown]@8)
  [2642510.245]  -> zxdg_output_manager_v1@8.get_xdg_output(new id 
zxdg_output_v1@9, wl_output@6)
  [2642510.252]  -> wl_disp...@1.sync(new id wl_callback@10)
  [2642510.258] wl_registry@2.global(7, "wl_data_device_manager", 3)
  [2642510.266]  -> wl_regis...@2.bind(7, "wl_data_device_manager", 3, new id 
[unknown]@11)
  [2642510.278] wl_registry@2.global(8, 
"zwp_primary_selection_device_manager_v1", 1)
  [2642510.283]  -> wl_regis...@2.bind(8, 
"zwp_primary_selection_device_manager_v1", 1, new id [unknown]@12)
  [2642510.291] wl_registry@2.global(9, "gtk_primary_selection_device_manager", 
1)
  [2642510.295]  -> wl_regis...@2.bind(9, 
"gtk_primary_selection_device_manager", 1, new id [unknown]@13)
  [2642510.300] wl_registry@2.global(10, "wl_subcompositor", 1)
  [2642510.305]  -> wl_regis...@2.bind(10, "wl_subcompositor", 1, new id 
[unknown]@14)
  [2642510.313] wl_registry@2.global(11, "xdg_wm_base", 4)
  [2642510.320] wl_registry@2.global(12, "zxdg_shell_v6", 1)
  [2642510.326] wl_registry@2.global(13, "gtk_shell1", 5)
  [2642510.332]  -> wl_regis...@2.bind(13, "gtk_shell1", 4, new id [unknown]@15)
  [2642510.337] wl_registry@2.global(14, "wp_viewporter", 1)
  [2642510.342] wl_registry@2.global(15, "zwp_pointer_gestures_v1", 3)
  [2642510.348]  -> wl_regis...@2.bind(15, "zwp_pointer_gestures_v1", 1, new id 
[unknown]@16)
  [2642510.354] wl_registry@2.global(16, "zwp_tablet_manager_v2", 1)
  [2642510.359]  -> wl_regis...@2.bind(16, "zwp_tablet_manager_v2", 1, new id 
[unknown]@17)
  [2642510.366] wl_registry@2.global(17, "wl_seat", 5)
  [2642510.372] wl_registry@2.global(18, "zwp_relative_pointer_manager_v1", 1)
  [2642510.376] wl_registry@2.global(19, "zwp_pointer_constraints_v1", 1)
  [2642510.382] wl_registry@2.global(20, "zxdg_exporter_v1", 1)
  [2642510.388]  -> wl_regis...@2.bind(20, "zxdg_exporter_v1", 1, new id 
[unknown]@18)
  [2642510.397] wl_registry@2.global(21, "zxdg_importer_v1", 1)
  [2642510.402]  -> wl_regis...@2.bind(21, "zxdg_importer_v1", 1, new id 
[unknown]@19)
  [2642510.409] wl_registry@2.global(22, "zwp_linux_dmabuf_v1", 4)
  [2642510.416] wl_registry@2.global(23, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [2642510.421]  -> wl_regis...@2.bind(23, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1, new id [unknown]@20)
  [2642510.431] wl_registry@2.global(24, "zwp_text_input_manager_v3", 1)
  [2642510.438] wl_registry@2.global(25, "wp_presentation", 1)
  [2642510.444] wl_registry@2.global(26, "xdg_activation_v1", 1)
  [2642510.449] wl_callb...@3.done(23195)
  [2642510.485]  -> wl_shm@5.create_pool(new id wl_shm_pool@3, fd 10, 2304)
  [2642510.623]  -> wl_shm_pool@3.resize(6912)
  [2642510.669]  -> wl_shm_pool@3.resize(16128)
  [2642510.745]  -> wl_shm_pool@3.resize(34560)
  [2642510.909]  -> wl_shm_pool@3.resize(71424)
  [2642511.697]  -> wl_shm_pool@3.resize(145152)
  [2642511.753]  -> wl_shm_pool@3.resize(292608)
  [2642512.954]  -> wl_shm_pool@3.resize(587520)
  [2642514.901]  -> wl_shm_pool@3.resize(1177344)
  [2642517.838]  -> wl_shm_pool@3.resize(2356992)
  [2642526.562]  -> wl_regis...@2.bind(17, "wl_seat", 5, new id [unknown]@21)
  [2642528.370]  -> wl_compositor@4.create_surface(new id wl_surface@22)
  [2642528.384]  -> zwp_primary_selection_device_manager_v1@12.get_device(new 
id zwp_primary_selection_device_v1@23, wl_seat@21)
  [2642528.389]  -> wl_data_device_manager@11.get_data_device(new id 
wl_data_device@24, wl_seat@21)
  [2642528.444]  -> wl_compositor@4.create_surface(new id wl_surface@25)
  [2642528.447]  -> zwp_tablet_manager_v2@17.get_tablet_seat(new id 
zwp_tablet_seat_v2@26, wl_seat@21)
  [2642528.451]  ->

[Desktop-packages] [Bug 1971415] Re: Remote desktop is automatically enabled after login

Here's an updated debdiff to also handle VNC. The debdiff is against the
version already in jammy.

** Patch added: "gnome-control-center-lp1971415-version2.debdiff"

https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1971415/+attachment/5590908/+files/gnome-control-center-lp1971415-version2.debdiff

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

Title:
Remote desktop is automatically enabled after login

Status in gnome-control-center package in Ubuntu:
Fix Released
Status in gnome-control-center source package in Jammy:
Confirmed

Bug description:
Details:
Turning off RDP Remote Desktop Sharing with gnome-control-center would only
turn off RDP sharing for the current session. Upon logging back in, RDP Sharing
would be enabled again without any additional user interaction or notification.

Other Info:
As mentioned in the comments at
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1825
this issue could have been avoided if Ubuntu's gnome-remote-desktop didn't
keep the systemd user service always running. I do intend to fix that issue
also but it is a more complicated fix. I think it will require a maintainer
script to remove the automatic conffiles added by dh. I will do the
gnome-remote-desktop bugfix as a normal non-security SRU.

Original Bug Report:
If I disable sharing/remote desktop in GNOME Control Center, then log out and
back in, it is automatically enabled again. I report this as a security
vulnerability because remote desktop is enabled without the user's knowledge.

Software versions:
- Ubuntu 22.04
- gnome-remote-desktop 42.0-4ubuntu1
- gnome-control-center 1:41.4-1ubuntu13

Steps to reproduce:
1. Start with Remote Desktop enabled. "systemctl --user status
gnome-remote-desktop.service" reports "active (running)".
2. Disable Remote Desktop in Control Center. systemctl reports "inactive
(dead)".
3. Log out and back in.
4. Open Control Center. Remote Desktop is enabled again. systemctl reports
"active (running)".

Expected behavior:
Remote Desktop should stay disabled upon the new login.

Actual behavior:
Remote Desktop was automatically enabled again.

Previous discussion: https://gitlab.gnome.org/GNOME/gnome-control-
center/-/issues/1775#note_1443319

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

[Desktop-packages] [Bug 1974028] [NEW] Cheese doesn't start in Wyaland

You have been subscribed to a public bug:

$ WAYLAND_DEBUG=1 cheese 
[2642509.975]  -> wl_display@1.get_registry(new id wl_registry@2)
[2642509.993]  -> wl_disp...@1.sync(new id wl_callback@3)
[2642510.089] wl_display@1.delete_id(3)
[2642510.101] wl_registry@2.global(1, "wl_compositor", 5)
[2642510.110]  -> wl_regis...@2.bind(1, "wl_compositor", 3, new id [unknown]@4)
[2642510.122] wl_registry@2.global(2, "wl_drm", 2)
[2642510.131] wl_registry@2.global(3, "wl_shm", 1)
[2642510.138]  -> wl_regis...@2.bind(3, "wl_shm", 1, new id [unknown]@5)
[2642510.147] wl_registry@2.global(5, "wl_output", 2)
[2642510.154]  -> wl_regis...@2.bind(5, "wl_output", 2, new id [unknown]@6)
[2642510.217]  -> wl_disp...@1.sync(new id wl_callback@7)
[2642510.223] wl_registry@2.global(6, "zxdg_output_manager_v1", 3)
[2642510.233]  -> wl_regis...@2.bind(6, "zxdg_output_manager_v1", 3, new id 
[unknown]@8)
[2642510.245]  -> zxdg_output_manager_v1@8.get_xdg_output(new id 
zxdg_output_v1@9, wl_output@6)
[2642510.252]  -> wl_disp...@1.sync(new id wl_callback@10)
[2642510.258] wl_registry@2.global(7, "wl_data_device_manager", 3)
[2642510.266]  -> wl_regis...@2.bind(7, "wl_data_device_manager", 3, new id 
[unknown]@11)
[2642510.278] wl_registry@2.global(8, 
"zwp_primary_selection_device_manager_v1", 1)
[2642510.283]  -> wl_regis...@2.bind(8, 
"zwp_primary_selection_device_manager_v1", 1, new id [unknown]@12)
[2642510.291] wl_registry@2.global(9, "gtk_primary_selection_device_manager", 1)
[2642510.295]  -> wl_regis...@2.bind(9, "gtk_primary_selection_device_manager", 
1, new id [unknown]@13)
[2642510.300] wl_registry@2.global(10, "wl_subcompositor", 1)
[2642510.305]  -> wl_regis...@2.bind(10, "wl_subcompositor", 1, new id 
[unknown]@14)
[2642510.313] wl_registry@2.global(11, "xdg_wm_base", 4)
[2642510.320] wl_registry@2.global(12, "zxdg_shell_v6", 1)
[2642510.326] wl_registry@2.global(13, "gtk_shell1", 5)
[2642510.332]  -> wl_regis...@2.bind(13, "gtk_shell1", 4, new id [unknown]@15)
[2642510.337] wl_registry@2.global(14, "wp_viewporter", 1)
[2642510.342] wl_registry@2.global(15, "zwp_pointer_gestures_v1", 3)
[2642510.348]  -> wl_regis...@2.bind(15, "zwp_pointer_gestures_v1", 1, new id 
[unknown]@16)
[2642510.354] wl_registry@2.global(16, "zwp_tablet_manager_v2", 1)
[2642510.359]  -> wl_regis...@2.bind(16, "zwp_tablet_manager_v2", 1, new id 
[unknown]@17)
[2642510.366] wl_registry@2.global(17, "wl_seat", 5)
[2642510.372] wl_registry@2.global(18, "zwp_relative_pointer_manager_v1", 1)
[2642510.376] wl_registry@2.global(19, "zwp_pointer_constraints_v1", 1)
[2642510.382] wl_registry@2.global(20, "zxdg_exporter_v1", 1)
[2642510.388]  -> wl_regis...@2.bind(20, "zxdg_exporter_v1", 1, new id 
[unknown]@18)
[2642510.397] wl_registry@2.global(21, "zxdg_importer_v1", 1)
[2642510.402]  -> wl_regis...@2.bind(21, "zxdg_importer_v1", 1, new id 
[unknown]@19)
[2642510.409] wl_registry@2.global(22, "zwp_linux_dmabuf_v1", 4)
[2642510.416] wl_registry@2.global(23, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
[2642510.421]  -> wl_regis...@2.bind(23, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1, new id [unknown]@20)
[2642510.431] wl_registry@2.global(24, "zwp_text_input_manager_v3", 1)
[2642510.438] wl_registry@2.global(25, "wp_presentation", 1)
[2642510.444] wl_registry@2.global(26, "xdg_activation_v1", 1)
[2642510.449] wl_callb...@3.done(23195)
[2642510.485]  -> wl_shm@5.create_pool(new id wl_shm_pool@3, fd 10, 2304)
[2642510.623]  -> wl_shm_pool@3.resize(6912)
[2642510.669]  -> wl_shm_pool@3.resize(16128)
[2642510.745]  -> wl_shm_pool@3.resize(34560)
[2642510.909]  -> wl_shm_pool@3.resize(71424)
[2642511.697]  -> wl_shm_pool@3.resize(145152)
[2642511.753]  -> wl_shm_pool@3.resize(292608)
[2642512.954]  -> wl_shm_pool@3.resize(587520)
[2642514.901]  -> wl_shm_pool@3.resize(1177344)
[2642517.838]  -> wl_shm_pool@3.resize(2356992)
[2642526.562]  -> wl_regis...@2.bind(17, "wl_seat", 5, new id [unknown]@21)
[2642528.370]  -> wl_compositor@4.create_surface(new id wl_surface@22)
[2642528.384]  -> zwp_primary_selection_device_manager_v1@12.get_device(new id 
zwp_primary_selection_device_v1@23, wl_seat@21)
[2642528.389]  -> wl_data_device_manager@11.get_data_device(new id 
wl_data_device@24, wl_seat@21)
[2642528.444]  -> wl_compositor@4.create_surface(new id wl_surface@25)
[2642528.447]  -> zwp_tablet_manager_v2@17.get_tablet_seat(new id 
zwp_tablet_seat_v2@26, wl_seat@21)
[2642528.451]  -> wl_disp...@1.sync(new id wl_callback@27)
[2642528.626] wl_display@1.delete_id(7)
[2642528.631] wl_display@1.delete_id(10)
[2642528.633] wl_display@1.delete_id(27)
[2642528.638] wl_shm@5.format(0)
[2642528.641] wl_shm@5.format(1)
[2642528.643] wl_shm@5.format(875708993)
[2642528.647] wl_shm@5.format(875709016)
[2642528.650] wl_shm@5.format(909199186)
[2642528.653] wl_shm@5.format(808669761)
[2642528.656] wl_shm@5.format(808669784)
[2642528.659] wl_shm@5.format(808665665)
[2642528.662] wl_shm@5.format(808665688)
[2642528.665] wl_shm@5.format(1211388481)
[2642528.669]

[Desktop-packages] [Bug 1973660] Re: [vmwgfx] Login screen not refreshing properly on vSphere when WaylandEnable=false

2022-05-18 Thread Hank Keanu

Thanks for your information, Daniel!

Then please feel free to close this issue.

Again, thanks for your prompt help!

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

Title:
  [vmwgfx] Login screen not refreshing properly on vSphere when
  WaylandEnable=false

Status in xserver-xorg-video-vmware package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using,
  gnome-shell:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 3.36.9-0ubuntu0.20.04.2
Version table:
   *** 3.36.9-0ubuntu0.20.04.2 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal-updates/main amd64 
Packages
  500 http://cn.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal/main amd64 Packages
  500 http://cn.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) What you expected to happen
  The login screen can resize properly and all its widgets shows properly. 

  4) What happened instead
  Login screen doesn't refresh properly when resize vShpere window, so that 
can't input username and password. And I found pressing Ctl-Alt-Tab can force 
the login screen refresh.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
   b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
   b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
   b'org.gnome.desktop.screensaver' b'lock-enabled' b'false'
   b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
  InstallationDate: Installed on 2020-08-13 (641 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 [modified: 
usr/lib/gnome-shell/libgnome-shell.so]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1973660/+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 1974018] Re: dmesg

2022-05-18 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  dmesg

Status in xorg package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:Ubuntu 22.04 LTS
  Release:22.04

  [   29.170087] 

  [   29.170097] UBSAN: invalid-load in 
/build/linux-WD899k/linux-5.15.0/net/mac80211/status.c:1164:21
  [   29.170102] load of value 255 is not a valid value for type '_Bool'
  [   29.170105] CPU: 3 PID: 549 Comm: in:imuxsock Tainted: P   OE 
5.15.0-30-generic #31-Ubuntu
  [   29.170110] Hardware name: ASUSTeK COMPUTER INC. X550CL/X550CL, BIOS 
X550CL.204 10/17/2013
  [   29.170113] Call Trace:
  [   29.170116]  
  [   29.170119]  show_stack+0x52/0x58
  [   29.170128]  dump_stack_lvl+0x4a/0x5f
  [   29.170136]  dump_stack+0x10/0x12
  [   29.170140]  ubsan_epilogue+0x9/0x45
  [   29.170144]  __ubsan_handle_load_invalid_value.cold+0x44/0x49
  [   29.170149]  ieee80211_tx_status_ext.cold+0x4e/0x5f [mac80211]
  [   29.170251]  ieee80211_tx_status+0x72/0xa0 [mac80211]
  [   29.170320]  ath_txq_unlock_complete+0x12d/0x160 [ath9k]
  [   29.170336]  ath_tx_edma_tasklet+0xef/0x4c0 [ath9k]
  [   29.170349]  ? del_timer_sync+0x6c/0xb0
  [   29.170355]  ath9k_tasklet+0x14e/0x290 [ath9k]
  [   29.170367]  tasklet_action_common.constprop.0+0xc0/0xf0
  [   29.170373]  tasklet_action+0x22/0x30
  [   29.170378]  __do_softirq+0xd9/0x2e3
  [   29.170385]  irq_exit_rcu+0x8c/0xb0
  [   29.170389]  common_interrupt+0x8a/0xa0
  [   29.170396]  
  [   29.170398]  
  [   29.170400]  asm_common_interrupt+0x1e/0x40
  [   29.170404] RIP: 0010:copy_user_generic_unrolled+0x89/0xc0
  [   29.170411] Code: 38 4c 89 47 20 4c 89 4f 28 4c 89 57 30 4c 89 5f 38 48 8d 
76 40 48 8d 7f 40 ff c9 75 b6 89 d1 83 e2 07 c1 e9 03 74 12 4c 8b 06 <4c> 89 07 
48 8d 76 08 48 8d 7f 08 ff c9 75 ee 21 d2 74 10 89 d1 8a
  [   29.170414] RSP: 0018:ae00c0b83c10 EFLAGS: 0202
  [   29.170419] RAX: 7f4885d52298 RBX: ae00c0b83c40 RCX: 
0007
  [   29.170422] RDX:  RSI: 7f4885d52260 RDI: 
ae00c0b83c40
  [   29.170424] RBP: ae00c0b83c30 R08:  R09: 
9a32e177e418
  [   29.170427] R10:  R11:  R12: 
0038
  [   29.170429] R13: ae00c0b83cd8 R14: ae00c0b83ce0 R15: 
0040
  [   29.170434]  ? _copy_from_user+0x2e/0x60
  [   29.170440]  __copy_msghdr_from_user+0x3d/0x130
  [   29.170446]  ___sys_recvmsg+0x68/0x110
  [   29.170450]  ? check_preempt_curr+0x5d/0x70
  [   29.170455]  ? ttwu_do_wakeup+0x1c/0x160
  [   29.170460]  ? rseq_get_rseq_cs.isra.0+0x1b/0x220
  [   29.170466]  ? ttwu_do_activate+0x72/0xf0
  [   29.170470]  ? __fget_files+0x86/0xc0
  [   29.170476]  ? __fget_light+0x32/0x80
  [   29.170481]  __sys_recvmsg+0x5f/0xb0
  [   29.170485]  ? switch_fpu_return+0x4e/0xc0
  [   29.170491]  ? exit_to_user_mode_prepare+0x92/0xb0
  [   29.170496]  ? syscall_exit_to_user_mode+0x27/0x50
  [   29.170501]  __x64_sys_recvmsg+0x1d/0x20
  [   29.170505]  do_syscall_64+0x5c/0xc0
  [   29.170510]  ? __x64_sys_futex+0x78/0x1e0
  [   29.170515]  ? exit_to_user_mode_prepare+0x37/0xb0
  [   29.170520]  ? syscall_exit_to_user_mode+0x27/0x50
  [   29.170524]  ? do_syscall_64+0x69/0xc0
  [   29.170528]  ? do_syscall_64+0x69/0xc0
  [   29.170533]  ? do_syscall_64+0x69/0xc0
  [   29.170537]  ? do_syscall_64+0x69/0xc0
  [   29.170541]  ? asm_common_interrupt+0x8/0x40
  [   29.170546]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   29.170550] RIP: 0033:0x7f48864179ef
  [   29.170554] Code: 44 00 00 89 54 24 0c 48 89 34 24 89 7c 24 08 e8 97 90 f6 
ff 8b 54 24 0c 48 8b 34 24 41 89 c0 8b 7c 24 08 b8 2f 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 31 4c 63 e0 44 89 c7 e8 de 90 f6 ff 48 83 c4
  [   29.170557] RSP: 002b:7f4885d52140 EFLAGS: 0293 ORIG_RAX: 
002f
  [   29.170561] RAX: ffda RBX:  RCX: 
7f48864179ef
  [   29.170564] RDX: 0040 RSI: 7f4885d52260 RDI: 
0003
  [   29.170566] RBP:  R08:  R09: 
7f4878000bb0
  [   29.170568] R10: 7f4878002b50 R11: 0293 R12: 
55d6ce037580
  [   29.170570] R13: 55d6cc64e4cc R14: 1fa0 R15: 
7f4878000bb0
  [   29.170575]  
  [   29.170585] 


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Wed May 18 13:36:06 2022
  DistUpgraded: 2022-05-16 13:44:28,450 DEBUG /openCache(), new

[Desktop-packages] [Bug 1974026] [NEW] webdav doesn't work with folder

2022-05-18 Thread Matthias Sprau

Public bug reported:

If I try with ubuntu 22.04 in nautilus "connect to server" with an
address like

`davs://webdav.foo.de/__test-intern`

I'm connected only to: davs://webdav.foo.de/

With Ubuntu 20.04 the connection is established as desired and still
works.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 18 14:00:54 2022
GsettingsChanges:
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
 b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 
'permissions', 'date_modified', 'starred']"
 b'org.gnome.nautilus.window-state' b'initial-size' b'(924, 1006)'
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
InstallationDate: Installed on 2022-04-22 (26 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 evince42.1-3
 file-roller   3.42.0-1
 nautilus-extension-brasero3.12.3-1
 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
 nautilus-share0.7.3-2ubuntu6

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  webdav doesn't work with folder

Status in nautilus package in Ubuntu:
  New

Bug description:
  If I try with ubuntu 22.04 in nautilus "connect to server" with an
  address like

  `davs://webdav.foo.de/__test-intern`

  I'm connected only to: davs://webdav.foo.de/

  With Ubuntu 20.04 the connection is established as desired and still
  works.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 18 14:00:54 2022
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'permissions', 'date_modified', 'starred']"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(924, 1006)'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
  InstallationDate: Installed on 2022-04-22 (26 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-brasero3.12.3-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1974026/+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 1973733] Re: no change rebuild to get security update out on riscv64

2022-05-18 Thread Robie Basak

Ah - is it that the same version is now built and published in Groovy
and we can't safely copy the binary backwards? If so, then my second
question of why this isn't going in via focal-security still stands.

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

Title:
  no change rebuild to get security update out on riscv64

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

Bug description:
  no change rebuild to get riscv64 build out

  [Impact]

   * riscv64 build of cups security update failed, and then succeeded in 
groovy. See https://launchpad.net/ubuntu/+source/cups/2.3.1-9ubuntu1.1
   * it means that focal-updates & focal-security are lacking a security update 
of cups on riscv64
   * do a no change rebuild of cups as an SRU to get updated cups package out 
on focal

  [Test Plan]

   * autopkgtests pass
   * riscv64 build is successful

  [Where problems could occur]

   * As usual, no change rebuilds of packages may introduce miss builds.

  [Other Info]

   * currently snap review tooling reports that cups has CVEs on riscv64
  when one builds base:core20 snaps for riscv64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+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 1974018] [NEW] dmesg

You have been subscribed to a public bug:

$ lsb_release -rd
Description:Ubuntu 22.04 LTS
Release:22.04

[   29.170087] 

[   29.170097] UBSAN: invalid-load in 
/build/linux-WD899k/linux-5.15.0/net/mac80211/status.c:1164:21
[   29.170102] load of value 255 is not a valid value for type '_Bool'
[   29.170105] CPU: 3 PID: 549 Comm: in:imuxsock Tainted: P   OE 
5.15.0-30-generic #31-Ubuntu
[   29.170110] Hardware name: ASUSTeK COMPUTER INC. X550CL/X550CL, BIOS 
X550CL.204 10/17/2013
[   29.170113] Call Trace:
[   29.170116]  
[   29.170119]  show_stack+0x52/0x58
[   29.170128]  dump_stack_lvl+0x4a/0x5f
[   29.170136]  dump_stack+0x10/0x12
[   29.170140]  ubsan_epilogue+0x9/0x45
[   29.170144]  __ubsan_handle_load_invalid_value.cold+0x44/0x49
[   29.170149]  ieee80211_tx_status_ext.cold+0x4e/0x5f [mac80211]
[   29.170251]  ieee80211_tx_status+0x72/0xa0 [mac80211]
[   29.170320]  ath_txq_unlock_complete+0x12d/0x160 [ath9k]
[   29.170336]  ath_tx_edma_tasklet+0xef/0x4c0 [ath9k]
[   29.170349]  ? del_timer_sync+0x6c/0xb0
[   29.170355]  ath9k_tasklet+0x14e/0x290 [ath9k]
[   29.170367]  tasklet_action_common.constprop.0+0xc0/0xf0
[   29.170373]  tasklet_action+0x22/0x30
[   29.170378]  __do_softirq+0xd9/0x2e3
[   29.170385]  irq_exit_rcu+0x8c/0xb0
[   29.170389]  common_interrupt+0x8a/0xa0
[   29.170396]  
[   29.170398]  
[   29.170400]  asm_common_interrupt+0x1e/0x40
[   29.170404] RIP: 0010:copy_user_generic_unrolled+0x89/0xc0
[   29.170411] Code: 38 4c 89 47 20 4c 89 4f 28 4c 89 57 30 4c 89 5f 38 48 8d 
76 40 48 8d 7f 40 ff c9 75 b6 89 d1 83 e2 07 c1 e9 03 74 12 4c 8b 06 <4c> 89 07 
48 8d 76 08 48 8d 7f 08 ff c9 75 ee 21 d2 74 10 89 d1 8a
[   29.170414] RSP: 0018:ae00c0b83c10 EFLAGS: 0202
[   29.170419] RAX: 7f4885d52298 RBX: ae00c0b83c40 RCX: 0007
[   29.170422] RDX:  RSI: 7f4885d52260 RDI: ae00c0b83c40
[   29.170424] RBP: ae00c0b83c30 R08:  R09: 9a32e177e418
[   29.170427] R10:  R11:  R12: 0038
[   29.170429] R13: ae00c0b83cd8 R14: ae00c0b83ce0 R15: 0040
[   29.170434]  ? _copy_from_user+0x2e/0x60
[   29.170440]  __copy_msghdr_from_user+0x3d/0x130
[   29.170446]  ___sys_recvmsg+0x68/0x110
[   29.170450]  ? check_preempt_curr+0x5d/0x70
[   29.170455]  ? ttwu_do_wakeup+0x1c/0x160
[   29.170460]  ? rseq_get_rseq_cs.isra.0+0x1b/0x220
[   29.170466]  ? ttwu_do_activate+0x72/0xf0
[   29.170470]  ? __fget_files+0x86/0xc0
[   29.170476]  ? __fget_light+0x32/0x80
[   29.170481]  __sys_recvmsg+0x5f/0xb0
[   29.170485]  ? switch_fpu_return+0x4e/0xc0
[   29.170491]  ? exit_to_user_mode_prepare+0x92/0xb0
[   29.170496]  ? syscall_exit_to_user_mode+0x27/0x50
[   29.170501]  __x64_sys_recvmsg+0x1d/0x20
[   29.170505]  do_syscall_64+0x5c/0xc0
[   29.170510]  ? __x64_sys_futex+0x78/0x1e0
[   29.170515]  ? exit_to_user_mode_prepare+0x37/0xb0
[   29.170520]  ? syscall_exit_to_user_mode+0x27/0x50
[   29.170524]  ? do_syscall_64+0x69/0xc0
[   29.170528]  ? do_syscall_64+0x69/0xc0
[   29.170533]  ? do_syscall_64+0x69/0xc0
[   29.170537]  ? do_syscall_64+0x69/0xc0
[   29.170541]  ? asm_common_interrupt+0x8/0x40
[   29.170546]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   29.170550] RIP: 0033:0x7f48864179ef
[   29.170554] Code: 44 00 00 89 54 24 0c 48 89 34 24 89 7c 24 08 e8 97 90 f6 
ff 8b 54 24 0c 48 8b 34 24 41 89 c0 8b 7c 24 08 b8 2f 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 31 4c 63 e0 44 89 c7 e8 de 90 f6 ff 48 83 c4
[   29.170557] RSP: 002b:7f4885d52140 EFLAGS: 0293 ORIG_RAX: 
002f
[   29.170561] RAX: ffda RBX:  RCX: 7f48864179ef
[   29.170564] RDX: 0040 RSI: 7f4885d52260 RDI: 0003
[   29.170566] RBP:  R08:  R09: 7f4878000bb0
[   29.170568] R10: 7f4878002b50 R11: 0293 R12: 55d6ce037580
[   29.170570] R13: 55d6cc64e4cc R14: 1fa0 R15: 7f4878000bb0
[   29.170575]  
[   29.170585] 


ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CompositorRunning: None
Date: Wed May 18 13:36:06 2022
DistUpgraded: 2022-05-16 13:44:28,450 DEBUG /openCache(), new cache size 71860
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed
 virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
 virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem:

[Desktop-packages] [Bug 1971415] Re: Remote desktop is automatically enabled after login

2022-05-18 Thread Marc Deslauriers

This patch is still broken. The same thing happens with VNC:

1- Turn on remote desktop, turn on VNC.
2- Only turn off remote desktop while leaving VNC checked
3- Reboot
4- The VNC port is listening to connections even though remote desktop says off
in the 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/1971415

Title:
Remote desktop is automatically enabled after login

Status in gnome-control-center package in Ubuntu:
Fix Released
Status in gnome-control-center source package in Jammy:
Confirmed

Software versions:
- Ubuntu 22.04
- gnome-remote-desktop 42.0-4ubuntu1
- gnome-control-center 1:41.4-1ubuntu13

Expected behavior:
Remote Desktop should stay disabled upon the new login.

Actual behavior:
Remote Desktop was automatically enabled again.

Previous discussion: https://gitlab.gnome.org/GNOME/gnome-control-
center/-/issues/1775#note_1443319

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

[Desktop-packages] [Bug 1753677] Re: es2gears_wayland on mutter sticks to 119 FPS on a 59.95Hz display

2022-05-18 Thread Bug Watch Updater

** Changed in: mesa
   Status: New => Fix Released

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

Title:
  es2gears_wayland on mutter sticks to 119 FPS on a 59.95Hz display

Status in Mesa:
  Fix Released
Status in mesa-demos package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  es2gears_wayland sticks to 119 FPS on a 59.95Hz display

  $ es2gears_wayland
  EGL_VERSION = 1.4 (DRI2)
  vertex shader info:
  fragment shader info:
  info:
  597 frames in 5.0 seconds = 119.138 FPS
  600 frames in 5.0 seconds = 119.880 FPS
  598 frames in 5.0 seconds = 119.481 FPS
  600 frames in 5.0 seconds = 119.952 FPS
  600 frames in 5.0 seconds = 119.880 FPS
  600 frames in 5.0 seconds = 119.880 FPS
  596 frames in 5.0 seconds = 119.105 FPS

  $ es2gears_x11
  EGL_VERSION = 1.4 (DRI2)
  vertex shader info:
  fragment shader info:
  info:
  315 frames in 5.0 seconds = 62.837 FPS
  300 frames in 5.0 seconds = 60.000 FPS
  300 frames in 5.0 seconds = 60.000 FPS
  300 frames in 5.0 seconds = 60.000 FPS
  300 frames in 5.0 seconds = 60.000 FPS
  301 frames in 5.0 seconds = 60.008 FPS

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mesa-utils-extra 8.4.0-1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Mar  6 16:39:18 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3 Processor Integrated Graphics Controller 
[8086:041a] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Xeon E3-1200 v3 Processor Integrated Graphics Controller 
[17aa:30a1]
  InstallationDate: Installed on 2017-12-12 (84 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  MachineType: LENOVO 30AJS05700
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=f9fe7460-9c41-4d4a-8376-e5ceb57bbec8 ro quiet splash vt.handoff=1
  SourcePackage: mesa-demos
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTB6AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50519 PRO
  dmi.chassis.type: 7
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 30AJS05700
  dmi.product.version: ThinkStation P300
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1753677/+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 1973733] Re: no change rebuild to get security update out on riscv64

2022-05-18 Thread Robie Basak

I'm not sure I follow. I see a retry button for the failed riscv64
build. Can't we just hit that?

If there's some reason that won't work, then why is this not going
through the security sponsorship queue? If we do it as an SRU, then
it'll hit focal-updates only, and focal-security will be left behind.
What's the plan for that?

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

Title:
  no change rebuild to get security update out on riscv64

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

Bug description:
  no change rebuild to get riscv64 build out

  [Impact]

   * riscv64 build of cups security update failed, and then succeeded in 
groovy. See https://launchpad.net/ubuntu/+source/cups/2.3.1-9ubuntu1.1
   * it means that focal-updates & focal-security are lacking a security update 
of cups on riscv64
   * do a no change rebuild of cups as an SRU to get updated cups package out 
on focal

  [Test Plan]

   * autopkgtests pass
   * riscv64 build is successful

  [Where problems could occur]

   * As usual, no change rebuilds of packages may introduce miss builds.

  [Other Info]

   * currently snap review tooling reports that cups has CVEs on riscv64
  when one builds base:core20 snaps for riscv64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+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 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution

2022-05-18 Thread Dani Llewellyn

I've updated the PR with a fix for this ugly message

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

Title:
  "xdg-settings check default-web-browser something.desktop" fails in
  Kubuntu 22.04: Bad substitution

Status in Xdg-utils:
  Unknown
Status in xdg-utils package in Ubuntu:
  Fix Released
Status in xdg-utils source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  The firefox snap (default in 22.04) will always report that it thinks
  it's not the default browser (even when it actually is) for KDE users
  (this can be seen when browsing to about:preferences).

  This is caused by an upstream bug in xdg-utils (using bashisms in KDE-
  specific functions whereas the default interpreter is dash).

  The fix is rather trivial and will visibly improve the UX for those
  users.

  
  [Test Plan]

  In Kubuntu 22.04:
   - make sure firefox isn't your default browser (by changing the setting to a 
different browser)
   - run the firefox snap, browse to "about:preferences", and observe that 
firefox claims NOT to be the default browser
   - click the "Set default" button
   - refresh the page (F5)
   - observe that now firefox claims to be the default browser
   - in a terminal, execute `xdg-open https://example.org`, and verify that the 
page is open in the firefox snap

  [Where problems could occur]

  The patch is changing KDE-specific functions (check_browser_kde and
  check_url_scheme_handler_kde), so in theory it shouldn't affect
  running xdg-utils in any other desktop environment.

  If the proposed patch is incorrect, it would affect the functionality
  of `xdg-settings check default-web-browser` and `xdg-settings check
  default-url-scheme-handler`, so this is what needs to be thoroughly
  tested in KDE.

  In the event of a regression, these functions wouldn't work as
  expected (they already don't, so the user wouldn't observe a
  functional regression, merely the absence of a fix).

  
  [Original description]

  I'm reporting this issue from stock Ubuntu, but the problem is
  observed only in Kubuntu (can be reliably reproduced in a Kubuntu
  22.04 VM). The version of xdg-utils is identical.

  This problem was initially reported on the snapcraft forum:
  https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
  browser/29708.

  $ xdg-settings check default-web-browser firefox_firefox.desktop
  /usr/bin/xdg-settings: 734: Bad substitution

  The offending line is:

  if [ x"!" == x"${browser:0:1}" ]; then

  If I modify /usr/bin/xdg-settings in place to set the interpreter to
  /bin/bash on the first line of the script, the problem goes away.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xdg-utils 1.1.3-4.1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 11:21:31 2022
  InstallationDate: Installed on 2020-09-16 (587 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  PackageArchitecture: all
  SourcePackage: xdg-utils
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1970594/+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 1965536] Re: Network icon disappeared in Unity

2022-05-18 Thread Anton (Jabberwocky) Kuchin

Had the same problem but it seems to be fixed after installing 
'indicator-applet' and 'indicator-application' packages. I think they were 
removed during upgrade for some reason.
I'm not sure both of them are required and believe 'indicator-applet' could fix 
this alone, but I'm just happy network icon is back and too lazy to double 
check which package fixed it.

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

Title:
  Network icon disappeared in Unity

Status in network-manager-applet package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 22.04, the network icon at the top right of
  the screen in Unity has disappeared. The only way to change wireless
  network is now gear icon -> System Settings -> Network.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager-gnome 1.24.0-1ubuntu3
  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: Unity:Unity7:ubuntu
  Date: Fri Mar 18 14:07:50 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2020-07-14 (611 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 10.0.0.1 dev wlp0s20f3 proto dhcp metric 600 
   10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 
   10.0.0.0/19 dev wlp0s20f3 proto kernel scope link src 10.0.7.124 metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
  SourcePackage: network-manager-applet
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1965536/+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 1973802] Re: Gnome Shell crashes when disconnecting external monitor

Try 'apport-cli' if 'ubuntu-bug' fails.

After the upload attempt also look at https://errors.ubuntu.com/user/ID
where ID is the content of file /var/lib/whoopsie/whoopsie-id on the
machine. Do you find any links to recent problems on that page? If so
then please send the links to us.

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

Title:
  Gnome Shell crashes when disconnecting external monitor

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04, gnome-shell 42.0-2ubuntu1

  When unplugging an external monitor connected via USB-C to my Thinkpad
  P14s, the entire UI session crashes. While the external monitor is
  plugged in, it is configured as the primary display. Here are the
  gnome-shell logs of the latest incident, I suppose the relevant part
  is `assertion 'window->stack_position >= 0' failed`.

  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212959: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212959 does not exist.
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212963: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212963 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212964: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212964 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212965: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212965 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212966: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212966 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212967: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212967 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 31 with keysym 31 (keycode a).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 32 with keysym 32 (keycode b).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 33 with keysym 33 (keycode c).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 38 with keysym 38 (keycode 11).
  May 17 09:56:49 snaut gnome-shell[2048]: Window

[Desktop-packages] [Bug 1973638] Re: System very laggy

** Package changed: ubuntu => gnome-shell (Ubuntu)

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

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

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

** Summary changed:

- System very laggy
+ gnome-shell leaks tens of megabytes with every screenshot

** Summary changed:

- gnome-shell leaks tens of megabytes with every screenshot
+ gnome-shell 42 leaks tens of megabytes with every screenshot

** Tags added: gnome-shell-leak

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

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

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

Title:
  gnome-shell 42 leaks tens of megabytes with every screenshot

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

Bug description:
  i running wine program and i want doing a lot screenshot. after did it
  and close program. my system very laggy. i see at htop program my ram
  and swap full.

  my system info.

  Host: mantari Kernel: 5.17.7-xanmod1 x86_64 bits: 64 compiler: gcc
  v: 11.2.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.17.7-xanmod1
  root=UUID=1dd447f7-2ae1-47c5-81cc-8584b22766d3 ro mitigations=off quiet
  splash vt.handoff=7
Desktop: GNOME 42.0 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3 42.0
  Distro: Ubuntu 22.04 LTS (Jammy Jellyfish)
  Machine:
Type: Portable System: Dell product: Inspiron 3442 v: N/A
Mobo: Dell model: 0T57PC v: A16 serial:  UEFI: Dell
  v: A16 date: 09/02/2020
  Battery:
ID-1: BAT0 charge: 14.9 Wh (100.0%) condition: 14.9/41.4 Wh (36.0%)
  volts: 16.8 min: 14.8 model: SMP-SDI2.8 DELL FW1MN31 type: Li-ion
  serial: 4862 status: Full
  Memory:
RAM: total: 3.75 GiB 
  Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
  compositor: gnome-shell driver: X: loaded: modesetting unloaded: 
fbdev,vesa
  gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: AU Optronics built: 2013 res: 1366x768 dpi: 112
  gamma: 1.2 size: 309x173mm (12.2x6.8") diag: 354mm (13.9") ratio: 16:9
  modes: 1366x768
OpenGL: renderer: Mesa Intel HD Graphics (HSW GT1) v: 4.6 Mesa 22.0.1
  compat-v: 3.1 direct render: Yes
  Drives:
Local Storage: total: 1.14 TiB used: 916.19 GiB (78.7%)
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
  model: WD7500BPVX-75JC3T0 size: 698.64 GiB block-size: physical: 4096 B
  logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: WXA1A33W6463
  rev: 1A01 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST500LM012 HN-M500MBB
  size: 465.76 GiB block-size: physical: 4096 B logical: 512 B
  speed: 3.0 Gb/s type: HDD rpm: 5400 serial: S2S7J9DC911744 rev: 0001
  scheme: GPT
  Swap:
Kernel: swappiness: 30 (default 60) cache-pressure: 50 (default 100)
ID-1: swap-1 type: zram size: 2.79 GiB used: 0 KiB (0.0%) priority: 5
  dev: /dev/zram0
ID-2: swap-2 type: zram size: 2.79 GiB used: 0 KiB (0.0%) priority: 5
  dev: /dev/zram1

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 42.0-2ubuntu1
Candidate: 42.0-2ubuntu1
Version table:
   *** 42.0-2ubuntu1 500
  500 https://mirror.internet.asn.au/pub/ubuntu/archive jammy/main 
amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1973638/+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 1973596] Re: SRU 1.14.3-0ubuntu3 to jammy

2022-05-18 Thread Olivier Tilloy

Successfully tested by executing the test plan in the description in a
fully up-to-date jammy VM:

 - installed the native messaging portal-enabled firefox snap
 - installed the chrome-gnome-shell native connector
 - installed the gnome shell integration extension in firefox
 - browsed to https://extensions.gnome.org/local/
 - observed that I'm not getting prompted for authorization, and that the 
extension complains that the connector cannot be talked to

 - enabled jammy-proposed, upgraded xdg-desktop-portal to version 
1.14.3-0ubuntu2.22.04.1
 - deleted ~/.local/share/flatpak/db/webextensions
 - restarted the VM
 - opened firefox and browsed to https://extensions.gnome.org/local/
 - observed that I'm now getting prompted for authorization

After granting the authorization, communication with the native connector 
initially fails, and won't work until the portal is killed and restarted. This 
is a separate issue that has been reported 
(https://github.com/flatpak/xdg-desktop-portal/pull/705#issuecomment-1123392120)
 and is being investigated.
The problem that this SRU addresses (lack of authorization prompt) is indeed 
fixed.

** 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 xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1973596

Title:
  SRU 1.14.3-0ubuntu3 to jammy

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  When testing native messaging support with the firefox snap (not yet
  released, see https://github.com/flatpak/xdg-desktop-portal/pull/705),
  gnome-shell won't prompt the user for permission to authorize a given
  extension to access the portal, because the app id being passed to the
  authorization request isn't what gnome-shell expects. This is
  https://github.com/flatpak/xdg-desktop-portal/issues/769.

  As a consequence, access is always denied, and native messaging just
  doesn't work.

  The patch that fixes this issue was discussed with the author of the
  native messaging portal (James Henstridge) and approved by him, and is
  now being cherry-picked here.

  
  [Test Plan]

  On jammy, fetch and install the latest test snap from 
https://launchpad.net/~osomon/+snap/firefox-native-messaging (manual 
installation requires the --dangerous flag).
  Install the chrome-gnome-shell native connector (`sudo apt install 
chrome-gnome-shell`).
  Open firefox and browse to 
https://addons.mozilla.org/firefox/addon/gnome-shell-integration/.
  Click the "Add to Firefox" button on the page.
  Accept the authorization request that appears as a popup to install the GNOME 
Shell integration extension.
  Browse to https://extensions.gnome.org/local/.

  You should be getting a GNOME Shell modal dialog that prompts you whether to 
allow Firefox to make use of the WebExtensions portal to launch the 
org.gnome.chrome_gnome_shell native connector.
  Without this patch, GNOME Shell silently rejects the authorization request, 
and you won't see any prompt.

  Note that if you've tested the functionality before installing the
  patched version of xdg-desktop-portal, you'll need to delete the
  database that stores the permissions on disk
  (~/.local/share/flatpak/db/webextensions) and restart the portal.

  
  [Where problems could occur]

  This patch affects a portal that is not being used anywhere yet (the
  implementation in the Firefox snap is work in progress and serves as a
  proof of concept). So there is no risk of affecting existing
  functionality or other portals.

  At worst, the patch doesn't fix the issue it claims it resolves.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973596/+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 1973638] [NEW] System very laggy

You have been subscribed to a public bug:

i running wine program and i want doing a lot screenshot. after did it
and close program. my system very laggy. i see at htop program my ram
and swap full.

my system info.

Host: mantari Kernel: 5.17.7-xanmod1 x86_64 bits: 64 compiler: gcc
v: 11.2.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.17.7-xanmod1
root=UUID=1dd447f7-2ae1-47c5-81cc-8584b22766d3 ro mitigations=off quiet
splash vt.handoff=7
  Desktop: GNOME 42.0 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3 42.0
Distro: Ubuntu 22.04 LTS (Jammy Jellyfish)
Machine:
  Type: Portable System: Dell product: Inspiron 3442 v: N/A
  Mobo: Dell model: 0T57PC v: A16 serial:  UEFI: Dell
v: A16 date: 09/02/2020
Battery:
  ID-1: BAT0 charge: 14.9 Wh (100.0%) condition: 14.9/41.4 Wh (36.0%)
volts: 16.8 min: 14.8 model: SMP-SDI2.8 DELL FW1MN31 type: Li-ion
serial: 4862 status: Full
Memory:
  RAM: total: 3.75 GiB 
Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: AU Optronics built: 2013 res: 1366x768 dpi: 112
gamma: 1.2 size: 309x173mm (12.2x6.8") diag: 354mm (13.9") ratio: 16:9
modes: 1366x768
  OpenGL: renderer: Mesa Intel HD Graphics (HSW GT1) v: 4.6 Mesa 22.0.1
compat-v: 3.1 direct render: Yes
Drives:
  Local Storage: total: 1.14 TiB used: 916.19 GiB (78.7%)
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD7500BPVX-75JC3T0 size: 698.64 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: WXA1A33W6463
rev: 1A01 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST500LM012 HN-M500MBB
size: 465.76 GiB block-size: physical: 4096 B logical: 512 B
speed: 3.0 Gb/s type: HDD rpm: 5400 serial: S2S7J9DC911744 rev: 0001
scheme: GPT
Swap:
  Kernel: swappiness: 30 (default 60) cache-pressure: 50 (default 100)
  ID-1: swap-1 type: zram size: 2.79 GiB used: 0 KiB (0.0%) priority: 5
dev: /dev/zram0
  ID-2: swap-2 type: zram size: 2.79 GiB used: 0 KiB (0.0%) priority: 5
dev: /dev/zram1

$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 42.0-2ubuntu1
  Candidate: 42.0-2ubuntu1
  Version table:
 *** 42.0-2ubuntu1 500
500 https://mirror.internet.asn.au/pub/ubuntu/archive jammy/main amd64 
Packages
100 /var/lib/dpkg/status

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


** Tags: jammy
-- 
System very laggy
https://bugs.launchpad.net/bugs/1973638
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution

2022-05-18 Thread Olivier Tilloy

Reported the "unexpected operator" error here:
https://gitlab.freedesktop.org/xdg/xdg-
utils/-/merge_requests/52#note_1389020.

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

Title:
  "xdg-settings check default-web-browser something.desktop" fails in
  Kubuntu 22.04: Bad substitution

Status in Xdg-utils:
  Unknown
Status in xdg-utils package in Ubuntu:
  Fix Released
Status in xdg-utils source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  The firefox snap (default in 22.04) will always report that it thinks
  it's not the default browser (even when it actually is) for KDE users
  (this can be seen when browsing to about:preferences).

  This is caused by an upstream bug in xdg-utils (using bashisms in KDE-
  specific functions whereas the default interpreter is dash).

  The fix is rather trivial and will visibly improve the UX for those
  users.

  
  [Test Plan]

  In Kubuntu 22.04:
   - make sure firefox isn't your default browser (by changing the setting to a 
different browser)
   - run the firefox snap, browse to "about:preferences", and observe that 
firefox claims NOT to be the default browser
   - click the "Set default" button
   - refresh the page (F5)
   - observe that now firefox claims to be the default browser
   - in a terminal, execute `xdg-open https://example.org`, and verify that the 
page is open in the firefox snap

  [Where problems could occur]

  The patch is changing KDE-specific functions (check_browser_kde and
  check_url_scheme_handler_kde), so in theory it shouldn't affect
  running xdg-utils in any other desktop environment.

  If the proposed patch is incorrect, it would affect the functionality
  of `xdg-settings check default-web-browser` and `xdg-settings check
  default-url-scheme-handler`, so this is what needs to be thoroughly
  tested in KDE.

  In the event of a regression, these functions wouldn't work as
  expected (they already don't, so the user wouldn't observe a
  functional regression, merely the absence of a fix).

  
  [Original description]

  I'm reporting this issue from stock Ubuntu, but the problem is
  observed only in Kubuntu (can be reliably reproduced in a Kubuntu
  22.04 VM). The version of xdg-utils is identical.

  This problem was initially reported on the snapcraft forum:
  https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
  browser/29708.

  $ xdg-settings check default-web-browser firefox_firefox.desktop
  /usr/bin/xdg-settings: 734: Bad substitution

  The offending line is:

  if [ x"!" == x"${browser:0:1}" ]; then

  If I modify /usr/bin/xdg-settings in place to set the interpreter to
  /bin/bash on the first line of the script, the problem goes away.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xdg-utils 1.1.3-4.1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 11:21:31 2022
  InstallationDate: Installed on 2020-09-16 (587 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  PackageArchitecture: all
  SourcePackage: xdg-utils
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1970594/+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 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution

2022-05-18 Thread Olivier Tilloy

Successfully tested by doing the following:

In a fully up-to-date jammy VM:

$ sudo apt -y install libkf5config-bin
$ export XDG_CURRENT_DESKTOP=KDE
$ export KDE_SESSION_VERSION=5
$ xdg-settings get default-web-browser
firefox.desktop
$ xdg-settings check default-web-browser firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution

Then enabled the jammy-proposed pocket and updated xdg-utils to version
1.1.3-4.1ubuntu1.22.04.1:

$ xdg-settings get default-web-browser
firefox.desktop
$ xdg-settings check default-web-browser foobar.desktop
no
$ xdg-settings check default-web-browser firefox.desktop
/usr/bin/xdg-settings: 734: [: x!: unexpected operator
yes

The result is as expected in all cases. Note the extra "/usr/bin/xdg-
settings: 734: [: x!: unexpected operator" on stderr in the last test.
This is not expected, but it is harmless as the output on stdout is as
expected. I will report a follow-up upstream bug to get that addressed.

** 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 xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594

Title:
  "xdg-settings check default-web-browser something.desktop" fails in
  Kubuntu 22.04: Bad substitution

Status in Xdg-utils:
  Unknown
Status in xdg-utils package in Ubuntu:
  Fix Released
Status in xdg-utils source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  The firefox snap (default in 22.04) will always report that it thinks
  it's not the default browser (even when it actually is) for KDE users
  (this can be seen when browsing to about:preferences).

  This is caused by an upstream bug in xdg-utils (using bashisms in KDE-
  specific functions whereas the default interpreter is dash).

  The fix is rather trivial and will visibly improve the UX for those
  users.

  
  [Test Plan]

  In Kubuntu 22.04:
   - make sure firefox isn't your default browser (by changing the setting to a 
different browser)
   - run the firefox snap, browse to "about:preferences", and observe that 
firefox claims NOT to be the default browser
   - click the "Set default" button
   - refresh the page (F5)
   - observe that now firefox claims to be the default browser
   - in a terminal, execute `xdg-open https://example.org`, and verify that the 
page is open in the firefox snap

  [Where problems could occur]

  The patch is changing KDE-specific functions (check_browser_kde and
  check_url_scheme_handler_kde), so in theory it shouldn't affect
  running xdg-utils in any other desktop environment.

  If the proposed patch is incorrect, it would affect the functionality
  of `xdg-settings check default-web-browser` and `xdg-settings check
  default-url-scheme-handler`, so this is what needs to be thoroughly
  tested in KDE.

  In the event of a regression, these functions wouldn't work as
  expected (they already don't, so the user wouldn't observe a
  functional regression, merely the absence of a fix).

  
  [Original description]

  I'm reporting this issue from stock Ubuntu, but the problem is
  observed only in Kubuntu (can be reliably reproduced in a Kubuntu
  22.04 VM). The version of xdg-utils is identical.

  This problem was initially reported on the snapcraft forum:
  https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
  browser/29708.

  $ xdg-settings check default-web-browser firefox_firefox.desktop
  /usr/bin/xdg-settings: 734: Bad substitution

  The offending line is:

  if [ x"!" == x"${browser:0:1}" ]; then

  If I modify /usr/bin/xdg-settings in place to set the interpreter to
  /bin/bash on the first line of the script, the problem goes away.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xdg-utils 1.1.3-4.1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 11:21:31 2022
  InstallationDate: Installed on 2020-09-16 (587 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  PackageArchitecture: all
  SourcePackage: xdg-utils
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1970594/+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 1973802] Re: Gnome Shell crashes when disconnecting external monitor

2022-05-18 Thread Ralf Sternberg

Thanks. I've found the corresponding crash log and tried to attach it
here, but the upload fails (always end up on a site saying "Uh oh :(".
Might be the file size (76M), even a gzipped version (55M) did not
succeed.

Using `ubuntu_bug` as recommended in
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
did not seem to do anything (perhaps running into that same problem).

Any ideas?

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

Title:
  Gnome Shell crashes when disconnecting external monitor

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04, gnome-shell 42.0-2ubuntu1

  When unplugging an external monitor connected via USB-C to my Thinkpad
  P14s, the entire UI session crashes. While the external monitor is
  plugged in, it is configured as the primary display. Here are the
  gnome-shell logs of the latest incident, I suppose the relevant part
  is `assertion 'window->stack_position >= 0' failed`.

  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212959: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212959 does not exist.
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212963: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212963 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212964: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212964 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212965: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212965 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212966: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212966 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212967: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212967 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 31 with keysym 31 (keycode a).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 32 with keysym 32 (keycode b).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 33 with keysym 33 (keycode c).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
  May 17 09:56:49 snaut gnome-shell[2048]:

[Desktop-packages] [Bug 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock

2022-05-18 Thread Bug Watch Updater

** Changed in: dash-to-dock
   Status: Unknown => 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/1967121

Title:
  Dock auto-hides when a right click context menu is opened while a
  window is under the dock

Status in Dash to dock:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  Triaged

Bug description:
  Currently testing a fresh install of the beta for 22.04.
  All packages are up to date.

  When having the dock auto-hide option enabled, a glitch occurs when opening 
the windows selector (when multiple instances of the same program are opened).
  The selector does open, but the dock will hide itself immediately instead of 
waiting for a selection. Selecting a window will then cause a glitch where the 
selector will align with the hidden dock in a non natural way before 
disappearing.

  A proposed fix would be to prevent the dock from auto-hiding when the
  miniatures selector opens and wait for a second input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1967121/+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 1973886] Re: "Install additional software" button does nothing

2022-05-18 Thread Robin Sheat

note: I apt installed gstreamer1.0-plugins-bad after trying the button,
but before doing ubuntu-bug, hence it showing up in the
GstreamerVersions.txt file.

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

Title:
  "Install additional software" button does nothing

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  I imported some m4a files, which by default can't be played. Rhythmbox
  gives me a button "Install Additional Software" to install the
  required codecs. Clicking this button does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: rhythmbox 3.4.4-5ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 18 11:06:03 2022
  InstallationDate: Installed on 2022-03-17 (61 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1973886/+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 1973886] [NEW] "Install additional software" button does nothing

2022-05-18 Thread Robin Sheat

Public bug reported:

I imported some m4a files, which by default can't be played. Rhythmbox
gives me a button "Install Additional Software" to install the required
codecs. Clicking this button does nothing.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: rhythmbox 3.4.4-5ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 18 11:06:03 2022
InstallationDate: Installed on 2022-03-17 (61 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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


** Tags: amd64 apport-bug jammy wayland-session

** Attachment added: "Screenshot showing the button in question"
   
https://bugs.launchpad.net/bugs/1973886/+attachment/5590645/+files/Screenshot%20from%202022-05-18%2011-09-56.png

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

Title:
  "Install additional software" button does nothing

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  I imported some m4a files, which by default can't be played. Rhythmbox
  gives me a button "Install Additional Software" to install the
  required codecs. Clicking this button does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: rhythmbox 3.4.4-5ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 18 11:06:03 2022
  InstallationDate: Installed on 2022-03-17 (61 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1973886/+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 1972790] Re: Can't connect to hotspot created on ubuntu

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

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

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

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1967843] Re: cheese display corrupted under Ubuntu 22.04

2022-05-18 Thread Stephan Oehlert

I can confirm that the update fixes the issue for me.
In particular, Zoom works again now.

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

Title:
  cheese display corrupted under  Ubuntu 22.04

Status in Cheese:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in cheese package in Ubuntu:
  Invalid
Status in clutter-gst-3.0 package in Ubuntu:
  Fix Released
Status in clutter-gst-3.0 source package in Jammy:
  Fix Committed

Bug description:
  Impact
  ==
  The cheese app is unusable with color bands showing in the main view.

  This bug doesn't affect all webcams. It's unknown what percentage of
  webcams are affected.

  Test Case
  
  On a system that experiences this bug:
  Install the update
  Run the cheese app
  Verify that the main view shows what your webcam can see normally.
  Click the camera button in the bottom toolbar area.
  Check if the photo looks normal. You can find it in ~/Pictures/Webcam

  What Could Go Wrong
  ===
  Only 4 apps in Ubuntu use clutter-gst: empathy, cheese, lyricue, pinpoint

  clutter-gst has been archived by GNOME. (It's recommended for apps to
  use GTK4 instead of GTK3 + Clutter). That means it's not possible for
  this patch to be accepted upstream. Instead, distros like Arch Linux
  are applying this patch.

  This patch removes 2 renderers that don't work (RGBx and BGRx) but
  still keeps ones that do work: RGBA and BRGA.

  Original Bug Report
  ===
  The cheese application produces a corrupted display under Ubuntu 22.04 with a 
Logitech C525 webcam. When started from the command line, cheese produces 
repeated warnings of the form...

  (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being 
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
  There may be a timestamping problem, or this computer is too slow.

  Adding /etc/modprobe.d/uvcvideo.conf

  with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue
  is not seen in either Ubuntu 21.10 or under Fedora-Workstation-
  Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both
  Wayland and X11 displays with the Nvidia drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 05:15:35 2022
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 UD
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 UD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cheese 41.1-1build1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  Tags: wayland-session third-party-packages jammy gstreamer-error
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm

[Desktop-packages] [Bug 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock

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

** Also affects: dash-to-dock via
   https://github.com/micheleg/dash-to-dock/issues/1714
   Importance: Unknown
   Status: Unknown

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

Title:
  Dock auto-hides when a right click context menu is opened while a
  window is under the dock

Status in Dash to dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  Triaged

Bug description:
  Currently testing a fresh install of the beta for 22.04.
  All packages are up to date.

  When having the dock auto-hide option enabled, a glitch occurs when opening 
the windows selector (when multiple instances of the same program are opened).
  The selector does open, but the dock will hide itself immediately instead of 
waiting for a selection. Selecting a window will then cause a glitch where the 
selector will align with the hidden dock in a non natural way before 
disappearing.

  A proposed fix would be to prevent the dock from auto-hiding when the
  miniatures selector opens and wait for a second input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1967121/+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 1954970] Re: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version"

2022-05-18 Thread Bryan Cebuliak

The 2.6.1+dfsg1-3ubuntu2 libfreerdp2-2 found on jammy-updates fixes the RD 
gateway access issue for me too. Thanks, I can use Remmina again.  A bit 
disconcerting that Remmina seems to be the only GUI option for this task. Much 
depends on it working. Shocking that the bug made it all the way to 22.04 LTS 
release. Happy for the  fix!
Your bleeding user

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

Title:
  remmina "Cannot connect to the RDP server ... via TLS. Check that the
  client and server support a common TLS version"

Status in freerdp2 package in Ubuntu:
  Confirmed
Status in freerdp2 source package in Jammy:
  Confirmed

Bug description:
  Xubuntu Jammy (21.04)
  after upgrade
 libfreerdp-client2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1)
 libfreerdp2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1)
  Remmina can't connect to any RDP server (Win2008 R2) with error:
  "Cannot connect to the RDP server ... via TLS. Check that the client and 
server support a common TLS version"

  Rollback to Impish version of libs
 libfreerdp-client2-2 2.3.0+dfsg1-2ubuntu2
 libfreerdp2-2 2.3.0+dfsg1-2ubuntu2
  makes it work normal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1954970/+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 1973748] Re: Updating any gsettings key makes user dconf database unreadable

This bug was fixed in the package adsys - 0.8.5

---
adsys (0.8.5) kinetic; urgency=medium

  [ Jean-Baptiste Lallement ]
  [ Didier Roche ]
  * Rename chapters to be in correct ascii order when viewed online.
Thanks to Anton Drastrup-Fjordbak.
  * Include 22.04 in admx/adml for lts only releases. (LP: #1973745)
  * Bump embedeed dependencies minor versions for both bug fixes and minor
security enhancements.
  * Fix dconf keys not being readable by user after applying policy.
(LP: #1973748)
  * Ensure we can execute machine and user scripts:
/run is now noexec on Ubuntu. Ensure that we can execute the scripts in
/run/adsys subdirectories. The scripts mecanism has been reviewed by the
security team, so we can reset them as executable. (LP: #1973751)
  * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen
to prepare future adwatchd daemon under cmd/ which will be SRUed with an
exception in next update. This is a no-op in the finale deploy binaries,
apart from admxgen which is now using Cobra. This binary though is not
shipped in any package and only used in CI.
  * Fix privilege permission which can not be set to disabled. (LP: #1973752)
  * Adaptation or new tests for all above changes.
  * Add fuzz tests and include new potential crash fixes on invalid files
generated by Windows AD.
  * CI fixes and changes (not impacting finale package):
- Move CI to Go 1.18 (package is already building with 1.18 in jammy).
- Fixes due to new github.
- Fix to generate all LTS releases in admx/adml (see above).

 -- Didier Roche   Mon, 16 May 2022 14:09:36 +0200

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

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

Title:
  Updating any gsettings key makes user dconf database unreadable

Status in adsys package in Ubuntu:
  Fix Released
Status in adsys source package in Jammy:
  New

Bug description:
  [Impact]
  Changing any gsettings key in AD resulted in user databases under /etc/dconf, 
owned by root, with 0600 as permissions. This change was done late in the cycle 
after passing some permissions checkers to harden the binaries.
  However, in that case, the user databases needs to be readable by the users 
so that they can apply those values, so we need to align with ibus profile and 
makes them 644.

  [Test case]
  * Change a gsettings key under AD, like picture-uri one.
  * Login on the Ubuntu laptop connected with AD by adsys
  * The background should now be changed to the set value.

  [Where problems could occur]
  This code is located in the dconf policy application manager and restricted 
to it. The negative impact in case of a new bug will be seen by gsettings key 
not being applied as it is already nowdays.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973748/+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 1973745] Re: adsys windows admx/adml lts only does not include 22.04

This bug was fixed in the package adsys - 0.8.5

---
adsys (0.8.5) kinetic; urgency=medium

  [ Jean-Baptiste Lallement ]
  [ Didier Roche ]
  * Rename chapters to be in correct ascii order when viewed online.
Thanks to Anton Drastrup-Fjordbak.
  * Include 22.04 in admx/adml for lts only releases. (LP: #1973745)
  * Bump embedeed dependencies minor versions for both bug fixes and minor
security enhancements.
  * Fix dconf keys not being readable by user after applying policy.
(LP: #1973748)
  * Ensure we can execute machine and user scripts:
/run is now noexec on Ubuntu. Ensure that we can execute the scripts in
/run/adsys subdirectories. The scripts mecanism has been reviewed by the
security team, so we can reset them as executable. (LP: #1973751)
  * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen
to prepare future adwatchd daemon under cmd/ which will be SRUed with an
exception in next update. This is a no-op in the finale deploy binaries,
apart from admxgen which is now using Cobra. This binary though is not
shipped in any package and only used in CI.
  * Fix privilege permission which can not be set to disabled. (LP: #1973752)
  * Adaptation or new tests for all above changes.
  * Add fuzz tests and include new potential crash fixes on invalid files
generated by Windows AD.
  * CI fixes and changes (not impacting finale package):
- Move CI to Go 1.18 (package is already building with 1.18 in jammy).
- Fixes due to new github.
- Fix to generate all LTS releases in admx/adml (see above).

 -- Didier Roche   Mon, 16 May 2022 14:09:36 +0200

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

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

Title:
  adsys windows admx/adml lts only does not include 22.04

Status in adsys package in Ubuntu:
  Fix Released
Status in adsys source package in Jammy:
  New

Bug description:
  [Impact] 
  Due to some misunterpretation in how the launchpad API works when listing lts 
only, 22.04 was not included there by the admx/adml files generated by CI.
  Consequently, when those files are deployed on Windows AD server with LTS 
only templates, this one is not listed.

  [Test Plan]
  * Deploy the admx/adml generated for "LTS Only" use cases on an AD server
  * Open any GPO rule like changing the background
  * Ensure there is an "Override for 22.04" entry.

  [Where problems could occur]
  Those files are statically generated and then shipped as thus. There is no 
runtime exercising this. The consequence of those generated files to be invalid 
is that Windows AD server will not show up "Ubuntu" in its GPO template.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973745/+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 1973751] Re: Machines or Users scripts are not executed

This bug was fixed in the package adsys - 0.8.5

---
adsys (0.8.5) kinetic; urgency=medium

  [ Jean-Baptiste Lallement ]
  [ Didier Roche ]
  * Rename chapters to be in correct ascii order when viewed online.
Thanks to Anton Drastrup-Fjordbak.
  * Include 22.04 in admx/adml for lts only releases. (LP: #1973745)
  * Bump embedeed dependencies minor versions for both bug fixes and minor
security enhancements.
  * Fix dconf keys not being readable by user after applying policy.
(LP: #1973748)
  * Ensure we can execute machine and user scripts:
/run is now noexec on Ubuntu. Ensure that we can execute the scripts in
/run/adsys subdirectories. The scripts mecanism has been reviewed by the
security team, so we can reset them as executable. (LP: #1973751)
  * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen
to prepare future adwatchd daemon under cmd/ which will be SRUed with an
exception in next update. This is a no-op in the finale deploy binaries,
apart from admxgen which is now using Cobra. This binary though is not
shipped in any package and only used in CI.
  * Fix privilege permission which can not be set to disabled. (LP: #1973752)
  * Adaptation or new tests for all above changes.
  * Add fuzz tests and include new potential crash fixes on invalid files
generated by Windows AD.
  * CI fixes and changes (not impacting finale package):
- Move CI to Go 1.18 (package is already building with 1.18 in jammy).
- Fixes due to new github.
- Fix to generate all LTS releases in admx/adml (see above).

 -- Didier Roche   Mon, 16 May 2022 14:09:36 +0200

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

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

Title:
  Machines or Users scripts are not executed

Status in adsys package in Ubuntu:
  Fix Released
Status in adsys source package in Jammy:
  New

Bug description:
  [Impact]
  Machine and user scripts are not executed on startup/shutdown/login/logoff.
  /run has been recently changed to be noexec on jammy. Ensure that we can 
execute the scripts in /run/adsys subdirectories. The scripts mecanism has been 
reviewed by the security team, so we can reset them as executable.

  
  [Test case]
  * Setup some scripts under AD to be executed, one for machine scripts (on 
startup), one for user scripts (on login). Those scripts can create some 
temporary files under /tmp for instance.
  * Reboot and login on the Ubuntu laptop connected with AD by adsys, with ua 
attached
  * Check that the scripts were executed by testing that the created file under 
/tmp are present.

  [Where problems could occur]
  This is technically a new .mount systemd unit service which takes the same 
mount option than /run, but don’t set noexec. The setup is similar than qemu 
.mount unit for instance.
  Worst impact could be that the script policy manager can’t run the scripts as 
it is already the case today.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973751/+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 1973752] Re: Fix privilege permission which can not be set to disabled

This bug was fixed in the package adsys - 0.8.5

---
adsys (0.8.5) kinetic; urgency=medium

  [ Jean-Baptiste Lallement ]
  [ Didier Roche ]
  * Rename chapters to be in correct ascii order when viewed online.
Thanks to Anton Drastrup-Fjordbak.
  * Include 22.04 in admx/adml for lts only releases. (LP: #1973745)
  * Bump embedeed dependencies minor versions for both bug fixes and minor
security enhancements.
  * Fix dconf keys not being readable by user after applying policy.
(LP: #1973748)
  * Ensure we can execute machine and user scripts:
/run is now noexec on Ubuntu. Ensure that we can execute the scripts in
/run/adsys subdirectories. The scripts mecanism has been reviewed by the
security team, so we can reset them as executable. (LP: #1973751)
  * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen
to prepare future adwatchd daemon under cmd/ which will be SRUed with an
exception in next update. This is a no-op in the finale deploy binaries,
apart from admxgen which is now using Cobra. This binary though is not
shipped in any package and only used in CI.
  * Fix privilege permission which can not be set to disabled. (LP: #1973752)
  * Adaptation or new tests for all above changes.
  * Add fuzz tests and include new potential crash fixes on invalid files
generated by Windows AD.
  * CI fixes and changes (not impacting finale package):
- Move CI to Go 1.18 (package is already building with 1.18 in jammy).
- Fixes due to new github.
- Fix to generate all LTS releases in admx/adml (see above).

 -- Didier Roche   Mon, 16 May 2022 14:09:36 +0200

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

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

Title:
  Fix privilege permission which can not be set to disabled

Status in adsys package in Ubuntu:
  Fix Released
Status in adsys source package in Jammy:
  New

Bug description:
  [Impact]
  Disallowing local administrator does not work as excepted:
  - on some AD server, setting in the UI this key (and some other similars) to 
disabled, go to next GPO rule, then back to this one, AD will display the key 
as enabled.
  - on the client machine, we can see that the key has no state and nothing is 
forcibly allowed or disallowed.

  [Test case]
  * Install the new admx/adml with this version on the AD server.
  * On AD, go to disallow local administator, set it to disabled
  * Go to next GPO rules and then go back
  * The rule should still be disabled.
  * On an Ubuntu machine connected with AD by adsys, with ua attached, force a 
machine refresh with adsysctl policy update -m.
  * Check in adsysctl policy applied --all that the key is displayed as disabled
  * Confirm that no local administrator (part of the sudo group) can run "sudo".

  [Where problems could occur]
  The privilege manager and other policies impacts both Windows and client:
  - on Windows, this is in the admx/adml are statically generated and then 
shipped as thus. There is no runtime exercising this. The consequence of those 
generated files to be invalid is that Windows AD server will not show up 
"Ubuntu" in its GPO template.
  - on the client, the privilege manager is the main consumer of those disabled 
key types. The other kinds of keys are not impacted.

  [Additional informations]
  * New test cases have been added for the client part.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973752/+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 1973816] Re: Deja Dup's Google support will break in September 2022 for versions < 43.3

Thanks Michael for the headsup. We will update to 43 for Kinetic now
that the LTS is out we plan to go with the current version of the GNOME
libraries but backports of the changes to older series would be welcome
as we will need to do SRUs.

I think it makes sense for you as an upstream to probably do 42 which is
the last GTK3 supported version and it's probably on us to backport to
older version as needed.

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => High

** Changed in: deja-dup (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Changed in: deja-dup (Ubuntu)
   Status: New => Triaged

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

Title:
  Deja Dup's Google support will break in September 2022 for versions <
  43.3

Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  Hello! I'm the maintainer of Deja Dup. I was recently made aware that
  Google is removing an oauth workflow that Deja Dup uses, in September.

  Here's their blog post about it:
  https://developers.googleblog.com/2022/02/making-oauth-flows-
  safer.html

  Here's the upstream bug about switching to a new oauth flow:
  https://gitlab.gnome.org/World/deja-dup/-/issues/222

  I've released version 43.3 with a new oauth workflow. This basically
  switches us from redirecting the oauth page to a local
  http://localhost:/ page being served by deja-dup and instead has
  the browser launch a custom URI like
  'com.googlecontent.xxx:/oauth2redirect?code=yyy', which then launches
  deja-dup and gives it the correct oauth token.

  The key differences for packagers is just to note that now deja-dup
  will register itself as a handler for those weird URI schemes (they
  are specific to deja-dup, as they include its client ids for the
  service).

  I think this deserves a backport to all supported releases. I can whip
  up a patch for you in a bit, just wanted to get this registered as an
  issue.

  To be a bit more specific about what will break:
  - Existing users that have already granted deja-dup access to Google will 
continue to work without any issue.
  - In August, users will see a warning on the oauth screen.
  - And then in September, any new attempt to connect deja-dup to Google will 
not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1973816/+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 1973660] Re: [vmwgfx] Login screen not refreshing properly on vSphere

> Could you please give me some hints how to identify it's a bug in the
VMware Xorg graphics driver?

The hint was that it only happened on the one system I've ever seen that
was using Xorg on VMware. :)

If the problem was more general than that then someone else would have
reported it in the 2+ years since Ubuntu 20.04 was released. Although
bug 1865963 might be the same issue, maybe?

** Summary changed:

- [vmwgfx] Login screen not refreshing properly on vSphere
+ [vmwgfx] Login screen not refreshing properly on vSphere when 
WaylandEnable=false

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

Title:
  [vmwgfx] Login screen not refreshing properly on vSphere when
  WaylandEnable=false

Status in xserver-xorg-video-vmware package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using,
  gnome-shell:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 3.36.9-0ubuntu0.20.04.2
Version table:
   *** 3.36.9-0ubuntu0.20.04.2 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal-updates/main amd64 
Packages
  500 http://cn.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal/main amd64 Packages
  500 http://cn.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) What you expected to happen
  The login screen can resize properly and all its widgets shows properly. 

  4) What happened instead
  Login screen doesn't refresh properly when resize vShpere window, so that 
can't input username and password. And I found pressing Ctl-Alt-Tab can force 
the login screen refresh.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
   b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
   b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
   b'org.gnome.desktop.screensaver' b'lock-enabled' b'false'
   b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
  InstallationDate: Installed on 2020-08-13 (641 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 [modified: 
usr/lib/gnome-shell/libgnome-shell.so]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1973660/+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 1865963] Re: Screen not repainting dirty regions on some apps (vmwgfx_scanout_update: failed to send dirty (-22, Invalid argument))