[Desktop-packages] [Bug 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end

[Daniel van Vugt]

** Summary changed:

- gnome-shell crashed with SIGSEGV in crocus_begin_query() from 
crocus_begin_query() from crocus_end_query() from crocus_end_query() from 
tc_call_end_query()
+ gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from 
crocus_begin_query() from crocus_end_query() from crocus_end_query() from 
tc_call_end_query()

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

Title:
  gnome-shell crashed (out of memory) with SIGSEGV in
  crocus_begin_query() from crocus_begin_query() from crocus_end_query()
  from crocus_end_query() from tc_call_end_query()

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Triaged

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1972977/+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 1983560] [NEW] package sgml-base 1.30 failed to install/upgrade: el subproceso instalado paquete sgml-base script post-installation devolvió el código de salida de error 2

[Juancar]

Public bug reported:

Installling spotify-client

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: sgml-base 1.30
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Aug  4 09:55:57 2022
ErrorMessage: el subproceso instalado paquete sgml-base script 
post-installation devolvió el código de salida de error 2
InstallationDate: Installed on 2022-07-22 (13 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.6
SourcePackage: sgml-base
Title: package sgml-base 1.30 failed to install/upgrade: el subproceso 
instalado paquete sgml-base script post-installation devolvió el código de 
salida de error 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sgml-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

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

Title:
  package sgml-base 1.30 failed to install/upgrade: el subproceso
  instalado paquete sgml-base script post-installation devolvió el
  código de salida de error 2

Status in sgml-base package in Ubuntu:
  New

Bug description:
  Installling spotify-client

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: sgml-base 1.30
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Aug  4 09:55:57 2022
  ErrorMessage: el subproceso instalado paquete sgml-base script 
post-installation devolvió el código de salida de error 2
  InstallationDate: Installed on 2022-07-22 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.6
  SourcePackage: sgml-base
  Title: package sgml-base 1.30 failed to install/upgrade: el subproceso 
instalado paquete sgml-base script post-installation devolvió el código de 
salida de error 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/1983560/+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 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

[Till Kamppeter]

Joel, thank you very much for your analysis and for posting Debian bug
#1016622, as the fix has to be applied in the Debian package.

** Package changed: cups (Ubuntu) => cups-filters (Ubuntu)

** Changed in: cups-filters (Ubuntu)
   Status: Confirmed => Triaged

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

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

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

Title:
  apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

Status in cups-filters package in Ubuntu:
  Triaged
Status in cups-filters package in Debian:
  Unknown

Bug description:
  In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents
  `/usr/sbin/cups-browsed` to change its nice value.

  $ sudo dmesg | grep apparmor
  [541870.509461] audit: type=1400 audit(1600898428.089:60): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=62030 comm="cups-browsed" capability=23  capname="sys_nice"
  [628298.779668] audit: type=1400 audit(1600984854.115:61): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=66850 comm="cups-browsed" capability=23  capname="sys_nice"
  [714667.424963] audit: type=1400 audit(1601071220.527:62): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=76828 comm="cups-browsed" capability=23  capname="sys_nice"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1897369/+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 1983010] Re: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size

[Olivier Tilloy]

It looks like you're using firefox distributed by Mozilla as a tarball.
Would you mind filing an issue at
https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox and sharing
the link to it here?

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

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

Title:
  Sandbox: attempt to open unexpected file
  /sys/devices/system/cpu/cpu0/cache/index2/size

Status in firefox package in Ubuntu:
  New

Bug description:
  I use Firefox Beta and launch it from the terminal. While watching
  Netflix on Firefox, I get the following messages on my terminal:

  Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/cpu0/cache/index2/size
  Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/cpu0/cache/index3/size
  Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present
  Sandbox: attempt to open unexpected file /sys/devices/system/cpu
  Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Jul 28 15:01:35 2022
  InstallationDate: Installed on 2022-06-21 (36 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1983010/+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 1848847] Re: Suspend and resume stopped working with nouveau driver after upgrade to 19.10

[Joachim Keinert]

I still see a problem with Linux Mint 20.2 kernel 5.15.0-43-generic
While it goes to suspend I see a noisy color screen after resume. I cannot 
login anymore and have to hard reset the laptop (Thinkpad T61p).

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

Title:
  Suspend and resume stopped working with nouveau driver after upgrade
  to 19.10

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Under Nouveau driver, suspend and resume of my laptop stopped working
  after i upgraded from 19.04 to 19.10.

  When desktop lid is closed, the fans will kick in and turn until
  battery is empty or hard shutdown using the power button.

  Worked before under xorg and wayland. Now doesn't work with either.
  Works with Nvidia driver 340.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 19 13:30:53 2019
  DistUpgraded: 2019-10-06 16:30:12,792 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-17-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-18-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA 
controller])
 Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00b9]
  InstallationDate: Installed on 2019-01-12 (279 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Apple Inc. MacBookPro5,5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=595c74ec-799d-4c25-bc8d-f06155d59f97 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to eoan on 2019-10-06 (12 days ago)
  dmi.bios.date: 06/15/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP55.88Z.00AC.B03.0906151708
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F2268AC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2268AC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP55.88Z.00AC.B03.0906151708:bd06/15/09:svnAppleInc.:pnMacBookPro5,5:pvr1.0:rvnAppleInc.:rnMac-F2268AC8:rvr:cvnAppleInc.:ct10:cvrMac-F2268AC8:
  dmi.product.family: MacBook
  dmi.product.name: MacBookPro5,5
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1848847/+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 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

[Bug Watch Updater]

** Changed in: cups-filters (Debian)
   Status: Unknown => New

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

Title:
  apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

Status in cups-filters package in Ubuntu:
  Triaged
Status in cups-filters package in Debian:
  New

Bug description:
  In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents
  `/usr/sbin/cups-browsed` to change its nice value.

  $ sudo dmesg | grep apparmor
  [541870.509461] audit: type=1400 audit(1600898428.089:60): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=62030 comm="cups-browsed" capability=23  capname="sys_nice"
  [628298.779668] audit: type=1400 audit(1600984854.115:61): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=66850 comm="cups-browsed" capability=23  capname="sys_nice"
  [714667.424963] audit: type=1400 audit(1601071220.527:62): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=76828 comm="cups-browsed" capability=23  capname="sys_nice"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1897369/+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 1981148] Re: saving dialog focus skips to search bar

[Olivier Tilloy]

Upstream issue: https://github.com/lxqt/xdg-desktop-portal-
lxqt/issues/14

** Bug watch added: github.com/lxqt/xdg-desktop-portal-lxqt/issues #14
   https://github.com/lxqt/xdg-desktop-portal-lxqt/issues/14

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

Title:
  saving dialog focus skips to search bar

Status in firefox package in Ubuntu:
  New

Bug description:
  I'm still wondering why my Ubuntu forces the snap version of Firefox
  onto me, despite apt-pinning, but OK, I guess being frustrated about
  that would be a lost cause.

  In any case:
  The snap version of Firefox that my Ubuntu has decided to install despite my 
apt-pinning has a bug in the saving dialog.

  I've recorded a video and left it online, here:
  https://anonfiles.com/X4ec15w7y3/simplescreenrecorder-2022-07-10_15.57.54_mkv

  Following protocol:

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

  2) $ apt-cache policy firefox
  firefox:
Installed: 1:1snap1-0ubuntu2
Candidate: 1:1snap1-0ubuntu2
Version table:
   *** 1:1snap1-0ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
   102.0.1+build1-0ubuntu0.18.04.1 999
  500 http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu 
bionic/main amd64 Packages
  500 
https://ppa.launchpadcontent.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main 
amd64 Packages

  (note how Ubuntu doesn't give a damn about the pin priority, but
  whatever)

  
  3) I'm trying to save a downloaded document. 
   3.1) Firefox opens the save dialogue.
   3.2) I would like to enter a filename into the filename bar

  4) following 3.1:
   4.2) When I try to change the filename, the focus immediately jumps to the 
search bar and the dialogue for some reason tries to search for the entered 
letters on the drive. I can click back to focus on the filename bar, sometimes 
I can manage to type one or two letters, before the focus jumps, again.


  This does not happen with the version I installed using apt, but which
  repeatedly gets removed by the Ubuntu updating process, to install the
  snap version, which sadly never seems to work without problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Sun Jul 10 16:00:53 2022
  InstallationDate: Installed on 2022-03-07 (125 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981148/+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 1983502] Re: [snap] seccomp denials for syscall=314 on amd64

[Olivier Tilloy]

syscall=314 is sys_sched_setattr on amd64

** Tags added: snap

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

Title:
  [snap] seccomp denials for syscall=314 on amd64

Status in thunderbird package in Ubuntu:
  New

Bug description:
  $ snap list thunderbird
  Name VersionRev  Tracking   Publisher   Notes
  thunderbird  102.1.0-2  237  latest/stable  canonical✓  -

  During normal operation, the following is logged:

  Aug 03 12:07:58 foo kernel: audit: type=1326
  audit(1659542878.718:511): auid=1000 uid=1000 gid=1000 ses=9 subj=?
  pid=154377 comm="thunderbird-bin"
  exe="/snap/thunderbird/237/thunderbird-bin" sig=0 arch=c03e
  syscall=314 compat=0 ip=0x7e4137c4473d code=0x5

  And something similar when the crash reporter executes:

  Aug 03 12:02:04 foo kernel: audit: type=1326
  audit(1659542524.642:510): auid=1000 uid=1000 gid=1000 ses=9 subj=?
  pid=150188 comm="crashreporter"
  exe="/snap/thunderbird/237/crashreporter" sig=0 arch=c03e
  syscall=314 compat=0 ip=0x7e5f095e773d code=0x5

  
  # Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  $ uname -a
  Linux foo 5.15.0-43-generic #46~20.04.1-Ubuntu SMP Thu Jul 14 15:20:17 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983502/+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 1983502] Re: [snap] seccomp denials for syscall=314 on amd64

[Olivier Tilloy]

This is probably harmless, but would require further investigation to
confirm.

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

Title:
  [snap] seccomp denials for syscall=314 on amd64

Status in thunderbird package in Ubuntu:
  New

Bug description:
  $ snap list thunderbird
  Name VersionRev  Tracking   Publisher   Notes
  thunderbird  102.1.0-2  237  latest/stable  canonical✓  -

  During normal operation, the following is logged:

  Aug 03 12:07:58 foo kernel: audit: type=1326
  audit(1659542878.718:511): auid=1000 uid=1000 gid=1000 ses=9 subj=?
  pid=154377 comm="thunderbird-bin"
  exe="/snap/thunderbird/237/thunderbird-bin" sig=0 arch=c03e
  syscall=314 compat=0 ip=0x7e4137c4473d code=0x5

  And something similar when the crash reporter executes:

  Aug 03 12:02:04 foo kernel: audit: type=1326
  audit(1659542524.642:510): auid=1000 uid=1000 gid=1000 ses=9 subj=?
  pid=150188 comm="crashreporter"
  exe="/snap/thunderbird/237/crashreporter" sig=0 arch=c03e
  syscall=314 compat=0 ip=0x7e5f095e773d code=0x5

  
  # Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  $ uname -a
  Linux foo 5.15.0-43-generic #46~20.04.1-Ubuntu SMP Thu Jul 14 15:20:17 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983502/+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 1979111] Re: Changing printer default still printers to previous default in browser

[Olivier Tilloy]

That sounds like potentially an upstream issue. Can you test with chrome
distributed by Google (https://www.google.com/chrome/)? If you can also
reproduce the problem there, can you please file an upstream bug at
https://bugs.chromium.org/p/chromium/issues/entry, and share the link to
it here?

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

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

Title:
  Changing printer default still printers to previous default in browser

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Desktop 20.04, fully updated.
  Budgie Desktop

  Pre-configured printer profiles with predefined settings so we get the
  exact profiles we need. Settings have not changed in well over a year.

  Noticed in the past few months that when a USB printer is swapped with
  a slightly different model but same manufacture we do the following.

  1. Update the device URI. Save. Test print which works.
  2. Set default printer to the new printer.
  3. In a chromium browser that has kiosk mode enabled for auto print. Attempt 
to print which prints to the previous defaulted printer.

  If that happens, we delete the previous defaulted printer profile and
  print again from the browser and it works. The entire time the browser
  hasn't been closed or refreshed.

  Run the command to add the previous default printer. Browser prints to
  the current default printer.

  Never restarted cups service between step 2 or 3.

  This has happened twice now on two different machines with the exact
  same software/configuration, possibly different printer models
  selected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1979111/+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 1975853] Re: Firefox does not respect policies.json file anymore.

[Olivier Tilloy]

With firefox installed as a snap, policies need to be placed in
/etc/firefox/policies/.

Can you please test and confirm whether this works for 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/1975853

Title:
  Firefox does not respect policies.json file anymore.

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  I use ansible to deploy policies.json file into
  /usr/lib/firefox/distribution/ folder in order to ensure that all
  family users use the same set of plugins on all of the ubuntu machines
  we have.

  I found that in ubuntu 22.04 this is not the case anymore.

  If I open the following page in firefox: about:policies I get the
  following message:

  The Enterprise Policies service is inactive.

  Please advise if this is intended and if there is a replacement
  mechanism.

  Note: I visited the documentation of mozilla and could not find
  anything on this subject related to linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 26 18:12:34 2022
  InstallationDate: Installed on 2022-05-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   3Done2022-05-26T12:01:32+02:00  2022-05-26T12:02:14+02:00  
Auto-refresh 4 snaps
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

Re: [Desktop-packages] [Bug 1983010] [NEW] Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size

[Vikram Vincent]

On Thursday, 4 August 2022, Olivier Tilloy <1983...@bugs.launchpad.net>
wrote:
> It looks like you're using firefox distributed by Mozilla as a tarball.
> Would you mind filing an issue at
> https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox and sharing
> the link to it here?
>
Done! https://bugzilla.mozilla.org/show_bug.cgi?id=1783163


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

Title:
  Sandbox: attempt to open unexpected file
  /sys/devices/system/cpu/cpu0/cache/index2/size

Status in firefox package in Ubuntu:
  New

Bug description:
  I use Firefox Beta and launch it from the terminal. While watching
  Netflix on Firefox, I get the following messages on my terminal:

  Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/cpu0/cache/index2/size
  Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/cpu0/cache/index3/size
  Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present
  Sandbox: attempt to open unexpected file /sys/devices/system/cpu
  Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Jul 28 15:01:35 2022
  InstallationDate: Installed on 2022-06-21 (36 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1983010/+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 1983010] Re: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size

[Vikram Vincent]

** Bug watch added: Mozilla Bugzilla #1783163
   https://bugzilla.mozilla.org/show_bug.cgi?id=1783163

** Bug watch added: github.com/webcompat/web-bugs/issues #108493
   https://github.com/webcompat/web-bugs/issues/108493

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

Title:
  Sandbox: attempt to open unexpected file
  /sys/devices/system/cpu/cpu0/cache/index2/size

Status in firefox package in Ubuntu:
  New

Bug description:
  I use Firefox Beta and launch it from the terminal. While watching
  Netflix on Firefox, I get the following messages on my terminal:

  Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/cpu0/cache/index2/size
  Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/cpu0/cache/index3/size
  Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present
  Sandbox: attempt to open unexpected file /sys/devices/system/cpu
  Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Jul 28 15:01:35 2022
  InstallationDate: Installed on 2022-06-21 (36 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1983010/+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 1983010] Re: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size

[Olivier Tilloy]

Thanks! I'm not sure why I'm not allowed to see the bug on
bugzilla.mozilla.org, and I'm not sure why this was also/separately
filed as a webcompat bug.

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

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

Title:
  Sandbox: attempt to open unexpected file
  /sys/devices/system/cpu/cpu0/cache/index2/size

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

Bug description:
  I use Firefox Beta and launch it from the terminal. While watching
  Netflix on Firefox, I get the following messages on my terminal:

  Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/cpu0/cache/index2/size
  Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/cpu0/cache/index3/size
  Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present
  Sandbox: attempt to open unexpected file /sys/devices/system/cpu
  Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Jul 28 15:01:35 2022
  InstallationDate: Installed on 2022-06-21 (36 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

Re: [Desktop-packages] [Bug 1983010] [NEW] Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size

[Vikram Vincent]

Hello!

On Thursday, 4 August 2022, Olivier Tilloy <1983...@bugs.launchpad.net>
wrote:
> Thanks! I'm not sure why I'm not allowed to see the bug on

I think this must be because I checked the box saying the bug might affect
a lot of other users(security bug). The content is the same as what is
posted on launchpad.

> bugzilla.mozilla.org, and I'm not sure why this was also/separately
> filed as a webcompat bug.
>

This was due to some confusion while trying to file the bug via the mobile
phone. I thought I was reporting a website (Netflix) messing with the web
browser.

-- 
Vikram Vincent, Ph.D.

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

Title:
  Sandbox: attempt to open unexpected file
  /sys/devices/system/cpu/cpu0/cache/index2/size

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

Bug description:
  I use Firefox Beta and launch it from the terminal. While watching
  Netflix on Firefox, I get the following messages on my terminal:

  Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/cpu0/cache/index2/size
  Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/cpu0/cache/index3/size
  Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present
  Sandbox: attempt to open unexpected file /sys/devices/system/cpu
  Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Jul 28 15:01:35 2022
  InstallationDate: Installed on 2022-06-21 (36 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1983010/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Nathan Teodosio]

The Nvidia/Intel issue mentioned in #127 has been addressed in Snapcraft
7.1.1 , which
is already available in the 7.x/candidate channel.

Now I will be working on the merge of the hwacc into latest/{beta,edge}.

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  1. Install the snap with

     sudo snap install --channel candidate/hwacc chromium

  2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
  --enable-features=VaapiVideoDecoder

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples

  4. Enter about:media-internals in the address bar and note what the
  page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if 
possible;
  - Distro version (if in doubt, `grep VERSION= /etc/os_release`);
  - GPU (if in doubt, attach the output of `lscpu`);
  - CPU generation (if in doubt, attach the output of `lscpu`).

  About the last point, it may be that unfortunately only those with
  newer generations of Intel CPUs will have luck with this, but it's
  still an uncertainty. So reports are highly welcome.

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1983483] Re: totem crashing inside nouveau DRI when replaying video (actually nouveau bug?)

[Jonathan Kamens]

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

Welp, I had disabled the proprietary nvidia driver because I use a
DisplayLink hub and DisplayLink was really unhappy about nvidia, but I
just tried it again with the current nvidia driver and it appears to be
working at least for the time being, so I'll stick with that for a while
and we'll see what happens. :shrug:

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

Title:
  totem crashing inside nouveau DRI when replaying video (actually
  nouveau bug?)

Status in totem package in Ubuntu:
  New

Bug description:
  When I try to play a video with totem it either crashes or hangs my
  display (mouse cursor still moves but nothing else works and I have to
  reboot). The crash is inside nouveau drivers, so this may be a nouveau
  bug rather than a totem bug. I can't report it with ubuntu-bug because
  of bug 1983481. I did manage to capture a stack trace with gdb, which
  I've attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: totem 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  3 10:43:36 2022
  InstallationDate: Installed on 2019-01-02 (1308 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  LogAlsaMixer:
   Simple mixer control 'Line',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined
 Capture channels: Mono
 Limits: Capture 0 - 15
 Mono: Capture 15 [100%] [15.00dB] [on]
  SourcePackage: totem
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (163 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1309 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  LogAlsaMixer:
   Simple mixer control 'Line',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined
 Capture channels: Mono
 Limits: Capture 0 - 15
 Mono: Capture 15 [100%] [15.00dB] [on]
  Package: totem 42.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Tags:  jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (163 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983483/+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 1983490] [NEW] Auto-hide taskbar does not work quite right

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In Gnome on the latest version of Ubuntu Jammy Jellyfish, the auto-hide
taskbar feature is broken. The task bar will disappear even when there
is no overlapping window and the only way to bring it back appears to be
to move a window down into that region of the display and back away from
it and then it will re-appear, until it disappears again on it own.

Sorry don't have the time to help with debug of this, but wanted you to
know. Also I submitted a ubuntu-bug on this bug for some reason it
gathered all my info and then failed to ask me what the specific problem
was. So you might want to x-ref this bug report with that filing to get
all the details.

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

-- 
Auto-hide taskbar does not work quite right
https://bugs.launchpad.net/bugs/1983490
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 1983508] Re: Moving windows between monitors with different scaling causes isues

[Petr Doležal]

apport information

** Tags added: apport-collected wayland-session

** Description changed:

  When two displays are connected and one has a 200% scaling, moving apps
  between them results in several issues:
  
  Apps that can actively scale (such as native Nautilus, Settings...):
  
   When dragging the window around, it automatically adjusts scaling based
  on on which of the monitors is the majority of the app (this is probably
  correct behaviour),
  
  BUT when using keyboard shortcuts [Ctrl] + [Super] + ←/↑/↓/→, fullscreen
  windows jump around and scale correctly, but half-full screen apps
  (arranged by [Super] + ←/→) cannot go from the larger monitor to the
  smaller, they get stuck in the scaled-up version and don't fit on the
  smaller display.
  
  Small non-maximized windows don't have this issue, possibly because when
  they first move in their scaled-up state, they do fit on the smaller
  monitor still, and only then are they scaled down.
  
  
  Apps that don't support changes in scaling and only apply the new scaling on 
a relaunch (such as Chrome) don't have these issues, but they obviously have 
that other problem.
  
  
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  mutter 3.36.9
  
  What I expect:
  Windows covering half a full screen, when moved to a different display with 
different scaling (using a keyboard), stay covering half a full screen.
  
  What happens instead:
  When moved to a display with higher scaling, this happens correctly, but when 
moved to a monitor with lower scaling, they get "stuck" on both monitors in 
their inflated state.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.24
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-10-14 (658 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ Package: mutter 3.36.9-0ubuntu0.20.04.2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
+ Tags:  focal wayland-session
+ Uname: Linux 5.15.0-43-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video
+ _MarkForUpload: True

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

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

Title:
  Moving windows between monitors with different scaling causes isues

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When two displays are connected and one has a 200% scaling, moving
  apps between them results in several issues:

  Apps that can actively scale (such as native Nautilus, Settings...):

   When dragging the window around, it automatically adjusts scaling
  based on on which of the monitors is the majority of the app (this is
  probably correct behaviour),

  BUT when using keyboard shortcuts [Ctrl] + [Super] + ←/↑/↓/→,
  fullscreen windows jump around and scale correctly, but half-full
  screen apps (arranged by [Super] + ←/→) cannot go from the larger
  monitor to the smaller, they get stuck in the scaled-up version and
  don't fit on the smaller display.

  Small non-maximized windows don't have this issue, possibly because
  when they first move in their scaled-up state, they do fit on the
  smaller monitor still, and only then are they scaled down.

  
  Apps that don't support changes in scaling and only apply the new scaling on 
a relaunch (such as Chrome) don't have these issues, but they obviously have 
that other problem.

  
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  mutter 3.36.9

  What I expect:
  Windows covering half a full screen, when moved to a different display with 
different scaling (using a keyboard), stay covering half a full screen.

  What happens instead:
  When moved to a display with higher scaling, this happens correctly, but when 
moved to a monitor with lower scaling, they get "stuck" on both monitors in 
their inflated state.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-14 (658 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: mutter 3.36.9-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Tags:  focal wayland-session
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu

[Desktop-packages] [Bug 1983508] ProcCpuinfoMinimal.txt

[Petr Doležal]

apport information

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

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

Title:
  Moving windows between monitors with different scaling causes isues

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When two displays are connected and one has a 200% scaling, moving
  apps between them results in several issues:

  Apps that can actively scale (such as native Nautilus, Settings...):

   When dragging the window around, it automatically adjusts scaling
  based on on which of the monitors is the majority of the app (this is
  probably correct behaviour),

  BUT when using keyboard shortcuts [Ctrl] + [Super] + ←/↑/↓/→,
  fullscreen windows jump around and scale correctly, but half-full
  screen apps (arranged by [Super] + ←/→) cannot go from the larger
  monitor to the smaller, they get stuck in the scaled-up version and
  don't fit on the smaller display.

  Small non-maximized windows don't have this issue, possibly because
  when they first move in their scaled-up state, they do fit on the
  smaller monitor still, and only then are they scaled down.

  
  Apps that don't support changes in scaling and only apply the new scaling on 
a relaunch (such as Chrome) don't have these issues, but they obviously have 
that other problem.

  
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  mutter 3.36.9

  What I expect:
  Windows covering half a full screen, when moved to a different display with 
different scaling (using a keyboard), stay covering half a full screen.

  What happens instead:
  When moved to a display with higher scaling, this happens correctly, but when 
moved to a monitor with lower scaling, they get "stuck" on both monitors in 
their inflated state.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-14 (658 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: mutter 3.36.9-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Tags:  focal wayland-session
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True

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

[Petr Doležal]

apport information

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

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

Title:
  Moving windows between monitors with different scaling causes isues

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When two displays are connected and one has a 200% scaling, moving
  apps between them results in several issues:

  Apps that can actively scale (such as native Nautilus, Settings...):

   When dragging the window around, it automatically adjusts scaling
  based on on which of the monitors is the majority of the app (this is
  probably correct behaviour),

  BUT when using keyboard shortcuts [Ctrl] + [Super] + ←/↑/↓/→,
  fullscreen windows jump around and scale correctly, but half-full
  screen apps (arranged by [Super] + ←/→) cannot go from the larger
  monitor to the smaller, they get stuck in the scaled-up version and
  don't fit on the smaller display.

  Small non-maximized windows don't have this issue, possibly because
  when they first move in their scaled-up state, they do fit on the
  smaller monitor still, and only then are they scaled down.

  
  Apps that don't support changes in scaling and only apply the new scaling on 
a relaunch (such as Chrome) don't have these issues, but they obviously have 
that other problem.

  
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  mutter 3.36.9

  What I expect:
  Windows covering half a full screen, when moved to a different display with 
different scaling (using a keyboard), stay covering half a full screen.

  What happens instead:
  When moved to a display with higher scaling, this happens correctly, but when 
moved to a monitor with lower scaling, they get "stuck" on both monitors in 
their inflated state.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-14 (658 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: mutter 3.36.9-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Tags:  focal wayland-session
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983508/+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 1983490] Re: Auto-hide taskbar does not work quite right

[Daniel Manrique]

** Project changed: canonical-identity-provider => gnome-shell (Ubuntu)

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

Title:
  Auto-hide taskbar does not work quite right

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In Gnome on the latest version of Ubuntu Jammy Jellyfish, the auto-
  hide taskbar feature is broken. The task bar will disappear even when
  there is no overlapping window and the only way to bring it back
  appears to be to move a window down into that region of the display
  and back away from it and then it will re-appear, until it disappears
  again on it own.

  Sorry don't have the time to help with debug of this, but wanted you
  to know. Also I submitted a ubuntu-bug on this bug for some reason it
  gathered all my info and then failed to ask me what the specific
  problem was. So you might want to x-ref this bug report with that
  filing to get all the details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1983490/+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 1983502] Re: [snap] seccomp denials for syscall=314 on amd64

[Simon Déziel]

thunderbird itself seems to be working fine but the crashreport seemed
to have other issues due to Apparmor:

Aug  3 12:02:04 sdeziel-lemur thunderbird_thunderbird.desktop[32515]: 
ExceptionHandler::GenerateDump cloned child 150187
Aug  3 12:02:04 sdeziel-lemur thunderbird_thunderbird.desktop[150187]: 
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Aug  3 12:02:04 sdeziel-lemur thunderbird_thunderbird.desktop[32515]: 
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
Aug  3 12:02:04 sdeziel-lemur kernel: [13893.569377] audit: type=1400 
audit(1659542524.386:509): apparmor="DENIED" operation="open" 
profile="snap.thunderbird.thunderbird" name="/proc/32515/environ" pid=150187 
comm="thunderbird-bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Aug  3 12:02:04 sdeziel-lemur thunderbird_thunderbird.desktop[32711]: Exiting 
due to channel error.
Aug  3 12:02:04 sdeziel-lemur kernel: [13893.827373] audit: type=1326 
audit(1659542524.642:510): auid=1000 uid=1000 gid=1000 ses=9 subj=? pid=150188 
comm="crashreporter" exe="/snap/thunderbird/237/crashreporter" sig=0 
arch=c03e syscall=314 compat=0 ip=0x7e5f095e773d code=0x5
Aug  3 12:02:07 sdeziel-lemur thunderbird_thunderbird.desktop[150188]: Failed 
to open curl lib from binary, use libcurl.so instead

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

Title:
  [snap] seccomp denials for syscall=314 on amd64

Status in thunderbird package in Ubuntu:
  New

Bug description:
  $ snap list thunderbird
  Name VersionRev  Tracking   Publisher   Notes
  thunderbird  102.1.0-2  237  latest/stable  canonical✓  -

  During normal operation, the following is logged:

  Aug 03 12:07:58 foo kernel: audit: type=1326
  audit(1659542878.718:511): auid=1000 uid=1000 gid=1000 ses=9 subj=?
  pid=154377 comm="thunderbird-bin"
  exe="/snap/thunderbird/237/thunderbird-bin" sig=0 arch=c03e
  syscall=314 compat=0 ip=0x7e4137c4473d code=0x5

  And something similar when the crash reporter executes:

  Aug 03 12:02:04 foo kernel: audit: type=1326
  audit(1659542524.642:510): auid=1000 uid=1000 gid=1000 ses=9 subj=?
  pid=150188 comm="crashreporter"
  exe="/snap/thunderbird/237/crashreporter" sig=0 arch=c03e
  syscall=314 compat=0 ip=0x7e5f095e773d code=0x5

  
  # Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  $ uname -a
  Linux foo 5.15.0-43-generic #46~20.04.1-Ubuntu SMP Thu Jul 14 15:20:17 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

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


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

[Desktop-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container

[Matthieu Clemenceau]

** Tags added: fr-2592

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1983085] [NEW] File window display problem

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Open the file window, enter a character through the keyboard to enter
the file search interface, and then click any file immediately from the
right mouse button, the original file information display page will turn
into a black window. I read that the problem is related to the program
"Nautilus", which can be solved by killing it

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

-- 
File window display problem
https://bugs.launchpad.net/bugs/1983085
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to nautilus 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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container

[Steve Langasek]

This fix was incomplete; because all of these packages were installed as
part of a task (ubuntu-server), they are all marked as manually
installed.  So additional changes are needed to remove the packages
pulled in by fwupd.

** Changed in: livecd-rootfs (Ubuntu)
   Status: Fix Released => In Progress

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1983085] Re: File window display problem

[Daniel Manrique]

** Project changed: canonical-identity-provider => nautilus (Ubuntu)

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

Title:
  File window display problem

Status in nautilus package in Ubuntu:
  New

Bug description:
  Open the file window, enter a character through the keyboard to enter
  the file search interface, and then click any file immediately from
  the right mouse button, the original file information display page
  will turn into a black window. I read that the problem is related to
  the program "Nautilus", which can be solved by killing it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1983085/+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 1983605] [NEW] exim4 autopkgtest failure on ppc64el with libx11 1.8

[Jeremy Bicha]

Public bug reported:

I'm just filing a tracker bug for this issue but am not working on it
myself.

exim4's autopkgtest fails with the new libx11 on kinetic on the ppc64el
architecture.

https://autopkgtest.ubuntu.com/packages/e/exim4/kinetic/ppc64el

This test doesn't fail on Debian. Ubuntu's ppc64el is slightly different
than Debian's (we enable -O3 for instance only on that architecture by
default).

https://ci.debian.net/packages/e/exim4/testing/ppc64el/

This issue is blocking other packages from migrating out of kinetic-
proposed.

** Affects: libx11 (Ubuntu)
 Importance: High
 Status: New


** Tags: kinetic update-excuse

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

Title:
  exim4 autopkgtest failure on ppc64el with libx11 1.8

Status in libx11 package in Ubuntu:
  New

Bug description:
  I'm just filing a tracker bug for this issue but am not working on it
  myself.

  exim4's autopkgtest fails with the new libx11 on kinetic on the
  ppc64el architecture.

  https://autopkgtest.ubuntu.com/packages/e/exim4/kinetic/ppc64el

  This test doesn't fail on Debian. Ubuntu's ppc64el is slightly
  different than Debian's (we enable -O3 for instance only on that
  architecture by default).

  https://ci.debian.net/packages/e/exim4/testing/ppc64el/

  This issue is blocking other packages from migrating out of kinetic-
  proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1983605/+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 1900445] Re: LibreOffice 7 Writer and Calc crash when creating new or opening documents

[Manuel]

A few months ago I retried to reset my LibreOffice profile while
starting LO in "safe mode" and ... it worked. The issue disappeared.
Strange as this was something I tried earlier (before attempting to test
the issue with a clean user account). But anyways that solved the issue.

Since then upgraded my Ubuntu 20.04 to 22.04 and the issue is definitely gone.
Thanks to all posters that gave hints helping to solve the issue and many more 
thanks to the LO developers maintaining and continuously improving LO !

Cheers,
Manuel

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

Title:
  LibreOffice 7 Writer and Calc crash when creating new or opening
  documents

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I'm using LibreOffice under Ubuntu 20.04 LTS.
  I've always used LibreOffice PPA depot instead of Ubuntu's.

  Up to version 6.4, no issues.
  When 7.0 became available, LibreOffice got automatically upgraded.
  Since then, when ever I try to create a new Writer or Calc document or when I 
try to open such existing document, LibreOffice crashes immediately, then 
reopens and proposes to recover the document I tried to create/open. If I opt 
to recover, it crashes again. If I opt to discard, LibreOffice opens up but as 
soon as I try to either create new/open either a Writer or Calc document, it 
crashes again.

  I tried to open LibreOffice in safe-mode but to no avail, same behaviour.
  I also tried to reset my user profile but again to no avail.
  I finally tried to disable Java, but here again the crashes continued.

  Opening Impress or Math Formula does not cause issues.
  I haven't tried with Draw, nor Base.

  Attached the crash report I found in /var/crash

  Any help would be welcome.
  In awaiting I rolled back to Ubuntu's depot, thus back to LibreOffice 6.4.6.2 
(as I'm writing these lines).

  Thanks in advance & kind regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1900445/+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 1875015] Re: Displaylink is extremely slow in Xorg sessions

[josh d]

Hi Jeremyszu,
That ppa fixed my issue! Is this going to prevent other upgrades? I am not 
super familiar with how different ppas for same packages would work. I imagine 
a later version will be marked as an update and override those updates.

Daniel,
Unfortunately I tried installing the kubuntu wayland packages and the 
experience was far worse on the dock. So I switched back to x as I'm a pretty 
big kde fan (I saw some reports that KDE wayland was a bit half baked as of yet 
across the web, I'm not really in the know). I might switch to gnome to try it 
out as it has been some years. When I do that I'll definitely try wayland again.

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

Title:
  Displaylink is extremely slow in Xorg sessions

Status in Nouveau Xorg driver:
  New
Status in OEM Priority Project:
  New
Status in xf86-video-amd:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  In Progress
Status in xorg-server source package in Focal:
  Fix Released
Status in xorg-server source package in Hirsute:
  Won't Fix
Status in xorg-server source package in Impish:
  Fix Released
Status in xorg-server source package in Jammy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Jammy:
  New
Status in xserver-xorg-video-nouveau source package in Jammy:
  New

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

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


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

[Desktop-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container

[Steve Langasek]

** Changed in: livecd-rootfs (Ubuntu)
   Status: In Progress => Fix Committed

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1952533] Re: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sometimes if I run `pulseaudio -k` a few times, sound returns.
  Sometimes if I run `sudo alsa force-reload`, sound returns.
  Sometimes if I shutdown and start the laptop, sound returns.

  This first occurred a few months ago when I was running 20.04, and I
  upgraded to 21.10 in the hope it would fix the issue. It did not -
  sound continues to be intermittent.

  I use the Brave browser, not firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sheehan3636 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 27 20:21:47 2021
  InstallationDate: Installed on 2021-10-15 (43 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IE:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   Nov 27 19:00:54 xps systemd[1436]: pulseaudio.service: Deactivated 
successfully.
   Nov 27 19:01:05 xps systemd[1436]: pulseaudio.socket: Deactivated 
successfully.
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2021
  dmi.bios.release: 1.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd07/09/2021:br1.16:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-27T18:59:43.285943

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952533/+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 1952533] Re: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while

[Michael Nahas]

I have the same problem.  It started late in 2021, I think.  I have no
damn clue what's going on.

Sound often works when booting from "off".  It often breaks if I put my
laptop to sleep and wake it.  It may break at other times?

When the sound stops, it stops sound on the whole machine.  I have a
USB-A to 3.5" headphone adapter and I thought I could use that because
it is separate hardware, but, no, that doesn't work either.

I've tried blacklisting the snd_hda_codec_realtek module, but it still happens. 
 
I've tried installing the original OS (Ubuntu 18.04 from Dell) and it still 
happens.  

Maybe I zapped the audio card with static electricity and it stopped
working?  But why would that affect the USB-A dongle?

Maybe there was a firmware update from Dell that changed its behavior?

I'm stupified.  But I need audio.  I love Linux, but I'm thinking of
abandoning Linux and going to MacOS, because I need working audio!

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

Title:
  [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sometimes if I run `pulseaudio -k` a few times, sound returns.
  Sometimes if I run `sudo alsa force-reload`, sound returns.
  Sometimes if I shutdown and start the laptop, sound returns.

  This first occurred a few months ago when I was running 20.04, and I
  upgraded to 21.10 in the hope it would fix the issue. It did not -
  sound continues to be intermittent.

  I use the Brave browser, not firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sheehan3636 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 27 20:21:47 2021
  InstallationDate: Installed on 2021-10-15 (43 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IE:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   Nov 27 19:00:54 xps systemd[1436]: pulseaudio.service: Deactivated 
successfully.
   Nov 27 19:01:05 xps systemd[1436]: pulseaudio.socket: Deactivated 
successfully.
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2021
  dmi.bios.release: 1.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd07/09/2021:br1.16:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-27T18:59:43.285943

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952533/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Nathan Teodosio]

** Description changed:

  To test the snap with VA-API changes,
  
- 1. Install the snap with
+ 0. If you have Nvidia GPU, you need Snapcraft >=7.1.1. Check `snap info
+ snapcraft`. At the time of writing,
+ 
+sudo snap refresh --channel 7.x/beta snapcraft
+ 
+ 1. Install the Chromium snap,
  
     sudo snap install --channel candidate/hwacc chromium
  
  2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
  --enable-features=VaapiVideoDecoder
  
  3. Open a video, e.g. one from https://github.com/chthomos/video-media-
  samples
  
  4. Enter about:media-internals in the address bar and note what the page
  says for kVideoDecoderName.
  
  Please report
  
  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
-   - If failed, the video used for testing, including codec and resolution if 
possible;
- - Distro version (if in doubt, `grep VERSION= /etc/os_release`);
- - GPU (if in doubt, attach the output of `lscpu`);
- - CPU generation (if in doubt, attach the output of `lscpu`).
+   - If failed, the video used for testing, including codec and resolution if 
possible;
+ - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
+ - Distro version (`grep VERSION= /etc/os_release`);
+ - GPU (`lscpu`);
+ - CPU generation (`lscpu`).
  
  About the last point, it may be that unfortunately only those with newer
  generations of Intel CPUs will have luck with this, but it's still an
  uncertainty. So reports are highly welcome.
  
  --Original Bug report -
  
  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)
  
  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium
  
  My amdgpu can use libva
  
  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  0. If you have Nvidia GPU, you need Snapcraft >=7.1.1. Check `snap
  info snapcraft`. At the time of writing,

 sudo snap refresh --channel 7.x/beta snapcraft

  1. Install the Chromium snap,

     sudo snap install --channel candidate/hwacc chromium

  2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
  --enable-features=VaapiVideoDecoder

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples

  4. Enter about:media-internals in the address bar and note what the
  page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
    - If failed, the video used for testing, including codec and resolution if 
possible;
  - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
  - Distro version (`grep VERSION= /etc/os_release`);
  - GPU (`lscpu`);
  - CPU generation (`lscpu`).

  About the last point, it may be that unfortunately only those with
  newer generations of Intel CPUs will have luck with this, but it's
  still an uncertainty. So reports are highly welcome.

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main

[Desktop-packages] [Bug 1983490] Re: Auto-hide taskbar does not work quite right

[David Spain]

Additional info on this issue, how to reproduce. If I have multiple
windows open in an app but collapsed onto the task bar, then click on
the taskbar app icon and put up one window and then left-click on the
icon again to see the other windows and then select another one (left-
click), the 2nd window pops up but the task bar hides even if the window
is not overlapping. Worst case is if I then minimize all windows I can't
get the task bar back unless I either disable auto-hide OR right click
on the desktop to bring up a new terminal window and then drag it down
into the task bar region and back up again. Just mousing into the hidden
task bar region does nothing.

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

Title:
  Auto-hide taskbar does not work quite right

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In Gnome on the latest version of Ubuntu Jammy Jellyfish, the auto-
  hide taskbar feature is broken. The task bar will disappear even when
  there is no overlapping window and the only way to bring it back
  appears to be to move a window down into that region of the display
  and back away from it and then it will re-appear, until it disappears
  again on it own.

  Sorry don't have the time to help with debug of this, but wanted you
  to know. Also I submitted a ubuntu-bug on this bug for some reason it
  gathered all my info and then failed to ask me what the specific
  problem was. So you might want to x-ref this bug report with that
  filing to get all the details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1983490/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Sergio Schvezov]

Snapcraft 7.1.1 is now on the stable channel

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  0. If you have Nvidia GPU, you need Snapcraft >=7.1.1. Check `snap
  info snapcraft`. At the time of writing,

 sudo snap refresh --channel 7.x/beta snapcraft

  1. Install the Chromium snap,

     sudo snap install --channel candidate/hwacc chromium

  2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
  --enable-features=VaapiVideoDecoder

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples

  4. Enter about:media-internals in the address bar and note what the
  page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
    - If failed, the video used for testing, including codec and resolution if 
possible;
  - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
  - Distro version (`grep VERSION= /etc/os_release`);
  - GPU (`lscpu`);
  - CPU generation (`lscpu`).

  About the last point, it may be that unfortunately only those with
  newer generations of Intel CPUs will have luck with this, but it's
  still an uncertainty. So reports are highly welcome.

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1981581] Re: failed to upgrade my system is unrecoverable

[Launchpad Bug Tracker]

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

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

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

Title:
  failed to upgrade my system is unrecoverable

Status in libwmf package in Ubuntu:
  Fix Released
Status in libwmf source package in Jammy:
  Confirmed
Status in libwmf source package in Kinetic:
  Fix Released

Bug description:
  Unpacking libwmf-0.2-7-gtk (0.2.12-5ubuntu1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-TGLGzY/48-libwmf-0.2-7-gtk_0.2.12-5ubuntu1_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/io-wmf.so', which is 
also in package libwmf0.2-7-gtk 0.2.8.4-17ubuntu2

  
  this exploaded my impish upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwmf/+bug/1981581/+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 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-meta (Ubuntu Jammy)
   Status: New => Confirmed

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

Title:
  autoinstall ssh:install-server:false is misleading in 22.04

Status in subiquity:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Jammy:
  Confirmed

Bug description:
  With 22.04, openssh-server is baked into the image curtin copies to
  the target.  The ssh:install-server key no longer controls whether
  openssh-server gets installed.  It should be easy enough to have the
  bit of code that installs openssh-server when the key is true also
  remove it when the key is false.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1974483/+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 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  autoinstall ssh:install-server:false is misleading in 22.04

Status in subiquity:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Jammy:
  Confirmed

Bug description:
  With 22.04, openssh-server is baked into the image curtin copies to
  the target.  The ssh:install-server key no longer controls whether
  openssh-server gets installed.  It should be easy enough to have the
  bit of code that installs openssh-server when the key is true also
  remove it when the key is false.

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


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

[Desktop-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.774

---
livecd-rootfs (2.774) kinetic; urgency=medium

  * Remove modemmanager and udisks2 from cloud images in addition to fwupd.
The use of tasks at install means all packages are marked manually
installed in the apt database, so removing fwupd does not remove its
dependencies.  LP: #1981109.

 -- Steve Langasek   Thu, 04 Aug 2022
11:24:55 -0700

** Changed in: livecd-rootfs (Ubuntu)
   Status: Fix Committed => Fix Released

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1983605] Re: exim4 autopkgtest failure on ppc64el with libx11 1.8

[Jeremy Bicha]

** Tags added: rls-kk-incoming

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

Title:
  exim4 autopkgtest failure on ppc64el with libx11 1.8

Status in libx11 package in Ubuntu:
  New

Bug description:
  I'm just filing a tracker bug for this issue but am not working on it
  myself.

  exim4's autopkgtest fails with the new libx11 on kinetic on the
  ppc64el architecture.

  https://autopkgtest.ubuntu.com/packages/e/exim4/kinetic/ppc64el

  This test doesn't fail on Debian. Ubuntu's ppc64el is slightly
  different than Debian's (we enable -O3 for instance only on that
  architecture by default).

  https://ci.debian.net/packages/e/exim4/testing/ppc64el/

  This issue is blocking other packages from migrating out of kinetic-
  proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1983605/+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 1875015] Re: Displaylink is extremely slow in Xorg sessions

[Daniel van Vugt]

When I say "Wayland in Mutter" I do mean GNOME. That's what we are
involved in the development of, and recommend as the primary Ubuntu
environment.

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

Title:
  Displaylink is extremely slow in Xorg sessions

Status in Nouveau Xorg driver:
  New
Status in OEM Priority Project:
  New
Status in xf86-video-amd:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  In Progress
Status in xorg-server source package in Focal:
  Fix Released
Status in xorg-server source package in Hirsute:
  Won't Fix
Status in xorg-server source package in Impish:
  Fix Released
Status in xorg-server source package in Jammy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Jammy:
  New
Status in xserver-xorg-video-nouveau source package in Jammy:
  New

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1983490] Re: Auto-hide taskbar does not work quite right

[Daniel van Vugt]

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

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 1983130, 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.


** Tags added: jammy

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

** This bug has been marked a duplicate of bug 1983130
   Ubuntu dock set to auto-hide hides after a right-click menu is closed even 
when there are no reasons for it to do so.

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

Title:
  Auto-hide taskbar does not work quite right

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

Bug description:
  In Gnome on the latest version of Ubuntu Jammy Jellyfish, the auto-
  hide taskbar feature is broken. The task bar will disappear even when
  there is no overlapping window and the only way to bring it back
  appears to be to move a window down into that region of the display
  and back away from it and then it will re-appear, until it disappears
  again on it own.

  Sorry don't have the time to help with debug of this, but wanted you
  to know. Also I submitted a ubuntu-bug on this bug for some reason it
  gathered all my info and then failed to ask me what the specific
  problem was. So you might want to x-ref this bug report with that
  filing to get all the details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1983490/+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 1983508] Re: Moving windows between monitors with different scaling causes isues

[Daniel van Vugt]

Thanks. This sounds like a problem with mutter's window constraints
logic.

I would recommend that you:

1. Confirm the bug is still present in GNOME 42 (Ubuntu 22.04); and then

2. Report it upstream at https://gitlab.gnome.org/GNOME/mutter/issues

3. Tell us the new issue ID.


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

** Tags added: multimonitor scaling

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

Title:
  Moving windows between monitors with different scaling causes isues

Status in mutter package in Ubuntu:
  New

Bug description:
  When two displays are connected and one has a 200% scaling, moving
  apps between them results in several issues:

  Apps that can actively scale (such as native Nautilus, Settings...):

   When dragging the window around, it automatically adjusts scaling
  based on on which of the monitors is the majority of the app (this is
  probably correct behaviour),

  BUT when using keyboard shortcuts [Ctrl] + [Super] + ←/↑/↓/→,
  fullscreen windows jump around and scale correctly, but half-full
  screen apps (arranged by [Super] + ←/→) cannot go from the larger
  monitor to the smaller, they get stuck in the scaled-up version and
  don't fit on the smaller display.

  Small non-maximized windows don't have this issue, possibly because
  when they first move in their scaled-up state, they do fit on the
  smaller monitor still, and only then are they scaled down.

  
  Apps that don't support changes in scaling and only apply the new scaling on 
a relaunch (such as Chrome) don't have these issues, but they obviously have 
that other problem.

  
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  mutter 3.36.9

  What I expect:
  Windows covering half a full screen, when moved to a different display with 
different scaling (using a keyboard), stay covering half a full screen.

  What happens instead:
  When moved to a display with higher scaling, this happens correctly, but when 
moved to a monitor with lower scaling, they get "stuck" on both monitors in 
their inflated state.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-14 (658 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: mutter 3.36.9-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Tags:  focal wayland-session
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True

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

[Rhustum L. Evaristo]

Using Remmina 1.4.27 (git n/a)

LSB Version:
core-11.1.0ubuntu4-noarch:printing-11.1.0ubuntu4-noarch:security-11.1.0ubuntu4-noarch
Distributor ID: Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename:   jammy

Not Working cannot connect to RDP

-- 
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:
  Incomplete
Status in freerdp2 source package in Jammy:
  Incomplete

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 1983638] [NEW] Ubuntu 22.10 Settings-sound-output-test does not work

[corrado venturini]

Public bug reported:

Open settings. select sound. System Volume and Volume for System Sounds are at 
maximum, Output Device is HDMI / DisplayPort2 - Built-in Audio
click on Test and then on Left or Right speaker has no effect (no sound) but 
clicking on Alert Sound works fine.
Playing a movie.MOV with totem sound is ok.
On the same PC different partition I have Ubuntu 22.04 and problem does not 
occur.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-control-center 1:42.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.22.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug  5 07:06:31 2022
InstallationDate: Installed on 2022-07-19 (16 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Ubuntu 22.10 Settings-sound-output-test does not work

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

Bug description:
  Open settings. select sound. System Volume and Volume for System Sounds are 
at maximum, Output Device is HDMI / DisplayPort2 - Built-in Audio
  click on Test and then on Left or Right speaker has no effect (no sound) but 
  clicking on Alert Sound works fine.
  Playing a movie.MOV with totem sound is ok.
  On the same PC different partition I have Ubuntu 22.04 and problem does not 
occur.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:42.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  5 07:06:31 2022
  InstallationDate: Installed on 2022-07-19 (16 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[msaxl]

@t2t-exe some questions:
is the error message exactly the one mentioned here?
what version is the target rdp server (Windows7, Windows 10, Windows Server 
2019, ..)?
since you use a new remmina version, what is the tls security level set to?

-- 
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:
  Incomplete
Status in freerdp2 source package in Jammy:
  Incomplete

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