date:20220919

The same workaround would fix https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4830

** Tags added: dt-651

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

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

Title:
  Screen freeze when performing memory stress in Wayland mode

Status in Linux:
  Unknown
Status in Mutter:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Opinion

Bug description:
  [Steps to reproduce]
  (disable systemd-oomd or executing over ssh)
  (below command allocates a lot of memory to stress kernel page fault)

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  [Expected result]
  Screen will update slowly when performing the stress-test.
  but screen needs back to work after stress.

  [Actual result]
  Screen freeze after stress test.

  [Additional information]
  kernel version: vmlinuz-5.17.0-1017-oem
  kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
  Mesa version: 22.0.5-0ubuntu0.1
  Mutter version: 42.2-0ubuntu1
  Gnome-shell version: 42.2-0ubuntu0.2

  * Issue happens in Wayland only

  * gnome-shell keeps issuing ioctl()
  ```
  (gdb) bt
  #0  __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at 
../sysdeps/unix/sysv/linux/ioctl.c:36
  #1  0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, 
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
  #2  iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, 
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
  #3  iris_wait_syncobj (bufmgr=, syncobj=, 
timeout_nsec=timeout_nsec@entry=9223372036854775807) at 
../src/gallium/drivers/iris/iris_fence.c:215
  #4  0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, 
wait=, query=0x55774159b800, ctx=) at 
../src/gallium/drivers/iris/iris_query.c:635
  #5  iris_get_query_result (ctx=, query=0x55774159b800, 
wait=, result=0x7fffc5404e50) at 
../src/gallium/drivers/iris/iris_query.c:601
  #6  0x7fcaca405e89 in tc_get_query_result (_pipe=, 
query=0x55774159b800, wait=, result=0x7fffc5404e50) at 
../src/gallium/auxiliary/util/u_threaded_context.c:881
  #7  0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, 
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at 
../src/mesa/main/queryobj.c:266
  #8  0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, 
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
  #9  get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 
"glGetQueryObjecti64v", id=, pname=34918, 
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
  at ../src/mesa/main/queryobj.c:1174
  #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, 
pname=, params=) at 
../src/mesa/main/queryobj.c:1257
  #11 0x7fcadfa39b90 in ?? () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #20 0x7fcae0743c24 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #22 0x7fcae0743293 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #23 0x7fcadf8d0849 in meta_context_run_main_loop () from 
/lib/x86_64-linux-gnu/libmutter-10.so.0
  #24 0x55773f1a4f12 in ?? ()
  #25 0x7fcadf429d90 in __libc_start_call_main 
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1, 
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
  #26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70, 
argc=1, argv=0x7fffc54053e8, init=, fini=, 
rtld_fini=, stack_end=0x7fffc54053d8)
  at ../csu/libc-start.c:392
  #27 0x55773f1a51b5 in ?? ()
  ```

  Other discussion thread:
  https://gitlab.freedesktop.org/drm/intel/-/issues/6851
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2431

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter (not installed)
  Uname: Linux 5.18.0-rc2+ x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5json:
   {

[Desktop-packages] [Bug 1990113] [NEW] Increase timeout on test doc-check for RISC-V

2022-09-19 Thread Alexandre Ghiti

Public bug reported:

The doc-check test fails on RISC-V because it is a very slow
architecture: fix this by increasing the timeout on this specific test.

** Affects: json-glib (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Increase timeout on test doc-check for RISC-V

Status in json-glib package in Ubuntu:
  New

Bug description:
  The doc-check test fails on RISC-V because it is a very slow
  architecture: fix this by increasing the timeout on this specific
  test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1990113/+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 1989844] Re: Quick settings changes spacing when toggling Dark Mode

** Bug watch added: github.com/ubuntu/yaru/issues #3734
   https://github.com/ubuntu/yaru/issues/3734

** Also affects: yaru via
   https://github.com/ubuntu/yaru/issues/3734
   Importance: Unknown
   Status: Unknown

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

Title:
  Quick settings changes spacing when toggling Dark Mode

Status in Yaru Theme:
  Unknown
Status in yaru-theme package in Ubuntu:
  New

Bug description:
  Quick settings changes spacing when toggling Dark Mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/1989844/+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 1990113] Re: Increase timeout on test doc-check for RISC-V

2022-09-19 Thread Alexandre Ghiti

The package built successfully here:

https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13962373/+listing-
archive-extra

** Attachment added: "debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1990113/+attachment/5616956/+files/debdiff

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

Title:
  Increase timeout on test doc-check for RISC-V

Status in json-glib package in Ubuntu:
  New

Bug description:
  The doc-check test fails on RISC-V because it is a very slow
  architecture: fix this by increasing the timeout on this specific
  test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1990113/+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 1970663]

2022-09-19 Thread wmccarty

(In reply to Alexandre LISSY :gerard-majax from comment #8)
> Anyone who might be still experiencing this, please reopen and share as much 
> as infos as possible.

Hey Alexandre,

I am on the development branch Kubuntu 22.10 and I am experiencing this
issue, this is on my HTPC using a 4K TV. My partner rebooted the
computer mid upgrade from 20.04 -> 22.04 so I had to choose to either
waste time by reinstalling and resetting all settings I made from
memory, or reinstall the OS to a newer version with 22.10 a little more
than a month away. Chromium seems to retain the correct cursor size
where Firefox does not. I have tried a few different options however
nothing was working.

Would it help to have a cursor override size something like widget.non-
native-theme.scrollbar.size.override does?

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

Title:
  Tiny mouse cursor in firefox snap

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Since a few day I've updated to Ubuntu Mate 22.04 with the firefox
  snap. Since then I've been having this strange bug. I have a 4k screen
  which I'm running at a 2180p resolution with scaling on HiDPI. This
  runs just fine except for in firefox. In the new firefox snap I get a
  really tiny mouse cursor. I also checked other snap, it is not the
  case there.

  Regards,
  Chris
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-02 (83 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: ubuntu-mate-artwork
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Snap: firefox 99.0.1-1 (stable)
  Snap.Changes: no changes found
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-02 (83 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: ubuntu-mate-artwork
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Snap: firefox 99.0.1-1 (stable)
  Snap.Changes: no changes found
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

2022-09-19 Thread Sahab-yazdani+github

I just updated from Ubuntu 20.04 LTS to Ubuntu 22.04 LTS and part of the
upgrade said that Firefox would be moving to Snap as opposed to apt (i
guess?) and I am now experiencing this cursor "too small issue".

I did some googling online and nothing really relevant popped up, but I
can confirm a couple of details that seemed relevant:

* Firefox version 104.0.2 (which I believe is the latest?)
* 4K display with scaling set to 200% in Gnome
* nVidia drivers up to date (515.65.01)
* doesn't matter if the compositor (i think that's what you call it?) is 
Wayland or x11
* according to Gnome Tweaks, cursor theme is "Yaru". I tried a couple of the 
other ones and didn't see any changes. In particular I tried DMZ-White and 
DMZ-Black since i read on some reddit post that it might help.

I've never filed a bug like this before, so not sure if there is any
other information that is relevant, but if you let me know what you need
to triage, I am happy to oblige.

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

Title:
  Tiny mouse cursor in firefox snap

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Since a few day I've updated to Ubuntu Mate 22.04 with the firefox
  snap. Since then I've been having this strange bug. I have a 4k screen
  which I'm running at a 2180p resolution with scaling on HiDPI. This
  runs just fine except for in firefox. In the new firefox snap I get a
  really tiny mouse cursor. I also checked other snap, it is not the
  case there.

  Regards,
  Chris
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-02 (83 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: ubuntu-mate-artwork
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Snap: firefox 99.0.1-1 (stable)
  Snap.Changes: no changes found
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-02 (83 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: ubuntu-mate-artwork
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Snap: firefox 99.0.1-1 (stable)
  Snap.Changes: no changes found
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1989325] Re: gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1

2022-09-19 Thread maarten

Well, I have the choice in my BIOS between hybrid graphics and discrete
graphics, no option to disable the discrete graphics card entirely. And
before you ask: I will not run on the discrete graphics card alone,
because of the battery drain that comes with it

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

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

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

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

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


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

[Desktop-packages] [Bug 1989656] Re: Unable to logout or switch user on Ubuntu 22.04

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

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

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

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

Title:
  Unable to logout or switch user on Ubuntu 22.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  - Whenever attempting to logout user or switch user, process is stuck
  on a black blank screen with flickering horizontal cursor.  Have to
  restart pc to exit state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989656/+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 1989729] Re: Problem with graphics card

Thanks for the bug report. I can't yet see anything wrong with the
machine. Can you describe the problem in more detail, maybe with a
video?


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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Problem with graphics card

Status in Ubuntu:
  Incomplete

Bug description:
  Hi,Names Hamdaan. I have installed Ubuntu on my PC about 4-5 days ago.
  At first I didn't seem to notice, But as I used my PC I've been
  noticing that it seems that my PC's graphics card is not working as
  efficient as before. But when I read the driver name I got to know
  that it has not downloaded the correct Driver software , and I don't
  know how to fix that?. Thanks in advance for answering.

  IN CASE YOU NEED IT:
   PC MODEL: Acer Aspire E1-572
   MEMORY  : 4.0 GiB
  PROCESSER: Intel® Core™ i5-4200U CPU @ 1.60GHz × 4
   OS TYPE : 64x

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 15 17:46:25 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Haswell-ULT Integrated Graphics 
Controller [1025:0775]
  InstallationDate: Installed on 2022-09-13 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Aspire E1-572
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=fcb232d7-2139-4cee-b321-7332acc47658 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2014
  dmi.bios.release: 2.17
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.17
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HW
  dmi.board.vendor: Acer
  dmi.board.version: V2.17
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 2.17
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.17:bd09/02/2014:br2.17:efr2.17:svnAcer:pnAspireE1-572:pvrV2.17:rvnAcer:rnEA50_HW:rvrV2.17:cvnAcer:ct10:cvrChassisVersion:skuAspireE1-572_0775_V2.17:
  dmi.product.family: SharkBay System
  dmi.product.name: Aspire E1-572
  dmi.product.sku: Aspire E1-572_0775_V2.17
  dmi.product.version: V2.17
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1989325] Re: gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1

OK, next time (each time) the crash happens, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

5. Redo the steps in comment #2 at the top of the page.

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

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

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

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

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


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

[Desktop-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode

2022-09-19 Thread Bug Watch Updater

** Changed in: linux
   Status: Unknown => New

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  Screen freeze when performing memory stress in Wayland mode

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Opinion

Bug description:
  [Steps to reproduce]
  (disable systemd-oomd or executing over ssh)
  (below command allocates a lot of memory to stress kernel page fault)

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  [Expected result]
  Screen will update slowly when performing the stress-test.
  but screen needs back to work after stress.

  [Actual result]
  Screen freeze after stress test.

  [Additional information]
  kernel version: vmlinuz-5.17.0-1017-oem
  kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
  Mesa version: 22.0.5-0ubuntu0.1
  Mutter version: 42.2-0ubuntu1
  Gnome-shell version: 42.2-0ubuntu0.2

  * Issue happens in Wayland only

  * gnome-shell keeps issuing ioctl()
  ```
  (gdb) bt
  #0  __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at 
../sysdeps/unix/sysv/linux/ioctl.c:36
  #1  0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, 
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
  #2  iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, 
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
  #3  iris_wait_syncobj (bufmgr=, syncobj=, 
timeout_nsec=timeout_nsec@entry=9223372036854775807) at 
../src/gallium/drivers/iris/iris_fence.c:215
  #4  0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, 
wait=, query=0x55774159b800, ctx=) at 
../src/gallium/drivers/iris/iris_query.c:635
  #5  iris_get_query_result (ctx=, query=0x55774159b800, 
wait=, result=0x7fffc5404e50) at 
../src/gallium/drivers/iris/iris_query.c:601
  #6  0x7fcaca405e89 in tc_get_query_result (_pipe=, 
query=0x55774159b800, wait=, result=0x7fffc5404e50) at 
../src/gallium/auxiliary/util/u_threaded_context.c:881
  #7  0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, 
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at 
../src/mesa/main/queryobj.c:266
  #8  0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, 
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
  #9  get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 
"glGetQueryObjecti64v", id=, pname=34918, 
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
  at ../src/mesa/main/queryobj.c:1174
  #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, 
pname=, params=) at 
../src/mesa/main/queryobj.c:1257
  #11 0x7fcadfa39b90 in ?? () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #20 0x7fcae0743c24 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #22 0x7fcae0743293 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #23 0x7fcadf8d0849 in meta_context_run_main_loop () from 
/lib/x86_64-linux-gnu/libmutter-10.so.0
  #24 0x55773f1a4f12 in ?? ()
  #25 0x7fcadf429d90 in __libc_start_call_main 
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1, 
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
  #26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70, 
argc=1, argv=0x7fffc54053e8, init=, fini=, 
rtld_fini=, stack_end=0x7fffc54053d8)
  at ../csu/libc-start.c:392
  #27 0x55773f1a51b5 in ?? ()
  ```

  Other discussion thread:
  https://gitlab.freedesktop.org/drm/intel/-/issues/6851
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2431

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter (not installed)
  Uname: Linux 5.18.0-rc2+ x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5json:
   {
     "result": "skip"
   }
  Date: Mon Sep 19 10:39:59 2022
  DistributionChannelDescriptor:
   # This is the distribution channel

[Desktop-packages] [Bug 1990024] Re: screenshot a window captures also a large border

2022-09-19 Thread Bug Watch Updater

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  screenshot a window captures also a large border

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Using screenshot to capture a window the screenshot contains also a large 
border.
  This not happen selecting an area.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 17 07:30:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-09-08 (8 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908)
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1990024/+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 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

** Changed in: snapd
   Status: New => In Progress

** Changed in: snapd
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

Status in snapd:
  In Progress
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  1) lsb_release -rd

  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04
  (Kubuntu Jammy live session in QEMU VM)

  2) apt-cache policy ubuntu-release-upgrader-core
  ubuntu-release-upgrader-core:
    Installed: 1:22.04.6

  3) expected

  (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.)

  * Firefox icon on panel to be intact.
  * Clicked icon launches browser.
  * Icon tooltip/mouse hover to describe application.

  4) happened instead

  * Icon is missing/replaced with a generic icon
  * Icon click produces error notification "Plasma Workspace - 
preferred://browser"
  * Icon tooltip/mouse hover appears, though is blank.

  Additional info:
  * firefox is still installed, works as expected.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-07 (2 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Package: ubuntu-release-upgrader (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1964036/+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 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-09-19 Thread J G

Problem to install/read Belgium e-Id. Is this the problem bug? Is there
a working work-around available?

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

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

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  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/firefox/+bug/1967632/+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 1857392] Re: Window manager warning: Overwriting existing binding of keysym...

2022-09-19 Thread Rudolf Leitgeb

System hangs may well be caused by this bug, because these log lines
tend to fill up the file system.

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

Title:
  Window manager warning: Overwriting existing binding of keysym...

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) Gnome 3.34.1
  3) No error.
  4) Error in Ubuntu Logs App.

  Sender: gnome-shell
  Message:
  4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 
GMT-0600 (CST)
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 37 with keysym 37 (keycode 10).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 36 with keysym 36 (keycode f).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 35 with keysym 35 (keycode e).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 34 with keysym 34 (keycode d).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 32 with keysym 32 (keycode b).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 39 with keysym 39 (keycode 12).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 33 with keysym 33 (keycode c).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 38 with keysym 38 (keycode 11).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 31 with keysym 31 (keycode a).
  Audit Session: 2
  Priority: 6

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1857392/+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 1987976] Re: firefox black window

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

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

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

Title:
  firefox black window

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

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1987976/+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 1989821] Re: Firefox hangs, unable to reload tabs for up to 2min after switching to session that was idle for several hours

Thanks for the detailed report Steve. What would be interesting to test
is whether this is an Ubuntu-specific problem caused by the packaging,
or if it also happens with binaries distributed by upstream. Could you
test that and report here? The upstream binaries can be downloaded from
https://download.mozilla.org/?product=firefox-latest-ssl&os=linux64.

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

Title:
  Firefox hangs, unable to reload tabs for up to 2min after switching to
  session that was idle for several hours

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  I am not sure when exactly this started. I feel like it was around FF
  v99.

  System is always on. 2 user accounts (mine, wife's). We keep the
  desktop sessions logged-in, just switch between accounts whenever
  needed. Firefox stays open since it's heavily used. When an active
  session is unlocked or switched to after being unused for several
  hours (not rigorously measured but I'd say more than 6-8 hours), we
  observe the following behavior in Firefox:

  * Gmail tab will show a message at the top of the page along the lines of 
"Not connected, retrying in 3:00" with the timer counting down
  * For the first 10-20s, clicking on another tab will have no effect - FF 
doesn't switch to the tab
  * From 20s to between 1-2 minutes:
    - Switching tabs will work albeit slowly.
    - Reloading an existing tab does nothing except cause the side-to-side 
loading indicator on the tab to cycle
    - I am able to open a new tab via ctrl-T
    - I can enter a URL into a new tab, but the site doesn't load. The loading 
indicator cycles in the tab title.
    - I cannot open about:performance to troubleshoot

  After some period of time, as short as 30-40s and as long as 2
  minutes, FF becomes usable again. Sites can be loaded/reloaded, etc.

  What I have tried, but has not resolved the issue:
  * Restart FF in troubleshooting mode
  * Upgrade to new releases as they are available in the package manager
  * Run in non-troubleshooting mode but with all extensions removed
  * Refresh the browser
  * Set browser.tabs.unloadOnLowMemory = false
  * rm -rf ~/.mozilla and start with a fresh profile

  Workaround: killall -9 firefox, then relaunch firefox

  Again, this seems to have started suddenly at some point possibly
  around the v99 timeframe. Prior to that, I did not observe this
  problem. Hardware, and to the best of my knowledge the usage habits of
  the 2 users, have not changed in quite some time.

  I've attached the output of a "vmstat 1" command that I launched when
  I unlocked a session that was idle for approximately 40h, before
  interacting with the existing firefox session. The firefox issue
  manifested for about 1min 20s. Once firefox became usable, I stopped
  the vmstat command.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 104.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195
  Uname: Linux 5.4.0-124-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyr   743015 F pulseaudio
   /dev/snd/controlC1:  tyr   743015 F pulseaudio
  BuildID: 20220818191623
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Sep 15 18:38:25 2022
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-01-05 (2444 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IpRoute:
   default via 192.168.1.1 dev eth0 proto static metric 100
   192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.100 metric 100
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:302
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=104.0/20220818191623 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2021-02-04 (588 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To

[Desktop-packages] [Bug 1971738] Re: [MIR] ell

2022-09-19 Thread Sebastien Bacher

The source had already been promoted it seems, I subscribed the desktop-
packages team and promoted libell0 now


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

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

Title:
  [MIR] ell

Status in ell package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
  The package ell is already in Ubuntu universe.
  The package ell build for the architectures it is designed to work on.
  It currently builds and works for architetcures: amd64 arm64 armhf ppc64el 
riscv64 s390x
  Link to package https://launchpad.net/ubuntu/+source/ell

  [Rationale]
  - The package ell is required in Ubuntu main as a depends of iwd which it is 
going to replace wpa as our default wireless daemon
  - The package ell is required in Ubuntu main no later than aug 25 due to 
feature freeze

  [Security]
  - Had 1 security issues in the past
    - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36081
    - https://ubuntu.com/security/CVE-2021-36081
  which is marked as needs triage in Ubuntu

  - no `suid` or `sgid` binaries
  - no executables in `/sbin` and `/usr/sbin`
  - Package does not install services, timers or recurring jobs
  - Packages does not open privileged ports (ports < 1024)
  - Packages does not contain extensions to security-sensitive software

  [Quality assurance - function/usage]
  - The package works well right after install

  [Quality assurance - maintenance]
  - The package is maintained well in Debian/Ubuntu and has no open reports
    - Ubuntu https://bugs.launchpad.net/ubuntu/+source/ell/+bug
    - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ell
  - The package does not deal with exotic hardware we cannot support

  [Quality assurance - testing]
  - The package runs a test suite on build time, if it fails
    it makes the build fail, link to build log 
https://launchpadlibrarian.net/599097548/buildlog_ubuntu-kinetic-amd64.ell_0.50-1_BUILDING.txt.gz

  
  Testsuite summary for ell 0.50
  
  # TOTAL: 40
  # PASS:  40

  - The package does not run an autopkgtest, patch submitted to Debian
  to add one https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010669

  and added to Ubuntu now
  https://autopkgtest.ubuntu.com/packages/e/ell

  [Quality assurance - packaging]
  - debian/watch is present and works

  - Lintian has only minor warnings, https://lintian.debian.org/sources/ell
  - Lintian overrides are not present

  - This package does not rely on obsolete or about to be demoted packages.
  - This package has no python2 or GTK2 dependencies

  - The package will be installed by default, but does not ask debconf
  - Packaging and build is easy, link to d/rules 
https://salsa.debian.org/debian/ell/-/blob/debian/sid/debian/rules

  [UI standards]
  - Application is not end-user facing (does not need translation)

  [Dependencies]
  - No further depends or recommends dependencies that are not yet in main

  [Standards compliance]
  - This package correctly follows FHS and Debian Policy

  [Maintenance/Owner]
  - desktop-packages is not yet, but will subscribe to the package before 
promotion

  - This does not use static builds
  - This does not use vendored code
  - The package has been built in the archive more recently than the last test 
rebuild

  [Background information]
  The Package description explains the package well
  Upstream Name is ell
  Link to upstream project https://git.kernel.org/pub/scm/libs/ell/ell.git/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ell/+bug/1971738/+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 1971739] Re: [MIR] iwd

2022-09-19 Thread Sebastien Bacher

desktop-packages subscribed and package promoted now

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

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

Title:
  [MIR] iwd

Status in iwd package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
  The package iwd is already in Ubuntu universe.
  The package iwd build for the architectures it is designed to work on.
  It currently builds and works for architetcures: amd64 arm64 armhf ppc64el 
riscv64 s390x 
  Link to package https://launchpad.net/ubuntu/+source/iwd

  [Rationale]
  - The package iwd is required in Ubuntu main to replace wpa as our default 
wireless service

  - The package iwd is required in Ubuntu main no later than aug 25 due
  to feature freeze

  [Security]
  - Had 5 security issues in the past
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-40861
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-40860
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-17497
 - https://ubuntu.com/security/CVE-2020-8689
 - https://ubuntu.com/security/CVE-2020-17497

  - no `suid` or `sgid` binaries
  - no executables in `/sbin` and `/usr/sbin`
  - Package does install a service as /lib/systemd/system/iwd.service
Which has the following security features: PrivateTmp=true, 
NoNewPrivileges=true, DevicePolicy=closed, ProtectSystem=strict, 
ProtectHome=yes, ProtectControlGroups=yes, ProtectKernelModules=yes, 
  - Packages does not open privileged ports (ports < 1024)
  - Packages does not contain extensions to security-sensitive software

  [Quality assurance - function/usage]
  - The package works well right after install

  [Quality assurance - maintenance]
  - The package is maintained well in Debian/Ubuntu and has a few bugs reported 
but nothing critical
- Ubuntu https://bugs.launchpad.net/ubuntu/+source/iwd/+bug
- Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=iwd
  - The package does not deal with exotic hardware we cannot support

  [Quality assurance - testing]
  - The package runs a test suite on build time, if it fails
it makes the build fail, link to build log 
https://launchpadlibrarian.net/599165412/buildlog_ubuntu-kinetic-amd64.iwd_1.27-1_BUILDING.txt.gz

  - The package runs an autopkgtest, and is currently passing on
amd64 arm64 armhf s390x ppc64el, 
https://autopkgtest.ubuntu.com/packages/i/iwd
  - The package does have not failing autopkgtests right now

  [Quality assurance - packaging]
  - debian/watch is present and works

  - The package has no important lintian warnings

  iwd-1.27# lintian --pedantic
  W: iwd source: mismatched-override 
missing-license-paragraph-in-dep5-copyright gpl-2\+ *
  W: iwd source: mismatched-override 
missing-license-paragraph-in-dep5-copyright gpl-3\+ *
  W: iwd source: mismatched-override 
missing-license-paragraph-in-dep5-copyright lgpl-2\.1\+ *
  W: iwd source: mismatched-override ... use --no-tag-display-limit to see all 
(or pipe to a file/program)
  W: iwd source: missing-license-paragraph-in-dep5-copyright debian/copyright 
gpl-2+ (line 57)
  W: iwd source: missing-license-paragraph-in-dep5-copyright debian/copyright 
gpl-3+ (line 153)
  W: iwd source: missing-license-paragraph-in-dep5-copyright debian/copyright 
lgpl-2.1+ (line 33)
  W: iwd source: missing-license-text-in-dep5-copyright debian/copyright GPL-2+ 
(line 236)
  W: iwd source: missing-license-text-in-dep5-copyright debian/copyright GPL-3+ 
(line 239)
  W: iwd source: missing-license-text-in-dep5-copyright debian/copyright 
LGPL-2.1+ (line 262)
  W: iwd source: orig-tarball-missing-upstream-signature iwd_1.27.orig.tar.xz
  W: iwd source: superfluous-file-pattern debian/copyright */Makefile.in 
(Files, line 59)
  W: iwd source: superfluous-file-pattern debian/copyright */configure (Files, 
line 35)
  W: iwd source: superfluous-file-pattern debian/copyright */ylwrap (Files, 
line 65)
  P: iwd source: very-long-line-length-in-source-file build-aux/libtool.m4 line 
6627 is 738 characters long (>512)
  P: iwd source: very-long-line-length-in-source-file configure line 10178 is 
704 characters long (>512)

  - Lintian overrides are not present

  - This package does not rely on obsolete or about to be demoted packages.
  - This package has no python2 or GTK2 dependencies

  - The package will be installed by default, but does not ask debconf
  questions

  - Packaging and build is easy,
  https://salsa.debian.org/debian/iwd/-/blob/debian/latest/debian/rules

  [UI standards]
  - Application is not end-user facing (does not need translation)

  [Dependencies]
  - There are further dependencies that are not yet in main, MIR for them
is at https://bugs.launchpad.net/ubuntu/+source/ell/+bug/1971738

  [Standards compliance]
  - This package correctly follows FHS and Debian Policy

  [Maintenance/Owner]
  - desktop-packages is

[Desktop-packages] [Bug 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

Ok, I know what happened in this specific case (just tested in a Kubuntu
20.04 VM that I upgraded to 22.04): during the upgrade, the firefox deb
package was uninstalled, resulting in the firefox.desktop file being
removed from the system.

I'm attaching /var/log/dist-upgrade/main.log.

** Attachment added: "main.log"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+attachment/5617056/+files/main.log

** No longer affects: snapd

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

Title:
  Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  1) lsb_release -rd

  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04
  (Kubuntu Jammy live session in QEMU VM)

  2) apt-cache policy ubuntu-release-upgrader-core
  ubuntu-release-upgrader-core:
    Installed: 1:22.04.6

  3) expected

  (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.)

  * Firefox icon on panel to be intact.
  * Clicked icon launches browser.
  * Icon tooltip/mouse hover to describe application.

  4) happened instead

  * Icon is missing/replaced with a generic icon
  * Icon click produces error notification "Plasma Workspace - 
preferred://browser"
  * Icon tooltip/mouse hover appears, though is blank.

  Additional info:
  * firefox is still installed, works as expected.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-07 (2 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Package: ubuntu-release-upgrader (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+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 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

Relevant excerpts from the above:

2022-09-19 12:16:55,064 DEBUG install of snap firefox succeeded
2022-09-19 12:17:00,921 DEBUG forced_obsoletes: ['firefox', 'ivman', 
'gtk-qt-engine']
2022-09-19 12:17:01,116 DEBUG remove_candidates: '{'ca-certificates-java', …, 
'firefox', …, 'default-jre-headless'}'
2022-09-19 12:18:33,328 DEBUG The following packages are marked for removal: 
ca-certificates-java … firefox-locale-en firefox-locale-fr … firefox …

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

Title:
  Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  1) lsb_release -rd

  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04
  (Kubuntu Jammy live session in QEMU VM)

  2) apt-cache policy ubuntu-release-upgrader-core
  ubuntu-release-upgrader-core:
    Installed: 1:22.04.6

  3) expected

  (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.)

  * Firefox icon on panel to be intact.
  * Clicked icon launches browser.
  * Icon tooltip/mouse hover to describe application.

  4) happened instead

  * Icon is missing/replaced with a generic icon
  * Icon click produces error notification "Plasma Workspace - 
preferred://browser"
  * Icon tooltip/mouse hover appears, though is blank.

  Additional info:
  * firefox is still installed, works as expected.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-07 (2 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Package: ubuntu-release-upgrader (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+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 1784774] Re: snapd is not autofs aware and fails with nfs home dir

2022-09-19 Thread Alberto Mardegan

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

I'm closing this bug and setting it as a duplicate of
https://bugs.launchpad.net/snapd/+bug/1917348

There are several issues related to NFS and remote filsystems in
general, and we will be tackling them one at a time.

** This bug has been marked a duplicate of bug 1917348
   NFS access not permitted for snap's on LDAP autofs system

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

Title:
  snapd is not autofs aware and fails with nfs home dir

Status in snapd:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  This is similar to bugs 1662552 and 1782873. In 1782873, jdstrand
  asked me to open a new bug for this specific issue.

  In 1662552, snapd fails for nfs mounted home directories as network
  permissions are not enabled. A work around was implemented that works
  if the mount is done via a /home mount at boot. However this does not
  work if people mount home directories via autofs. This is probably the
  fundamental problem for 1782873 although there may be other issues.

  [ Why use autofs? If some but not all of users want to use nfs homes.
  In particular, I have a local user on all my accounts that does not
  require the nfs server to be up or the kerberos server to be up, or
  kerberos working on the client machines, etc. It is very useful when
  something goes wrong. It means I mount /home/user rather than /home
  (for several users). ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1784774/+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 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

'firefox' being in the forced_obsoletes list is of course suspicious. I
think this is caused by https://git.launchpad.net/ubuntu/+source/ubuntu-
release-
upgrader/tree/DistUpgrade/DistUpgradeQuirks.py?h=ubuntu/jammy#n694 (last
line of the _replaceDebsAndSnaps() function).

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

Title:
  Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  1) lsb_release -rd

  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04
  (Kubuntu Jammy live session in QEMU VM)

  2) apt-cache policy ubuntu-release-upgrader-core
  ubuntu-release-upgrader-core:
    Installed: 1:22.04.6

  3) expected

  (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.)

  * Firefox icon on panel to be intact.
  * Clicked icon launches browser.
  * Icon tooltip/mouse hover to describe application.

  4) happened instead

  * Icon is missing/replaced with a generic icon
  * Icon click produces error notification "Plasma Workspace - 
preferred://browser"
  * Icon tooltip/mouse hover appears, though is blank.

  Additional info:
  * firefox is still installed, works as expected.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-07 (2 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Package: ubuntu-release-upgrader (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+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 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled

2022-09-19 Thread wastrel

I finally upgraded to 22.04 and the workaround in my previous message is
now also no longer working for me, though it had been in 21.04. Had to
remove the YubiKey to log in.

My new workaround is to add an option to the gdm-smartcard alternatives
configuration that's just password, no smartcard.

I added the final 2 lines in the file here:

$ cat /var/lib/dpkg/alternatives/gdm-smartcard
manual
/etc/pam.d/gdm-smartcard

/etc/pam.d/gdm-smartcard-pkcs11-exclusive
30
/etc/pam.d/gdm-smartcard-sssd-exclusive
50
/etc/pam.d/gdm-smartcard-sssd-or-password
40
/etc/pam.d/gdm-password
60

$

Now I choose that option using the same command as my previous
workaround:

$ sudo update-alternatives --config gdm-smartcard
There are 4 choices for the alternative gdm-smartcard (providing 
/etc/pam.d/gdm-smartcard).

  SelectionPath   Priority   Status

  0/etc/pam.d/gdm-password 60auto mode
  1/etc/pam.d/gdm-smartcard-pkcs11-exclusive   30manual mode
  2/etc/pam.d/gdm-smartcard-sssd-exclusive 50manual mode
  3/etc/pam.d/gdm-smartcard-sssd-or-password   40manual mode
* 4/etc/pam.d/gdm-password 60manual mode

Press  to keep the current choice[*], or type selection number: 4
$ 


This is slightly more dangerous than the previous workaround as you may mess up 
your gdm login completely if you edit the file incorrectly but removing the 
YubiKey should default you back to just password so you'll be able to fix it.

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

Title:
  Gdm3 with smartcard asks for login/smartcard pin even if there is no
  smartcard authentication enabled

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  I use my Ubuntu PC with Yubikey almost always plugged in. It provides
  several security token interfaces, such as U2F, GPG smartcard,
  proprieritary Yubico interfaces (of which I mostly use TOTP codes),
  and also PIV smartcard. However, I haven't configured a PIV smartcard
  on it.

  Whenever I login into the system having Yubikey plugged in, I'm prompted for 
login name, and then for PIN for some smartcard while also being asked to plug 
in one. This is very misleading on several layers:
  1. I have the device providing smartcard plugged id,
  2. But it's not the smartcard GDM would think it is as it's not configured 
properly,
  3. There are no local smartcard-authenticating users right now in the system,
  3. There are no remote authentication systems configured on the system (so no 
ActiveDirectory-smartcard logins or such).

  If I unplug the token UX goes back on old good track.

  Given the circumstances above, I'd consider that GDM (and, on my bet,
  any PAM configuration it uses) shouldn't offer to login using
  smartcard if there is no way to actually do so. I feel something is
  off here, so I'm reporting a bug. It could be an upstream problem
  though; it also could be an upstream SSSD problem, or all combined.

  I believe there is a more clear user experience:
  1. GDM should display users that can login into the system, as it always does 
(if configured). It may also provide entering other login name (also if 
configured). This is GDM usually does without smartcards altogether.
  2. When user is chosen (from the list or manually typed in), check can this 
user even authenticate with smartcards (i.e. if any of available smartcards is 
actually recognised for this user). If so, then ask for PIN. Else, don't show 
anything about smartcards at all (this includes when SSSD is not configured for 
any AD or related and this user has no local smartcard configuration). This can 
switch there & back based on device events.
  I've seen other OS doing this.

  Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock
  screen, so I guess it doesn't support it at all or correctly finds out
  it can't be used. Even more, I couldn't find a way to actually add my
  smartcard as a local login method.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gdm3 3.38.2.1-2ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 20 14:02:02 2021
  InstallationDate: Installed on 2017-03-05 (1567 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  Upgrade

[Desktop-packages] [Bug 1897562] Re: gedit snap fails to save or open files in miscellaneous directories including dot-folders, ~/bin, and system folders.

2022-09-19 Thread Paddy Landau

** Description changed:

  The snap version of gedit prevents viewing and editing files outside a
  strictly limited set of folders. For example, it cannot change files in
  standard folders ~/bin, ~/.local, ~/.config, ~/.ssh, or standard files
  such as ~/.bashrc or ~/.profile. Even "sudo -H gedit /etc/fstab" doesn't
  work. Using sudoedit doesn't work, as access to /var/tmp is rejected.
  
- EDIT: ~/bin is now available to gedit.
+ EDIT: ~/bin is now available to gedit. EDIT: Nope, not any more.
  
  As there is a bug in the non-snap versions [1], the snap version is
  important, but sadly it is unusable for a certain number of cases.
  
  I understand that the only solution is to make gedit available in
  classic confinement.
  
  Please would you do this.
  
  Thank you
  
  [1] https://gitlab.gnome.org/GNOME/gedit/-/issues/361

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

Title:
  gedit snap fails to save or open files in miscellaneous directories
  including dot-folders, ~/bin, and system folders.

Status in gedit package in Ubuntu:
  Triaged

Bug description:
  The snap version of gedit prevents viewing and editing files outside a
  strictly limited set of folders. For example, it cannot change files
  in standard folders ~/bin, ~/.local, ~/.config, ~/.ssh, or standard
  files such as ~/.bashrc or ~/.profile. Even "sudo -H gedit /etc/fstab"
  doesn't work. Using sudoedit doesn't work, as access to /var/tmp is
  rejected.

  EDIT: ~/bin is now available to gedit. EDIT: Nope, not any more.

  As there is a bug in the non-snap versions [1], the snap version is
  important, but sadly it is unusable for a certain number of cases.

  I understand that the only solution is to make gedit available in
  classic confinement.

  Please would you do this.

  Thank you

  [1] https://gitlab.gnome.org/GNOME/gedit/-/issues/361

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1897562/+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 1989714] Re: FFE: Switch dependencies from webkitgtk 4.0 to 4.1

2022-09-19 Thread Łukasz Zemczak

Seeing that we're basically nearing Beta Freeze slowly, I'm not that
fond of starting a transition this late. The list of packages is not
terribklyhuge, but substantial nevertheless. Since we won't be able to
drop 4.0 with this change, what merit does it give us that would warrant
doing it so late in the cycle? What was the reason why it wasn't done
earlier? How bad would it be if we'd postpone it till 23.04?

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

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

Title:
  FFE: Switch dependencies from webkitgtk 4.0 to 4.1

Status in webkit2gtk package in Ubuntu:
  Incomplete

Bug description:
  Impact
  --
  The webkit2gtk source package provides 3 different API builds:
  - 4.0 for GTK3 using libsoup2
  - 4.1 for GTK3 using libsoup3 (otherwise same as 4.0)
  - 5.0 for GTK4 using libsoup3

  I am requesting a Feature Freeze Exception to be able to switch
  dependencies from 4.0 to 4.1 for Ubuntu 22.10

  The Desktop Team has an outstanding todo item to stop using libsoup2 in main. 
We got more than halfway done for Ubuntu 22.10 but still won't finish for 
22.10, even with this Feature Freeze Exception but it gets us closer.
  
https://people.canonical.com/~ubuntu-archive/transitions/html/libsoup3-main.html

  It's bad for security updates that we need to do so many builds as
  part of the webkit2gtk source package. We still won't be able to drop
  the 4.0 build for 22.10 but this gets us closer for 23.04.

  Affected Packages
  -
  
https://people.canonical.com/~ubuntu-archive/transitions/html/webkit2gtk-4.0.html

  Example
  ---
  https://salsa.debian.org/gnome-team/gnome-feeds/-/commit/32183b4
  https://salsa.debian.org/gnome-team/gnome-feeds/-/commit/fc58345

  Many packages will also need their
  meson.build/configure.ac/CMakeLists.txt patches to look for 4.1
  instead of 4.0

  Future Goals
  
  Stop building the webkitgtk 4.0 API for Ubuntu 23.04
  Stop using libsoup2 in main for Ubuntu 23.04
  Stop building libsoup2 for Ubuntu 23.10

  Debian will begin freezing in early January and will be frozen for
  several months while they prepare for the Debian 12 release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1989714/+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 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

** Also affects: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided
   Status: 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/1964036

Title:
  Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd

  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04
  (Kubuntu Jammy live session in QEMU VM)

  2) apt-cache policy ubuntu-release-upgrader-core
  ubuntu-release-upgrader-core:
    Installed: 1:22.04.6

  3) expected

  (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.)

  * Firefox icon on panel to be intact.
  * Clicked icon launches browser.
  * Icon tooltip/mouse hover to describe application.

  4) happened instead

  * Icon is missing/replaced with a generic icon
  * Icon click produces error notification "Plasma Workspace - 
preferred://browser"
  * Icon tooltip/mouse hover appears, though is blank.

  Additional info:
  * firefox is still installed, works as expected.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-07 (2 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Package: ubuntu-release-upgrader (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+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 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

I just tested a focal->jammy upgrade in a regular Ubuntu VM, and this
resulted in the same problem: the firefox deb being removed, seemingly
because the snap was installed.

As a result, the firefox favourite icon disappeared entirely from the
gnome shell dock. This is definitely unwanted behaviour.

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

Title:
  Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd

  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04
  (Kubuntu Jammy live session in QEMU VM)

  2) apt-cache policy ubuntu-release-upgrader-core
  ubuntu-release-upgrader-core:
    Installed: 1:22.04.6

  3) expected

  (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.)

  * Firefox icon on panel to be intact.
  * Clicked icon launches browser.
  * Icon tooltip/mouse hover to describe application.

  4) happened instead

  * Icon is missing/replaced with a generic icon
  * Icon click produces error notification "Plasma Workspace - 
preferred://browser"
  * Icon tooltip/mouse hover appears, though is blank.

  Additional info:
  * firefox is still installed, works as expected.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-07 (2 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Package: ubuntu-release-upgrader (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+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 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/

2022-09-19 Thread Raphael Kubo da Costa

For the record, I've landed some updates to 
:
* Use a policy that is easier to verify in the example 
(https://chromium-review.googlesource.com/c/website/+/3899081)
* Mention Ubuntu's custom policy path 
(https://chromium-review.googlesource.com/c/website/+/3899088)

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

Title:
  [snap] apparmor denials on /etc/chromium-browser/policies/

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  [1565519.440403] audit: type=1400 audit(1504185084.568:68574811):
  apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
  name="/etc/chromium-browser/policies/managed/" pid=19433
  comm="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  [1565519.440527] audit: type=1400 audit(1504185084.568:68574812):
  apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
  name="/etc/chromium-browser/policies/recommended/" pid=19433
  comm="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  Those denials don't appear to prevent the app from running. Still,
  they should be investigated and fixed if possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+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 1941891] Re: Constant and frequent SSL handshake errors in logs

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

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

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

Title:
  Constant and frequent SSL handshake errors in logs

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I am seeing constant and frequest SSL errors in the logs from gnome-
  shell:

  cloudbox gnome-shell[13711]:
  [13757:13763:0827/085507.253897:ERROR:ssl_client_socket_impl.cc(981)]
  handshake failed; returned -1, SSL error code 1, net_error -202

  mike@cloudbox:/opt/qbittorrentvpn/qBittorrent/config$ sudo lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  mike@cloudbox:/opt/qbittorrentvpn/qBittorrent/config$ sudo apt-cache policy 
gnome-shell
  gnome-shell:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 3.36.9-0ubuntu0.20.04.2
Version table:
   *** 3.36.9-0ubuntu0.20.04.2 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Aug 27 08:52:33 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2021-08-06 (20 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1941891/+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 1990170] [NEW] refresh rate at 4k 144hz cant be set

2022-09-19 Thread qihouji

Public bug reported:

in the setting,when i set a refresh rate>60Hz, there will be a black
screen for about half a minute and the refresh rate is automatically
reset to 60Hz.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..0d.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 14:00:58 
UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: fail
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 19 23:41:05 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GA102 [GeForce RTX 3080 Ti] [10de:2208] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GA102 [GeForce RTX 3080 Ti] 
[1458:4081]
InstallationDate: Installed on 2022-08-22 (27 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=UUID=00c387f2-1035-4d26-a66d-d9bcc66f1b7b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/12/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F36e
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS MASTER
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36e:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: X570 MB
dmi.product.name: X570 AORUS MASTER
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy resolution ubuntu

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

Title:
  refresh rate at 4k 144hz cant be set

Status in xorg package in Ubuntu:
  New

Bug description:
  in the setting,when i set a refresh rate>60Hz, there will be a black
  screen for about half a minute and the refresh rate is automatically
  reset to 60Hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0d.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckMismatches: ./casper/filesystem.squashfs
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 19 23:41:05 2022

[Desktop-packages] [Bug 1990173] [NEW] [kinetic] gnome-initial-setup shows minimize button

2022-09-19 Thread Jeremy Bicha

Public bug reported:

In Ubuntu 22.10, gnome-initial-setup shows a minimize window button. It
didn't show this button in Ubuntu 22.04 LTS.

gnome-initial-setup was ported to GTK4 this cycle so this may be a
regression.

Test Case
-
Run

/usr/libexec/gnome-initial-setup --existing-user

** Affects: gnome-initial-setup (Ubuntu)
 Importance: Low
 Status: Confirmed


** Tags: kinetic rls-kk-incoming

** Tags added: kinetic

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

Title:
  [kinetic] gnome-initial-setup shows minimize button

Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 22.10, gnome-initial-setup shows a minimize window button.
  It didn't show this button in Ubuntu 22.04 LTS.

  gnome-initial-setup was ported to GTK4 this cycle so this may be a
  regression.

  Test Case
  -
  Run

  /usr/libexec/gnome-initial-setup --existing-user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1990173/+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 1988744] Update Released

2022-09-19 Thread Łukasz Zemczak

The verification of the Stable Release Update for libreoffice has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
   [SRU] libreoffice 7.3.6 for jammy

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

Bug description:
  [Impact]

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

   * Version 7.3.5 is currently released in jammy. For a list of fixed bugs 
compared to 7.3.5 see the list of bugs fixed in the release candidates of 7.3.6 
(that's a total of 50 bugs):
   https://wiki.documentfoundation.org/Releases/7.3.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.3.6/RC2#List_of_fixed_bugs

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

  [Testing]

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

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

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

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220903_204748_cb772@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20220903_234903_5c5f9@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220903_221954_4437b@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220903_203030_f897a@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220903_202914_32e82@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

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

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

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

This bug was fixed in the package libreoffice - 1:7.3.6-0ubuntu0.22.04.1

---
libreoffice (1:7.3.6-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #1988744)

  [ Rico Tzschichholz ]
  * Bump yaru source to "2022-08-15"
  * debian/patches/tdf-108560-horribly-slow-to-paste-many-lines-into-ed.patch:
- Calc very slow to open/save documents with large cell contents

  [ Rene Engelhard ]
  * debian/libreoffice-common.preinst.in,debian/rules,
debian/shell-lib-extensions.sh:
- Broken libreoffice trigger and /usr/lib/libreoffice/share/extensions
  missing; libreoffice fails to start when last extension is removed
  (/usr/lib/libreoffice/share/extensions being a 0-byte file)

 -- Rico Tzschichholz   Mon, 05 Sep 2022 16:18:50
+0200

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

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

Title:
   [SRU] libreoffice 7.3.6 for jammy

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

Bug description:
  [Impact]

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

   * Version 7.3.5 is currently released in jammy. For a list of fixed bugs 
compared to 7.3.5 see the list of bugs fixed in the release candidates of 7.3.6 
(that's a total of 50 bugs):
   https://wiki.documentfoundation.org/Releases/7.3.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.3.6/RC2#List_of_fixed_bugs

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

  [Testing]

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

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

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

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220903_204748_cb772@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20220903_234903_5c5f9@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220903_221954_4437b@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220903_203030_f897a@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220903_202914_32e82@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744/+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 1987038] Re: Fix slow refresh rate when AMD GPU screen in reverse prime mode

This bug was fixed in the package xserver-xorg-video-amdgpu -
19.1.0-1ubuntu0.1

---
xserver-xorg-video-amdgpu (19.1.0-1ubuntu0.1) focal; urgency=medium

  * Added patch from git to fix slow refresh rate with AMD GPU Screen
output in reverse prime mode. (LP: #1987038)

 -- Kai-Heng Feng   Wed, 24 Aug 2022
15:42:19 +0800

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Fix slow refresh rate when AMD GPU screen in reverse prime mode

Status in HWE Next:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Focal:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Jammy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  When AMD GPU is a GPU screen using reverse prime and its the only display, 
the fresh rate is very slow.

  [Fix]
  Enable present extension for GPU screen so it can be a viable CRTC to be 
selected.

  [Test]
  On a I+A laptop and external displays are routed to AMDGPU, disable internal 
display like closing lid can observe the issue.

  With the fix applied, the external display becomes very smooth.

  [Where problems could occur]
  I personally don't see why GPU screen can't use present extension, but this 
is Xorg so there might be some arcane reasons I didn't think of.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1987038/+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 1311795] Re: Chromium aura doesn't honor the --class parameter anymore

This was fixed in the meantime.

  $ chromium --class=o
  $ wmctrl -lx
  0x0322  0 chromium.ocanonical New Tab - Chromium

If you can still reproduce the bug, please bump this report.

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

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

Title:
  Chromium aura doesn't honor the --class parameter anymore

Status in BAMF:
  Won't Fix
Status in Chromium Browser:
  Unknown
Status in Unity:
  Won't Fix
Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  At Ubuntu 13.10, I could have different instances of chromium (with
  different profiles) have separate icons in unity. All I had to do was
  change the StartupWMClass=  and the --class= in the exec= line in the
  desktop launcher. Starting with 14.04, Unity ignores these values and
  groups the chromium windows together. Similarly, webapp instances
  (created using file-> create application shortcuts) are also grouped
  under the one chromium icon. This beats the purpose of webapps, as it
  makes it much more difficult to regard a webpage as an application.

  To replicate: 
  1. copy the chromium-browser.desktop to two different locations: 1.desktop 
and 2.desktop. 
  2. Edit 1.desktop to the following values: 
  Exec=chromium-browser --temp-profile --class=Other %U
  StartupWMClass=Other
  3. Edit 2.desktop to the following values:
  Exec=chromium-browser --temp-profile --class=Other2 %U
  StartupWMClass=Other2
  4. Start both from nautilus or from the desktop. 

  In 13.10, this results in separate icons on the launcher, in 14.04,
  only one.

  It seems that I'm not the only one to encounter this problem:
  http://askubuntu.com/questions/450113/multiple-chromium-icons-in-
  launcher-of-14-04-lts

  And this is further evidence that the icons were separable in previous
  versions: http://ricardofeliciano.me/how-to-create-a-unity-launcher-
  icon-for-each-chromechromium-profile-in-ubuntu/

  Thanks,
  UCP

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1311795/+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 1321602] Re: chromium browser chews 100% CPU in epoll_wait()

Please bump if still reproducible.

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

Title:
  chromium browser chews 100% CPU in epoll_wait()

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  This happens frequently (I have a script that monitors CPU usage).

  $ top -b -n1 | head
  top - 07:44:06 up 30 min,  3 users,  load average: 1.35, 1.08, 0.82
  Tasks: 329 total,   2 running, 327 sleeping,   0 stopped,   0 zombie
  %Cpu(s): 17.4 us,  1.6 sy,  0.4 ni, 80.1 id,  0.5 wa,  0.1 hi,  0.0 si,  0.0 
st
  KiB Mem:  12182444 total,  5215508 used,  6966936 free,   338356 buffers
  KiB Swap: 12455932 total,0 used, 12455932 free.  2614244 cached Mem

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  16165 james 20   0 1428628  72860  50624 R  95.5  0.6   3:11.69 
chromium-browse
   2908 james 20   0 1329964 485940  87724 S  12.7  4.0   2:17.25 firefox
  15993 james 20   0 3303180 257376 104592 S   6.4  2.1   0:18.28 
chromium-browse
  $ sudo cat /proc/16165/stack
  [] 0x
  $ sudo strace -fFv -s 1024 -p 16165
  Process 16165 attached with 9 threads
  [pid 16241] futex(0x7fe0ff7fdac4, FUTEX_WAIT_PRIVATE, 1, NULL 
  [pid 16182] futex(0x7fe0eac4, FUTEX_WAIT_PRIVATE, 1, NULL 
  [pid 16181] futex(0x7fe1279b7f88, FUTEX_WAIT_PRIVATE, 0, NULL 
  [pid 16179] futex(0x7fe1279e7e68, FUTEX_WAIT_PRIVATE, 0, NULL 
  [pid 16178] futex(0x7fe1279d00f8, FUTEX_WAIT_PRIVATE, 0, NULL 
  [pid 16180] futex(0x7fe1279eeb88, FUTEX_WAIT_PRIVATE, 0, NULL 
  [pid 16177] futex(0x7fe1279fa918, FUTEX_WAIT_PRIVATE, 0, NULL 
  [pid 16176] epoll_wait(3, 
  ^C

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.15.0-1.5-generic 3.15.0-rc5
  Uname: Linux 3.15.0-1-generic x86_64
  ApportVersion: 2.14.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 21 07:42:35 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-11 (39 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (12 days ago)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-05-06T16:47:55.748923

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1321602/+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 1332226] Re: sensible-browser opens a new chromium even if one is already running

I cannot verify that.

  BROWSER=chromium sensible-browser a & 
  BROWSER=chromium sensible-browser b &

gives me two tabs in one Chromium window.

 Since the report is old, I'm marking it as invalid, but please bump it
if still reproducible for you.

** Also affects: sensible-utils (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: sensible-utils (Ubuntu)
   Status: New => Confirmed

** Changed in: sensible-utils (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  sensible-browser opens a new chromium even if one is already running

Status in chromium-browser package in Ubuntu:
  Invalid
Status in sensible-utils package in Ubuntu:
  Invalid

Bug description:
  This fails terribly because the new chromium cannot lock the profile
  and just generally doesn't work well. sensible-browser should be
  opening a new window in an existing instance of a browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: sensible-utils 0.0.9
  Uname: Linux 3.13.0-031300rc3-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 19 10:50:21 2014
  Dependencies:
   
  InstallationDate: Installed on 2013-01-14 (521 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64+mac 
(20121017.3)
  PackageArchitecture: all
  SourcePackage: sensible-utils
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1332226/+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 1990030] [NEW] Webpage in Firefox crashes computer

You have been subscribed to a public bug:

I could not reproduce this today, but the web page at
https://celebratingsweets.com/big-chewy-ginger-molasses-cookies/
crashed my computer.  This website has every advertisement, popup, and video 
known to man on it.

I had a monitor connected to my laptop by an HDMI cable, and I had the
Firefox browser (I have the latest version 104.0.2, 64-bit) open in the
laptop screen to this web page.

This was the only window I had open (the only other [user] program
running was wallch, which rotates the desktop background image), when
the screen went blank after a period of inactivity, and the screen
wouldn't redraw when I moved my finger on the laptop touchpad or pressed
the space bar to wake it up. It just stayed black, ctl-alt-del was not
recognized, nor were any keys, and the only thing I could figure out to
get it back was to press the power button until the computer shut off.
Then reboot.  This happened twice.  The touchpad was hot, like something
was overheating inside the laptop.  This laptop was built by System76
and is some sort of generic Lenovo under the hood.

No web site has ever crashed my computer before.  I have Ubuntu,
upgraded from version 20 to 22.04.1 LTS three weeks ago, and upgraded
from DSL to fiber Internet two weeks ago.  Maybe one of these is causing
the problem.  I'll try to also report it to the other components'
producers.

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


** Tags: bot-comment
-- 
Webpage in Firefox crashes computer
https://bugs.launchpad.net/bugs/1990030
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to firefox in Ubuntu.

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

[Desktop-packages] [Bug 1441963] Re: ubuntu touch source code build fail (repo_branch = 'phablet-trusty' dedault )

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

Title:
  ubuntu touch  source code build fail   (repo_branch = 'phablet-
  trusty'  dedault )

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  when i get ubuntu touch source default like : phablet-dev-bootstrap
  ./  (repo_branch = 'phablet-trusty'   )

  it download all source success,  [ part of android source  is android
  4.2.2 ?   ]

  when i build it ,meet error, it reports frameworks/native/    some
  head file can not find ,  and other error exit

   default  repo_branch  is right  (about aosp part ) ?  i compare which
  it nd head can find on android 4.4.2 ,

  does default   repo_branch have wrong branch with aosp 4.2.2  (right
  is 4.4.2 /)


  and@y460:~/phablet/ubuntuTouch$ make -j4
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1441963/+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 1333477] Re: Fatal debug logging causes unnecessary crashes

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

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

Title:
  Fatal debug logging causes unnecessary crashes

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  This is a simple one.  It relates to these upstream bug reports
  (dupes):

  https://code.google.com/p/chromium/issues/detail?id=357473
  https://code.google.com/p/chromium/issues/detail?id=371355

  Basically, the Chromium devs put a LOG(FATAL) in unofficial builds. So
  Chrome works fine, but not Chromium. The browser isn't actually
  crashing on its own, instead the LOG(FATAL) is killing the browser in
  order to get the attention of the user so they'll file a bug report.
  This sounds fine if it's a developer running the browser, but end
  users shouldn't have their browser crash because of an arbitrary FATAL
  log message.

  The Ubuntu package should remove the LOG(FATAL) entirely so that the
  Chromium builds will work like the Chrome builds do, and not crash.
  The exact file/line/code is mentioned in the second bug report above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1333477/+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 1990030] Re: Webpage in Firefox crashes computer

2022-09-19 Thread Brian Murray

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

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

Title:
  Webpage in Firefox crashes computer

Status in firefox package in Ubuntu:
  New

Bug description:
  I could not reproduce this today, but the web page at
  https://celebratingsweets.com/big-chewy-ginger-molasses-cookies/
  crashed my computer.  This website has every advertisement, popup, and video 
known to man on it.

  I had a monitor connected to my laptop by an HDMI cable, and I had the
  Firefox browser (I have the latest version 104.0.2, 64-bit) open in
  the laptop screen to this web page.

  This was the only window I had open (the only other [user] program
  running was wallch, which rotates the desktop background image), when
  the screen went blank after a period of inactivity, and the screen
  wouldn't redraw when I moved my finger on the laptop touchpad or
  pressed the space bar to wake it up. It just stayed black, ctl-alt-del
  was not recognized, nor were any keys, and the only thing I could
  figure out to get it back was to press the power button until the
  computer shut off.  Then reboot.  This happened twice.  The touchpad
  was hot, like something was overheating inside the laptop.  This
  laptop was built by System76 and is some sort of generic Lenovo under
  the hood.

  No web site has ever crashed my computer before.  I have Ubuntu,
  upgraded from version 20 to 22.04.1 LTS three weeks ago, and upgraded
  from DSL to fiber Internet two weeks ago.  Maybe one of these is
  causing the problem.  I'll try to also report it to the other
  components' producers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1990030/+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 1451099] Re: hardcoded bash dependency

I'm marking this as won't fix because it's low importance and that
dependency doesn't exist in the snap, only in the .deb, which is only
for Bionic, which will soon reach its end-of-life.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  hardcoded bash dependency

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  chromium has hardcoded dependency on bash (>= 4) which is very strange
  - I expect browser to work regardless of which shell is installed in
  my system. The dependency should be changed to dash and all the
  bashisms in source code (if any) should be eliminated to improve
  portability.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1451099/+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 1449607] Re: Random Chromium / Chrome slowdowns with hardware acceleration

Please bump if the bug is still verified.

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

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

Title:
  Random Chromium / Chrome slowdowns with hardware acceleration

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Since update from 14.04 --> 15.04, bot Chromium and Chrome randomly
  slow down to a complete halt after a while using them. There doesn't
  seem to be any pattern on when this starts happening. Sometimes when
  opening a new tab from a unity-webapp (eg Gmail) but not always.

  As well as either Chrome or Chromium, this also makes Unity itself
  unresponsive - eg I can't act on anything on the UI be it the dash or
  another app. I can log into a terminal outside X (eg CTRL+ALT+F1) and
  this is perfectly responsive even when the whole UI is locked up.
  There's barely any system load - often with several gigs of ram free
  and very low CPU load and no usage on the swap.

  After I manually kill the "--type=gpu-broker" associated with either
  chrome or chromium they both seem to recover, together with Unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: chromium-browser 41.0.2272.76-0ubuntu1.1134
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 28 15:41:18 2015
  InstallationDate: Installed on 2014-01-16 (467 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (5 days ago)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/opt/google/chrome/google-chrome\n'/desktop/gnome/url-handlers/https/command 
= b'/opt/google/chrome/google-chrome 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = 
b'/opt/google/chrome/google-chrome 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1449607/+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 1464958] Re: chromium-browser does not run in guest account

** No longer affects: google-chrome-beta (Ubuntu)

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

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

Title:
  chromium-browser does not run in guest account

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Description:

  In guest account, start chromium browser shows nothing.  Start with
  command line shows error:

  guest-1qFsXl@home:~$ chromium-browser http://www.google.com
  Check failed: NamespaceUtils::DenySetgroups()

  This used to work for months and found failed for few weeks.

  Version:

  Ubuntu 14.04 LTS
  chromium-browser43.0.2357.81-0ubuntu0.14.04.1.1
  linux-image-3.13.0-54-generic3.13.0-54.91
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Desktop-Session:
   'None'
   'None'
   'None'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  Load-Avg-1min: 0.28
  Load-Processes-Running-Percent:   0.2%
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: chromium-browser 43.0.2357.81-0ubuntu0.14.04.1.1089
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-54-generic 
root=UUID=85a7733c-fbc4-49bf-84ce-02be4c5ba907 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: H97M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd12/15/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2015-01-14T08:39:14.796369

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1464958/+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 1493187] Re: Typographical error in message of source language [webkit-strings]

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

Title:
  Typographical error in message of source language [webkit-strings]

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  There is a typographical error in the source language of the template
  webkit-strings, message 45:

  "number of seconds ofmovie remaining"

  Obviously a space is missing between "of" and "movie".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1493187/+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 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

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

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

Title:
  Chromium start-up script doesn't accept argument values with spaces in
  $CHROMIUM_FLAGS, cause is lack of quotes

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  You can't have arguments with spaces inside CHROMIUM_FLAGS, whatever
  comes after the first space is going to be interpreted as an URL by
  the actual chromium binary. Easy repro:

  1. Set user's CHROMIUM_FLAGS with an argument containing spaces, eg:
  $ echo 'CHROMIUM_FLAGS=--user-agent="A B C"' > .chromium-browser.init

  2. Run chromium:
  $ /usr/bin/chromium-browser

  3. See 2 extra open tabs, one trying to open URL 'B', the other 'C'.

  The cause for this funny behavior is the lack of quotes around
  $CHROMIUM_FLAGS in the script installed in /usr/bin/chromium-browser
  -- it calls $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@" by the end of the
  script. I've tried working around it but couldn't, no amount of
  escaping and extra quotes seems to help if it's called like that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1514484/+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 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

** Tags removed: patch

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

Title:
  Chromium start-up script doesn't accept argument values with spaces in
  $CHROMIUM_FLAGS, cause is lack of quotes

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  You can't have arguments with spaces inside CHROMIUM_FLAGS, whatever
  comes after the first space is going to be interpreted as an URL by
  the actual chromium binary. Easy repro:

  1. Set user's CHROMIUM_FLAGS with an argument containing spaces, eg:
  $ echo 'CHROMIUM_FLAGS=--user-agent="A B C"' > .chromium-browser.init

  2. Run chromium:
  $ /usr/bin/chromium-browser

  3. See 2 extra open tabs, one trying to open URL 'B', the other 'C'.

  The cause for this funny behavior is the lack of quotes around
  $CHROMIUM_FLAGS in the script installed in /usr/bin/chromium-browser
  -- it calls $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@" by the end of the
  script. I've tried working around it but couldn't, no amount of
  escaping and extra quotes seems to help if it's called like that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1514484/+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 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

2022-09-19 Thread Brian Murray

IIRC the dist upgrade quirk is designed to replace a deb with a snap and
so the deb then gets marked for removal. It sounds like this is the
incorrect behavior for the firefox deb.

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

Title:
  Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd

  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04
  (Kubuntu Jammy live session in QEMU VM)

  2) apt-cache policy ubuntu-release-upgrader-core
  ubuntu-release-upgrader-core:
    Installed: 1:22.04.6

  3) expected

  (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.)

  * Firefox icon on panel to be intact.
  * Clicked icon launches browser.
  * Icon tooltip/mouse hover to describe application.

  4) happened instead

  * Icon is missing/replaced with a generic icon
  * Icon click produces error notification "Plasma Workspace - 
preferred://browser"
  * Icon tooltip/mouse hover appears, though is blank.

  Additional info:
  * firefox is still installed, works as expected.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-07 (2 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Package: ubuntu-release-upgrader (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+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 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

When a string is put in a shell variable, white-space loses its
syntactical information.

Merely quoting $CHROMIUM_FLAGS in the launcher won't do, since we rely
on word splitting to split arguments, as noted in #3.

The launcher has a #!/bin/sh shebang, so it's meant as a POSIX compliant
shell script. As such, we don't have access to arrays, which are a Korn
shell extension, _except_ for the argument list, which can be used as
one.

So I see two reasonable options here, and both are backwards-compatible,
i.e., won't upset users who are fine with the current state of
CHROMIUM_FLAGS.

>> OPTION 1 (already works in the current state of things) <<

Leave the launcher alone and instead instruct the user to abandon
CHROMIUM_FLAGS and take advantage of the argument list by writing this
~/.chromium-browser.init:

  set -- --enable-logging=stderr --user-agent='A B C' "$@"

>> OPTION 2 <<

Make these changes in the launcher:

  #!/bin/sh -> #!/bin/bash
  CHROMIUM_FLAGS -> "${CHROMIUM_FLAGS[@]}"

Then ~/.chromium-browser.init would allow for arrays whose elements can
contain spaces:

  CHROMIUM_FLAGS=(--enable-logging=stderr --user-agent="A B C")

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

Title:
  Chromium start-up script doesn't accept argument values with spaces in
  $CHROMIUM_FLAGS, cause is lack of quotes

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  You can't have arguments with spaces inside CHROMIUM_FLAGS, whatever
  comes after the first space is going to be interpreted as an URL by
  the actual chromium binary. Easy repro:

  1. Set user's CHROMIUM_FLAGS with an argument containing spaces, eg:
  $ echo 'CHROMIUM_FLAGS=--user-agent="A B C"' > .chromium-browser.init

  2. Run chromium:
  $ /usr/bin/chromium-browser

  3. See 2 extra open tabs, one trying to open URL 'B', the other 'C'.

  The cause for this funny behavior is the lack of quotes around
  $CHROMIUM_FLAGS in the script installed in /usr/bin/chromium-browser
  -- it calls $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@" by the end of the
  script. I've tried working around it but couldn't, no amount of
  escaping and extra quotes seems to help if it's called like that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1514484/+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 1990189] [NEW] brlttty claiming CH341 usbtty device blocking access

2022-09-19 Thread beattie

Public bug reported:

While this problem seems to have been fixed for FTDI and CP210 based
devices CH340/CH341 based (and possibly other USB serial adapters) are
unusable except by brltty.

[139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using xhci_hcd
[139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, 
idProduct=7523, bcdDevice= 2.63
[139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0
[139099.370782] usb 1-2.1.2: Product: USB2.0-Serial
[139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected
[139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0
[139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input24
[139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 'brltty' 
sets config #1
[139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected from 
ttyUSB0
[139100.786136] ch341 1-2.1.2:1.0: device disconnected
[143917.740171] usb 1-2.1.2: USB disconnect, device number 17

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: brltty 6.4-4ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Mon Sep 19 12:01:21 2022
InstallationDate: Installed on 2022-08-23 (27 days ago)
InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: brltty
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  brlttty claiming CH341 usbtty device blocking access

Status in brltty package in Ubuntu:
  New

Bug description:
  While this problem seems to have been fixed for FTDI and CP210 based
  devices CH340/CH341 based (and possibly other USB serial adapters) are
  unusable except by brltty.

  [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using 
xhci_hcd
  [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, 
idProduct=7523, bcdDevice= 2.63
  [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0
  [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial
  [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected
  [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0
  [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input24
  [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 
'brltty' sets config #1
  [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected 
from ttyUSB0
  [139100.786136] ch341 1-2.1.2:1.0: device disconnected
  [143917.740171] usb 1-2.1.2: USB disconnect, device number 17

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: brltty 6.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon Sep 19 12:01:21 2022
  InstallationDate: Installed on 2022-08-23 (27 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: brltty
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+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 1487082] Re: Loading icon doesn't match (gtk) theme

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Loading icon doesn't match (gtk) theme

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  The loading spinner in the tabs no longer matches the theme as of the
  version 44 update. Attached is part of a screen shot that shows the
  spinner with the default blue theme, whereas the rest of the
  application uses my gtk theme. Before the last update, the spinner was
  a dark grey.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: chromium-browser 44.0.2403.89-0ubuntu0.15.04.1.1177
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: GNOME
  DRM.card0.DVI.D.1:
   edid-base64: 
AP///wAebdlWJZoAAAwVAQOANR546q7FoldKnCUSUFSna4CzAIGAgUBxTwEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4Sx5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgAL8=
   dpms: On
   modes: 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1280x960 1152x864 
1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0.HDMI.A.1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.VGA.1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card1.DIN.1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  Date: Thu Aug 20 08:47:19 2015
  Desktop-Session:
   'gnome'
   '/etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg'
   '/usr/share/gnome:/usr/local/share/:/usr/share/'
  DetectedPlugins:
   
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-08-21 (364 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  Load-Avg-1min: 2.72
  Load-Processes-Running-Percent:   0.8%
  MachineType: MSI MS-7721
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed 
root=UUID=9b43238c-d6b1-4285-ac61-d8fe87d66d35 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to vivid on 2015-04-07 (134 days ago)
  dmi.bios.date: 03/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.3:bd03/14/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1487082/+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 1487082] Re: Loading icon doesn't match (gtk) theme

I can't verify this.

  GTK_THEME=Yaru chromium
  GTK_THEME=Adwaita chromium

give me different loading icon colors, which indicates it is respecting
the theme.

** Changed in: chromium-browser (Ubuntu)
   Status: Won't Fix => 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/1487082

Title:
  Loading icon doesn't match (gtk) theme

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  The loading spinner in the tabs no longer matches the theme as of the
  version 44 update. Attached is part of a screen shot that shows the
  spinner with the default blue theme, whereas the rest of the
  application uses my gtk theme. Before the last update, the spinner was
  a dark grey.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: chromium-browser 44.0.2403.89-0ubuntu0.15.04.1.1177
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: GNOME
  DRM.card0.DVI.D.1:
   edid-base64: 
AP///wAebdlWJZoAAAwVAQOANR546q7FoldKnCUSUFSna4CzAIGAgUBxTwEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4Sx5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgAL8=
   dpms: On
   modes: 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1280x960 1152x864 
1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0.HDMI.A.1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.VGA.1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card1.DIN.1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  Date: Thu Aug 20 08:47:19 2015
  Desktop-Session:
   'gnome'
   '/etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg'
   '/usr/share/gnome:/usr/local/share/:/usr/share/'
  DetectedPlugins:
   
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-08-21 (364 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  Load-Avg-1min: 2.72
  Load-Processes-Running-Percent:   0.8%
  MachineType: MSI MS-7721
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed 
root=UUID=9b43238c-d6b1-4285-ac61-d8fe87d66d35 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to vivid on 2015-04-07 (134 days ago)
  dmi.bios.date: 03/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.3:bd03/14/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1487082/+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 1990189] [NEW] brlttty claiming CH341 usbtty device blocking access

2022-09-19 Thread Samuel thibault

Hello,

beattie, le lun. 19 sept. 2022 19:07:54 -, a ecrit:
> [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, 
> idProduct=7523, bcdDevice= 2.63

Could you run

lsusb -v

so we get more information on how the generic bridge announces itself?

Samuel

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

Title:
  brlttty claiming CH341 usbtty device blocking access

Status in brltty package in Ubuntu:
  New

Bug description:
  While this problem seems to have been fixed for FTDI and CP210 based
  devices CH340/CH341 based (and possibly other USB serial adapters) are
  unusable except by brltty.

  [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using 
xhci_hcd
  [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, 
idProduct=7523, bcdDevice= 2.63
  [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0
  [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial
  [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected
  [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0
  [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input24
  [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 
'brltty' sets config #1
  [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected 
from ttyUSB0
  [139100.786136] ch341 1-2.1.2:1.0: device disconnected
  [143917.740171] usb 1-2.1.2: USB disconnect, device number 17

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: brltty 6.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon Sep 19 12:01:21 2022
  InstallationDate: Installed on 2022-08-23 (27 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: brltty
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+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 1990189] Re: brlttty claiming CH341 usbtty device blocking access

2022-09-19 Thread beattie

** Attachment added: "output of lsusb"
   
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+attachment/5617194/+files/lsusb

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

Title:
  brlttty claiming CH341 usbtty device blocking access

Status in brltty package in Ubuntu:
  New

Bug description:
  While this problem seems to have been fixed for FTDI and CP210 based
  devices CH340/CH341 based (and possibly other USB serial adapters) are
  unusable except by brltty.

  [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using 
xhci_hcd
  [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, 
idProduct=7523, bcdDevice= 2.63
  [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0
  [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial
  [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected
  [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0
  [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input24
  [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 
'brltty' sets config #1
  [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected 
from ttyUSB0
  [139100.786136] ch341 1-2.1.2:1.0: device disconnected
  [143917.740171] usb 1-2.1.2: USB disconnect, device number 17

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: brltty 6.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon Sep 19 12:01:21 2022
  InstallationDate: Installed on 2022-08-23 (27 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: brltty
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+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 1930887] Re: [snap] Thunderbird 78.11 does not play new email sound

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

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

Title:
  [snap] Thunderbird 78.11 does not play new email sound

Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  (Was the same before v. 78.11.)

  TB does not play a sound when a new mail incomes, even if the correct option 
is selected.
  Changing from default to custom sound does not change the issue.

  New emails notifications do work as intended, except sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1930887/+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 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

Yes, indeed. How can we address this?

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

Title:
  Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04

Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd

  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04
  (Kubuntu Jammy live session in QEMU VM)

  2) apt-cache policy ubuntu-release-upgrader-core
  ubuntu-release-upgrader-core:
    Installed: 1:22.04.6

  3) expected

  (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.)

  * Firefox icon on panel to be intact.
  * Clicked icon launches browser.
  * Icon tooltip/mouse hover to describe application.

  4) happened instead

  * Icon is missing/replaced with a generic icon
  * Icon click produces error notification "Plasma Workspace - 
preferred://browser"
  * Icon tooltip/mouse hover appears, though is blank.

  Additional info:
  * firefox is still installed, works as expected.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-07 (2 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Package: ubuntu-release-upgrader (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+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 1990030] Re: Webpage in Firefox crashes computer

This is not necessarily a crash caused by firefox, it could be any
component really.

Can you check in /var/crash whether there are .crash files with a
timestamp that corresponds to when the problem happened?

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

Title:
  Webpage in Firefox crashes computer

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  I could not reproduce this today, but the web page at
  https://celebratingsweets.com/big-chewy-ginger-molasses-cookies/
  crashed my computer.  This website has every advertisement, popup, and video 
known to man on it.

  I had a monitor connected to my laptop by an HDMI cable, and I had the
  Firefox browser (I have the latest version 104.0.2, 64-bit) open in
  the laptop screen to this web page.

  This was the only window I had open (the only other [user] program
  running was wallch, which rotates the desktop background image), when
  the screen went blank after a period of inactivity, and the screen
  wouldn't redraw when I moved my finger on the laptop touchpad or
  pressed the space bar to wake it up. It just stayed black, ctl-alt-del
  was not recognized, nor were any keys, and the only thing I could
  figure out to get it back was to press the power button until the
  computer shut off.  Then reboot.  This happened twice.  The touchpad
  was hot, like something was overheating inside the laptop.  This
  laptop was built by System76 and is some sort of generic Lenovo under
  the hood.

  No web site has ever crashed my computer before.  I have Ubuntu,
  upgraded from version 20 to 22.04.1 LTS three weeks ago, and upgraded
  from DSL to fiber Internet two weeks ago.  Maybe one of these is
  causing the problem.  I'll try to also report it to the other
  components' producers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1990030/+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 1990189] Re: brlttty claiming CH341 usbtty device blocking access

2022-09-19 Thread Samuel thibault

Ok. That'd be tricky to filter. Fortunately with brltty 6.5 such generic
entries are kept apart so that they can be packaged separately.

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

Title:
  brlttty claiming CH341 usbtty device blocking access

Status in brltty package in Ubuntu:
  New

Bug description:
  While this problem seems to have been fixed for FTDI and CP210 based
  devices CH340/CH341 based (and possibly other USB serial adapters) are
  unusable except by brltty.

  [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using 
xhci_hcd
  [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, 
idProduct=7523, bcdDevice= 2.63
  [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0
  [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial
  [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected
  [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0
  [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input24
  [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 
'brltty' sets config #1
  [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected 
from ttyUSB0
  [139100.786136] ch341 1-2.1.2:1.0: device disconnected
  [143917.740171] usb 1-2.1.2: USB disconnect, device number 17

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: brltty 6.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon Sep 19 12:01:21 2022
  InstallationDate: Installed on 2022-08-23 (27 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: brltty
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+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 1989590] Re: Can't click on dock items if status drop-down is shown

2022-09-19 Thread Bug Watch Updater

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

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

Title:
  Can't click on dock items if status drop-down is shown

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

Bug description:
  Steps:
  1. open any of the system status drop-downs
  2. click on any app icon in the Ubuntu Dock

  Expected:
  1. the system status drop-down goes away

  Current:
  1. nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 14 16:49:59 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-08-31 (13 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/zsh
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1989590/+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 1980408] Re: Update glib to 2.72.3

2022-09-19 Thread Jeremy Bicha

There is a regression introduced in the 2.72.3 update so we're going to
prepare 2.72.4 for Jammy when it's released.

https://gitlab.gnome.org/GNOME/glib/-/issues/2687

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

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

** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2687
   https://gitlab.gnome.org/GNOME/glib/-/issues/2687

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

Title:
  Update glib to 2.72.3

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

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1980408/+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 1980781] Re: SRU of ubuntu-advantage-desktop-daemon to older series

2022-09-19 Thread Robert Ancell

** Also affects: ubuntu-advantage-desktop-daemon (Ubuntu Bionic)
Importance: Undecided
Status: New

** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu Bionic)
Status: New => Fix Committed

** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu Bionic)
Importance: Undecided => High

** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu Bionic)
Assignee: (unassigned) => Sebastien Bacher (seb128)

** Also affects: ubuntu-advantage-desktop-daemon (Ubuntu Xenial)
Importance: Undecided
Status: New

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

Title:
SRU of ubuntu-advantage-desktop-daemon to older series

Status in ubuntu-advantage-desktop-daemon package in Ubuntu:
Fix Released
Status in ubuntu-advantage-desktop-daemon source package in Xenial:
New
Status in ubuntu-advantage-desktop-daemon source package in Bionic:
Fix Committed
Status in ubuntu-advantage-desktop-daemon source package in Focal:
Fix Committed

Bug description:
[Impact]

ubuntu-advantage-desktop-daemon is a service we added in 22.04 to let
desktop application interact easily with Ubuntu Advantage

adsys makes use of is to check if the system is connected to UA. This is
supported in 20.04 LTS but until now the daemon was not available there.
Installing the daemon enables advanced usages (scripts, privilege
delegation…) which require an Ubuntu Pro account

Ubuntu Pro integration is being added to software-properties which
also require the service to be available.

[Test Plan]

A. Verify the service

1. Install:
$ sudo apt install ubuntu-advantage-desktop-daemon
2. Check able to access daemon
$ gdbus call --system --dest com.canonical.UbuntuAdvantage --object-path
/com/canonical/UbuntuAdvantage/Manager --method
org.freedesktop.DBus.Properties.GetAll 'com.canonical.UbuntuAdvantage.Manager'
({'Attached': , 'DaemonVersion': <'1.8'>},)

B. Software-properties

Verify that the new 'Ubuntu Pro' page is working as expected, SRU bug
#, especially that it reflects the correct status and that
attaching/detaching a token and enabling/disabling services is working

C. Adsys (focal)

1. Ensure that you have an Ubuntu Advantage subcription enabled.
2. Setup some scripts under AD to be executed, one for machine scripts (on
startup), one for user scripts (on login). Those scripts can create some
temporary files under /tmp for instance.
3. Reboot and login on the Ubuntu laptop connected with AD by adsys.
4. Check that the scripts were executed by testing that the created file
under /tmp are present.

[Where problems could occur]

This is a code that has not previously been used on 20.04 and thus
could trigger new bugs. It has been used for since jammy though
without major issues.

A. The service itself

The service shouldn't be active unless it's needed. If you don't have ubuntu
advantage nor adsys configured check that the service is not loaded.
The service should low on resource usage, check that it's the case by
checking the RAM and CPU consumption.

B. Software-properties

The Ubuntu Pro tab didn't exist before so there should be no
regression possible there due to the service. The livepatch enablement
is handled through the service as part of UA now so check that
livepatch is correctly working still on upgraded systems

C. Adsys (focal)

The behaviour change in adsys should be limited to enabling features
which weren't available in focal before but we should ensure those are
correctly working and not providing a buggy user experience

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-desktop-daemon/+bug/1980781/+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 1990039] Re: gsd-xsettings crashed with SIGSEGV in g_closure_invoke()

2022-09-19 Thread Apport retracing service

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!


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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1990039/+attachment/5616705/+files/CoreDump.gz

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

Title:
  gsd-xsettings crashed with SIGSEGV in g_closure_invoke()

Status in gnome-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  sudden crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-settings-daemon 43~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7
  Uname: Linux 5.19.0-16-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 17 21:28:17 2022
  Disassembly: => 0x7f321c9854f0:   Cannot access memory at address 
0x7f321c9854f0
  ExecutablePath: /usr/libexec/gsd-xsettings
  InstallationDate: Installed on 2020-06-25 (813 days ago)
  InstallationMedia:
   
  JournalErrors:
   Error: command ['journalctl', '--priority=warning', '--since=@1663421287', 
'--until=@1663421307'] failed with exit code 1: Hint: You are currently not 
seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/libexec/gsd-xsettings
  SegvAnalysis:
   Segfault happened at: 0x7f321c9854f0:Cannot access memory at address 
0x7f321c9854f0
   PC (0x7f321c9854f0) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gsd-xsettings crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (144 days ago)
  UserGroups: nordvpn sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1990039/+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 1990010] Re: VA error: resource allocation failed

2022-09-19 Thread Bram Stolk

The hex value 0100   0008 decodes to:

#define I915_FORMAT_MOD_Y_TILED_GEN12_RC_CCS_CC fourcc_mod_code(INTEL,
8)

This is not listed as supported by
MediaLibvaCapsG12::SetExternalSurfaceTileFormat()

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

Title:
  VA error: resource allocation failed

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When I play a H264/AAC video with HW decoding enabled on Alderlake
  12600k, I get the error:

  vaCreateSurfaces (import mode) failed, VA error: resource allocation
  failed

  After which, chromium will proceed to play the video without HW
  acceleration using ffmpeg.

  This is both with using the pre-built snap from channel beta/hwacc and
  a snap built from source.

  To get more information on this VA error, I built the snap with debug
  versions of gmmlib and media-driver (latest git) using the latest git
  from valib as well.

  The log output from chromium now mentions why the allocation fails:

  [390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
  [389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)] 
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
  [390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
  [390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
  [390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
  [390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder

  Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
  modifier."

  I am on wayland, and use these chromium flags:

  export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
  features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
  features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
  --disable-gpu-driver-bug-workaround --ozone-platform=wayland"

  
  The video that fails: the 1080p/60 version downloaded from here: 
https://github.com/chthomos/video-media-samples/

  I will figure out which is the "unsupported modifier" and report back,
  here.

  Note: currently gmmlib and media-driver have failing debug builds, but I have 
created pull requests to both:
  https://github.com/intel/media-driver/pull/1491
  https://github.com/intel/gmmlib/pull/97

  
  CPU: 12600k

  GPU: Intel Alderlake_s (Gen12)

  Snap built with: core20

  Host OS: Ubuntu Kinetic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+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 1990189] Re: brlttty claiming CH341 usbtty device blocking access

2022-09-19 Thread beattie

is there a work around?

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

Title:
  brlttty claiming CH341 usbtty device blocking access

Status in brltty package in Ubuntu:
  New

Bug description:
  While this problem seems to have been fixed for FTDI and CP210 based
  devices CH340/CH341 based (and possibly other USB serial adapters) are
  unusable except by brltty.

  [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using 
xhci_hcd
  [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, 
idProduct=7523, bcdDevice= 2.63
  [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0
  [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial
  [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected
  [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0
  [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input24
  [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 
'brltty' sets config #1
  [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected 
from ttyUSB0
  [139100.786136] ch341 1-2.1.2:1.0: device disconnected
  [143917.740171] usb 1-2.1.2: USB disconnect, device number 17

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: brltty 6.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon Sep 19 12:01:21 2022
  InstallationDate: Installed on 2022-08-23 (27 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: brltty
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+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 1990207] [NEW] "Night Light unavailable" in Settings (but the quick settings toggle for it works)

Public bug reported:

"Night Light unavailable" in Settings (but the quick settings toggle for
it works).

** Affects: gnome-control-center
 Importance: Unknown
 Status: Unknown

** Affects: mutter
 Importance: Unknown
 Status: Unknown

** Affects: gnome-control-center (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: mutter (Ubuntu)
 Importance: Medium
 Status: Fix Committed


** Tags: fixed-in-43.1 fixed-upstream kinetic regression-release

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

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2056
   Importance: Unknown
   Status: Unknown

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

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

Title:
  "Night Light unavailable" in Settings (but the quick settings toggle
  for it works)

Status in gnome-control-center:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  "Night Light unavailable" in Settings (but the quick settings toggle
  for it works).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1990207/+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 1990207] Re: "Night Light unavailable" in Settings (but the quick settings toggle for it works)

Looks like the fix is in mutter 43.1 ?

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2623

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

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

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2424
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2424

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

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

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

Title:
  "Night Light unavailable" in Settings (but the quick settings toggle
  for it works)

Status in gnome-control-center:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  "Night Light unavailable" in Settings (but the quick settings toggle
  for it works).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1990207/+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 1990209] [NEW] To support Goodix fp device [27C6:631C]

2022-09-19 Thread Andy Chi

Public bug reported:

https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/3a8299158600e06b126e72238ebd9156c7f59fc4

This ID is included in upstream.

[Impact]

 * Devices have Goodix [27C6:631C] fingerprint component will get
   supported.

[Test Plan]

 * Find a machine with this fingerprint device

 * Launch `settings` and enable `Fingerprint Login`

 * Enroll finger and then logout

 * Login system with enrolled finger

[Where problems could occur]

 * The only impact will be [27C6:631C] will be supported.

** Affects: oem-priority
 Importance: Critical
 Assignee: Andy Chi (andch)
 Status: Confirmed

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


** Tags: oem-priority originate-from-1980477 somerville

** Tags added: oem-priority originate-from-1980477 somerville

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

** Changed in: oem-priority
   Status: New => Confirmed

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

Title:
  To support Goodix fp device [27C6:631C]

Status in OEM Priority Project:
  Confirmed
Status in libfprint package in Ubuntu:
  New

Bug description:
  
https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/3a8299158600e06b126e72238ebd9156c7f59fc4

  This ID is included in upstream.

  [Impact]

   * Devices have Goodix [27C6:631C] fingerprint component will get
 supported.

  [Test Plan]

   * Find a machine with this fingerprint device

   * Launch `settings` and enable `Fingerprint Login`

   * Enroll finger and then logout

   * Login system with enrolled finger

  [Where problems could occur]

   * The only impact will be [27C6:631C] will be supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990209/+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 1857392] Re: Window manager warning: Overwriting existing binding of keysym...

System hangs are generally not related to this bug, unless it really has
filled up your whole disk...

So that the causes of system hangs can be investigated properly, please
report them as separate bugs by running:

  ubuntu-bug gnome-shell


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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Window manager warning: Overwriting existing binding of keysym...

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) Gnome 3.34.1
  3) No error.
  4) Error in Ubuntu Logs App.

  Sender: gnome-shell
  Message:
  4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 
GMT-0600 (CST)
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 37 with keysym 37 (keycode 10).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 36 with keysym 36 (keycode f).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 35 with keysym 35 (keycode e).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 34 with keysym 34 (keycode d).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 32 with keysym 32 (keycode b).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 39 with keysym 39 (keycode 12).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 33 with keysym 33 (keycode c).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 38 with keysym 38 (keycode 11).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 31 with keysym 31 (keycode a).
  Audit Session: 2
  Priority: 6

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1857392/+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 1990170] Re: HDMI refresh rate at 4k 144hz cant be set