date:20221120

[Desktop-packages] [Bug 1942791] Re: _has_integrated_gpu() needs to consider the desktop case

2022-11-20 Thread jeremyszu

as #2.

** Changed in: oem-priority
   Status: Confirmed => Fix Released

** Changed in: nvidia-prime (Ubuntu)
   Status: New => Fix Released

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

Title:
  _has_integrated_gpu() needs to consider the desktop case

Status in OEM Priority Project:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released

Bug description:
  In recovery (from a storage) case, the /var/lib/ubuntu-drivers-
  common/last_gfx_boot is empty. Thus, the _has_integrated_gpu() returns
  false in I+N laptop case. In this case, there is a iGPU actually.

  ---

  During the recovery, a worker executes ubuntu-drivers install.

  The expected result is "on-demand" but it goes to "on" because
  /var/lib/ubuntu-drivers-common/last_gfx_boot doesn't exist

  `ubuntu-drivers install` calls `prime-select on-demand` calls
  enable_profile() and then enable_profile() calls _has_integrated_gpu()
  before switching mode.

  Since _has_integrated_gpu() returns false, it won't switch nvidia mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942791/+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 1994027] Re: Can't move window by drag and drop by using touch screen

2022-11-20 Thread Rex Tsai

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

** Changed in: oem-priority
   Status: Triaged => Won't Fix

** Changed in: oem-priority
   Status: Won't Fix => Fix Committed

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

Title:
  Can't move window by drag and drop by using touch screen

Status in OEM Priority Project:
  Fix Committed
Status in XServer:
  Unknown
Status in xorg package in Ubuntu:
  New

Bug description:
  [Impact]
  Users using touch screen could not move windows with 'Drag-n-drop'.
  This SRU fixes the issue.

  [Test Plan]
  1. Install the 22.04
  2. Boot and login
  3. Open a folder or terminal
  4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch
  5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom 
Pen

  Expected: Both finger touch and wacom pen work normally.

  Actual: Wacom Pen works normally, finger touch can not move the
  windows.

  [Where problems could occur]
  It's a regression of upstream packages, 
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866

  It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e.

  [Version]
  xserver-xorg-core 2:21.1.3-2ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1997201] [NEW] BlueZ 5.66 release

2022-11-20 Thread Daniel van Vugt

Public bug reported:

Release to Lunar:

http://www.bluez.org/release-of-bluez-5-66/

** Affects: bluez (Ubuntu)
 Importance: Medium
 Assignee: Daniel van Vugt (vanvugt)
 Status: Triaged


** Tags: lunar

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

Title:
  BlueZ 5.66 release

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  Release to Lunar:

  http://www.bluez.org/release-of-bluez-5-66/

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


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

[Desktop-packages] [Bug 1989503] Re: Wrong change of dock zoom on multiple screens

2022-11-20 Thread Daniel van Vugt

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

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

Title:
  Wrong change of dock zoom on multiple screens

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

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

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


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

[Desktop-packages] [Bug 1990312] Re: Can't change desktop language in Ubuntu 22.04

2022-11-20 Thread Launchpad Bug Tracker

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Can't change desktop language in Ubuntu 22.04

Status in ubuntu-meta package in Ubuntu:
  Expired

Bug description:
  I initially installed Ubuntu 22.04 with the English language.
  Now, I'd like to use the Ubuntu desktop in the German language.
  I believe I've done everything needed. I rebooted of course. The login screen 
is now in German, but my user desktop is still in English, except the calendar 
showing the date.

  See the attached screenshot.

  Here is the output of the "locale" command:

  LANG=de_DE.UTF-8
  LANGUAGE=en
  LC_CTYPE=en_US.UTF-8
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE=en_US.UTF-8
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES=en_US.UTF-8
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  Am I the only one having this issue?
  Thanks in advance
  Michael

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990312/+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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode

2022-11-20 Thread Kai-Chuan Hsieh

** No longer affects: oem-priority

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

Title:
  Fibcom FM350-GL not able connect to network with 5G mode

Status in libmbim package in Ubuntu:
  Confirmed
Status in libqmi package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  Fibcom FM350-GL can support 5G network
  (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu
  22.04, system can only connect to mobile network with 4G mode.


General  | path: /org/freedesktop/ModemManager1/Modem/0
 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e

Hardware | manufacturer: generic
 |model: MBIM [14C3:4D75]
 |firmware revision: 81600..00.29.18.01_GC
 |   C01
 | h/w revision: V1.0.6
 |supported: gsm-umts, lte
 |  current: gsm-umts, lte
 | equipment id: 352750140002001

System   |   device: 
/sys/devices/pci:00/:00:1c.0/:73:00.0
 |  drivers: mtk_t7xx
 |   plugin: generic
 | primary port: wwan0mbim0
 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 
(mbim)

Status   |   unlock retries: sim-pin (3), sim-pin2 (3)
 |state: connected
 |  power state: on
 |  access tech: lte
 |   signal quality: 74% (recent)

Modes|supported: allowed: 3g, 4g; preferred: none
 |  current: allowed: 3g, 4g; preferred: none

IP   |supported: ipv4, ipv6, ipv4v6

3GPP | imei: 352750140002001
 |enabled locks: sim, fixed-dialing
 |  operator id: 46692
 |operator name: Chunghwa Telecom
 | registration: home

3GPP EPS | ue mode of operation: csps-2
 |  initial bearer path: /org/freedesktop/ModemManager1/Bearer/0

SIM  | primary sim path: /org/freedesktop/ModemManager1/SIM/0

Bearer   |paths: /org/freedesktop/ModemManager1/Bearer/1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-06-15 (26 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: modemmanager 1.18.6-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9
  Tags:  jammy
  Uname: Linux 5.17.0-9012-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1981190/+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 1994027] Re: Can't move window by drag and drop by using touch screen

2022-11-20 Thread Bin Li

Built a new packages for testing in my ppa. This issue is fixed with
xserver-xorg-core 2:21.1.3-2ubuntu2.2binli1.

https://launchpad.net/~binli/+archive/ubuntu/gnome/


** Changed in: oem-priority
   Status: In Progress => Triaged

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

Title:
  Can't move window by drag and drop by using touch screen

Status in OEM Priority Project:
  Triaged
Status in XServer:
  Unknown
Status in xorg package in Ubuntu:
  New

Bug description:
  [Impact]
  Users using touch screen could not move windows with 'Drag-n-drop'.
  This SRU fixes the issue.

  [Test Plan]
  1. Install the 22.04
  2. Boot and login
  3. Open a folder or terminal
  4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch
  5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom 
Pen

  Expected: Both finger touch and wacom pen work normally.

  Actual: Wacom Pen works normally, finger touch can not move the
  windows.

  [Where problems could occur]
  It's a regression of upstream packages, 
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866

  It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e.

  [Version]
  xserver-xorg-core 2:21.1.3-2ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] Re: Can't move window by drag and drop by using touch screen

2022-11-20 Thread Bin Li

** Patch added: "xorg-server_21.1.3-2ubuntu2.3.debdiff"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1994027/+attachment/5631780/+files/xorg-server_21.1.3-2ubuntu2.3.debdiff

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

Title:
Can't move window by drag and drop by using touch screen

Status in OEM Priority Project:
In Progress
Status in XServer:
Unknown
Status in xorg package in Ubuntu:
New

Bug description:
[Impact]
Users using touch screen could not move windows with 'Drag-n-drop'.
This SRU fixes the issue.

[Test Plan]
1. Install the 22.04
2. Boot and login
3. Open a folder or terminal
4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch
5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom
Pen

Expected: Both finger touch and wacom pen work normally.

Actual: Wacom Pen works normally, finger touch can not move the
windows.

[Where problems could occur]
It's a regression of upstream packages,
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866

It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e.

[Version]
xserver-xorg-core 2:21.1.3-2ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-11-20 Thread jeremyszu

** Tags added: nvidia-wayland

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .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  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1

[Desktop-packages] [Bug 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time

2022-11-20 Thread jeremyszu

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  System fallback to gdm login screen when hot-plugging a external
  monitor in 1st time

Status in OEM Priority Project:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released

Bug description:
  [Steps to reproduce]
  1. Install Jammy daily build
  2. dist-upgrade to verify https://bugs.launchpad.net/mutter/+bug/1964037
  3. reboot with no attach monitor
  4. attach monitor after booting

  [Expect result]
  external monitor works directly

  [Actual result]
  system go back to gdm login screen

  [Additional information]
  1. the external port is connecting to dGPU.
  2. happens on wayland only
  3. Only back to login screen in 1st attach, 2nd, 3rd, etc.. works good

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Apr 14 21:22:47 2022
  InstallationDate: Installed on 2022-04-13 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969121/+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 1994027] Re: Can't move window by drag and drop by using touch screen

2022-11-20 Thread Bin Li

Here is the patch from upstream.

** Patch added: "dix-Don-t-send-touch-end-to-clients-that-do-async-grab.patch"
   
https://bugs.launchpad.net/xserver/+bug/1994027/+attachment/5631766/+files/dix-Don-t-send-touch-end-to-clients-that-do-async-grab.patch

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

Title:
  Can't move window by drag and drop by using touch screen

Status in OEM Priority Project:
  In Progress
Status in XServer:
  Unknown
Status in xorg package in Ubuntu:
  New

Bug description:
  [Impact]
  Users using touch screen could not move windows with 'Drag-n-drop'.
  This SRU fixes the issue.

  [Test Plan]
  1. Install the 22.04
  2. Boot and login
  3. Open a folder or terminal
  4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch
  5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom 
Pen

  Expected: Both finger touch and wacom pen work normally.

  Actual: Wacom Pen works normally, finger touch can not move the
  windows.

  [Where problems could occur]
  It's a regression of upstream packages, 
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866

  It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e.

  [Version]
  xserver-xorg-core 2:21.1.3-2ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] Re: Can't move window by drag and drop by using touch screen

2022-11-20 Thread Bin Li

** Description changed:

- [Summary]
- For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed.
+ [Impact]
+ Users using touch screen could not move windows with 'Drag-n-drop'.
+ This SRU fixes the issue.
  
- [Steps to reproduce]
+ [Test Plan]
  1. Install the 22.04
  2. Boot and login
  3. Open a folder or terminal
  4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch
  5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom 
Pen
  
- [Expected result]
- Both finger touch and wacom pen work normally.
+ Expected: Both finger touch and wacom pen work normally.
  
- [Actual result]
- Wacom Pen works normally, finger touch can not move the windows.
+ Actual: Wacom Pen works normally, finger touch can not move the windows.
  
- [Failure rate]
- 100%
+ [Where problems could occur]
+ It's a regression of upstream packages, 
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866
  
- [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop`
- output]
+ It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e.
  
- [Other Information]
- xorg  1:7.7+23ubuntu2
- mutter-common 42.2-0ubuntu1
- gnome-shell 42.4-0ubuntu0.22.04.1
+ [Version]
+ xserver-xorg-core 2:21.1.3-2ubuntu2.2

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

Title:
  Can't move window by drag and drop by using touch screen

Status in OEM Priority Project:
  In Progress
Status in XServer:
  Unknown
Status in xorg package in Ubuntu:
  New

Bug description:
  [Impact]
  Users using touch screen could not move windows with 'Drag-n-drop'.
  This SRU fixes the issue.

  [Test Plan]
  1. Install the 22.04
  2. Boot and login
  3. Open a folder or terminal
  4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch
  5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom 
Pen

  Expected: Both finger touch and wacom pen work normally.

  Actual: Wacom Pen works normally, finger touch can not move the
  windows.

  [Where problems could occur]
  It's a regression of upstream packages, 
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866

  It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e.

  [Version]
  xserver-xorg-core 2:21.1.3-2ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] Re: Can't move window by drag and drop by using touch screen

2022-11-20 Thread Bin Li

** No longer affects: gtk+3.0 (Ubuntu)

** Changed in: oem-priority
   Status: New => In Progress

** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1255
   https://gitlab.freedesktop.org/xorg/xserver/-/issues/1255

** Project changed: mutter => xserver

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

** Changed in: xserver
 Remote watch: gitlab.gnome.org/GNOME/mutter/-/issues #2057 => 
gitlab.freedesktop.org/xorg/xserver/-/issues #1255

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

Title:
  Can't move window by drag and drop by using touch screen

Status in OEM Priority Project:
  In Progress
Status in XServer:
  Unknown
Status in xorg package in Ubuntu:
  New

Bug description:
  [Summary]
  For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed.

  [Steps to reproduce]
  1. Install the 22.04
  2. Boot and login
  3. Open a folder or terminal
  4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch
  5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom 
Pen

  [Expected result]
  Both finger touch and wacom pen work normally.

  [Actual result]
  Wacom Pen works normally, finger touch can not move the windows.

  [Failure rate]
  100%

  [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop`
  output]

  [Other Information]
  xorg  1:7.7+23ubuntu2
  mutter-common 42.2-0ubuntu1
  gnome-shell 42.4-0ubuntu0.22.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1997187] Re: UBSAN: array-index-out-of-bounds in /build/linux-3Zc9YS/linux-5.19.0/sound/pci/emu10k1/emupcm.c:127:40

2022-11-20 Thread Daniel LaSalle

https://lore.kernel.org/all/3707dcab-320a-62ff-63c0-73fc201ef...@tasossah.com/

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

Title:
  UBSAN: array-index-out-of-bounds in
  /build/linux-3Zc9YS/linux-5.19.0/sound/pci/emu10k1/emupcm.c:127:40

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have disabled onboard audio card;
  I have plugged in a PCI-E Creative Labs audio card;
  Sound works but I have the following at boot:
  [   25.985937] UBSAN: array-index-out-of-bounds in 
/build/linux-3Zc9YS/linux-5.19.0/sound/pci/emu10k1/emupcm.c:127:40
  [   25.985940] index 65 is out of range for type 'snd_emu10k1_voice [64]'

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  t  1546 F wireplumber
   /dev/snd/controlC0:  t  1546 F wireplumber
   /dev/snd/seq:t  1544 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Sun Nov 20 17:40:54 2022
  InstallationDate: Installed on 2022-11-03 (17 days ago)
  InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1997187/+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 1871360] Re: Ubuntu Cant find keyboard layout languages

2022-11-20 Thread Kangarooo Jānis

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

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

Title:
  Ubuntu Cant find keyboard layout languages

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

Bug description:
  Ubuntu Cant find keyboard layout languages
  List is empty when filtering as in image: "latvian"

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 11:00:13 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871360/+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 1992678] Re: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-11-20 Thread Launchpad Bug Tracker

This bug was fixed in the package firefox - 1:1snap1-0ubuntu3

---
firefox (1:1snap1-0ubuntu3) lunar; urgency=medium

  * Update the Vcs-Bzr URL for Ubuntu 23.04 (the Lunar Lobster)
- debian/control

 -- Olivier Tilloy   Sun, 06 Nov 2022
12:26:12 +0100

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

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

Title:
  package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new
  firefox package pre-installation script subprocess returned error exit
  status 1

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Terminal showed me how to install the missing dependencies and I was
  able to follow that and get Firefox working by myself.  I'd have
  thought sorting missing dependencies ought to have been built in to
  the upgrade program instead of coming up with a worrying report that
  the upgrade had failed

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Oct 11 21:03:22 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  Snap: firefox 105.0.3-1 (stable)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   6Done2022-10-12T11:31:22+07:00  2022-10-12T11:33:55+07:00  Install 
"firefox" snap
  Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new 
firefox package pre-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-10-11 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992678/+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 1997187] [NEW] UBSAN: array-index-out-of-bounds in /build/linux-3Zc9YS/linux-5.19.0/sound/pci/emu10k1/emupcm.c:127:40

2022-11-20 Thread Daniel LaSalle

Public bug reported:

I have disabled onboard audio card;
I have plugged in a PCI-E Creative Labs audio card;
Sound works but I have the following at boot:
[   25.985937] UBSAN: array-index-out-of-bounds in 
/build/linux-3Zc9YS/linux-5.19.0/sound/pci/emu10k1/emupcm.c:127:40
[   25.985940] index 65 is out of range for type 'snd_emu10k1_voice [64]'

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: pulseaudio 1:16.1+dfsg1-1ubuntu3
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  t  1546 F wireplumber
 /dev/snd/controlC0:  t  1546 F wireplumber
 /dev/snd/seq:t  1544 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Nov 20 17:40:54 2022
InstallationDate: Installed on 2022-11-03 (17 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5809
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug kinetic

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

Title:
  UBSAN: array-index-out-of-bounds in
  /build/linux-3Zc9YS/linux-5.19.0/sound/pci/emu10k1/emupcm.c:127:40

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have disabled onboard audio card;
  I have plugged in a PCI-E Creative Labs audio card;
  Sound works but I have the following at boot:
  [   25.985937] UBSAN: array-index-out-of-bounds in 
/build/linux-3Zc9YS/linux-5.19.0/sound/pci/emu10k1/emupcm.c:127:40
  [   25.985940] index 65 is out of range for type 'snd_emu10k1_voice [64]'

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  t  1546 F wireplumber
   /dev/snd/controlC0:  t  1546 F wireplumber
   /dev/snd/seq:t  1544 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Sun Nov 20 17:40:54 2022
  InstallationDate: Installed on 2022-11-03 (17 days ago)
  InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1997187/+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 1997178] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver redux

2022-11-20 Thread Jesse Johnson

** Attachment added: "journalctl log of sleep-wake-forced reboot around Nov 20 
10:28:37"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1997178/+attachment/5631722/+files/reboot.txt

** Description changed:

  When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia
  driver 515, screen is black, and never changes after 10 minutes of
  waiting.
  
  However journalctl shows activity after wake (see attached log excerpt,
- where wake occurs around Nov 20 10:28:37). This makes me think the issue
- is around Nvidia driver <-> Linux kernel communication.
+ where wake occurs around Nov 20 10:28:37 with black screen, followed by
+ forced REISUB reboot a couple minutes later when screen failed to
+ update). This makes me think the issue is around Nvidia driver <-> Linux
+ kernel communication.
  
  I [previously
  reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134)
  similar black screen after wake behavior that seemed resolve with a
  Linux kernel update, but subsequent Linux kernel and Nvidia driver
  updates steadily regressed back to the previous behavior. The most
  recent kernel update from a few days ago (5.15.0-53-generic) never wakes
  from suspend (so far out of 5 trials). Previous few kernels where
  regression was first noticed it was 50/50 odds of successful wake, so
  most recent kernel is a noticeable regression.
  
- Important note: most recent kernel (5.15.0-53) upgrade freezed mid-
- upgrade (first time this has happened to me on Linux in at least 5
+ Important note: most recent kernel (5.15.0-53) upgrade freezed system
+ mid-upgrade (first time this has happened to me on Linux in at least 5
  years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB,
  the kernel, Nvidia drivers, and a GRUB update (in that order).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-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:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
+  GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
  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: Sun Nov 20 11:20:45 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
-  NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131]
+  NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
+    Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131]
  InstallationDate: Installed on 2022-08-17 (95 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/usr/bin/zsh
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic 
root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.70
  dmi.board.name: X470 Taichi Ultimate
  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:

[Desktop-packages] [Bug 1997178] [NEW] Black screen after wake from S3 suspend on Nvidia proprietary driver redux

2022-11-20 Thread Jesse Johnson

Public bug reported:

When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia
driver 515, screen is black, and never changes after 10 minutes of
waiting.

However journalctl shows activity after wake (see attached log excerpt,
where wake occurs around Nov 20 10:28:37 with black screen, followed by
forced REISUB reboot a couple minutes later when screen failed to
update). This makes me think the issue is around Nvidia driver <-> Linux
kernel communication.

I [previously
reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134)
similar black screen after wake behavior that seemed resolve with a
Linux kernel update, but subsequent Linux kernel and Nvidia driver
updates steadily regressed back to the previous behavior. The most
recent kernel update from a few days ago (5.15.0-53-generic) never wakes
from suspend (so far out of 5 trials). Previous few kernels where
regression was first noticed it was 50/50 odds of successful wake, so
most recent kernel is a noticeable regression.

Important note: most recent kernel (5.15.0-53) upgrade freezed system
mid-upgrade (first time this has happened to me on Linux in at least 5
years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB,
the kernel, Nvidia drivers, and a GRUB update (in that order).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
Uname: Linux 5.15.0-53-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:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
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: Sun Nov 20 11:20:45 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Within the last week or two
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131]
InstallationDate: Installed on 2022-08-17 (95 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic 
root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.70
dmi.board.name: X470 Taichi Ultimate
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.:bvrP4.70:bd03/29/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: 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.
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.2
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 freeze jammy ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is

[Desktop-packages] [Bug 1997177] [NEW] package libaa1:i386 1.4p5-50build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

2022-11-20 Thread Alexander Grosu

Public bug reported:

ran into issue after installing ubuntu for the first time and trying to
install a package reader like wine or bottles

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libaa1:i386 1.4p5-50build1
ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
Uname: Linux 5.15.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
AptOrdering: NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sun Nov 20 20:20:05 2022
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2022-11-20 (0 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
PackageArchitecture: i386
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: aalib
Title: package libaa1:i386 1.4p5-50build1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 jammy

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

Title:
  package libaa1:i386 1.4p5-50build1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in aalib package in Ubuntu:
  New

Bug description:
  ran into issue after installing ubuntu for the first time and trying
  to install a package reader like wine or bottles

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libaa1:i386 1.4p5-50build1
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Nov 20 20:20:05 2022
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2022-11-20 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: aalib
  Title: package libaa1:i386 1.4p5-50build1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aalib/+bug/1997177/+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 1997175] [NEW] Help doesn't open the installed help files

2022-11-20 Thread Robin Sheat

Public bug reported:

Open, for example, libreoffice calc. In the menu, open Help ->
LibreOffice Help

Firefox opens and says "Firefox can’t find the file at
/usr/share/libreoffice/help/index.html?Target=scalc/.uno:HelpIndex=en-
US=UNIX=7.4."

$ ls /usr/share/libreoffice/help/index.html
/usr/share/libreoffice/help/index.html

I'm guessing this is due to firefox being in a snap and not having
normal file system access.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: libreoffice-core 1:7.4.2~rc3-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 20 20:15:08 2022
InstallationDate: Installed on 2022-03-23 (242 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to kinetic on 2022-10-22 (29 days ago)

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


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

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

Title:
  Help doesn't open the installed help files

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Open, for example, libreoffice calc. In the menu, open Help ->
  LibreOffice Help

  Firefox opens and says "Firefox can’t find the file at
  
/usr/share/libreoffice/help/index.html?Target=scalc/.uno:HelpIndex=en-
  US=UNIX=7.4."

  $ ls /usr/share/libreoffice/help/index.html
  /usr/share/libreoffice/help/index.html

  I'm guessing this is due to firefox being in a snap and not having
  normal file system access.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libreoffice-core 1:7.4.2~rc3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 20 20:15:08 2022
  InstallationDate: Installed on 2022-03-23 (242 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to kinetic on 2022-10-22 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1997175/+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 1993889] Re: nautilus does not launch

2022-11-20 Thread Judah Richardson

Filed a bug with the Gnome project
https://gitlab.gnome.org/GNOME/nautilus/-/issues/2643 as it looks like
it's affecting other distros too
https://www.reddit.com/r/linuxquestions/comments/yxoto0/nautilus_broken_after_update_symbol_lookup_error/
Kindly chime in at the Gnome bug so we can get some attention on this.

In the meantime, the Nightly build flatpak works via the following:

1. Set up flatpak: https://flatpak.org/setup/
2. Install Nightly build: # flatpak install --from
https://nightly.gnome.org/repo/appstream/org.gnome.NautilusDevel.flatpakref
3. Launch Nightly build: flatpak run org.gnome.NautilusDevel
4. Pin Nightly build to Dash

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2643
https://gitlab.gnome.org/GNOME/nautilus/-/issues/2643

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

Title:
nautilus does not launch

Status in nautilus package in Ubuntu:
Confirmed

Bug description:
Problem:
nautilus does not launch after it was closed previously.

Expectation:
Close nautilus, start nautilus again -> new nautilus window spawns.

What happens:
nautilus does not launch a second time. The cursor spins, but no window opens.

Observations:
the nautilus process does not get terminated properly. There is a nautilus
process remaining with almost no CPU consumption.

Workarounds:
Killing the process and starting nautilus again works. Starting it via
console and exiting it via X button does not end the task in the terminal.
CTRL+C terminates the process and it's restarting fine.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: nautilus 1:43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 22 14:03:06 2022
GsettingsChanges:
b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
b'org.gnome.nautilus.window-state' b'initial-size' b'(1033, 685)'
InstallationDate: Installed on 2022-10-22 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
file-roller 43.0-1
nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
python3-nautilus 4.0-1

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

[Desktop-packages] [Bug 1993889] Re: nautilus does not launch

2022-11-20 Thread Judah Richardson

Same problem here on this machine (specs at link):
https://github.com/jdrch/Hardware/blob/master/HP%20ProBook%204530s.md.
Also running 22.10. Problem started after I upgraded in-place from
22.04.

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

Title:
  nautilus does not launch

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Problem:
  nautilus does not launch after it was closed previously.

  Expectation:
  Close nautilus, start nautilus again -> new nautilus window spawns.

  What happens:
  nautilus does not launch a second time. The cursor spins, but no window opens.

  Observations:
  the nautilus process does not get terminated properly. There is a nautilus 
process remaining with almost no CPU consumption.

  Workarounds:
  Killing the process and starting nautilus again works. Starting it via 
console and exiting it via X button does not end the task in the terminal. 
CTRL+C terminates the process and it's restarting fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 14:03:06 2022
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1033, 685)'
  InstallationDate: Installed on 2022-10-22 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   python3-nautilus  4.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993889/+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 1956005] Re: Firefox Snap won't open links to WhatsApp API

2022-11-20 Thread HD

This URL
https://api.whatsapp.com/send/?text=https%3A%2F%2Fyoutu.be%2F8WgmjTwqtKY=custom_url_absent=0

in Firefox opens this box (attached)

Then a gnome error message
"No Apps available - No apps installed can open (This URL), You can fine more 
applications in software"

Button (Find more in Software)

Firefox can`t find "gnome-software"
((( because the real name is ubuntu-software, and by the way there is not 
whatsapp app there"



** Attachment added: "whatsapp in firefox.png"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956005/+attachment/5631689/+files/whatsapp%20in%20firefox.png

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

Title:
  Firefox Snap won't open links to WhatsApp API

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

Bug description:
  The .deb version of Firefox handles links to WhatsApp API
  (https://api.whatsapp.com/send/?phone=) without any problem: these
  links open the WhatsApp web client.

  Snap version of Firefox doesn't know how to handle these links. It
  opens the pop up "Choose an application to open whatsapp lnks" that
  only shows the option System Handler (which fails opening them if
  selected).

  Choosing Firefox is not possible as /bin and similar folders are out
  of range for the snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1956005/+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 1993800] Re: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2>

2022-11-20 Thread Gianfranco Costamagna

Fix uploaded in Debian, will be syncd in some hours.

** Changed in: llvm-toolchain-15 (Ubuntu)
   Status: Confirmed => Fix Released

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

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

Title:
  LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8,
  Constant:i32<2>

Status in LLVM:
  Fix Released
Status in llvm-toolchain-15 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in llvm-toolchain-15 package in openSUSE:
  Unknown

Bug description:
  LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, 
Constant:i32<2>
    0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 
0x2f84090:1, Constant:i32<4>
  0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), 
> 0x2aad434, 0x2f63a30, Constant:i32<64>
    0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23
  0x2f51c10: i32 = Register %23
    0x2f82500: i32 = Constant<64>
  0x2f81b28: i32 = Constant<4>
    0x2f81e40: i32 = Constant<2>
  In function: fs_variant_partial

  [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic-
  armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz]

  Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't
  determine what project "fs_variant_partial" is in. Sounds like it
  might be in some old version of Mesa? The start of the log suggests
  it's running on focal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/llvm/+bug/1993800/+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 1994121] Re: Webcam image not shown in Cheese

2022-11-20 Thread Daniel Frein

The bug is still relevant for ubuntu 22.10 (with cheese 43~alpha-1 under
wayland) - see attached log. This upstream bug could be a similar issue:


Webcam works as expected with other applications e.g.
"GST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src ! xvimagesink"


** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #134
   https://gitlab.gnome.org/GNOME/cheese/-/issues/134

** Attachment added: "cheese.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1994121/+attachment/5631688/+files/cheese.txt

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

Title:
  Webcam image not shown in Cheese

Status in cheese package in Ubuntu:
  Confirmed

Bug description:
  See title.

  Observed in Ubuntu 22.04.1 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1994121/+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 1997168] [NEW] [snap] Passwords are saved but not loaded with gnome keyring

2022-11-20 Thread Alexander Stricker

Public bug reported:

Steps to reproduce:

* System: Fresh (minimal, desktop) installation of Ubuntu 22.04 LTS in 
VirtualBox to rule out any side-effects from preexisting configurations
* Install latest updates: `sudo apt update && sudo apt upgrade -y && sudo apt 
dist-upgrade -y && sudo snap refresh`
* Install chromium from snap (`sudo snap install chromium`)
* Connect chromium to password manager service (`sudo snap connect 
chromium:password-manager-service`) -> now chromium should be able to use gnome 
keyring to store its master password
* Launch chromium, navigate to "chrome://settings/passwords"
* Add a new password ("Saved Passwords" -> "Add")
* Password shows up under "Saved Passwords" as expected.
* Close chromium and open it again, navigate to "chrome://settings/passwords"
* Expected: Password should show up. Instead: The list is empty.
* Add another password: List stays empty.

What I found out so far:
 
* Despite of the list showing up as empty in chromium, both passwords have been 
stored in "~/snap/chromium/common/chromium/Default/Login Data" (to confirm, 
grep for the username of the saved login, as the password itself will be 
encrypted)
* It seems that the snap version of chromium does not create the entries 
"Chrome Safe Storage" and "Chrome Safe Storage Control" in the gnome keyring, 
which seems to be necessary at the moment (see http://crbug.com/660005). If a 
non-snap version of chromium (e.g. from 
https://launchpad.net/~savoury1/+archive/ubuntu/chromium) is installed first, 
which is used to bootstrap the user's chromium config folder and which creates 
the aforementioned entries in the gnome keyring, things are working fine, even 
after transitioning to the snap version.

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


** Tags: gnome keyring snap

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

Title:
  [snap] Passwords are saved but not loaded with gnome keyring

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  * System: Fresh (minimal, desktop) installation of Ubuntu 22.04 LTS in 
VirtualBox to rule out any side-effects from preexisting configurations
  * Install latest updates: `sudo apt update && sudo apt upgrade -y && sudo apt 
dist-upgrade -y && sudo snap refresh`
  * Install chromium from snap (`sudo snap install chromium`)
  * Connect chromium to password manager service (`sudo snap connect 
chromium:password-manager-service`) -> now chromium should be able to use gnome 
keyring to store its master password
  * Launch chromium, navigate to "chrome://settings/passwords"
  * Add a new password ("Saved Passwords" -> "Add")
  * Password shows up under "Saved Passwords" as expected.
  * Close chromium and open it again, navigate to "chrome://settings/passwords"
  * Expected: Password should show up. Instead: The list is empty.
  * Add another password: List stays empty.

  What I found out so far:
   
  * Despite of the list showing up as empty in chromium, both passwords have 
been stored in "~/snap/chromium/common/chromium/Default/Login Data" (to 
confirm, grep for the username of the saved login, as the password itself will 
be encrypted)
  * It seems that the snap version of chromium does not create the entries 
"Chrome Safe Storage" and "Chrome Safe Storage Control" in the gnome keyring, 
which seems to be necessary at the moment (see http://crbug.com/660005). If a 
non-snap version of chromium (e.g. from 
https://launchpad.net/~savoury1/+archive/ubuntu/chromium) is installed first, 
which is used to bootstrap the user's chromium config folder and which creates 
the aforementioned entries in the gnome keyring, things are working fine, even 
after transitioning to the snap version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997168/+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 1973084] Re: transmission-daemon high RAM usage

2022-11-20 Thread Andrew

Confirmed happening in x86_64 build (and has been for at least six
months, under both 22.04 and 22.10...though it was fine at some point in
the past as I used it successfully for many years with no issue. Please,
please, please fix (even if the solution is giving us some mechanism to
upgrade to the 4.0 beta via PPA or something (as the commits mention
several fixes to memory leaks)...this has been driving me nuts!

No specific torrent, reboot or restart fixes issue (temporarily).

Transmission 3.00 (bb6b5a062e).
51 files seeding (currently), though it doesn't seem sensitive to the number.
16MB disk cache. Max 240 peers.
Tried disabling PEX, DHT and LPD to see if that would help as I don't 
particularly need them anyway (but it doesn't help).

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

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign
  on a Raspberry Pi 4.

  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.

  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.

  
  Description:Ubuntu 22.04 LTS
  Release:22.04

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


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

[Desktop-packages] [Bug 1996927] Re: Nautilus send mail not working

2022-11-20 Thread frenchy82

Same problem here with thunderbird (ubuntu 22.10 too).

just to add that this bug does not exist with evolution

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

Title:
  Nautilus send mail not working

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  After upgrade   from   22.04 to 22.10  Send an attached file   to email from 
nautilus  is not working anymore.
  Menu sendmail ( courriel in french)  appears  when i  right click  on file ,  
then thunderbird  appears   but without   the attachement  . It was working 
very well with previous releases .
  regards 
  Yanick

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 17 18:42:19 2022
  InstallationDate: Installed on 2021-10-16 (397 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   nautilus-image-converter  0.4.0-2
   python3-nautilus  4.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1996927/+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 1942791] Re: _has_integrated_gpu() needs to consider the desktop case

[Desktop-packages] [Bug 1994027] Re: Can't move window by drag and drop by using touch screen

[Desktop-packages] [Bug 1997201] [NEW] BlueZ 5.66 release

[Desktop-packages] [Bug 1989503] Re: Wrong change of dock zoom on multiple screens

[Desktop-packages] [Bug 1990312] Re: Can't change desktop language in Ubuntu 22.04

[Desktop-packages] [Bug 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode

[Desktop-packages] [Bug 1994027] Re: Can't move window by drag and drop by using touch screen

[Desktop-packages] [Bug 1994027] Re: Can't move window by drag and drop by using touch screen

[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

[Desktop-packages] [Bug 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time

[Desktop-packages] [Bug 1994027] Re: Can't move window by drag and drop by using touch screen

[Desktop-packages] [Bug 1994027] Re: Can't move window by drag and drop by using touch screen

[Desktop-packages] [Bug 1994027] Re: Can't move window by drag and drop by using touch screen

[Desktop-packages] [Bug 1997187] Re: UBSAN: array-index-out-of-bounds in /build/linux-3Zc9YS/linux-5.19.0/sound/pci/emu10k1/emupcm.c:127:40

[Desktop-packages] [Bug 1871360] Re: Ubuntu Cant find keyboard layout languages

[Desktop-packages] [Bug 1992678] Re: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

[Desktop-packages] [Bug 1997187] [NEW] UBSAN: array-index-out-of-bounds in /build/linux-3Zc9YS/linux-5.19.0/sound/pci/emu10k1/emupcm.c:127:40

[Desktop-packages] [Bug 1997178] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver redux

[Desktop-packages] [Bug 1997178] [NEW] Black screen after wake from S3 suspend on Nvidia proprietary driver redux

[Desktop-packages] [Bug 1997177] [NEW] package libaa1:i386 1.4p5-50build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

[Desktop-packages] [Bug 1997175] [NEW] Help doesn't open the installed help files

[Desktop-packages] [Bug 1993889] Re: nautilus does not launch

[Desktop-packages] [Bug 1993889] Re: nautilus does not launch

[Desktop-packages] [Bug 1956005] Re: Firefox Snap won't open links to WhatsApp API

[Desktop-packages] [Bug 1993800] Re: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2>

[Desktop-packages] [Bug 1994121] Re: Webcam image not shown in Cheese

[Desktop-packages] [Bug 1997168] [NEW] [snap] Passwords are saved but not loaded with gnome keyring

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

[Desktop-packages] [Bug 1996927] Re: Nautilus send mail not working

29 matches

Site Navigation

Mail list logo

Footer information