date:20240128

You have been subscribed to a public bug:

Using last release of Ubuntu Desktop, I can cut & paste files or folders from 
the desktop to another location, but I can't do it by drag and drop.
Although the mouse pointer changes properly on pressing or releasing the shift 
key while dragging, files and/or folders are always copied, not moved.

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


** Tags: bot-comment
-- 
Can't move files or folders from desktop by dragging
https://bugs.launchpad.net/bugs/2051364
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to nautilus in Ubuntu.

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

[Desktop-packages] [Bug 2051383] Re: gnome-shell high CPU utilization when moving mouse cursor

20% when idle is 20% too much. So if we find out what that is then the
60% might become 40%.

Do you have any extra gnome-shell extensions active? Can you provide a
photo or screenshot of the desktop?


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

** Tags added: cursor performance

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

Title:
  gnome-shell high CPU utilization when moving mouse cursor

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I simply move my mouse cursor on an empty desktop, gnome-shell's
  CPU usage goes up from 20% (when idle) to 60%, which causes
  stuttering.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 23:31:26 2024
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-03-17 (2140 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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 2051444] Re: Ubuntu Desktop (Wayland) freeze on hybrid sytem Intel GPU + NVIDIA GPU, when using XWayland application

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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. 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.

3. If step 2 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.


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

Title:
  Ubuntu Desktop (Wayland) freeze on hybrid sytem Intel GPU + NVIDIA
  GPU, when using XWayland application

Status in Ubuntu:
  Incomplete

Bug description:
  I am experiencing freezes since relatively recently (maybe since driver or 
LTS update), when I am using Visual Studio Code. For example it just froze 
while I was typing in VSCode.
  This happens several times a week. 

  It may be related to this bug about slow downs when using Firefox,
  VSCode, etc.: https://bugs.launchpad.net/ubuntu/+bug/2050866

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-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..01.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  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 28 08:57:34 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:0798]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798]
  InstallationDate: Installed on 2022-05-01 (636 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 065C71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2022-05-17T00:40:19.420743
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.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.4-2ubuntu1.7~22.04.7
  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

[Desktop-packages] [Bug 2051445] Re: Xorg freeze

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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. 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.

3. If step 2 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.


** Summary changed:

- Xorg freeze
+ Freeze

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

Title:
  Freeze

Status in Ubuntu:
  Incomplete

Bug description:
  It happens randomly, but always after a few minutes and usually when a
  heavy computing process is in place.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-92.102~20.04.1-generic 5.15.131
  Uname: Linux 5.15.0-92-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..01.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  525.147.05  Wed Oct 25 
20:27:35 UTC 2023
   GCC version:  gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2)
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 28 10:06:54 2024
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 1.14.1, 5.15.0-91-generic, x86_64: installed
   evdi, 1.14.1, 5.15.0-92-generic, x86_64: installed
   nvidia, 525.147.05, 5.15.0-92-generic, x86_64: installed
   virtualbox, 6.1.48, 5.15.0-91-generic, x86_64: installed
   virtualbox, 6.1.48, 5.15.0-92-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Intel Corporation Device [8086:9a70] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0a69]
   NVIDIA Corporation Device [10de:24b6] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0a69]
  InstallationDate: Installed on 2023-05-09 (263 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Precision 7560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-92-generic 
root=UUID=0fd48384-218e-4590-b3f8-0b2b64eeed79 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2023
  dmi.bios.release: 1.27
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.27.0
  dmi.board.name: 0Y1R4H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.27.0:bd11/03/2023:br1.27:svnDellInc.:pnPrecision7560:pvr:rvnDellInc.:rn0Y1R4H:rvrA01:cvnDellInc.:ct10:cvr:sku0A69:
  dmi.product.family: Precision
  dmi.product.name: Precision 7560
  dmi.product.sku: 0A69
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  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:1.20.13-1ubuntu1~20.04.14
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1

[Desktop-packages] [Bug 2051450] Re: n/a

If there is any bug here then please describe what the problem is.


** Package changed: gnome-session (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 gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/2051450

Title:
  n/a

Status in Ubuntu:
  Incomplete

Bug description:
  n/a

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-session-bin 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 28 09:29:28 2024
  ExecutablePath: /usr/libexec/gnome-session-binary
  InstallationDate: Installed on 2023-12-27 (31 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.cron.daily.apport: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2051450/+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 2051315] Re: syslog filling up

Does it always follow with "The offending signal was notify on
GnomeWallClock"?

Can you attach a log showing the problem in detail?

See also similar bug 2042909, bug 1994125, bug 1908429 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2760

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

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

Title:
  syslog filling up

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  ─| lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  └─| apt-cache policy gnome-shell
  gnome-shell:
Installed: 42.9-0ubuntu2
Candidate: 42.9-0ubuntu2
Version table:
   *** 42.9-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.0-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  
  No gnome extensions installed.  very limited use of the desktop as most 
everything is manages thru ssh remotely.

  The error causes /var/log/syslog file to rapidly grow until the disk
  is full.

  The following line are repeated thousands and thousands of times in
  the syslog file.

  z440 gnome-shell: Attempting to call back into JSAPI during the sweeping 
phase of GC. This is most likely caused by not destroying a Clutter actor or 
Gtk+ widget with ::destroy signals connected, but can also be caused by using 
the destroy(), dispose(), or remove() vfuncs. Because it would crash the 
application, it has been blocked and the JS callback not invoked.
  z440 gnome-shell: The offending signal was notify on GnomeWallClock 
0x55c4f6b7d830.
  z440 nxpreload.sh: == Stack trace for context 0x55c4f52f64a0 ==

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2 [modified: 
usr/share/applications/org.gnome.Shell.desktop]
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jan 25 21:07:01 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-10-29 (89 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051315/+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 2051292] Re: [BCM43142] Bluetooth headset disconnects

It looks like there are Bluetooth packet problems at the kernel level
(if not hardware), so reassigning there.

** Summary changed:

- blutooth
+ [BCM43142] Bluetooth headset disconnects

** Package changed: bluez (Ubuntu) => linux-hwe-6.5 (Ubuntu)

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

Title:
  [BCM43142] Bluetooth headset disconnects

Status in linux-hwe-6.5 package in Ubuntu:
  New

Bug description:
  when I connect to my headset it's work couple of seconds or  minutes
  then disconnect  alone

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 25 22:15:26 2024
  InstallationDate: Installed on 2023-06-27 (211 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. Inspiron 3721
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=4d42ff5a-4c75-44c8-a459-6df10d860db0 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 044D20
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/29/2013:efr1.1:svnDellInc.:pnInspiron3721:pvrA11:rvnDellInc.:rn044D20:rvrA00:cvnDellInc.:ct8:cvrA11:skuInspiron3721:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 3721
  dmi.product.sku: Inspiron 3721
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 9C:2A:70:BE:D0:62  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:5227 acl:60 sco:0 events:440 errors:0
TX bytes:36549 acl:67 sco:0 commands:391 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2051292/+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 2051303] Re: T14s Gen4 Intel under 23.10 started freezing / locking up hard

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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. 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.

3. If step 2 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.

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

Title:
  T14s Gen4 Intel under 23.10 started freezing / locking up hard

Status in Ubuntu:
  Incomplete

Bug description:
  Everything's been great for a couple of months on this new machine

  Yesterday or the day before it started locking up hard, spontaneously, 
without high load.
  X11 freezes. Keyboard is unresponsive.  Sound still worked for a while once.

  Other context: 
  I accept OS updates when they arrive. Recently it's been telling me to do 
firmware updates, too.

  It's happening frequently enough that it's not safe for me to do anything 
much on the computer.
  I normally use this machine ~14 hours per day.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 25 19:40:13 2024
  DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
   virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b]
  InstallationDate: Installed on 2022-09-02 (510 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=ebdb1e4f-ba82-441f-bc71-f4507cc97f9d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to mantic on 2024-01-15 (11 days ago)
  dmi.bios.date: 10/30/2023
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3PET20W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21F6CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3PET20W(1.11):bd10/30/2023:br1.11:efr1.8:svnLENOVO:pn21F6CTO1WW:pvrThinkPadT14sGen4:rvnLENOVO:rn21F6CTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21F6_BU_Think_FM_ThinkPadT14sGen4:
  dmi.product.family: ThinkPad T14s Gen 4
  dmi.product.name: 21F6CTO1WW
  dmi.product.sku: LENOVO_MT_21F6_BU_Think_FM_ThinkPad T14s Gen 4
  dmi.product.version: ThinkPad T14s Gen 4
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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/2051303/+subscriptions


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

[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

This bug is still open for Firefox. Also the issue mentioned in comment
#146 isn't resolved yet. Unless comment #146 is wrong?

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

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux 
browsers.
  We will close this bug when both browsers will have Va-api decoding working 
OOTB without user interaction like in WinOS and MacOS

  August 2022 :

  * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with
  intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1
  )

     -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works
 -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need 
to fix this as most youtube is AV1 now.

  * In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497

  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  * In 2015 I opened this bug , no easy solution was available and
  battery drained when playing video in browser was crazy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

Yes I believe 22.04 is the only supported release that has/had this bug.
But we'd like to know what caused it there (and if it's still
happening).

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

Title:
  [i915] Blanked screen doesn't wake up after locking
  [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid
  argument]

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  Add to /etc/environment (in Ubuntu 22.04):

    MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

  or in Ubuntu 22.10 and later:

    MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and then reboot.

  [ Upstream bugs ]

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2268
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2749

  [ Original report ]

  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 1925683] Re: Cursor Tracking with Gnome Shell Magnifier on Wayland

Upstream bug gnome-shell#4112 was closed as a duplicate of #5509 which
was fixed in gnome-shell 43.0 via !2301

** Changed in: gnome-shell (Ubuntu)
   Status: Won't Fix => 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/1925683

Title:
  Cursor Tracking with Gnome Shell Magnifier on Wayland

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

Bug description:
  Affected version
  GNOME 3.36 - 3.40.
  Ubuntu 20.04, 20.10, 21.04 and Fedora 34 Beta.
  Wayland only.
  Bug summary
  When running GNOME shell with Wayland, the cursor and focus tracking 
functionality of the magnifier (a11y feature) do not correctly compute the 
cursor/focus location. The position is calculated from the top left of the 
window but the windows position is not included. This causes the magnifier to 
track the wrong location when the window is not maximiser or is on a second 
monitor.

  I suspect this is related to the way in which wayland is designed. But
  my experience in this area is minimal. When using X11 this feature
  works correctly.

  The wiki page states that under wayland the cursor and focus tracking
  work but this information is either out dated or was not tested
  correctly.

  Steps to reproduce
  From the Gnome desktop, open a terminal by pressing ctrl + alt + t or by 
opening the activities overlay and searching for "terminal".
  Press super + left arrow key to maximize the terminal window on the left side 
of the screen.
  Activity the magnifier by pressing super + alt + 8.
  Type text into the terminal window. The magnified view will move with the 
text cursor.
  Press super + right arrow key to maximize the terminal windows on the right 
side of the screen.
  Type text into the terminal. The magnified view will move but it will not 
show the text cursor. It will move when text is entered but will focus on the 
left side of the screen.
  What happened
  The magnified view does not follow the text/focus cursor correctly.

  What did you expect to happen
  The magnified view should follow the cursor and show the cursor as it does 
when the widnows is maximized. The correct behaviour can also be seen in Gnome 
shell running with X11.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 22 20:55:25 2021
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2021-04-22 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  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/1925683/+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 2044588] Re: Gnome crash after suspend mode , all openapps auto closed

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

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

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

Title:
  Gnome crash after suspend mode , all openapps auto closed

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  ubuntu-bug gnome-shell - all open apps crashed after suspend mode

  chrome, 
  fir fox, 
  terminal etc..

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 25 08:54:29 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-11-23 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2044588/+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 1926799] Re: Cursor is not rendered in the correct location when at maximum desktop zoom

The upstream bug seems to have been closed as mostly fixed. But bug
2022941 remains.

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

Title:
  Cursor is not rendered in the correct location when at maximum desktop
  zoom

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

Bug description:
  Affected version
  LSB Version: 
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
 
  Gnome Version: 3.38.4 
  Occurs in: Xorg and Wayland

  Bug summary

  1. zoom focus shifts - lets assume a window in the center of the
  screen and i am at 3x zoom and i try to point my mouse at something
  and try to click that. 90% of the time zoom focus shifts away from the
  mouse location to mostly top left corner of the screen.

  2. mouse pointing away from the object - Similarly when i reach above
  some zoom limit sets say 4x and now lets say i am in a browser trying
  to click a link i point at the link cursor changes to hand and when i
  try to click i couldnt. So i try to zoom out and i fid that the
  pointer was not exactly placed on the link. To sum up when zoomed in
  it seems like i am pointing at a link while the cursor is actually
  placed away from the link

  3. Compressing text - after reaching certain high zoom level as said
  4x or 5x the content on the screen becomes a bit compressed on the
  sides texts and images and everything on screen becomes elongated

  Steps to reproduce

  1. Turn on zoom from settings -> Accessibility
  2. Zoom in above 3.x
  3. Try clicking on some object inside a window
  4. Choose Follow mouse cursor or on screen part droopdown choose full screen.
  5. My current settings are Screen part: Full Screen, Magnifier cursor pushes 
content arround. However these issues persist with all the other options under 
magnifier position. Such as Follow mouse cursor or magnifier cursor pushes 
content arround or any such option provided.
  Screenshot_from_2021-05-03_14-37-09

  What happened

  1. Zoom focus shifts away from the cursor mostly towards top left of the 
window or the desktop.
  2.While zoomed in cursor seems to be placed above a link or an object but is 
actually placed awway either to the left or right of the object. Original 
position of the cursor reveals when zoomed out.
  3.Content on screen seems to be compressed from the sides as text and other 
objects appear elongated.

  I have also posted the same issue on the GNOME Community: 
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4228
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.04
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 3.38.4-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  Tags:  wayland-session hirsute
  Uname: Linux 5.11.0-16-generic 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/gnome-shell/+bug/1926799/+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 2013107] Re: GNOME does not display high contrast app icons

** Summary changed:

- [lunar] GNOME does not display high contrast app icons
+ GNOME does not display high contrast app icons

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

Title:
  GNOME does not display high contrast app icons

Status in Yaru Theme:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-themes-extra package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  Won't Fix
Status in gnome-shell source package in Mantic:
  Triaged
Status in gnome-shell source package in Noble:
  Triaged

Bug description:
  gnome-accessibility-themes (3.28-2ubuntu1) offers an incomplete set of
  high contrast icons, resulting in a very inconsistent look when the
  user enables Accessibility > Seeing > High Contrast from gnome-
  control-center.  A screenshot showing of the current sad state of
  affairs is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/2013107/+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 2028698] Re: desktop freezes when copying file to android phone

2024-01-28 Thread Michael Shulman

Files with a quotation mark (") in the filename also seem to trigger it.
I haven't exhaustively tested to determine if there are other characters
that also trigger it.

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

Title:
  desktop freezes when copying file to android phone

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  If you try to copy a file named a:b.m4b using the nautilus file
  manager to a USB-connected Android phone in MTP mode, the desktop will
  freeze until you disconnect the USB cable. Then you'll get an error
  from nautilus:

  "Fehler beim Kopieren von »a:b.m4b«.
  Beim Kopieren der Datei nach mtp://Google_Pixel_7_291...
  mer%Speicher/Audiobooks ist ein Fehler aufgetreten

  libmtp-Fehler: Could not send object."

  This happens when the file to be copied contains the colon symbol :

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gvfs-backends 1.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
  Uname: Linux 5.19.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 25 21:46:45 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-08-20 (704 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to jammy on 2022-09-10 (318 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2028698/+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 2051454] Re: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel

2024-01-28 Thread Anthony Harrington

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

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

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

Title:
  pipewire wireplumber can not detect the sound output device  when
  using an unofficial linux kernel

Status in apparmor package in Ubuntu:
  New
Status in pipewire package in Ubuntu:
  Confirmed
Status in wireplumber package in Ubuntu:
  New

Bug description:
  Ubuntu 24.04 noble

  I tested on Kernel-6.7.2, 6.7.1, 6.6.8, don't work.

  relating service status:
   
  gsd-media-keys[6441]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD 
(card)' failed

  pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: 
ERROR command:-1 (invalid) tag:418 error:25 (Input/output error)
  pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: 
ERROR command:-1 (invalid) tag:426 error:25 (Input/output error)
  pipewire-pulse[5298]: default: snap_get_audio_permissions: failed to get the 
AppArmor info.

  wireplumber[61568]:  si-standard-link: 
in/out items are not valid anymore
  wireplumber[61568]:  2 of 2 PipeWire links 
failed to activate

  It's worked on kernel linux-image-6.5.0-14-generic.

  I built the same version 1.0.1 from the
  https://gitlab.freedesktop.org/pipewire source code, The sound card
  can be detected normally and shown in the gnome setting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2051454/+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 2049988] Re: Latest kernel kills wifi.

2024-01-28 Thread Patrick M

Has anyone figured out a patch for this? there was an update today,
which I applied. Did not change anything with new kernel, but now old
version boots to airplane mode. I can get the wifi going on older kernel
still.

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

Title:
  Latest kernel kills wifi.

Status in network-manager package in Ubuntu:
  New

Bug description:
  New kernel 6.0.5-14 boot up system does not recognize built in wifi
  adapter. When I drop to last kernel install wifi works fine.

  HP Pavillion With intel core I7 chip.

  Output of lshow --C network:

   *-network 
 description: Wireless interface
 product: MT7921 802.11ax PCI Express Wireless Network Adapter
 vendor: MEDIATEK Corp.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:8c:9d:28:0e:cb
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2379 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-15 (432 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Laptop 15-eg2xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2023
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89F7
  dmi.board.vendor: HP
  dmi.board.version: 14.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.27
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg2xxx
  dmi.product.sku: 6W540UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+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 2034395] Re: Console is not accessible to the screen reader

2024-01-28 Thread Jeremy Bícha

** Tags removed: lunar
** Tags added: noble

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

Title:
  Console is not accessible to the screen reader

Status in GNOME Console:
  New
Status in gnome-console package in Ubuntu:
  Triaged
Status in gtk4 package in Ubuntu:
  Triaged

Bug description:
  Test Case
  =
  0. Install the gnome-console app
  1. Open the Settings app
  2. Switch to the Accessibility panel. Select Seeing and enable Screen Reader
  3. Open the Console app
  4. Type cd /
  5. Type ls

  The screen reader should read the list of files in /

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-console/+bug/2034395/+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 2050856] Re: Needs packaging: wayland-protocols 1.33

This bug was fixed in the package wayland-protocols - 1.33-1

---
wayland-protocols (1.33-1) unstable; urgency=medium

  * Team upload.
  * New upstream release. (Closes: #1061535, LP: #2050856)
  * Update standards version to 4.6.2, no changes needed.
  * Convert debian/copyright to DEP5 format.

 -- Dylan Aïssi   Sun, 28 Jan 2024 11:29:16 +0100

** Changed in: wayland-protocols (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Needs packaging: wayland-protocols 1.33

Status in wayland-protocols package in Ubuntu:
  Fix Released

Bug description:
  Please package: https://gitlab.freedesktop.org/wayland/wayland-
  protocols/-/releases/1.33

  It's now a prerequisite for building mutter 46.beta.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland-protocols/+bug/2050856/+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 1993867] Re: Telegram sometimes start endless use 100% CPU

2024-01-28 Thread Sebastian Ramacher

** Changed in: libvpx (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Telegram sometimes start endless use 100% CPU

Status in libvpx package in Ubuntu:
  Invalid
Status in telegram-desktop package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 22.04 all was fine.

  After upgrade to Ubuntu 22.10 Telegram was also updated. And
  sometimes, randomly, TG starts to use 100% CPU.

  Nothing on logs. But in starce i see a lot of these messages:
  [pid 33581] poll([{fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, 
events=POLLIN}, {fd=14, events=POLLIN}, {fd=19, events=POLLIN}, {fd=51, 
events=POLLIN}], 6, 8) = 0 (Timeout)

  
  PSA. Thousand messages.

  In normal state, when TG use 0-2% CPU, i see same messages. So, not
  related with bug.

  Please, ask me additional information, i can provide any logs.

  Today this bug occurs two times.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: telegram-desktop 4.1.1+ds-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 01:53:36 2022
  InstallationDate: Installed on 2018-05-02 (1633 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: telegram-desktop
  UpgradeStatus: Upgraded to kinetic on 2022-10-20 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1993867/+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 2021987] Re: The gnome session doesn't work when connected via XDMCP

2024-01-28 Thread Jeremy Bícha

** Changed in: gdm3 (Ubuntu)
   Status: New => Invalid

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

Title:
  The gnome session doesn't work when connected via XDMCP

Status in gdm3 package in Ubuntu:
  Invalid

Bug description:
  I used following setup:

  1. The login screen is handled by gdm3. 
  2. The wayland is disabled for gdm3 and xdmcp is enabled:

  [xdmcp]
  # Enable XDMCP. This is important for using VNC.
  Enable=true
  Port=177

  
  [daemon]
  # Uncomment the line below to force the login screen to use Xorg
  WaylandEnable=false

  3. I'm using tigernvc server, that connects via xdmcp to the xorg and
  exposes me login screen (I followed:
  
https://wiki.archlinux.org/title/TigerVNC#Running_Xvnc_with_XDMCP_for_on_demand_sessions)
  document for that.

  That setup worked for me very well. And since some time (unfortunately
  I'm not able to say when), instead of GDM login screen I get black
  screen. I'm not able to see login screen, and nothing happens.

  I tried to change gdm3 to lightdm3. This somehow improved situation.
  I'm able to see lightdm and login, but if I chose gnome session -
  screen gets all black after login. For testing, I installed openbox.
  Selection of openbox as session helped - I was able to use openbox
  normally, via tigernvc client.

  I tried to check logs (using journalctl --follow) when I starting new
  session. I haven't found anything really weird, but this is something
  that I see only for "failed" remote sessions:

  maj 31 16:31:25 pecet gsd-color[36841]: Przekroczono czas oczekiwania
  maj 31 16:31:25 pecet gsd-color[36841]: Przekroczono czas oczekiwania
  maj 31 16:31:25 pecet gsd-color[36841]: Przekroczono czas oczekiwania
  maj 31 16:31:25 pecet gsd-color[36841]: Przekroczono czas oczekiwania
  maj 31 16:31:25 pecet gsd-color[36841]: Przekroczono czas oczekiwania
  maj 31 16:31:25 pecet gsd-color[36841]: failed to obtain 
org.freedesktop.color-manager.create-profile auth

  (Przekroczono czas oczekiwania => The waiting time has been exceeded
  (timeout)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2021987/+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 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set

This bug was fixed in the package tracker-miners - 3.4.6-3

---
tracker-miners (3.4.6-3) unstable; urgency=medium

  * Allow getsockopt in seccomp filter (Closes: #1057617)

 -- Laurent Bigonville   Sun, 28 Jan 2024 12:04:38
+0100

** Changed in: tracker-miners (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gvfsd process does not have the KRB5CCNAME environment set

Status in tracker-miners package in Ubuntu:
  Fix Released
Status in tracker-miners source package in Bionic:
  Won't Fix
Status in tracker-miners source package in Focal:
  In Progress
Status in tracker-miners source package in Jammy:
  In Progress
Status in tracker-miners source package in Lunar:
  Won't Fix
Status in tracker-miners source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

  The KRB5CCNAME environment variable points to the Kerberos ticket of
  the current machine and this ticket is used for authentication in
  Active Directory  servers.

  This variable is set by pam_sss when the user authenticates and can be
  used by other processes, such as gio, to skip the credentials input
  when accessing network shares, for example.

  Some services rely on gvfs-daemon in order to properly function, such
  as tracker-extract-3.service and tracker-miner-fs-3.service, which
  means they will ask for the gvfs-daemon to be initialized when they
  are executed by systemd. This creates problems if one service that
  relies on gvfsd is started too early, as it would result in gvfsd
  being started too early as well.

  As of version 3.1 of tracker-miners, the install target of tracker-
  miners-fs-3.service was set to gnome-session.target:
  https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283

  However, the tracker-extract-3.service was not updated and its target
  is still default.target, which is too early for the service to start.

  Starting tracker-extract too early is also starting gvfsd too early,
  before the session environment gets fully updated. Which means that
  gvfsd does not have the KRB5CCNAME variable and can not do any
  operations with it.

  Tracker-extract is supposed to be a helper service managed by tracker-
  miner-fs-3.service. By using a [Install] section, we are actually
  telling systemd that it should manage this service as well, when it
  shouldn't.

  So, by removing the [Install] section and having tracker-miner-
  fs-3.service being tied to gnome-session.target, we fix the issue of
  gvfsd starting too early without the updated session environment.

  [ Test Plan ]

  In order to test this issue, it's required to have an Active Directory server 
running.
  1) Authenticate with an AD user (as this would set the KRB5CCNAME env);
  2) Check gvfsd environment. This can be done by running:
  cat /proc/$(pidof gvfsd)/environ | xargs --null -n1

     You will be able to see that it does not have the variable listed.
  3) Check that the information mentioned above about tracker-miner-fs-
     3.service is true.
  4) Disable tracker-extract-3.service (This is a bit tricky, since its
     target was default.target. The easiest way is to remove the symlink that
     systemd created when enabling the unit, located under
     /etc/systemd/user/default.target.wants/tracker-extract-3.service
  5) Reboot the machine;
  6) Repeat steps 1 and 2.
     This will show that gvfsd is now started with the proper environment.

  Is not enough to look at ptree and the pids of the processes, instead
  it's better to look into the session logs with:

     journalctl --user -b

  And check the order in which the services were started and when they
  were triggered.

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test

  After installing test packages of tracker-miners, KRB5CCNAME should be
  set in gvfs environment upon login to gnome.

  [ Where problems could occur ]

  The tracker project is a search engine that speeds up search
  operations in Gnome. The tracker-miners is the indexing daemon that
  populates the database with information, so changing its start does
  not affect the system behavior.

  This changes fix the startup of gvfs-daemon.service, which could delay
  services that relied on it running to be executed.

  [ Other info ]

  This was fixed upstream by the following commit:

  commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3
  From: Denison Barbosa 
  Date: Tue, 21 Mar 2023 15:04:28 +
  Subject: Removing [Install] section from tracker-extract-3.service
  Link: 
https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3

  Focal requires four additional patches to solve the issue, namely:

  commit 8065985c8d818414a36fe151862afdf42c5eda8a
  Author: Laurent Bigonville 
  Date:

[Desktop-packages] [Bug 1600367] Re: package libusb-1.0-0:i386 2:1.0.20-1 failed to install/upgrade: package libusb-1.0-0:i386 is already installed and configured

2024-01-28 Thread Tormod Volden

Reassigning from libusb-1.0 to dpkg. The libusb-1.0 package was just one
out of several packages that dpkg failed on:

dpkg: error processing package libgd3:i386 (--configure):
 package libgd3:i386 is already installed and configured
dpkg: error processing package libltdl7:i386 (--configure):
 package libltdl7:i386 is already installed and configured
dpkg: error processing package libusb-1.0-0:i386 (--configure):
 package libusb-1.0-0:i386 is already installed and configured

Seems like an issue in the 32->64 bit transition and probably not an
issue in supported versions of Ubuntu.

** Package changed: libusb-1.0 (Ubuntu) => dpkg (Ubuntu)

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

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

Title:
  package libusb-1.0-0:i386 2:1.0.20-1 failed to install/upgrade:
  package libusb-1.0-0:i386 is already installed and configured

Status in dpkg package in Ubuntu:
  Incomplete

Bug description:
  what?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libusb-1.0-0:i386 2:1.0.20-1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Jul  8 22:40:21 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
   libudev1 229-4ubuntu6
  DuplicateSignature:
   package:libusb-1.0-0:i386:2:1.0.20-1
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libgd3:i386 (--configure):
package libgd3:i386 is already installed and configured
  ErrorMessage: package libusb-1.0-0:i386 is already installed and configured
  InstallationDate: Installed on 2016-07-07 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libusb-1.0
  Title: package libusb-1.0-0:i386 2:1.0.20-1 failed to install/upgrade: 
package libusb-1.0-0:i386 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1600367/+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 1308113] Re: [ 14.04-devel ] Nautilus doing weird things when mounting USB storage

2024-01-28 Thread Tormod Volden

This is likely not related to libusb. If this is still an issue in a
supported version of Ubuntu, please provide more info. For instance, run
dbus-monitor while plugging in the USB drive and paste the output here.

** Package changed: libusb-1.0 (Ubuntu) => udisks2 (Ubuntu)

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

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

Title:
  [ 14.04-devel ] Nautilus doing weird things when mounting USB storage

Status in udisks2 package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd:
  Description:Ubuntu 14.04 LTS
  Release:14.04

  apt-cache policy nautilus
  nautilus:
Installed: 1:3.10.1-0ubuntu8
Candidate: 1:3.10.1-0ubuntu8
Version table:
   *** 1:3.10.1-0ubuntu8 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  This just started happening today (at least I noted this issue today):
  When I insert a pendrive Nautilus mounts it *twice*; if that wasn't that 
weird it does it with wicked names:

  ~> sudo umount /media/msx/Kubuntu\\04014.04\\040LTS\\040amd64
  [sudo] password for msx:
  umount: /media/msx/Kubuntu\04014.04\040LTS\040amd64: not found
  ~> cd /media/msx/
  ~> ls
  Kubuntu 14.04 LTS amd64/  Kubuntu 14.04 LTS amd641/
  ~>

  //

  As asked on Ubuntu QA list, here are the versions of my installed
  libusb packages:

  ~> apt-cache policy libusb-0.1-4:amd64
  libusb-0.1-4:
Installed: 2:0.1.12-23.3ubuntu1
Candidate: 2:0.1.12-23.3ubuntu1
Version table:
   *** 2:0.1.12-23.3ubuntu1 0

  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ~> apt-cache policy libusb-1.0-0:amd64
  libusb-1.0-0:
Installed: 2:1.0.17-1ubuntu2
Candidate: 2:1.0.17-1ubuntu2
Version table:
   *** 2:1.0.17-1ubuntu2 0

  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ~> apt-cache policy libusb-1.0-0:i386
  libusb-1.0-0:i386:
Installed: 2:1.0.17-1ubuntu2
Candidate: 2:1.0.17-1ubuntu2
Version table:
   *** 2:1.0.17-1ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
  100 /var/lib/dpkg/status

  ~> apt-cache policy libusbredirparser1:amd64
  libusbredirparser1:
Installed: 0.6-2ubuntu1
Candidate: 0.6-2ubuntu1
Version table:
   *** 0.6-2ubuntu1 0

  
  Please let me know if you need anything else.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1308113/+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 2051459] Re: duplicity missing from /usr/bin in current deb package.

2024-01-28 Thread Kenneth Loafman

See https://gitlab.com/duplicity/duplicity/-/issues/797

This is not a Ubuntu duplicity error, rather a GitLab duplicity error.
We moved.


** Bug watch added: gitlab.com/duplicity/duplicity/-/issues #797
   https://gitlab.com/duplicity/duplicity/-/issues/797

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

Title:
  duplicity missing from /usr/bin in current deb package.

Status in duplicity package in Ubuntu:
  New

Bug description:
  See:
  
https://discourse.mailinabox.email/t/the-latest-release-of-duplicity-is-missing-the-duplicity-binary/11439

  and

  https://discourse.mailinabox.email/t/backup-duplicity-error-file-not-
  found-backup-never-run/11438

  Getting error: 
  [Errno 2] No such file or directory: ‘/usr/bin/duplicity’

  .../duplicity_2.2.0-ppa202401271616~ubuntu22.04.1_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2051459/+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 2051459] Re: duplicity missing from /usr/bin in current deb package.

2024-01-28 Thread Richard Anthony Horan

** Tags added: jammy

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

Title:
  duplicity missing from /usr/bin in current deb package.

Status in duplicity package in Ubuntu:
  New

Bug description:
  See:
  
https://discourse.mailinabox.email/t/the-latest-release-of-duplicity-is-missing-the-duplicity-binary/11439

  and

  https://discourse.mailinabox.email/t/backup-duplicity-error-file-not-
  found-backup-never-run/11438

  Getting error: 
  [Errno 2] No such file or directory: ‘/usr/bin/duplicity’

  .../duplicity_2.2.0-ppa202401271616~ubuntu22.04.1_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2051459/+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 2051459] [NEW] duplicity missing from /usr/bin in current deb package.

2024-01-28 Thread Richard Anthony Horan

Public bug reported:

See:
https://discourse.mailinabox.email/t/the-latest-release-of-duplicity-is-missing-the-duplicity-binary/11439

and

https://discourse.mailinabox.email/t/backup-duplicity-error-file-not-
found-backup-never-run/11438

Getting error: 
[Errno 2] No such file or directory: ‘/usr/bin/duplicity’

.../duplicity_2.2.0-ppa202401271616~ubuntu22.04.1_amd64.deb

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

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

Title:
  duplicity missing from /usr/bin in current deb package.

Status in duplicity package in Ubuntu:
  New

Bug description:
  See:
  
https://discourse.mailinabox.email/t/the-latest-release-of-duplicity-is-missing-the-duplicity-binary/11439

  and

  https://discourse.mailinabox.email/t/backup-duplicity-error-file-not-
  found-backup-never-run/11438

  Getting error: 
  [Errno 2] No such file or directory: ‘/usr/bin/duplicity’

  .../duplicity_2.2.0-ppa202401271616~ubuntu22.04.1_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2051459/+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 2051454] [NEW] pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel

2024-01-28 Thread Frank Tian

Public bug reported:

Ubuntu 24.04 noble

I tested on Kernel-6.7.2, 6.7.1, 6.6.8, don't work.

relating service status:
 
gsd-media-keys[6441]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD 
(card)' failed

pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR 
command:-1 (invalid) tag:418 error:25 (Input/output error)
pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR 
command:-1 (invalid) tag:426 error:25 (Input/output error)
pipewire-pulse[5298]: default: snap_get_audio_permissions: failed to get the 
AppArmor info.

wireplumber[61568]:  si-standard-link: in/out 
items are not valid anymore
wireplumber[61568]:  2 of 2 PipeWire links 
failed to activate

It's worked on kernel linux-image-6.5.0-14-generic.

I built the same version 1.0.1 from the
https://gitlab.freedesktop.org/pipewire source code, The sound card can
be detected normally and shown in the gnome setting.

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

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

Title:
  pipewire wireplumber can not detect the sound output device  when
  using an unofficial linux kernel

Status in pipewire package in Ubuntu:
  New

Bug description:
  Ubuntu 24.04 noble

  I tested on Kernel-6.7.2, 6.7.1, 6.6.8, don't work.

  relating service status:
   
  gsd-media-keys[6441]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD 
(card)' failed

  pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: 
ERROR command:-1 (invalid) tag:418 error:25 (Input/output error)
  pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: 
ERROR command:-1 (invalid) tag:426 error:25 (Input/output error)
  pipewire-pulse[5298]: default: snap_get_audio_permissions: failed to get the 
AppArmor info.

  wireplumber[61568]:  si-standard-link: 
in/out items are not valid anymore
  wireplumber[61568]:  2 of 2 PipeWire links 
failed to activate

  It's worked on kernel linux-image-6.5.0-14-generic.

  I built the same version 1.0.1 from the
  https://gitlab.freedesktop.org/pipewire source code, The sound card
  can be detected normally and shown in the gnome setting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2051454/+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 2050856] Re: Needs packaging: wayland-protocols 1.33

2024-01-28 Thread Jeremy Bícha

** Changed in: wayland-protocols (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Needs packaging: wayland-protocols 1.33

Status in wayland-protocols package in Ubuntu:
  Fix Committed

Bug description:
  Please package: https://gitlab.freedesktop.org/wayland/wayland-
  protocols/-/releases/1.33

  It's now a prerequisite for building mutter 46.beta.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland-protocols/+bug/2050856/+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 186771] Re: use more GTK stock icons.

2024-01-28 Thread Bug Watch Updater

** Changed in: firefox
   Status: Confirmed => Won't Fix

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

Title:
  use more GTK stock icons.

Status in Mozilla Firefox:
  Won't Fix
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: firefox-3.0

  I think Firefox would look better and more integrated with gnome if
  some of its icons were replaced with gnome defaults:

  -the search icon at the right of the search bar could be replaced with
  /usr/share/icons/gnome/16x16/actions/find.png

  -the RSS icon in the URL bar could be replaced with the one in
  Epiphany, which follows the Tango guidelines. It can be found in
  /usr/share/epiphany-browser/icons/hicolor/16x16/status

  -the lockpad icon when you visit a secure webpage could be replaced
  with /usr/share/icons/gnome/16x16/status/security-medium.png or
  security-high.png.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/186771/+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 2040453] Re: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”]

I can confirm this patch solved my issues also. I have some other issue
that ends up in a mutter restart on suspend resume and this bug made
supending compleatly unusable since I lost the desktop.


To get around the build issue with "apt-src install mutter" I changed the rules 
file in the debian directory to not run the test on my arch

from
ifeq (,$(filter mips mips64el mipsel riscv64 s390x alpha hppa powerpc sparc64 
x32,$(DEB_HOST_ARCH)))

to
ifeq (,$(filter mips mips64el mipsel riscv64 s390x alpha hppa powerpc sparc64 
x32 amd64,$(DEB_HOST_ARCH)))

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

Title:
  Gnome 45 crash on restart in X11 session [Window manager error:
  Another compositing manager is already running on screen 0 on display
  “:0”]

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell package in Arch Linux:
  New

Bug description:
  Hello,

  Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer
  possible to restart gnome-shell without crashing the session. The only
  way not to crash it is to close all applications before restarting
  gnome-shell. I have verified this too.

  This has already been reported upstream: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050
  a tentative patch for mutter proposed: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598

  Please consider reviewing/testing this patch and pushing an update so
  people can restart gnome-shell session without crashing it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2040453/+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 2051188] Re: Firefox 122 update breaks webextensions permission

2024-01-28 Thread Bug Watch Updater

** Changed in: firefox
   Status: Confirmed => 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/2051188

Title:
  Firefox 122 update breaks webextensions permission

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

Bug description:
  We build webextensions for Firefox.

  Since the latest update to Firefox 122, the native webextension bridge
  stopped working.

  ```
  $ flatpak permission-show snap.firefox
  Table ObjectApp  
Permissions   Data
  desktop-used-apps application/vnd.debian.binary-package snap.firefox 
gnome-software-local-file,1,3 0x00
  webextensions net.downloadhelper.coapp  snap.firefox yes  
 0x00
  ```

  This used to work and be enough, but not anymore.

  In the logs I see:

  
  ```
  Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”
  Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop 
firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”: 'glib warning', file 
/build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187
  ```

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

2024-01-28 Thread Amin Bandali

I've posted a quick post-mortem write up on the Ubuntu Discourse for
folks who may be interested in reading what exactly happened:

[Firefox 122 snap temporary native messaging breakage for Ubuntu 22.04
users (fixed since)](https://discourse.ubuntu.com/t/firefox-122-snap-
temporary-native-messaging-breakage-for-ubuntu-22-04-users-fixed-
since/41940)

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

Title:
  Firefox 122 update breaks webextensions permission

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

Bug description:
  We build webextensions for Firefox.

  Since the latest update to Firefox 122, the native webextension bridge
  stopped working.

  ```
  $ flatpak permission-show snap.firefox
  Table ObjectApp  
Permissions   Data
  desktop-used-apps application/vnd.debian.binary-package snap.firefox 
gnome-software-local-file,1,3 0x00
  webextensions net.downloadhelper.coapp  snap.firefox yes  
 0x00
  ```

  This used to work and be enough, but not anymore.

  In the logs I see:

  
  ```
  Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”
  Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop 
firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”: 'glib warning', file 
/build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/2051188/+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 1959027] Re: [snap] Various UI and theming issues when running in Plasma Wayland session

2024-01-28 Thread Dan

This has not fixed the bug. GTK snap and flatpak apps still refuse to
use the correct theme and font settings in a plasma Wayland session with
xdg-desktop-portal-gtk installed. Tested on Kubuntu 23.10.

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

Title:
[snap] Various UI and theming issues when running in Plasma Wayland
session

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

Bug description:
Hello,

after installing the current live image of Kubuntu Jammy, I tested the
preinstalled Firefox snap on the Plasma Wayland session (which I use
by default), and discovered multiple UI and theming issues:

1. I had switched my global theme to Breeze Dark. Nevertheless Firefox
used a light theme when I launched it for the first time.
Interestingly, at further runs Firefox properly came up with a dark
theme. But I had restarted my session in between and also had removed
and reinstalled the Firefox snap, so it's possible that one of these
actions triggered Firefox to finally use a dark theme.

2. The font size in the UI is too big (compare with other KDE apps on
screenshots).

3. It apparently doesn't use Breeze (light or dark) as the UI theme,
but something else (Adwaita I guess).

4. The mouse cursor uses the wrong theme and is too big (it changes
visible if move the cursor in and out of the Firefox window).

5. If I click e.g. on "File -> Open file...", the file dialog is not
the one from KDE but the one from GTK/Gnome. And the UI text is
displayed in a rather jagged/distorted way (see screenshot).

The issues described above do _not_ appear:
* If I run Firefox as snap in Plasma X11 session.
* If I run Firefox as deb (both Plasma Wayland and X11 session work fine).

Kind regards, Jan

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 96.0.2+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
Uname: Linux 5.15.0-17-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
BuildID: 20220119190439
CasperMD5CheckResult: pass
Channel: Unavailable
CurrentDesktop: KDE
Date: Tue Jan 25 17:19:38 2022
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:365
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2022-01-25 (0 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
(20220125.1)
IpRoute:
default via 192.168.178.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44
metric 100
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:365
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 (Default) - LastVersion=None/None (Out of date)
Profile0 - LastVersion=96.0.2/20220119190439
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F14
dmi.board.name: P35-DS3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
dmi.product.name: P35-DS3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

2024-01-28 Thread Donal Meehan

Marking this bug as resolved

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

Title:
  Firefox 122 update breaks webextensions permission

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

Bug description:
  We build webextensions for Firefox.

  Since the latest update to Firefox 122, the native webextension bridge
  stopped working.

  ```
  $ flatpak permission-show snap.firefox
  Table ObjectApp  
Permissions   Data
  desktop-used-apps application/vnd.debian.binary-package snap.firefox 
gnome-software-local-file,1,3 0x00
  webextensions net.downloadhelper.coapp  snap.firefox yes  
 0x00
  ```

  This used to work and be enough, but not anymore.

  In the logs I see:

  
  ```
  Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”
  Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop 
firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”: 'glib warning', file 
/build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187
  ```

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

2024-01-28 Thread Snegritas

Created attachment 9376642
Screenshot from 2024-01-26 14-52-14.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/2051188

Title:
  Firefox 122 update breaks webextensions permission

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

Bug description:
  We build webextensions for Firefox.

  Since the latest update to Firefox 122, the native webextension bridge
  stopped working.

  ```
  $ flatpak permission-show snap.firefox
  Table ObjectApp  
Permissions   Data
  desktop-used-apps application/vnd.debian.binary-package snap.firefox 
gnome-software-local-file,1,3 0x00
  webextensions net.downloadhelper.coapp  snap.firefox yes  
 0x00
  ```

  This used to work and be enough, but not anymore.

  In the logs I see:

  
  ```
  Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”
  Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop 
firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”: 'glib warning', file 
/build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187
  ```

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

2024-01-28 Thread Snegritas

Hello! 
I have managed to reproduce the issue with firefox 122.0-2 on Ubuntu 22.04. I 
can confirm that the issue is fixed with firefox 122.0-2.1.
I would like to mention that there is still an error in the console when 
intalling the addon mentioned in the description, see attached screen shot 
Updating the flags and the status of this bug.

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

Title:
  Firefox 122 update breaks webextensions permission

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

Bug description:
  We build webextensions for Firefox.

  Since the latest update to Firefox 122, the native webextension bridge
  stopped working.

  ```
  $ flatpak permission-show snap.firefox
  Table ObjectApp  
Permissions   Data
  desktop-used-apps application/vnd.debian.binary-package snap.firefox 
gnome-software-local-file,1,3 0x00
  webextensions net.downloadhelper.coapp  snap.firefox yes  
 0x00
  ```

  This used to work and be enough, but not anymore.

  In the logs I see:

  
  ```
  Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”
  Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop 
firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”: 'glib warning', file 
/build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/2051188/+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 2037182] Re: Restarting GNOME doesn't work

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

** This bug has been marked a duplicate of bug 2040453
   Gnome 45 crash on restart in X11 session [Window manager error: Another 
compositing manager is already running on screen 0 on display “:0”]

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

Title:
  Restarting GNOME doesn't work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Triggering a restart through Alt-F2 then "r" causes GNOME to hang for
  a few seconds before going to the "something went wrong" screen
  prompting the user to log out. But once you log out and back in, the
  system still has issues, with application now taking far longer to
  launch. This is ultimately resolved by a full system restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 23 14:56:37 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-02 (53 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-09-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+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 2051450] [NEW] n/a

2024-01-28 Thread Joel Vázquez Ortiz

Public bug reported:

n/a

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-session-bin 42.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 28 09:29:28 2024
ExecutablePath: /usr/libexec/gnome-session-binary
InstallationDate: Installed on 2023-12-27 (31 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.cron.daily.apport: [deleted]

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


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

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

Title:
  n/a

Status in gnome-session package in Ubuntu:
  New

Bug description:
  n/a

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-session-bin 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 28 09:29:28 2024
  ExecutablePath: /usr/libexec/gnome-session-binary
  InstallationDate: Installed on 2023-12-27 (31 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.cron.daily.apport: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2051450/+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 2037182] Re: Restarting GNOME doesn't work

So I have this every time. alt f2 r gives me the "something went wrong"

If I do this without any opened windows on the desktop I do not get the
error but just one opened window is enough to get it.

I do not get a crash in /var/crash


** Attachment added: "altf2r_no_windows.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+attachment/5742878/+files/altf2r_no_windows.txt

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

Title:
  Restarting GNOME doesn't work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Triggering a restart through Alt-F2 then "r" causes GNOME to hang for
  a few seconds before going to the "something went wrong" screen
  prompting the user to log out. But once you log out and back in, the
  system still has issues, with application now taking far longer to
  launch. This is ultimately resolved by a full system restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 23 14:56:37 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-02 (53 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-09-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+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 2037182] Re: Restarting GNOME doesn't work

this is what happens if I have a window when doing the restart

** Attachment added: "altf2r_windows.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+attachment/5742879/+files/altf2r_windows.txt

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

Title:
  Restarting GNOME doesn't work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Triggering a restart through Alt-F2 then "r" causes GNOME to hang for
  a few seconds before going to the "something went wrong" screen
  prompting the user to log out. But once you log out and back in, the
  system still has issues, with application now taking far longer to
  launch. This is ultimately resolved by a full system restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 23 14:56:37 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-02 (53 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-09-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+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 1573508] Re: SRU Request: nvidia-: nvidia- kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

2024-01-28 Thread galbadrakh

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
 Assignee: (unassigned) => galbadrakh (dagvadorj)

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

Title:
  SRU Request: nvidia-*: nvidia-* kernel module failed to build [error:
  too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.

  [Test Case]
  1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low.

  ___

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+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 2036473] Re: [82Y7, Realtek ALC287, Speaker, Internal] volume either 100% or off