date:20211025

Thanks for the bug report.

I think this looks like faulty RAM so the first thing you should do is
run memory tests for a few hours by booting one of these tools:

  http://memtest.org/
  https://www.memtest86.com/

If no memory errors are found then the next steps are outlined in:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment


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

** Tags added: focal

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

Title:
  segfault with gnome-shell & gdm-session-worker

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Using Ubuntu 20.04.3 LTS with 5.11.0-38-generic #42~20.04.1-Ubuntu,
  gnome-shell/focal-updates,now 3.36.9-0ubuntu0.20.04.2 amd64 
[installed,automatic]
  gnome-shell/focal-security 3.36.4-1ubuntu1~20.04.2 amd64
  gnome-shell/focal 3.36.1-5ubuntu1 amd64
  gnome-session/focal,focal 3.36.0-2ubuntu1 all

  Oct 22 19:41:09 ourserver kernel: [15260.574496] show_signal_msg: 29 
callbacks suppressed
  Oct 22 19:41:09 ourserver kernel: [15260.574503] gnome-shell[1475]: segfault 
at 11390db8 ip 7f3fd36f716c sp 7ffe50e6d788 error 4 in 
libmozjs-68.so.68.6.0[7f3fd3234000+843000]
  Oct 22 19:41:09 ourserver kernel: [15260.574525] Code: 50 10 85 d2 75 d0 0f 
b6 40 14 83 e8 01 3c 01 41 0f 96 c0 44 89 c0 c3 0f 1f 80 00 00 00 00 48 89 f0 
45 31 c0 48 25 00 00 f0 ff <48> 8b 90 f8 ff 0f 00 48 39 17 74 08 44 89 c0 c3 0f 
1f 40 00 48 85
  Oct 22 19:41:09 ourserver kernel: [15260.619146] apport[2636]: segfault at 3 
ip 0003 sp 7fffe172cb48 error 14 in python3.8[40+23000]
  Oct 22 19:41:09 ourserver kernel: [15260.619165] Code: Unable to access 
opcode bytes at RIP 0xffd9.
  Oct 22 19:41:09 ourserver kernel: [15260.619186] Process 2636(apport) has 
RLIMIT_CORE set to 1
  Oct 22 19:41:09 ourserver kernel: [15260.619189] Aborting core
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e761320' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: message repeated 3 times: [ 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e761320' of type 'GCancellable']
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e7d7860' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e80f8e0' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e811b20' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e80e0a0' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x7fd938006460' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e82c1e0' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e7fc320' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x7fd934004a60' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e80ff60' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e8317a0' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e8145e0' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x7fd934005020' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e82c420' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e80fea0' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e7c05e0' of type 'GCancellable'
  Oct

[Desktop-packages] [Bug 1948710] Re: Suspend issues with nvidia proprietary driver

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470
(Ubuntu)

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

Title:
  Suspend issues with nvidia proprietary driver

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  When I suspend my system, after the screen goes black, the desktop and
  the suspend login screen are briefly shown in succession, and only
  then the screen, power LED and fan turn off like normally.

  The timing of the brief "fake resume" is not consistent: sometimes it
  only shows the login screen, sometimes it stops the suspension until
  briefly after I login.

  When resuming after this has happened, the login screen appears as
  normal, but I have to wait for any internet connection to restart, and
  my second screen remains blacks despite it being detected and the
  display mode remaining on "join displays", until I change the display
  mode back and forth to fix it.

  These issues occur after switching to the nvidia-driver-470 driver on
  a fresh install of Ubuntu 21.10, but I have been experiencing at least
  the "fake-resume" since at least 20.10, without being able to find any
  solution.

  These issues persist (with slightly altered timing) if I switch to an
  older proprietary driver (I tried nvidia-driver-390 and nvidia-
  driver-460), but do not appear while using the nouveau driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-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  470.74  Mon Sep 13 23:09:15 
UTC 2021
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2)
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 21:09:03 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 470.74, 5.13.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:177d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d]
  InstallationDate: Installed on 2021-10-21 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: ASUSTeK COMPUTER INC. N551JK
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=64128e5f-ba67-49c1-aa02-c19feef6be26 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JK.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551JK.203:bd10/06/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnN551JK:pvr1.0:skuASUS-NotebookSKU:rvnASUSTeKCOMPUTERINC.:rnN551JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N551JK
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  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
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To

[Desktop-packages] [Bug 1948647] Re: Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange circle persists

Thanks. I still can't find the reason you're experiencing this problem.
Can you please check for crashes using these instructions?

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

If no evidence of crashes can be found then you should next report the
bug upstream at:

  https://gitlab.gnome.org/GNOME/gnome-shell/issues

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

Title:
  Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange
  circle persists

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Running 21.10 and Gnome 40.4 the screen recording no longer works with
  the Ctrl+Alt+Shift+R keystroke. A .webm file does appear in the Videos
  folder but it is empty. The orange circle does appear in the upper
  corner, but it will not go away.

  Further Ctrl+Alt+Shift+R strokes do not make a new .webm file or
  remove the orange circle.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  Uname: Linux 5.15.0-rc4-soffixes x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 11:11:13 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-12 (12 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948647/+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 1948704] [NEW] segfault with gnome-shell & gdm-session-worker

2021-10-25 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Using Ubuntu 20.04.3 LTS with 5.11.0-38-generic #42~20.04.1-Ubuntu,
gnome-shell/focal-updates,now 3.36.9-0ubuntu0.20.04.2 amd64 
[installed,automatic]
gnome-shell/focal-security 3.36.4-1ubuntu1~20.04.2 amd64
gnome-shell/focal 3.36.1-5ubuntu1 amd64
gnome-session/focal,focal 3.36.0-2ubuntu1 all

Oct 22 19:41:09 ourserver kernel: [15260.574496] show_signal_msg: 29 callbacks 
suppressed
Oct 22 19:41:09 ourserver kernel: [15260.574503] gnome-shell[1475]: segfault at 
11390db8 ip 7f3fd36f716c sp 7ffe50e6d788 error 4 in 
libmozjs-68.so.68.6.0[7f3fd3234000+843000]
Oct 22 19:41:09 ourserver kernel: [15260.574525] Code: 50 10 85 d2 75 d0 0f b6 
40 14 83 e8 01 3c 01 41 0f 96 c0 44 89 c0 c3 0f 1f 80 00 00 00 00 48 89 f0 45 
31 c0 48 25 00 00 f0 ff <48> 8b 90 f8 ff 0f 00 48 39 17 74 08 44 89 c0 c3 0f 1f 
40 00 48 85
Oct 22 19:41:09 ourserver kernel: [15260.619146] apport[2636]: segfault at 3 ip 
0003 sp 7fffe172cb48 error 14 in python3.8[40+23000]
Oct 22 19:41:09 ourserver kernel: [15260.619165] Code: Unable to access opcode 
bytes at RIP 0xffd9.
Oct 22 19:41:09 ourserver kernel: [15260.619186] Process 2636(apport) has 
RLIMIT_CORE set to 1
Oct 22 19:41:09 ourserver kernel: [15260.619189] Aborting core
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e761320' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: message repeated 3 times: [ 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e761320' of type 'GCancellable']
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e7d7860' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e80f8e0' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e811b20' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e80e0a0' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x7fd938006460' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e82c1e0' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e7fc320' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x7fd934004a60' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e80ff60' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e8317a0' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e8145e0' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x7fd934005020' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e82c420' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e80fea0' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e7c05e0' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e7dfc20' of type 'GCancellable'
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e761320' of type 'GCancellable'
Oct 22 19:41:09 ourserver gnome-session[1446]: gnome-session-binary[1446]: 
WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Oct 22 19:41:09 ourserver gnome-session-binary[1446]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 11
Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e761320' of type 'GCancellable'
Oct 22 19:41:09 ourserver kernel: [15260.661119] general protection fault, 
probably for

[Desktop-packages] [Bug 1945203] Re: Wayland: Useage of touchscreen on dock freezes the dock

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

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

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

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

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


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

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

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

Title:
  Wayland: Useage of touchscreen on dock freezes the dock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  General information:

  Ubuntu 21.04
  Device: Dell XPS13 2-in-1

  When using the touchscreen to start or switch between apps in the
  dock, the dock freezes after 1-5 events. A tooltip is shown
  permanently and the dock is no longer responsive and can't be used for
  app switching anymore. The top menu bar with wifi and bt settings etc.
  is also frozen.

  This problem only occurs with Wayland, not with classic X. And only
  touch events trigger the freeze. Other input devices such as the
  touchpad, the digitizer or an external mouse do not trigger this
  problem.

  Workaround:
  Alt+Tab is not affected and can still be used for app switching, but it sucks 
if the device is in tablet mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xwayland 2:21.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-36.40-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 27 15:05:59 2021
  EcryptfsUse: Yes
  InstallationDate: Installed on 2021-09-15 (12 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xwayland
  UpgradeStatus: Upgraded to hirsute on 2021-09-25 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945203/+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 1948355] Re: Firefox settings font size dropdown flashes, hard to select

2021-10-25 Thread Janne Moren

Also see bug #1948356.

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

Title:
  Firefox settings font size dropdown flashes, hard to select

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Go to settings, then font, and try to change the font size. The
  dropdown flashes and disappears, and is very difficult to select.
  Happens both on the main screen and the "advanced.." screen for all
  size selectors.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948355/+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 1948355] Re: Firefox settings font size dropdown flashes, hard to select

2021-10-25 Thread Janne Moren

$ apport-collect 1948355
The authorization page:
 
(https://launchpad.net/+authorize-token?oauth_token=DlTgxHSNx0mzplR9KKS8_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
Package firefox not installed and no hook available, ignoring

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

Title:
  Firefox settings font size dropdown flashes, hard to select

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Go to settings, then font, and try to change the font size. The
  dropdown flashes and disappears, and is very difficult to select.
  Happens both on the main screen and the "advanced.." screen for all
  size selectors.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948355/+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 1948356] Re: Firefox 93.0 tabs are not remembered across sessions

2021-10-25 Thread Janne Moren

Attached the info.

As an aside, I have a second system, installed at the same time and in
the same way (Ubuntu 21.04, then upgraded to 21.10). The second system
(my desktop at home) shows neither of these issues (this one and bug
#1948355). The bookmarks and settings are all synced from the same
Firefox account, and they're synced with each other.

The hardware differences are that this machine is an intel laptop with
integrated graphics, the other system is an AMD desktop with an AMD GPU.
For software, I may not have all the same extensions enabled. I will get
this data from home and compare tonight or tomorrow.

** Attachment added: "about-support.txt"

https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948356/+attachment/5536089/+files/about-support.txt

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

Title:
Firefox 93.0 tabs are not remembered across sessions

Status in firefox package in Ubuntu:
Incomplete

Bug description:
If I close Firefox with a bunch of tabs, then open again, the tabs are
gone. I get a list of empty tabs without any actual link to them. Only
the last visited site is actually filled with the URL. Up until now
Firefox always remembers and restores the list of tabs.

I am using Tree Style Tab, but I believe it uses the regular tab list
for itself.

Ubuntu 21.10
firefox 93.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948356/+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 1948723] [NEW] /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning: 'str' object is not callable; perhaps you missed a comma? raise Exceptions.LayoutFi

2021-10-25 Thread Norbert

Public bug reported:

Steps to reproduce:
1. Install or reinstall Onboard with

sudo apt-get install --reinstall onboard onboard-common onboard-data

Expected results:
* no warnings

Actual results:
* the following warning is shown -

```
$ sudo apt-get install --reinstall onboard onboard-common onboard-data 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 3 reinstalled, 0 to remove and 0 not upgraded.
Need to get 5 217 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu jammy/universe amd64 onboard-common all 
1.4.1-5build4 [595 kB]
Get:2 http://archive.ubuntu.com/ubuntu jammy/universe amd64 onboard amd64 
1.4.1-5build4 [380 kB]
Get:3 http://archive.ubuntu.com/ubuntu jammy/universe amd64 onboard-data all 
1.4.1-5build4 [4 242 kB]
Fetched 5 217 kB in 2s (2 938 kB/s)   
(Reading database ... 243599 files and directories currently installed.)
Preparing to unpack .../onboard-common_1.4.1-5build4_all.deb ...
Unpacking onboard-common (1.4.1-5build4) over (1.4.1-5build4) ...
Preparing to unpack .../onboard_1.4.1-5build4_amd64.deb ...
Unpacking onboard (1.4.1-5build4) over (1.4.1-5build4) ...
Preparing to unpack .../onboard-data_1.4.1-5build4_all.deb ...
Unpacking onboard-data (1.4.1-5build4) over (1.4.1-5build4) ...
Setting up onboard-common (1.4.1-5build4) ...
Setting up onboard (1.4.1-5build4) ...
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning: 
'str' object is not callable; perhaps you missed a comma?
  raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \
Processing triggers for mailcap (3.70ubuntu1) ...
Processing triggers for bamfdaemon (0.5.5+21.10.20210710-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for desktop-file-utils (0.26-1ubuntu2) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu2) ...
Processing triggers for libglib2.0-0:amd64 (2.68.4-1ubuntu1) ...
Processing triggers for man-db (2.9.4-2build1) ...
Setting up onboard-data (1.4.1-5build4) ...

```

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: onboard 1.4.1-5build4
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Tue Oct 26 01:08:47 2021
InstallationDate: Installed on 2021-10-24 (1 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211024)
SourcePackage: onboard
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: onboard
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug focal hirsute impish jammy

** Also affects: onboard
   Importance: Undecided
   Status: New

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

Title:
  /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447:
  SyntaxWarning: 'str' object is not callable; perhaps you missed a
  comma?   raise Exceptions.LayoutFileError("Unrecognized modifier %s
  in" \

Status in Onboard:
  New
Status in onboard package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install or reinstall Onboard with

  sudo apt-get install --reinstall onboard onboard-common onboard-
  data

  Expected results:
  * no warnings

  Actual results:
  * the following warning is shown -

  ```
  $ sudo apt-get install --reinstall onboard onboard-common onboard-data 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  0 upgraded, 0 newly installed, 3 reinstalled, 0 to remove and 0 not upgraded.
  Need to get 5 217 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Get:1 http://archive.ubuntu.com/ubuntu jammy/universe amd64 onboard-common 
all 1.4.1-5build4 [595 kB]
  Get:2 http://archive.ubuntu.com/ubuntu jammy/universe amd64 onboard amd64 
1.4.1-5build4 [380 kB]
  Get:3 http://archive.ubuntu.com/ubuntu jammy/universe amd64 onboard-data all 
1.4.1-5build4 [4 242 kB]
  Fetched 5 217 kB in 2s (2 938 kB/s)   
  (Reading database ... 243599 files and directories currently installed.)
  Preparing to unpack .../onboard-common_1.4.1-5build4_all.deb ...
  Unpacking onboard-common (1.4.1-5build4) over (1.4.1-5build4) ...
  Preparing to unpack .../onboard_1.4.1-5build4_amd64.deb ...
  Unpacking onboard (1.4.1-5build4) over (1.4.1-5build4) ...
  Preparing to unpack .../onboard-data_1.4.1-5build4_all.deb ...
  Unpacking onboard-data (1.4.1-5build4) over (1.4.1-5build4) ...
  Setting up onboard-common (1.4.1-5build4) ...
  Setting up onboard (1.4.1-5build4) ...

[Desktop-packages] [Bug 1874938] Re: SyntaxWarning at install

2021-10-25 Thread Norbert

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

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

Title:
  SyntaxWarning at install

Status in Onboard:
  New
Status in onboard package in Ubuntu:
  New

Bug description:
  Installing in a fresh-up-to-date Focal Fossa gives:

  Configurando onboard (1.4.1-2ubuntu7) ...
  /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning: 
'str' object is not callable; perhaps you missed a comma?
raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \

To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1874938/+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 1948566] Re: Sync java-atk-wrapper 0.38.0-5 (main) from Debian unstable (main)

2021-10-25 Thread Mathew Hodson

** Changed in: java-atk-wrapper (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync java-atk-wrapper 0.38.0-5 (main) from Debian unstable (main)

Status in java-atk-wrapper package in Ubuntu:
  New

Bug description:
  Please sync java-atk-wrapper 0.38.0-5 (main) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* No-change rebuild to build packages with zstd compression.
* No-change rebuild to build packages with zstd compression.
* Import an unreleased debian patch to better address the s390x FTBFS
  - debian/patches/werror
* Import an unreleased debian patch to better address the s390x FTBFS
  - debian/patches/werror

  Werror patch has been included in Debian package.

  Changelog entries since current jammy version 0.38.0-2ubuntu3:

  java-atk-wrapper (0.38.0-5) unstable; urgency=medium

[ Debian Janitor ]
* Bump debhelper from old 12 to 13.
* Update standards version to 4.5.1, no changes needed.
* Remove constraints unnecessary since buster:
  + Build-Depends: Drop versioned constraint on java-common.

[ Samuel Thibault ]
* libatk-wrapper-java.lintian-overrides: Drop lintian warning for jar name.

   -- Samuel Thibault   Sat, 18 Sep 2021 18:34:13
  +0200

  java-atk-wrapper (0.38.0-4) unstable; urgency=medium

* patches/dbus: Also detect at-spi through dbus.

   -- Samuel Thibault   Thu, 26 Aug 2021 02:50:17
  +0200

  java-atk-wrapper (0.38.0-3) unstable; urgency=medium

* patches/werror: Only enable -Werror in upstream development
  (Closes: Bug#984069).
* control: Set Rules-Requires-Root to no.
* rules: Drop ddeb-migration rules, now useless

   -- Samuel Thibault   Sun, 15 Aug 2021 22:56:34
  +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/1948566/+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 1700085] Re: Mouse cursor is tiny on HiDPI screens

2021-10-25 Thread Will Bender

I also experience this problem.

OS: Ubuntu 20.04.1 LTS (fossa-bulbasaur X54)
External Monitor: 2k
Laptop Monitor: 4k

Display Config external + laptop screens: 2560x1440 + 1920x1200 (100% scaling)
Display Config only laptop screen: 3840x2400 (200% scale)

It happens when I switch from external monitor + laptop to just my
laptop. The "display scale" goes to 200% or 100%

Duplication notes
1. start application while only using laptop then plug in external monitor 
(200% -> 100% scale): Cursor is HUGE
2. start application while both monitors are in use then unplug external 
monitor (100% -> 200% scale): Cursor is TINY
3. Restarting the app fixes the cursor size problem

Apps tested where bug **occurs**
"VSCode": YES. Restarting vscode fixes it
"Webstorm": YES. Restarting fixes it. Happens on multiple jetbrains products 
including "toolbox"
"Slack": YES. Restarting fixes it.
"Google Chrome": NO. I have a hunch google fixed it themselves or are immune
"Gedit": NO. 
"Gnome Terminal": NO.

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

Title:
  Mouse cursor is tiny on HiDPI screens

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I am on Artful and have switched to GNOME as GNOME is the default
  desktop now and Unity shows some instabilities.

  I am using a Lenovo Thinkpad X1 Carbon (2nd gen.) notebook with
  14-inch QHD (2560x1440) display, so I am well over the good old 72-dpi
  CRT resolution.

  With some effort I have at least got a somewhat useful scaling of the
  GUI elements (esp. text size), mainly by getting into Unity7, getting
  into the Display Settings there, removing my ~1.5 scaling factor,
  returning to GNOME, installing the advanced settings manager (gnome-
  tweak-tool or so) and setting a scaling factor of ~2). Large text in
  accessibilty does not work for me as it makes the text huge.

  Now the mouse cursor does no bother on all these changes. It stays
  always in its 72-dpi hard-coded size which is really tiny under GNOME
  on my QHD screen. It gets easily totally invisible for me, especially
  on text fields where it gets a skinny vertical bar.

  Therefore there are two fixes needed:

  1. Mouse cursor needs to scale with scale factor for the desktop, so
  that it is in a good size relation with the rest of the desktop.
  Please take this into account for fractional scaling efforts.

  2. Even a standard-sized mouse cursor can be too small for people with
  vision problems, so the accessibility options need a possibility to
  apply a (fractional) adjustable scaling factor to the mouse cursor's
  standard size.

  Please take these changes into account ASAP, ideally on 17.10 at the
  latest. Please consider backporting upstream fixes for achieving this
  goal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1700085/+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 1948046] Re: [upstream] Flameshot won't paste on Chrome with Ozone enabled

2021-10-25 Thread otheos

Chrome.

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

Title:
  [upstream] Flameshot won't paste on Chrome with Ozone enabled

Status in Chromium Browser:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  This is a unique problem to Ubuntu 21.04 and later and all derivatives
  (pop, mint etc).

  Since Chrome stable 91, when Ozone was enabled by default, unless
  Ozone is disabled in Chrome, flameshot (any version) cannot paste on
  sites such as github, gitlab or kami.

  The workaround has been so far to disable Ozone in Chrome flags, but
  since Chrome 95, Ozone cannot be disabled, which means that flameshot
  no longer works with Chrome and those (and potentially more) sites.

  Everything works fine in Fedora 33/34/35 and Manjaro 20+.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1948046/+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 1948486] Re: Keyboard Brightness control not operable using keyboard or mouse scrollwheel

Thanks!

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Triaged

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

Title:
  Keyboard Brightness control not operable using keyboard or mouse
  scrollwheel

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

Bug description:
  At the power settings there is a slider for setting the "Keyboard Brightness".
  My ThinkPad T460s supports three levels: off, dim, bright

  With clicking and/or dragging I could move the slider to either the
  left-most, center, or right-most position.

  However when place the mouse cursor on top of it and use the scroll wheel, I 
could not move the slider.
  Same happens when I try to use the cursor keys on the keyboard.

  My assumption: When using the scroll wheel or the keyboard, the slider
  is moved by only a small fraction. So if the left-most position is 0%
  and the right-most is 100%, it will try to increment it by 10%. It
  does so, but as the only valid values are 0%, 50%, and 100%, it tries
  to round it to the nearest value, which is 0%, so it jumps back to
  where it was. You can see the slider briefly jump a short distance but
  only very briefly, not much more than a flicker.

  While I could just click/drag with the mouse to change the slider, for
  some people it might be an accessibility issue and thus I believe this
  should be fixed somehow.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-control-center 1:40.0-1ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 22 19:16:07 2021
  InstallationDate: Installed on 2019-11-25 (697 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to impish on 2021-10-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1948486/+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 1948665] Re: No stylus found for Wacom HID 49A3 Pen (Latitude 7320)

it sounds like libwacom isn't knowing about it then, reassigning. You
might want to report the issue directly to upstream on
https://github.com/linuxwacom/libwacom/issues

** Package changed: gnome-control-center (Ubuntu) => libwacom (Ubuntu)

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

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

Title:
  No stylus found for Wacom HID 49A3 Pen (Latitude 7320)

Status in libwacom package in Ubuntu:
  New

Bug description:
  I have a Dell Latitude 7320 Detachable with a 7320 Detachable Active
  Pen (PN7320A). The pen mostly works, aside from a periodic bug
  (https://github.com/linuxwacom/input-wacom/issues/281). It shows up as
  a Wacom pen from libinput:

  Device:   Wacom HID 49A3 Pen
  Kernel:   /dev/input/event4
  Group:6
  Seat: seat0, default
  Size: 274x183mm
  Capabilities: tablet 
  Tap-to-click: n/a
  Tap-and-drag: n/a
  Tap drag lock:n/a
  Left-handed:  n/a
  Nat.scrolling:n/a
  Middle emulation: n/a
  Calibration:  identity matrix
  Scroll methods:   none
  Click methods:none
  Disable-w-typing: n/a
  Accel profiles:   none
  Rotation: n/a

  I cannot configure it via the Wacom Tablet settings in the control
  center. It always says "No stylus found" despite being able to use the
  stylus with applications such as Xournal++.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-control-center 1:40.0-1ubuntu5
  Uname: Linux 5.15.0-rc4-soffixes x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 13:47:11 2021
  InstallationDate: Installed on 2021-10-12 (12 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1948665/+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 1948046] Re: [upstream] Flameshot won't paste on Chrome with Ozone enabled

Is this chrome, or chromium?

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

Title:
  [upstream] Flameshot won't paste on Chrome with Ozone enabled

Status in Chromium Browser:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  This is a unique problem to Ubuntu 21.04 and later and all derivatives
  (pop, mint etc).

  Since Chrome stable 91, when Ozone was enabled by default, unless
  Ozone is disabled in Chrome, flameshot (any version) cannot paste on
  sites such as github, gitlab or kami.

  The workaround has been so far to disable Ozone in Chrome flags, but
  since Chrome 95, Ozone cannot be disabled, which means that flameshot
  no longer works with Chrome and those (and potentially more) sites.

  Everything works fine in Fedora 33/34/35 and Manjaro 20+.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1948046/+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 1948710] [NEW] Suspend issues with nvidia proprietary driver

2021-10-25 Thread Lorenzo Ranieri

Public bug reported:

When I suspend my system, after the screen goes black, the desktop and
the suspend login screen are briefly shown in succession, and only then
the screen, power LED and fan turn off like normally.

The timing of the brief "fake resume" is not consistent: sometimes it
only shows the login screen, sometimes it stops the suspension until
briefly after I login.

When resuming after this has happened, the login screen appears as
normal, but I have to wait for any internet connection to restart, and
my second screen remains blacks despite it being detected and the
display mode remaining on "join displays", until I change the display
mode back and forth to fix it.

These issues occur after switching to the nvidia-driver-470 driver on a
fresh install of Ubuntu 21.10, but I have been experiencing at least the
"fake-resume" since at least 20.10, without being able to find any
solution.

These issues persist (with slightly altered timing) if I switch to an
older proprietary driver (I tried nvidia-driver-390 and nvidia-
driver-460), but do not appear while using the nouveau driver.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-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  470.74  Mon Sep 13 23:09:15 
UTC 2021
 GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2)
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 25 21:09:03 2021
DistUpgraded: Fresh install
DistroCodename: impish
DistroVariant: ubuntu
DkmsStatus: nvidia, 470.74, 5.13.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics 
Controller [1043:177d]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d]
InstallationDate: Installed on 2021-10-21 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: ASUSTeK COMPUTER INC. N551JK
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=64128e5f-ba67-49c1-aa02-c19feef6be26 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/06/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N551JK.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N551JK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551JK.203:bd10/06/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnN551JK:pvr1.0:skuASUS-NotebookSKU:rvnASUSTeKCOMPUTERINC.:rnN551JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N551JK
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
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
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug impish nvidia suspend-resume ubuntu

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

Title:
  Suspend issues with nvidia proprietary driver

Status in xorg package in Ubuntu:
  New

Bug description:
  When I suspend my system, after the screen goes black, the desktop and
  the suspend login screen are briefly shown in

[Desktop-packages] [Bug 1948486] Re: Keyboard Brightness control not operable using keyboard or mouse scrollwheel

2021-10-25 Thread nomike

Filed as upstream issue:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1500

** Summary changed:

- Keyboard Brightness controll not operable using keyboard or mouse scrollwheel
+ Keyboard Brightness control not operable using keyboard or mouse scrollwheel

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

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

Title:
  Keyboard Brightness control not operable using keyboard or mouse
  scrollwheel

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

Bug description:
  At the power settings there is a slider for setting the "Keyboard Brightness".
  My ThinkPad T460s supports three levels: off, dim, bright

  With clicking and/or dragging I could move the slider to either the
  left-most, center, or right-most position.

  However when place the mouse cursor on top of it and use the scroll wheel, I 
could not move the slider.
  Same happens when I try to use the cursor keys on the keyboard.

  My assumption: When using the scroll wheel or the keyboard, the slider
  is moved by only a small fraction. So if the left-most position is 0%
  and the right-most is 100%, it will try to increment it by 10%. It
  does so, but as the only valid values are 0%, 50%, and 100%, it tries
  to round it to the nearest value, which is 0%, so it jumps back to
  where it was. You can see the slider briefly jump a short distance but
  only very briefly, not much more than a flicker.

  While I could just click/drag with the mouse to change the slider, for
  some people it might be an accessibility issue and thus I believe this
  should be fixed somehow.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-control-center 1:40.0-1ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 22 19:16:07 2021
  InstallationDate: Installed on 2019-11-25 (697 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to impish on 2021-10-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1948486/+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 1948046] Re: [upstream] Flameshot won't paste on Chrome with Ozone enabled

2021-10-25 Thread otheos

Thanks for this! It seems promising, although the last post was over a
month ago, and C95 is out, and the workaround to disable Ozone is gone,
which means effectively pasting is done with C95 on Ubuntu and
derivatives.

On a personal note it is Kami (a teaching tool) that is more important
that pasting doesn't work (with flameshot).

Finally, why only Ubuntu? How come even with Ozone enabled, all versions
of Chrome have no issue on non Ubuntu distributions?

Thanks again.

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

Title:
  [upstream] Flameshot won't paste on Chrome with Ozone enabled

Status in Chromium Browser:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  This is a unique problem to Ubuntu 21.04 and later and all derivatives
  (pop, mint etc).

  Since Chrome stable 91, when Ozone was enabled by default, unless
  Ozone is disabled in Chrome, flameshot (any version) cannot paste on
  sites such as github, gitlab or kami.

  The workaround has been so far to disable Ozone in Chrome flags, but
  since Chrome 95, Ozone cannot be disabled, which means that flameshot
  no longer works with Chrome and those (and potentially more) sites.

  Everything works fine in Fedora 33/34/35 and Manjaro 20+.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1948046/+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 1916640] Re: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed

2021-10-25 Thread Butterfly

@freewee, xorg-modulepath-fix package is not require for installing
nvidia-340 package. xorg-modulepath-fix package is automatically
modified  xorg.conf file for adding module-path fixes. If you do not
need to create xorg.conf files or you have already added module-path fix
by manually, you do not need to install the xorg-modulepath-fix package.

Note: I updated xorg-modulepath-fix package to use nvidia-xconfig
command options.

Nvidia-340 package in the PPA repository has supports up to kernel 5.15
and also supports bionic, focal, hirsute and impish bases.

https://launchpad.net/~kelebek333/+archive/ubuntu/nvidia-legacy

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

Title:
  Nvidia 340.108 fails to install with kernels 5.11.x - new patches
  needeed

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  As usual I have opened this (no more) new bug report...

  As ALWAYS happened in the past, EVERY TWO MONTHS new patches are
  needed for old Nvidia 340.108 drivers, that is, with each release of a
  new kernel...

  Nvidia 340.108 fails to install with kernels 5.11.x - new patches
  needeed

  Just to inform develepers that a new patch for Nvidia 340.108 and
  kernel 5.11 is not yet available here:

  
https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/

  Anyway thanks for your great contribution to community and hope you
  publish new patched drivers without having to always report the same
  bug...

  Good day to all the developers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+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 1948700] Re: Unable to connect to scanner

2021-10-25 Thread poet_imp

More complete syslog:

Oct 25 11:36:27 lemix python3[528720]: io/hpmud/musb.c 427: Found interface 
conf=0, iface=0, altset=0, index=1
Oct 25 11:36:28 lemix python3[528720]: io/hpmud/musb.c 389: Active kernel 
driver on interface=0 ret=0
Oct 25 11:36:28 lemix python3[528720]: io/hpmud/musb.c 535: claimed 7/1/2 
interface
Oct 25 11:36:28 lemix python3[528720]: io/hpmud/musb.c 781: read actual 
device_id successfully fd=1 len=323
Oct 25 11:36:28 lemix python3[528720]: io/hpmud/musb.c 561: released 7/1/2 
interface
Oct 25 11:36:28 lemix python3[528720]: common/utils.c 212: unable to load 
library libm.so: /lib/x86_64-linux-gnu/libm.so: invalid ELF header
Oct 25 11:36:28 lemix python3[528720]: common/utils.c 79: unable to open 
/var/lib/hp/hplip.state: No such file or directory
Oct 25 11:36:28 lemix python3[528720]: common/utils.c 129: 
validate_plugin_version() Failed to get Plugin version from 
[/var/lib/hp/hplip.state]
Oct 25 11:36:28 lemix python3[528720]: common/utils.c 173: Plugin version is 
not matching
Oct 25 11:36:28 lemix python3[528720]: common/utils.c 244: Invalid Library 
handler pLibHandler = NULL.
Oct 25 11:36:28 lemix hp-scan[528720]: hp-scan[528720]: error: SANE: Error 
during device I/O (code=9)

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

Title:
  Unable to connect to scanner

Status in hplip package in Ubuntu:
  New

Bug description:
  unable to load library libm.so: /lib/x86_64-linux-gnu/libm.so: invalid ELF 
header
  unable to open /var/lib/hp/hplip.state: No such file or directory
  validate_plugin_version() Failed to get Plugin version from 
[/var/lib/hp/hplip.state]

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: hplip 3.21.6+dfsg0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   
  Date: Mon Oct 25 10:46:13 2021
  InstallationDate: Installed on 2017-02-27 (1701 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170222)
  Lpstat:
   device for HP-ColorLaserJet-MFP-M282-M285: 
hp:/usb/HP_ColorLaserJet_MFP_M282-M285?serial=VNBRNB6581
   device for HP-ColorLaserJet-MFP-M282-M285-Fax-2: 
hpfax:/usb/HP_ColorLaserJet_MFP_M282-M285?serial=VNBRNB6581
   device for HP_Color_LaserJet_MFP_M283fdw_76254B_: 
implicitclass://HP_Color_LaserJet_MFP_M283fdw_76254B_/
   device for OfficeFax: 
hpfax:/usb/HP_ColorLaserJet_MFP_M282-M285?serial=VNBRNB6581
   device for OfficePrinter: 
hp:/usb/HP_ColorLaserJet_MFP_M282-M285?serial=VNBRNB6581
  MachineType: HP HP Z240 Tower Workstation
  Papersize: letter
  PpdFiles:
   HP-ColorLaserJet-MFP-M282-M285-Fax-2: HP Fax2 hpcups
   HP-ColorLaserJet-MFP-M282-M285: HP ColorLaserJet MFP M282-M285, Fax, 
driverless, cups-filters 1.28.8
   HP_Color_LaserJet_MFP_M283fdw_76254B_: HP ColorLaserJet MFP M282-M285, 
driverless, cups-filters 1.28.10
   OfficePrinter: HP ColorLaserJet MFP M282-M285 Postscript (recommended)
   OfficeFax: HP Fax2 hpcups
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=6e305f7e-4b50-4d8c-89d2-45681f2fd2e1 ro quiet splash 
scsi_mod.use_blk_mq=1 vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to impish on 2021-10-15 (10 days ago)
  dmi.bios.date: 12/02/2016
  dmi.bios.release: 1.35
  dmi.bios.vendor: HP
  dmi.bios.version: N51 Ver. 01.35
  dmi.board.name: 802F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.30
  dmi.chassis.asset.tag: 2UA7032SD0
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 5.48
  dmi.modalias: 
dmi:bvnHP:bvrN51Ver.01.35:bd12/02/2016:br1.35:efr5.48:svnHP:pnHPZ240TowerWorkstation:pvr:skuL9K63UT#ABA:rvnHP:rn802F:rvrKBCVersion05.30:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53335X G=D
  dmi.product.name: HP Z240 Tower Workstation
  dmi.product.sku: L9K63UT#ABA
  dmi.sys.vendor: HP

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

2021-10-25 Thread Rico Tzschichholz

Upgraded libreoffice from 1:7.2.1-0ubuntu3 to 1:7.2.2-0ubuntu0.21.10.1
from impish-proposed in a clean and up-to-date impish amd64 VM, and
successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.

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

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

** Changed in: libreoffice (Ubuntu Impish)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

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

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

Title:
  [SRU] libreoffice 7.2.2 for impish

Status in libreoffice package in Ubuntu:
  Fix Committed
Status in libreoffice source package in Impish:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.2.2 is in its second bugfix release of the 7.2 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.2_release

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

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

  [Testing]

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

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

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

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/amd64/libr/libreoffice/20211010_212128_a2213@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/arm64/libr/libreoffice/20211011_063847_cff27@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/armhf/libr/libreoffice/20211010_152042_46a77@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/ppc64el/libr/libreoffice/20211010_131403_b895a@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/s390x/libr/libreoffice/20211010_145947_98155@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1946558/+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 1948700] [NEW] Unable to connect to scanner

2021-10-25 Thread poet_imp

Public bug reported:

unable to load library libm.so: /lib/x86_64-linux-gnu/libm.so: invalid ELF 
header
unable to open /var/lib/hp/hplip.state: No such file or directory
validate_plugin_version() Failed to get Plugin version from 
[/var/lib/hp/hplip.state]

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: hplip 3.21.6+dfsg0-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: unknown
CupsErrorLog:
 
Date: Mon Oct 25 10:46:13 2021
InstallationDate: Installed on 2017-02-27 (1701 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170222)
Lpstat:
 device for HP-ColorLaserJet-MFP-M282-M285: 
hp:/usb/HP_ColorLaserJet_MFP_M282-M285?serial=VNBRNB6581
 device for HP-ColorLaserJet-MFP-M282-M285-Fax-2: 
hpfax:/usb/HP_ColorLaserJet_MFP_M282-M285?serial=VNBRNB6581
 device for HP_Color_LaserJet_MFP_M283fdw_76254B_: 
implicitclass://HP_Color_LaserJet_MFP_M283fdw_76254B_/
 device for OfficeFax: 
hpfax:/usb/HP_ColorLaserJet_MFP_M282-M285?serial=VNBRNB6581
 device for OfficePrinter: 
hp:/usb/HP_ColorLaserJet_MFP_M282-M285?serial=VNBRNB6581
MachineType: HP HP Z240 Tower Workstation
Papersize: letter
PpdFiles:
 HP-ColorLaserJet-MFP-M282-M285-Fax-2: HP Fax2 hpcups
 HP-ColorLaserJet-MFP-M282-M285: HP ColorLaserJet MFP M282-M285, Fax, 
driverless, cups-filters 1.28.8
 HP_Color_LaserJet_MFP_M283fdw_76254B_: HP ColorLaserJet MFP M282-M285, 
driverless, cups-filters 1.28.10
 OfficePrinter: HP ColorLaserJet MFP M282-M285 Postscript (recommended)
 OfficeFax: HP Fax2 hpcups
ProcEnviron:
 TERM=xterm-color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=6e305f7e-4b50-4d8c-89d2-45681f2fd2e1 ro quiet splash 
scsi_mod.use_blk_mq=1 vt.handoff=7
SourcePackage: hplip
UpgradeStatus: Upgraded to impish on 2021-10-15 (10 days ago)
dmi.bios.date: 12/02/2016
dmi.bios.release: 1.35
dmi.bios.vendor: HP
dmi.bios.version: N51 Ver. 01.35
dmi.board.name: 802F
dmi.board.vendor: HP
dmi.board.version: KBC Version 05.30
dmi.chassis.asset.tag: 2UA7032SD0
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 5.48
dmi.modalias: 
dmi:bvnHP:bvrN51Ver.01.35:bd12/02/2016:br1.35:efr5.48:svnHP:pnHPZ240TowerWorkstation:pvr:skuL9K63UT#ABA:rvnHP:rn802F:rvrKBCVersion05.30:cvnHP:ct3:cvr:
dmi.product.family: 103C_53335X G=D
dmi.product.name: HP Z240 Tower Workstation
dmi.product.sku: L9K63UT#ABA
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug impish

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

Title:
  Unable to connect to scanner

Status in hplip package in Ubuntu:
  New

Bug description:
  unable to load library libm.so: /lib/x86_64-linux-gnu/libm.so: invalid ELF 
header
  unable to open /var/lib/hp/hplip.state: No such file or directory
  validate_plugin_version() Failed to get Plugin version from 
[/var/lib/hp/hplip.state]

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: hplip 3.21.6+dfsg0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   
  Date: Mon Oct 25 10:46:13 2021
  InstallationDate: Installed on 2017-02-27 (1701 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170222)
  Lpstat:
   device for HP-ColorLaserJet-MFP-M282-M285: 
hp:/usb/HP_ColorLaserJet_MFP_M282-M285?serial=VNBRNB6581
   device for HP-ColorLaserJet-MFP-M282-M285-Fax-2: 
hpfax:/usb/HP_ColorLaserJet_MFP_M282-M285?serial=VNBRNB6581
   device for HP_Color_LaserJet_MFP_M283fdw_76254B_: 
implicitclass://HP_Color_LaserJet_MFP_M283fdw_76254B_/
   device for OfficeFax: 
hpfax:/usb/HP_ColorLaserJet_MFP_M282-M285?serial=VNBRNB6581
   device for OfficePrinter: 
hp:/usb/HP_ColorLaserJet_MFP_M282-M285?serial=VNBRNB6581
  MachineType: HP HP Z240 Tower Workstation
  Papersize: letter
  PpdFiles:
   HP-ColorLaserJet-MFP-M282-M285-Fax-2: HP Fax2 hpcups
   HP-ColorLaserJet-MFP-M282-M285: HP ColorLaserJet MFP M282-M285, Fax, 
driverless, cups-filters 1.28.8
   HP_Color_LaserJet_MFP_M283fdw_76254B_: HP ColorLaserJet MFP M282-M285, 
driverless, cups-filters 1.28.10
   OfficePrinter: HP ColorLaserJet MFP M282-M285 Postscript (recommended)
   OfficeFax: HP Fax2 hpcups
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=6e305f7e-4b50-4d8c-89d2-45681f2fd2e1 ro quiet splash 
scsi_mod.use_blk_mq=1 vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to impish on

[Desktop-packages] [Bug 1948046] Re: Flameshot won't paste on Chrome with Ozone enabled

This appears to be a known upstream regression:
https://bugs.chromium.org/p/chromium/issues/detail?id=1247919.

** Summary changed:

- Flameshot won't paste on Chrome with Ozone enabled
+ [upstream] Flameshot won't paste on Chrome with Ozone enabled

** Tags added: upstream

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

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

Title:
  [upstream] Flameshot won't paste on Chrome with Ozone enabled

Status in Chromium Browser:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  This is a unique problem to Ubuntu 21.04 and later and all derivatives
  (pop, mint etc).

  Since Chrome stable 91, when Ozone was enabled by default, unless
  Ozone is disabled in Chrome, flameshot (any version) cannot paste on
  sites such as github, gitlab or kami.

  The workaround has been so far to disable Ozone in Chrome flags, but
  since Chrome 95, Ozone cannot be disabled, which means that flameshot
  no longer works with Chrome and those (and potentially more) sites.

  Everything works fine in Fedora 33/34/35 and Manjaro 20+.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1948046/+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 1948592] Re: Switching between workspaces is now Ctrl-Alt-Right or Left, no longer Up or Down

2021-10-25 Thread Gunnar Hjalmarsson

Thanks for your report.

I suppose you mean this page:

https://help.ubuntu.com/stable/ubuntu-help/shell-workspaces-switch.html

That's actually an upstream issue, and it would be great if you could
report it upstream too:

https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues

If you do, please post the URL to the upstream issue here for tracking
purposes.

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

** Changed in: gnome-user-docs (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-user-docs (Ubuntu)
   Status: New => Confirmed

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

Title:
  Switching between workspaces is now Ctrl-Alt-Right or Left, no longer
  Up or Down

Status in gnome-user-docs package in Ubuntu:
  Confirmed

Bug description:
  Workspaces seem to have gone from vertically oriented to horizontally,
  but the arrow specifier in the documentation for 21.10 did not change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1948592/+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 1948592] [NEW] Switching between workspaces is now Ctrl-Alt-Right or Left, no longer Up or Down

2021-10-25 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Workspaces seem to have gone from vertically oriented to horizontally,
but the arrow specifier in the documentation for 21.10 did not change.

** Affects: gnome-user-docs (Ubuntu)
 Importance: Medium
 Status: Confirmed

-- 
Switching between workspaces is now Ctrl-Alt-Right or Left, no longer Up or Down
https://bugs.launchpad.net/bugs/1948592
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-user-docs 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 1948665] Re: No stylus found for Wacom HID 49A3 Pen (Latitude 7320)

libwacom-list-local-devices prints nothing.

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

Title:
  No stylus found for Wacom HID 49A3 Pen (Latitude 7320)

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

Bug description:
  I have a Dell Latitude 7320 Detachable with a 7320 Detachable Active
  Pen (PN7320A). The pen mostly works, aside from a periodic bug
  (https://github.com/linuxwacom/input-wacom/issues/281). It shows up as
  a Wacom pen from libinput:

  Device:   Wacom HID 49A3 Pen
  Kernel:   /dev/input/event4
  Group:6
  Seat: seat0, default
  Size: 274x183mm
  Capabilities: tablet 
  Tap-to-click: n/a
  Tap-and-drag: n/a
  Tap drag lock:n/a
  Left-handed:  n/a
  Nat.scrolling:n/a
  Middle emulation: n/a
  Calibration:  identity matrix
  Scroll methods:   none
  Click methods:none
  Disable-w-typing: n/a
  Accel profiles:   none
  Rotation: n/a

  I cannot configure it via the Wacom Tablet settings in the control
  center. It always says "No stylus found" despite being able to use the
  stylus with applications such as Xournal++.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-control-center 1:40.0-1ubuntu5
  Uname: Linux 5.15.0-rc4-soffixes x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 13:47:11 2021
  InstallationDate: Installed on 2021-10-12 (12 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1948665/+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 1948652] Re: [upstream, regression] Firefox does not save tabs when quitting with Ctrl+Q

2021-10-25 Thread Bug Watch Updater

Launchpad has imported 13 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1726736.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2021-08-20T09:52:22+00:00 Gijskruitbosch+bugs wrote:

Created attachment 9237163
Spec for dialog

Right now, `browser.tabs.warnOnClose` governs a warning that appears
when closing multiple tabs.

We'll want a separate pref, `browser.warnOnQuitShortcut`, that defaults
to true on macOS and Linux, and false on Windows.

We'll want to check this pref when the user quits the browser using the
``.

Right now, the quit warnings hook into this BrowserGlue.jsm code:
https://searchfox.org/mozilla-
central/rev/12770bd668c0a6bdaa8eb96ad9507c6febe8d23d/browser/components/BrowserGlue.jsm#2779
.

For the telemetry work in an earlier bug (bug 1712306), we added
`_quitSource` on the BrowserGlue object; we can check if it is
`shortcut` to see if that was the case, and if so, show an appropriate
warning prompt. If we show this prompt, we should not also show the
"regular" quit / close-multiple tabs prompt, even if that would
otherwise have been shown; there's no point confirming it twice!

We should be able to have the single `confirmEx` call for quitting use
either the quit shortcut text and checkbox text, or the "multiple tabs"
version and checkbox text (x-ref bug 1724964), depending on our reason
for showing the warning.

To include the shortcut text in the text, we'll want to grab the `key`
element in one of the open windows for the shortcut, and use
`ShortcutUtils.prettifyShortcut` to get text for the shortcut, that we
can then insert in the message we display.

Note that this shortcut warning applies even if there is only 1 tab
(`pagecount == 1` in the BrowserGlue code, where it currently returns
early if `pagecount < 2`).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948652/comments/0

On 2021-08-31T16:38:48+00:00 Enn wrote:

There are three existing preferences related to closing tabs/quitting:

browser.warnOnQuit - hidden preference that overrides all others if false
browser.sessionstore.warnOnQuit - hidden preference that disables warning on 
quit when session store is active
browser.tabs.warnOnClose - disables close tab warning, corresponds to checkbox 
in preferences

Is the intent here (and for the other related bugs) to remove the
'browser.sessionstore.warnOnQuit' preference and use
'browser.tabs.warnOnClose' for closing or quitting without the keyboard
shortcut (close button or quit from the menu), and add a new preference
'browser.warnOnQuitShortcut' for quitting with Ctrl/Cmd+Q?

Will the new 'browser.warnOnQuitShortcut' preference have UI in
preferences?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948652/comments/1

On 2021-08-31T16:44:11+00:00 Gijskruitbosch+bugs wrote:

(In reply to Neil Deakin from comment #1)
> There are three existing preferences related to closing tabs/quitting:
> 
> browser.warnOnQuit - hidden preference that overrides all others if false
> browser.sessionstore.warnOnQuit - hidden preference that disables warning on 
> quit when session store is active
> browser.tabs.warnOnClose - disables close tab warning, corresponds to 
> checkbox in preferences
> 
> Is the intent here (and for the other related bugs) to remove the 
> 'browser.sessionstore.warnOnQuit' preference and use 
> 'browser.tabs.warnOnClose' for closing or quitting without the keyboard 
> shortcut (close button or quit from the menu), and add a new preference 
> 'browser.warnOnQuitShortcut' for quitting with Ctrl/Cmd+Q?

Yep, that's all correct. I think my assumption was that we could deal
with the session store pref removal in bug 1724976.

> Will the new 'browser.warnOnQuitShortcut' preference have UI in
preferences?

Yes. The authoritative spec is in figma; I'll add another screenshot for
the preferences portion.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948652/comments/2

On 2021-08-31T16:45:00+00:00 Gijskruitbosch+bugs wrote:

Created attachment 9238724
Preference update for the new shortcut-related warning

The expectation is that this warning only shows up on macOS+Linux, with
the relevant shortcut embedded in the message.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948652/comments/3

On 2021-09-01T17:40:00+00:00 Enn wrote:

Created attachment 9238974
Bug 1726736, add a separate preference when quitting using the shortcut key, 
and

[Desktop-packages] [Bug 1948652] Re: Firefox do not save tabs

This is probably related to
https://bugzilla.mozilla.org/show_bug.cgi?id=1726736 (I couldn't find a
bug describing exactly this regression).

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

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

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

** Summary changed:

- Firefox do not save tabs
+ [upstream,regression] Firefox does not save tabs when quitting with Ctrl+Q

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

Title:
  [upstream,regression] Firefox does not save tabs when quitting with
  Ctrl+Q

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  1) % lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  2) % apt-cache policy firefox
  firefox:
Установлен: 93.0+build1-0ubuntu0.20.04.1
Кандидат:   93.0+build1-0ubuntu0.20.04.1
Таблица версий:
   *** 93.0+build1-0ubuntu0.20.04.1 500
  500 http://ua.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   75.0+build3-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) After start Firefox expected to restore previous session
  4) Firefox start with new tab

  If I close Firefox by Ctrl-Q with opened tabs and start it again Firefox 
opens with one new tab. When profile was recreated issue was gone but appeared 
again after Firefox was closed by Ctrl-W.
  The option "Restore previous session" is on. Without extension behavior the 
same. I'm not sure but this begins after last update of Firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1948652/+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 1948652] Re: Firefox do not save tabs

I just tested a 94.0 beta 10 build in the same VM, and the regression
appears to be fixed there.

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

Title:
  Firefox do not save tabs

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  1) % lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  2) % apt-cache policy firefox
  firefox:
Установлен: 93.0+build1-0ubuntu0.20.04.1
Кандидат:   93.0+build1-0ubuntu0.20.04.1
Таблица версий:
   *** 93.0+build1-0ubuntu0.20.04.1 500
  500 http://ua.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   75.0+build3-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) After start Firefox expected to restore previous session
  4) Firefox start with new tab

  If I close Firefox by Ctrl-Q with opened tabs and start it again Firefox 
opens with one new tab. When profile was recreated issue was gone but appeared 
again after Firefox was closed by Ctrl-W.
  The option "Restore previous session" is on. Without extension behavior the 
same. I'm not sure but this begins after last update of Firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948652/+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 1948652] Re: Firefox do not save tabs

I can indeed observe this problem in a VM, following your instructions.

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

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

Title:
  Firefox do not save tabs

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  1) % lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  2) % apt-cache policy firefox
  firefox:
Установлен: 93.0+build1-0ubuntu0.20.04.1
Кандидат:   93.0+build1-0ubuntu0.20.04.1
Таблица версий:
   *** 93.0+build1-0ubuntu0.20.04.1 500
  500 http://ua.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   75.0+build3-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) After start Firefox expected to restore previous session
  4) Firefox start with new tab

  If I close Firefox by Ctrl-Q with opened tabs and start it again Firefox 
opens with one new tab. When profile was recreated issue was gone but appeared 
again after Firefox was closed by Ctrl-W.
  The option "Restore previous session" is on. Without extension behavior the 
same. I'm not sure but this begins after last update of Firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948652/+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 1948008] Re: Copying and pasting to/from Nautilus does not work

2021-10-25 Thread Dariusz Gadomski

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

Thank you Mathew. I assumed it's the same package in later releases.

The reason behind splitting the bug was the fact that I believe these are 2
separate problems by coincidence having their root causes in similar portions
of code.

Bug #1843588 is focal specific and is about altered contents of clipboard and
fixing it requires fixing reverting the change in nautilus.

This one on the other hand is about not being able to copy from the
desktop to nautilus and vice versa. And fixing this should require
fixing:

For focal (beside fixing bug #1843588):
* gnome-shell
* gnome-shell-extension-desktop-icons

For hirsute & impish:
* gnome-shell-extension-desktop-icons-ng

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

Title:
Copying and pasting to/from Nautilus does not work

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
Incomplete
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
Won't Fix

Bug description:
[Impact]

* After upstream Nautilus has reverted the following commit [1]
related to upstream bug [2] the desktop icons extension lost it's
ability to copy to/from nautilus.

* This is related to the fact that before there was some metadata
passed along in the clipboard along with text data. This was causing
issues with compatibility with some applications that were not
expecting any metadata (MIME type in this case) was glued to the text
clipboard contents. Hence, it was reverted upstream [3].

* Fixing the root cause of this issue required changes to Nautilus
[3], gnome-shell [4] and desktop-icons [5] [6]. Nautilus and gnome-
shell parts are already implemented and present in Hirsute and Impish.

[Test Plan]

1) Make sure desktop-icons extension is enabled.
2) Open nautilus window and copy any file from there by right-clicking and
selecting "Copy" from the popup menu.
3) Right-click on desktop and select "Paste" from the context menu.

Expected result: selected file is copied to the desktop.
Actual result: "Paste" item is disabled in the menu.

[Where problems could occur]

* Mixing a version of nautilus without commit [3] and fixed version
of desktop-icons may still lead to a scenario when copying will not
work.

* Any extension/application copying to desktop using the smuggled-in-
text clipboard behavior should be expected to stop working.

[Other Info]

[1] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/289
[2] https://gitlab.gnome.org/GNOME/nautilus/-/issues/634
[3] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573
[4] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1321
[5]
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186
[6]
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195

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

[Desktop-packages] [Bug 1946525] Re: Removable media are not mounted automatically

2021-10-25 Thread Björn Hutmacher

Okay, so now I've also tried this with 5.13.0-20-generic from the
official repository with the exact same result.

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

Title:
  Removable media are not mounted automatically

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu Desktop amd 64 20211008.1 daily build
  2) udisks 2.9.4-1 
  3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions 
disk images, should be mounted automatically
  4) the automount feature seems to be gone or non-functional in the last 
couple of days

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: udisks2 2.9.4-1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 
60-vboxadd.rules 70-snap.snap-store.rules
  Date: Sat Oct  9 01:37:13 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash
  SourcePackage: udisks2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1946525/+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 1946525] Re: Removable media are not mounted automatically

2021-10-25 Thread Björn Hutmacher

I'm using kernel 5.15.0-051500rc5-lowlatency from
https://kernel.ubuntu.com/~kernel-ppa/mainline. I guess I could try the
official standard kernel as well.

udevadm monitor reports this on insertion of a USB pen drive:

KERNEL[34211.745784] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3 (usb)
KERNEL[34211.766347] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0 (usb)
KERNEL[34211.766487] add  /devices/virtual/workqueue/scsi_tmf_15 (workqueue)
KERNEL[34211.766582] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15 (scsi)
KERNEL[34211.766596] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/scsi_host/host15
 (scsi_host)
KERNEL[34211.766623] bind 
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0 (usb)
KERNEL[34211.766651] bind 
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3 (usb)
UDEV  [34211.768695] add  /devices/virtual/workqueue/scsi_tmf_15 (workqueue)
UDEV  [34211.782340] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3 (usb)
UDEV  [34211.786977] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0 (usb)
UDEV  [34211.787738] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15 (scsi)
UDEV  [34211.788758] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/scsi_host/host15
 (scsi_host)
UDEV  [34211.789765] bind 
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0 (usb)
UDEV  [34211.792650] bind 
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3 (usb)
KERNEL[34212.770824] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0
 (scsi)
KERNEL[34212.770866] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0
 (scsi)
KERNEL[34212.770889] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_device/15:0:0:0
 (scsi_device)
KERNEL[34212.770943] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_generic/sg11
 (scsi_generic)
KERNEL[34212.770964] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_disk/15:0:0:0
 (scsi_disk)
KERNEL[34212.771058] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/bsg/15:0:0:0
 (bsg)
UDEV  [34212.772488] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0
 (scsi)
UDEV  [34212.773741] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0
 (scsi)
UDEV  [34212.774701] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_device/15:0:0:0
 (scsi_device)
UDEV  [34212.775890] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_generic/sg11
 (scsi_generic)
UDEV  [34212.776260] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_disk/15:0:0:0
 (scsi_disk)
UDEV  [34212.776657] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/bsg/15:0:0:0
 (bsg)
KERNEL[34212.781211] add  /devices/virtual/bdi/8:160 (bdi)
UDEV  [34212.781712] add  /devices/virtual/bdi/8:160 (bdi)
KERNEL[34212.850686] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/block/sdk
 (block)
KERNEL[34212.850733] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/block/sdk/sdk1
 (block)
KERNEL[34212.852993] bind 
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0
 (scsi)
UDEV  [34212.887689] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/block/sdk
 (block)
UDEV  [34212.921072] add  
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/block/sdk/sdk1
 (block)
UDEV  [34212.922117] bind 
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0
 (scsi)

... and this on removal:

KERNEL[34235.065672] remove   
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/bsg/15:0:0:0
 (bsg)
KERNEL[34235.065742] remove   
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_generic/sg11
 (scsi_generic)
KERNEL[34235.065759] remove   
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_device/15:0:0:0
 (scsi_device)
KERNEL[34235.065784] remove   
/devices/pci:00/:00:01.3/:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_disk/15:0:0:0
 (scsi_disk)
KERNEL[34235.065875] remove

[Desktop-packages] [Bug 1946525] Re: Removable media are not mounted automatically

@Björn, do you use the standard kernel?

Could you start
$ udevadm monitor

connect a device which isn't working properly and then copy the log to
the bug?

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

Title:
  Removable media are not mounted automatically

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu Desktop amd 64 20211008.1 daily build
  2) udisks 2.9.4-1 
  3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions 
disk images, should be mounted automatically
  4) the automount feature seems to be gone or non-functional in the last 
couple of days

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: udisks2 2.9.4-1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 
60-vboxadd.rules 70-snap.snap-store.rules
  Date: Sat Oct  9 01:37:13 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash
  SourcePackage: udisks2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1946525/+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 1948667] Re: Elantech Touchpad not working on Fujitsu E5410

2021-10-25 Thread Peter Smith

additional info: the output of 
sudo acpidump | grep -C3 ELAN
yields
   39D60: 0D 41 54 4D 4C 32 39 35 32 00 5F 48 49 44 70 00  .ATML2952._HIDp.
   39D70: 48 49 44 32 70 0A 4A 42 41 44 52 70 0C 80 1A 06  HID2p.JBADRp
   39D80: 00 53 50 45 44 A4 00 A0 30 93 54 50 4C 54 0A 03  .SPED...0.TPLT..
   39D90: 70 0D 45 4C 41 4E 32 30 39 37 00 5F 48 49 44 70  p.ELAN2097._HIDp
   39DA0: 01 48 49 44 32 70 0A 10 42 41 44 52 70 0C 80 1A  .HID2p..BADRp...
   39DB0: 06 00 53 50 45 44 A4 00 A0 30 93 54 50 4C 54 0A  ..SPED...0.TPLT.
   39DC0: 04 70 0D 4E 54 52 47 30 30 30 31 00 5F 48 49 44  .p.NTRG0001._HID
--
   3A560: 54 0A 02 70 0D 41 54 4D 4C 32 39 35 32 00 5F 48  T..p.ATML2952._H
   3A570: 49 44 70 00 48 49 44 32 70 0A 4A 42 41 44 52 70  IDp.HID2p.JBADRp
   3A580: 0C 80 1A 06 00 53 50 45 44 A4 00 A0 30 93 54 50  .SPED...0.TP
   3A590: 4C 54 0A 03 70 0D 45 4C 41 4E 32 30 39 37 00 5F  LT..p.ELAN2097._
   3A5A0: 48 49 44 70 01 48 49 44 32 70 0A 10 42 41 44 52  HIDp.HID2p..BADR
   3A5B0: 70 0C 80 1A 06 00 53 50 45 44 A4 00 A0 30 93 54  p.SPED...0.T
   3A5C0: 50 4C 54 0A 04 70 0D 4E 54 52 47 30 30 30 31 00  PLT..p.NTRG0001.
--
   3B530: 50 4C 54 0A 02 70 0D 41 54 4D 4C 32 39 35 32 00  PLT..p.ATML2952.
   3B540: 5F 48 49 44 70 00 48 49 44 32 70 0A 4A 42 41 44  _HIDp.HID2p.JBAD
   3B550: 52 70 0C 80 1A 06 00 53 50 45 44 A4 00 A0 30 93  Rp.SPED...0.
   3B560: 54 50 4C 54 0A 03 70 0D 45 4C 41 4E 32 30 39 37  TPLT..p.ELAN2097
   3B570: 00 5F 48 49 44 70 01 48 49 44 32 70 0A 10 42 41  ._HIDp.HID2p..BA
   3B580: 44 52 70 0C 80 1A 06 00 53 50 45 44 A4 00 A0 30  DRp.SPED...0
   3B590: 93 54 50 4C 54 0A 04 70 0D 4E 54 52 47 30 30 30  .TPLT..p.NTRG000

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

Title:
  Elantech Touchpad not working on Fujitsu E5410

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

Bug description:
  The Fujitsu E5410 (model type 5E14A1 according to the bottom sticker)
  is supplied with an Elantech(?) Touchpad. This apparently requires
  i2c_hid and does not properly work in Ubuntu 20.04. It seems also to
  interfere with the (internal) keyboard.

  Problem behavior:

  booting Ubuntu 20.04 with kernel 5.11.0-27:
  keyboard works, touchpad is not recognized.
  Running sudo modprobe i2c_hid manually from a terminal sometimes results in 
the touchpad working. Sometimes however the keyboard does not recognize any 
input anymore. After rebooting, approx 1/2 times the keyboard is not working 
anymore.

  Making sudo modprobe i2c_hid permanent via /etc/modules-load.d/
  permanently crashes the keyboard on startup such that it is impossible
  to log in.

  booting with kernel 5.14.0-1004-oem:
  sudo modprobe i2c_hid has no effect, the touchpad is never recognized. 
Booting with this kernel, 9/10 times the keyboard is not recognized at all and 
one cannot log in. Permanently loading the module via /etc/modules-load.d has 
no effect.

  booting with kernel 5.14.9-051409 (a mainline kernel from 
ppa:tuxinvader/lts-mainline ):
  modprobing the i2c_hid module has no effect. The keyboard works.

  probably not just xserver-xorg-input-libinput but also i2c_hid is
  affected. However w.r.t.
  https://wiki.ubuntu.com/DebuggingTouchpadDetection and without being
  able to further diagnose the problem I filed this bug against xserver-
  xorg-input-libinput.

  
  (likely) relevant output of cat /proc/bus/input/devices:

  I: Bus=0018 Vendor=04f3 Product=308a Version=0100
  N: Name="0X45 0X4C 0X41 0X4E 04F3:308A Touchpad"
  P: Phys=i2c-0X45 0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00
  S: Sysfs=/devices/pci:00/:00:15.3/i2c_designware.1/i2c-2/i2c-0X45 
0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00/0018:04F3:308A.0002/input/input26
  U: Uniq=
  H: Handlers=mouse2 event14 
  B: PROP=1
  B: EV=1b
  B: KEY=e520 3 0 0 0 0
  B: ABS=2e08003
  B: MSC=20

  
  I: Bus=0018 Vendor=04f3 Product=308a Version=0100
  N: Name="0X45 0X4C 0X41 0X4E 04F3:308A Mouse"
  P: Phys=i2c-0X45 0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00
  S: Sysfs=/devices/pci:00/:00:15.3/i2c_designware.1/i2c-2/i2c-0X45 
0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00/0018:04F3:308A.0002/input/input24
  U: Uniq=
  H: Handlers=mouse1 event13 
  B: PROP=0
  B: EV=17
  B: KEY=3 0 0 0 0
  B: REL=3
  B: MSC=10

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab54
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input2
  U: Uniq=
  H: Handlers=sysrq kbd event2 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Fujitsu FUJ02E3"
  P: Phys=FUJ02E3/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/FUJ02E3:00/input/input7
  U: Uniq=
  H: Handlers=rfkill kbd event3 
  B: PROP=0
  B:

[Desktop-packages] [Bug 1941962] Re: pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from pa_x11_wrapper_unref()

** Tags added: desktop-lts-wishlist

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

Title:
  pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from
  pa_x11_wrapper_unref()

Status in X.Org X server:
  Unknown
Status in libx11 package in Ubuntu:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/52094416ad4b4132ebf639ec8530fed1fdbac584

  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  Uname: Linux 5.13.13-xanmod1-cacule x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anasc  1719 F pulseaudio
   /dev/snd/pcmC0D0p:   anasc  1719 F...m pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Aug 28 21:00:59 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-08-26 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210824)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  SegvAnalysis:
   Segfault happened at: 0x7fbcc9d6a8a4 :  mov%edx,0x4(%rax)
   PC (0x7fbcc9d6a8a4) ok
   source "%edx" ok
   destination "0x4(%rax)" (0x0004) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   XFreeGC () from /lib/x86_64-linux-gnu/libX11.so.6
   XCloseDisplay () from /lib/x86_64-linux-gnu/libX11.so.6
   pa_x11_wrapper_unref () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
   module_x11_publish_LTX_pa__done () from 
/usr/lib/pulse-15.0+dfsg1/modules/module-x11-publish.so
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
  Title: pulseaudio crashed with SIGSEGV in XFreeGC()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 02/05/2021
  dmi.bios.release: 15.14
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 86E2
  dmi.board.vendor: HP
  dmi.board.version: 95.36
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.36
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd02/05/2021:br15.14:efr95.36:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:sku5SU52EA#BH4:rvnHP:rn86E2:rvr95.36:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cs3xxx
  dmi.product.sku: 5SU52EA#BH4
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1941962/+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 1948599] Re: Nautilus icon missing from taskbar (21.10; Xorg)

Thank you for your bug report. Could you add a screenshot showing the
issue as well as a 'journalctl -b 0' log?

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Nautilus icon missing from taskbar (21.10; Xorg)

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Upgraded to 21.10.  I am using Ubuntu Tweaks to set a bottom of screen 
taskbar. Nautilus (Files) was pinned to the taskbar.  I discovered that Waland 
was incompatible with my graphics card, so switched to Xorg.  I think at this 
point the Files icon disappeared (and just possibly some others I have not 
noticed).  I can launch Nautilus from the launcher, but the icon does not 
appear.
  Nautilus version 1:40.2-1ubuntu1

  Expected behaviour 1:  The pinned icon would remain visible on the taskbar.
  Observed behaviour 1:  The pinned icon disappeared from the taskbar.

  Expected behaviour 2:  When Nautilus is open the icon will be visible on the 
taskbar.
  Observed behaviour 2:  When Nautilus is open the icon is not visible on the 
taskbar.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: nautilus 1:40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 24 21:28:18 2021
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2021-05-27 (149 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  usr_lib_nautilus:
   evince40.4-2
   file-roller   3.40.0-2
   nautilus-dropbox  2019.02.14-1ubuntu1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu2
   nautilus-share0.7.3-2ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1948599/+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 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.

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

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

Title:
Support manual firmware upgrading for Foxconn and Quectel modems.

Status in OEM Priority Project:
In Progress
Status in modemmanager package in Ubuntu:
New

Bug description:
[Impact]

The modem certification requires that different modem firmware is used for
different network carrier.
This needs the firmware upgrading capability during the modem certification
process.

The modem manufacture vendors (Foxconn and Quectel) provided utilities to do
modem's firmware upgrading manually.(LP#1943774, LP#1943780)
These utilities are verified to be working when the recent versions(> v
1.18.2) of ModemManager are used with.

To support manual firmware upgrading on the current Focal release which is
using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2.
The requested upstream patches are listed as below:
* for Quectel EM160 4G
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
* for Foxconn T99W175
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9
**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154

The firmware upgrading was verified using the patched ModemManager v 1.16.6
with the following 2 modems:
* Foxconn SDX55 T99W175 5G sub6 PCIE Modem
* Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

[Test Plan]

1. Install the Ubuntu image.
2. Boot and login the system.
3. Prepare the modem’s firmware and install the firmware upgrading
application provided by Foxconn and Quectel
4. Using the firmware upgrading application to upgrade the modem’s firmware
5. Verify if the modem’s firmware upgrading is successful
6. Reboot
7. Verify if the upgraded modem firmware is still working

[Where problems could occur]

The requested upstream patches are for these 2 specific modems.
This should not affect existing generic functions and other modems.

[Other Info]

The firmware and the upgrading utilities can be downloaded from the following
link:
* LP#1943774 for Quectel modems
* LP#1943780 for Foxconn modems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions

[Desktop-packages] [Bug 1920587] Re: cmake support files are installed into a wrong directory

Thanks, that's fixed now in
https://bugs.launchpad.net/ubuntu/+source/libical3/+bug/1938334

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

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

Title:
  cmake support files are installed into a wrong directory

Status in libical3 package in Ubuntu:
  Fix Released

Bug description:
  This problem was discovered when updating kmymoney's cmake build
  system with respect to libical (see
  https://invent.kde.org/office/kmymoney/-/merge_requests/63) with
  ubuntu:20.04.

  libical-dev:amd64 (3.0.8-1) ...
  /# sed -i -- 's/#[ ]*deb-src/deb-src/g' /etc/apt/sources.list
  /# apt update
  /# apt-get install libical-dev
  /# dpkg -L libical-dev | grep 'LibIcal$'
  /usr/lib/x86_64-linux-gnu/cmake/cmake/LibIcal

  The correct location is /usr/lib/x86_64-linux-gnu/cmake/LibIcal.

  The issue was not fixed with ubuntu 20.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libical3/+bug/1920587/+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 1938334] Re: Please upgrade libical to 3.0.10

https://launchpad.net/ubuntu/+source/libical3/3.0.11-2

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

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

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

Title:
  Please upgrade libical to 3.0.10

Status in libical3 package in Ubuntu:
  Fix Released
Status in libical3 package in Debian:
  New

Bug description:
  A bug in libical causes incorrect parsing of certain time zones,
  leading to incorrectly created calendar events. I confirmed by
  building libical from source that upgrading to the 3.0.10 release
  fixes this problem, as described in detail here:
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/344

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libical3/+bug/1938334/+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 1946963] Re: libical3-dev does not provide CMake config files

the fix has been uploaded to Debian and autosynced to the new Ubuntu
serie

https://launchpad.net/ubuntu/+source/libical3/3.0.11-2

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

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

Title:
  libical3-dev does not provide CMake config files

Status in libical3 package in Ubuntu:
  Fix Released

Bug description:
  The libical-dev package on Ubuntu 21.10 (impish) does not provide
  CMake config files.

  % dpkg -L libical-dev | grep cmake
  ... returns nothing.

  As of today:

  # Packages file listings on 20.04, 20.10

  The package provides CMake config files in:

  ```
  /usr/lib/x86_64-linux-gnu/cmake/cmake/LibIcal/LibIcalConfig.cmake
  /usr/lib/x86_64-linux-gnu/cmake/cmake/LibIcal/LibIcalConfigVersion.cmake
  /usr/lib/x86_64-linux-gnu/cmake/cmake/LibIcal/LibIcalTargets-none.cmake
  /usr/lib/x86_64-linux-gnu/cmake/cmake/LibIcal/LibIcalTargets.cmake
  ```

  ... which is wrong, but tracked here:
  https://bugs.launchpad.net/ubuntu/+source/libical/+bug/1920587

  
  # Packages file listings on 21.04, 21.10:

  The package does not provide CMake config files at all, while it
  should.

  See:

  https://packages.ubuntu.com/hirsute/amd64/libical-dev/filelist
  https://packages.ubuntu.com/impish/amd64/libical-dev/filelist

  Seems like there are multiple issues with libcal packaging here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libical3/+bug/1946963/+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 1948665] Re: No stylus found for Wacom HID 49A3 Pen (Latitude 7320)

Thank you for your bug report. Could you add the output of 
$ libwacom-list-local-devices
?

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

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

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

Title:
  No stylus found for Wacom HID 49A3 Pen (Latitude 7320)

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

Bug description:
  I have a Dell Latitude 7320 Detachable with a 7320 Detachable Active
  Pen (PN7320A). The pen mostly works, aside from a periodic bug
  (https://github.com/linuxwacom/input-wacom/issues/281). It shows up as
  a Wacom pen from libinput:

  Device:   Wacom HID 49A3 Pen
  Kernel:   /dev/input/event4
  Group:6
  Seat: seat0, default
  Size: 274x183mm
  Capabilities: tablet 
  Tap-to-click: n/a
  Tap-and-drag: n/a
  Tap drag lock:n/a
  Left-handed:  n/a
  Nat.scrolling:n/a
  Middle emulation: n/a
  Calibration:  identity matrix
  Scroll methods:   none
  Click methods:none
  Disable-w-typing: n/a
  Accel profiles:   none
  Rotation: n/a

  I cannot configure it via the Wacom Tablet settings in the control
  center. It always says "No stylus found" despite being able to use the
  stylus with applications such as Xournal++.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-control-center 1:40.0-1ubuntu5
  Uname: Linux 5.15.0-rc4-soffixes x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 13:47:11 2021
  InstallationDate: Installed on 2021-10-12 (12 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1948665/+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 1948647] Re: Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange circle persists

** Attachment added: "packages.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948647/+attachment/5535833/+files/packages.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/1948647

Title:
  Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange
  circle persists

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Running 21.10 and Gnome 40.4 the screen recording no longer works with
  the Ctrl+Alt+Shift+R keystroke. A .webm file does appear in the Videos
  folder but it is empty. The orange circle does appear in the upper
  corner, but it will not go away.

  Further Ctrl+Alt+Shift+R strokes do not make a new .webm file or
  remove the orange circle.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  Uname: Linux 5.15.0-rc4-soffixes x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 11:11:13 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-12 (12 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948647/+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 1948647] Re: Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange circle persists

** Attachment added: "vainfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948647/+attachment/5535832/+files/vainfo.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/1948647

Title:
  Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange
  circle persists

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Running 21.10 and Gnome 40.4 the screen recording no longer works with
  the Ctrl+Alt+Shift+R keystroke. A .webm file does appear in the Videos
  folder but it is empty. The orange circle does appear in the upper
  corner, but it will not go away.

  Further Ctrl+Alt+Shift+R strokes do not make a new .webm file or
  remove the orange circle.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  Uname: Linux 5.15.0-rc4-soffixes x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 11:11:13 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-12 (12 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948647/+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 1948647] Re: Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange circle persists

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948647/+attachment/5535834/+files/journal.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/1948647

Title:
  Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange
  circle persists

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Running 21.10 and Gnome 40.4 the screen recording no longer works with
  the Ctrl+Alt+Shift+R keystroke. A .webm file does appear in the Videos
  folder but it is empty. The orange circle does appear in the upper
  corner, but it will not go away.

  Further Ctrl+Alt+Shift+R strokes do not make a new .webm file or
  remove the orange circle.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  Uname: Linux 5.15.0-rc4-soffixes x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 11:11:13 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-12 (12 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948647/+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 1948667] [NEW] Elantech Touchpad not working on Fujitsu E5410

2021-10-25 Thread Peter Smith

Public bug reported:

The Fujitsu E5410 (model type 5E14A1 according to the bottom sticker) is
supplied with an Elantech(?) Touchpad. This apparently requires i2c_hid
and does not properly work in Ubuntu 20.04. It seems also to interfere
with the (internal) keyboard.

Problem behavior:

booting Ubuntu 20.04 with kernel 5.11.0-27:
keyboard works, touchpad is not recognized.
Running sudo modprobe i2c_hid manually from a terminal sometimes results in the 
touchpad working. Sometimes however the keyboard does not recognize any input 
anymore. After rebooting, approx 1/2 times the keyboard is not working anymore.

Making sudo modprobe i2c_hid permanent via /etc/modules-load.d/
permanently crashes the keyboard on startup such that it is impossible
to log in.

booting with kernel 5.14.0-1004-oem:
sudo modprobe i2c_hid has no effect, the touchpad is never recognized. Booting 
with this kernel, 9/10 times the keyboard is not recognized at all and one 
cannot log in. Permanently loading the module via /etc/modules-load.d has no 
effect.

booting with kernel 5.14.9-051409 (a mainline kernel from 
ppa:tuxinvader/lts-mainline ):
modprobing the i2c_hid module has no effect. The keyboard works.

probably not just xserver-xorg-input-libinput but also i2c_hid is
affected. However w.r.t.
https://wiki.ubuntu.com/DebuggingTouchpadDetection and without being
able to further diagnose the problem I filed this bug against xserver-
xorg-input-libinput.


(likely) relevant output of cat /proc/bus/input/devices:

I: Bus=0018 Vendor=04f3 Product=308a Version=0100
N: Name="0X45 0X4C 0X41 0X4E 04F3:308A Touchpad"
P: Phys=i2c-0X45 0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00
S: Sysfs=/devices/pci:00/:00:15.3/i2c_designware.1/i2c-2/i2c-0X45 0X4C 
0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00/0018:04F3:308A.0002/input/input26
U: Uniq=
H: Handlers=mouse2 event14 
B: PROP=1
B: EV=1b
B: KEY=e520 3 0 0 0 0
B: ABS=2e08003
B: MSC=20


I: Bus=0018 Vendor=04f3 Product=308a Version=0100
N: Name="0X45 0X4C 0X41 0X4E 04F3:308A Mouse"
P: Phys=i2c-0X45 0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00
S: Sysfs=/devices/pci:00/:00:15.3/i2c_designware.1/i2c-2/i2c-0X45 0X4C 
0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00/0018:04F3:308A.0002/input/input24
U: Uniq=
H: Handlers=mouse1 event13 
B: PROP=0
B: EV=17
B: KEY=3 0 0 0 0
B: REL=3
B: MSC=10

I: Bus=0011 Vendor=0001 Product=0001 Version=ab54
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input2
U: Uniq=
H: Handlers=sysrq kbd event2 leds 
B: PROP=0
B: EV=120013
B: KEY=40200 3803078f800d001 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor= Product= Version=
N: Name="Fujitsu FUJ02E3"
P: Phys=FUJ02E3/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/FUJ02E3:00/input/input7
U: Uniq=
H: Handlers=rfkill kbd event3 
B: PROP=0
B: EV=13
B: KEY=4 0 0 0 0 1810c00 30 0 0
B: MSC=10

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-input-libinput 0.29.0-1
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 25 13:50:39 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
InstallationDate: Installed on 2021-10-04 (21 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b6a0 Chicony Electronics Co., Ltd FJ Camera
 Bus 001 Device 004: ID 8087:0026 Intel Corp. 
 Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=521e4756-042b-473e-adce-11bbb047275b ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-input-libinput
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2021
dmi.bios.release: 2.20
dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
dmi.bios.version: Version 2.20
dmi.board.name: FJNB2D6
dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
dmi.board.version: A2
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
dmi.chassis.version: LIFEBOOK E5410
dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.20:bd07/06/2021:br2.20:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:
dmi.product.family: LIFEBOOK-FTS
dmi.product.name: LIFEBOOK E5410
dmi.product.sku: SK00

[Desktop-packages] [Bug 1948665] [NEW] No stylus found for Wacom HID 49A3 Pen (Latitude 7320)

Public bug reported:

I have a Dell Latitude 7320 Detachable with a 7320 Detachable Active Pen
(PN7320A). The pen mostly works, aside from a periodic bug
(https://github.com/linuxwacom/input-wacom/issues/281). It shows up as a
Wacom pen from libinput:

Device:   Wacom HID 49A3 Pen
Kernel:   /dev/input/event4
Group:6
Seat: seat0, default
Size: 274x183mm
Capabilities: tablet 
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock:n/a
Left-handed:  n/a
Nat.scrolling:n/a
Middle emulation: n/a
Calibration:  identity matrix
Scroll methods:   none
Click methods:none
Disable-w-typing: n/a
Accel profiles:   none
Rotation: n/a

I cannot configure it via the Wacom Tablet settings in the control
center. It always says "No stylus found" despite being able to use the
stylus with applications such as Xournal++.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-control-center 1:40.0-1ubuntu5
Uname: Linux 5.15.0-rc4-soffixes x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 25 13:47:11 2021
InstallationDate: Installed on 2021-10-12 (12 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

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


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

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

Title:
  No stylus found for Wacom HID 49A3 Pen (Latitude 7320)

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

Bug description:
  I have a Dell Latitude 7320 Detachable with a 7320 Detachable Active
  Pen (PN7320A). The pen mostly works, aside from a periodic bug
  (https://github.com/linuxwacom/input-wacom/issues/281). It shows up as
  a Wacom pen from libinput:

  Device:   Wacom HID 49A3 Pen
  Kernel:   /dev/input/event4
  Group:6
  Seat: seat0, default
  Size: 274x183mm
  Capabilities: tablet 
  Tap-to-click: n/a
  Tap-and-drag: n/a
  Tap drag lock:n/a
  Left-handed:  n/a
  Nat.scrolling:n/a
  Middle emulation: n/a
  Calibration:  identity matrix
  Scroll methods:   none
  Click methods:none
  Disable-w-typing: n/a
  Accel profiles:   none
  Rotation: n/a

  I cannot configure it via the Wacom Tablet settings in the control
  center. It always says "No stylus found" despite being able to use the
  stylus with applications such as Xournal++.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-control-center 1:40.0-1ubuntu5
  Uname: Linux 5.15.0-rc4-soffixes x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 13:47:11 2021
  InstallationDate: Installed on 2021-10-12 (12 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

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

2021-10-25 Thread jclaverogarcia

*** Bug 2016947 has been marked as a duplicate of this bug. ***

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

Title:
  gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
  [st-focus-manager.c:199]

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

Bug description:
  https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae

  ---

  Testing daily Ubuntu Impish ISO 2021-07-19

  Test machine : Dell [Latitude] 7280 (i5-7300U,

  Received the error message - Ubuntu has experienced an internal error
  ...do you want to send ...etc, etc.

  This bug occurred when I was scrolling up and down on the "Settings"
  app and selected "Appearance".

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 19 12:15:54 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
   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-07-19 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

2021-10-25 Thread andres.rico

*** Bug 2016920 has been marked as a duplicate of this bug. ***

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

Title:
  gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
  [st-focus-manager.c:199]

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

Bug description:
  https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae

  ---

  Testing daily Ubuntu Impish ISO 2021-07-19

  Test machine : Dell [Latitude] 7280 (i5-7300U,

  Received the error message - Ubuntu has experienced an internal error
  ...do you want to send ...etc, etc.

  This bug occurred when I was scrolling up and down on the "Settings"
  app and selected "Appearance".

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 19 12:15:54 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
   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-07-19 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1936826/+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 1948652] Re: Firefox do not save tabs

2021-10-25 Thread Alexander

1) When open some tabs and quit Firefox by Ctrl+Q session doesn't restore
2) When delete profile (~/.mozilla) and recreate it, session restore but
3) When close last tab with Ctrl+w, run firefox, open some tabs, quit with 
Ctrl+Q and run again, session doesn't restore

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

Title:
  Firefox do not save tabs

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  1) % lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  2) % apt-cache policy firefox
  firefox:
Установлен: 93.0+build1-0ubuntu0.20.04.1
Кандидат:   93.0+build1-0ubuntu0.20.04.1
Таблица версий:
   *** 93.0+build1-0ubuntu0.20.04.1 500
  500 http://ua.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   75.0+build3-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) After start Firefox expected to restore previous session
  4) Firefox start with new tab

  If I close Firefox by Ctrl-Q with opened tabs and start it again Firefox 
opens with one new tab. When profile was recreated issue was gone but appeared 
again after Firefox was closed by Ctrl-W.
  The option "Restore previous session" is on. Without extension behavior the 
same. I'm not sure but this begins after last update of Firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948652/+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 1945203] Re: Wayland: Useage of touchscreen on dock freezes the dock

** Package changed: xwayland (Ubuntu) => mutter (Ubuntu)

** Description changed:

  General information:
  
  Ubuntu 21.04
- X-Wayland
  Device: Dell XPS13 2-in-1
  
  When using the touchscreen to start or switch between apps in the dock,
  the dock freezes after 1-5 events. A tooltip is shown permanently and
  the dock is no longer responsive and can't be used for app switching
  anymore. The top menu bar with wifi and bt settings etc. is also frozen.
  
- This problem only occurs with Xwayland, not with classic X. And only
+ This problem only occurs with Wayland, not with classic X. And only
  touch events trigger the freeze. Other input devices such as the
  touchpad, the digitizer or an external mouse do not trigger this
  problem.
  
  Workaround:
  Alt+Tab is not affected and can still be used for app switching, but it sucks 
if the device is in tablet mode.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xwayland 2:21.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-36.40-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 27 15:05:59 2021
  EcryptfsUse: Yes
  InstallationDate: Installed on 2021-09-15 (12 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xwayland
  UpgradeStatus: Upgraded to hirsute on 2021-09-25 (1 days ago)

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

Title:
  Wayland: Useage of touchscreen on dock freezes the dock

Status in mutter package in Ubuntu:
  New

Bug description:
  General information:

  Ubuntu 21.04
  Device: Dell XPS13 2-in-1

  When using the touchscreen to start or switch between apps in the
  dock, the dock freezes after 1-5 events. A tooltip is shown
  permanently and the dock is no longer responsive and can't be used for
  app switching anymore. The top menu bar with wifi and bt settings etc.
  is also frozen.

  This problem only occurs with Wayland, not with classic X. And only
  touch events trigger the freeze. Other input devices such as the
  touchpad, the digitizer or an external mouse do not trigger this
  problem.

  Workaround:
  Alt+Tab is not affected and can still be used for app switching, but it sucks 
if the device is in tablet mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xwayland 2:21.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-36.40-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 27 15:05:59 2021
  EcryptfsUse: Yes
  InstallationDate: Installed on 2021-09-15 (12 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xwayland
  UpgradeStatus: Upgraded to hirsute on 2021-09-25 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1945203/+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 1940504] Re: Support Alder Lake P graphics

2021-10-25 Thread Timo Aaltonen

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Support Alder Lake P graphics

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Focal:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  [SRU Justification:linux-firmware]

  [Impact]

  It shows the firmware is missing, and runtime power management has been
  disabled:

i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.

  [Fix]

  Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").

  [Test Case]

  Verified on Intel ADL-M/ADL-P RVPs.

  [Where problems could occur]

  It's a new firmware for new GPU, not possible to introduce
  regressions.

  [Other Info]

  Impish has this already. And while ADL-P/M support begins since v5.14,
  only focal (for oem-5.14) is being nominated.

  =

  [SRU Justification:mesa,libdrm]

  NOTE: this is for focal only, hirsute/impish do not and will not have
  kernel support for this.

  [Impact]

  ADL-P machines need to use the native driver.

  [Fix]

  Backport support from upstream.

  libdrm: a single patch from 2.4.107
  mesa: three commits to add pci-id's and a workaround
  kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports

  [Test case]
  Boot a machine and check that it's using the native driver and that the usual 
workloads are fine.

  [Where things could go wrong]
  For older gpu's there's little to go wrong, since the commits are for ADL-P 
only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1948652] Re: Firefox do not save tabs

Ctrl+W will close the currently focused tab. If you have only one tab
open, this tab will be closed and firefox will exit. It is therefore
expected that at the next start, nothing will be restored. If you want
your one tab to be restored at the next startup, use Ctrl+Q or Alt+F4 to
close Firefox.

Or did you have more than one tab open?

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

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

Title:
  Firefox do not save tabs

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  1) % lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  2) % apt-cache policy firefox
  firefox:
Установлен: 93.0+build1-0ubuntu0.20.04.1
Кандидат:   93.0+build1-0ubuntu0.20.04.1
Таблица версий:
   *** 93.0+build1-0ubuntu0.20.04.1 500
  500 http://ua.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   75.0+build3-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) After start Firefox expected to restore previous session
  4) Firefox start with new tab

  If I close Firefox by Ctrl-Q with opened tabs and start it again Firefox 
opens with one new tab. When profile was recreated issue was gone but appeared 
again after Firefox was closed by Ctrl-W.
  The option "Restore previous session" is on. Without extension behavior the 
same. I'm not sure but this begins after last update of Firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948652/+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 1948647] Re: Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange circle persists

I also wonder if this is caused by you installing 21.04 and then
upgrading to 21.10...

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

Title:
  Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange
  circle persists

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Running 21.10 and Gnome 40.4 the screen recording no longer works with
  the Ctrl+Alt+Shift+R keystroke. A .webm file does appear in the Videos
  folder but it is empty. The orange circle does appear in the upper
  corner, but it will not go away.

  Further Ctrl+Alt+Shift+R strokes do not make a new .webm file or
  remove the orange circle.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  Uname: Linux 5.15.0-rc4-soffixes x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 11:11:13 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-12 (12 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948647/+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 1948647] Re: Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange circle persists

I can't seem to reproduce the bug in 21.10 here. It works properly for
me.

Please:

1. Reboot fresh.

2. Reproduce the bug again.

3. Run these commands in a Terminal:

   journalctl -b0 > journal.txt
   sudo apt install vainfo
   vainfo > vainfo.txt
   dpkg -l > packages.txt

4. Attach the resulting text files here.


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

Title:
  Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange
  circle persists

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Running 21.10 and Gnome 40.4 the screen recording no longer works with
  the Ctrl+Alt+Shift+R keystroke. A .webm file does appear in the Videos
  folder but it is empty. The orange circle does appear in the upper
  corner, but it will not go away.

  Further Ctrl+Alt+Shift+R strokes do not make a new .webm file or
  remove the orange circle.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  Uname: Linux 5.15.0-rc4-soffixes x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 11:11:13 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-12 (12 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948647/+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 1948652] [NEW] Firefox do not save tabs

2021-10-25 Thread Alexander

Public bug reported:

1) % lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04

2) % apt-cache policy firefox
firefox:
  Установлен: 93.0+build1-0ubuntu0.20.04.1
  Кандидат:   93.0+build1-0ubuntu0.20.04.1
  Таблица версий:
 *** 93.0+build1-0ubuntu0.20.04.1 500
500 http://ua.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
100 /var/lib/dpkg/status
 75.0+build3-0ubuntu1 500
500 http://ua.archive.ubuntu.com/ubuntu focal/main amd64 Packages

3) After start Firefox expected to restore previous session
4) Firefox start with new tab

If I close Firefox by Ctrl-Q with opened tabs and start it again Firefox opens 
with one new tab. When profile was recreated issue was gone but appeared again 
after Firefox was closed by Ctrl-W.
The option "Restore previous session" is on. Without extension behavior the 
same. I'm not sure but this begins after last update of Firefox

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

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

Title:
  Firefox do not save tabs

Status in firefox package in Ubuntu:
  New

Bug description:
  1) % lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  2) % apt-cache policy firefox
  firefox:
Установлен: 93.0+build1-0ubuntu0.20.04.1
Кандидат:   93.0+build1-0ubuntu0.20.04.1
Таблица версий:
   *** 93.0+build1-0ubuntu0.20.04.1 500
  500 http://ua.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   75.0+build3-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) After start Firefox expected to restore previous session
  4) Firefox start with new tab

  If I close Firefox by Ctrl-Q with opened tabs and start it again Firefox 
opens with one new tab. When profile was recreated issue was gone but appeared 
again after Firefox was closed by Ctrl-W.
  The option "Restore previous session" is on. Without extension behavior the 
same. I'm not sure but this begins after last update of Firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948652/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()

** Description changed:

+ * Impact
+ 
+ The pulseaudio service sometime segfaults on session closing which
+ trigger a bug report dialog
+ 
+ * Test plan
+ 
+ Log out of a desktop session and back in, there should be no error
+ prompt
+ 
+ The issue isn't triggered only randomly it seems so it might be easier to 
check that reports stop on
  https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e
+ 
+ * Where problems could occur
+ 
+ The change is in the X session closing handling so shouldn't impact on
+ normal use, if incorrect the fix could lead to increase the chance of
+ hitting the segfault when an Xsession is closed
+ 
  
  ---
  
  Installing Xubuntu Impish daily ISO 04092021
  
  After install I rebooted - applied updates and then rebooted again-
  
  the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() )
  occurred after logging in.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kx  847 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Sep  4 16:43:45 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-04 (0 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6
   _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6
   ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so
  Title: pulseaudio crashed with SIGSEGV in _IceTransClose()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN51WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V14-IIL
  dmi.ec.firmware.release: 1.51
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL:
  dmi.product.family: V14-IIL
  dmi.product.name: 82C4
  dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL
  dmi.product.version: Lenovo V14-IIL
  dmi.sys.vendor: LENOVO
  separator:

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

Title:
  pulseaudio crashed with SIGSEGV in _IceTransClose()

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  * Impact

  The pulseaudio service sometime segfaults on session closing which
  trigger a bug report dialog

  * Test plan

  Log out of a desktop session and back in, there should be no error
  prompt

  The issue isn't triggered only randomly it seems so it might be easier to 
check that reports stop on
  https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e

  * Where problems could occur

  The change is in the X session closing handling so shouldn't impact on
  normal use, if incorrect the fix could lead to increase the chance of
  hitting the segfault when an Xsession is closed

  
  ---

  Installing Xubuntu Impish daily ISO 04092021

  After install I rebooted - applied updates and then rebooted again-

  the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() )
  occurred after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kx  847 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Sep  4 16:43:45 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-04 (0 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6
   _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   IceCloseConnection () from

[Desktop-packages] [Bug 1948647] [NEW] Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange circle persists

Public bug reported:

Running 21.10 and Gnome 40.4 the screen recording no longer works with
the Ctrl+Alt+Shift+R keystroke. A .webm file does appear in the Videos
folder but it is empty. The orange circle does appear in the upper
corner, but it will not go away.

Further Ctrl+Alt+Shift+R strokes do not make a new .webm file or remove
the orange circle.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.5-1ubuntu2
Uname: Linux 5.15.0-rc4-soffixes x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 25 11:11:13 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-10-12 (12 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
RelatedPackageVersions: mutter-common 40.5-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

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


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

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

Title:
  Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange
  circle persists

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Running 21.10 and Gnome 40.4 the screen recording no longer works with
  the Ctrl+Alt+Shift+R keystroke. A .webm file does appear in the Videos
  folder but it is empty. The orange circle does appear in the upper
  corner, but it will not go away.

  Further Ctrl+Alt+Shift+R strokes do not make a new .webm file or
  remove the orange circle.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  Uname: Linux 5.15.0-rc4-soffixes x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 11:11:13 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-12 (12 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948647/+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 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken

2021-10-25 Thread Bug Watch Updater

** Changed in: dash-to-dock
   Status: Unknown => New

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

Title:
  Click actions "previews" and "minimize-or-previews" are broken

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

Bug description:
  Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or-
  previews" options no longer work as expected.

  For "previews":
  No previews are shown when clicking on the app icon.

  For "minimize-or-previews":
  When multiple windows of the same application are open and I click on the app 
icon, no previews are shown anymore.

  
  Schema: org.gnome.shell.extensions.dash-to-dock
  Name: click-action
  Value: "minimize-or-previews"
  Value: "previews"

  
  Description:  Ubuntu 21.10
  Release:  21.10

  gnome-shell-extension-ubuntu-dock:
Installed: 70~ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 11:32:51 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-21 (1090 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1947445/+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 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken

2021-10-25 Thread Paul White

Upstream report:
https://github.com/micheleg/dash-to-dock/issues/1545

** Bug watch added: github.com/micheleg/dash-to-dock/issues #1545
   https://github.com/micheleg/dash-to-dock/issues/1545

** Also affects: dash-to-dock via
   https://github.com/micheleg/dash-to-dock/issues/1545
   Importance: Unknown
   Status: Unknown

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

Title:
  Click actions "previews" and "minimize-or-previews" are broken

Status in Dash to dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or-
  previews" options no longer work as expected.

  For "previews":
  No previews are shown when clicking on the app icon.

  For "minimize-or-previews":
  When multiple windows of the same application are open and I click on the app 
icon, no previews are shown anymore.

  
  Schema: org.gnome.shell.extensions.dash-to-dock
  Name: click-action
  Value: "minimize-or-previews"
  Value: "previews"

  
  Description:  Ubuntu 21.10
  Release:  21.10

  gnome-shell-extension-ubuntu-dock:
Installed: 70~ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 11:32:51 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-21 (1090 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1947445/+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 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore

2021-10-25 Thread Michael Kuster

i installed the following package:

https://launchpad.net/ubuntu/+source/nautilus/1:3.36.3-0ubuntu1.20.04.1/+build/22328302/+files/nautilus_3.36.3-0ubuntu1.20.04.1_amd64.deb

with nautilus all works fine. well done.

but copying desktop items is still the same. looks like the gnome-shell-
extension is not part of this package.

there was no file change under this path:
/usr/share/gnome-shell/extensions/desktop-icons@csoriano

where can i find the package for updating the gnome-shell-extension?

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

Title:
  Nautilus doesn't copy filenames for paste to other programs anymore

Status in Nautilus:
  New
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Confirmed
Status in gnome-shell-extension-desktop-icons source package in Focal:
  Confirmed
Status in nautilus source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * One of the upstream changes changed behavior of clipboard copying 
files/directories from nautilus to applications accepting text only (e.g. 
gnome-terminal). In such case the pasted input is prefixed with:
  x-special/nautilus-clipboard
  copy file://

  This was not the case in earlier releases and this change has been
  reverted in later upstream releases.

  Reverting the problematic commit will fix the usecase reported in this
  bug (and all applications where copying from Nautilus and pasting the
  data into a text-based input makes sense), but will break copying
  to/from Desktop Icons extension.

  I recommend reporting the Desktop Icons extension issue (present
  already in every later Ubuntu release) in a separate bug and track the
  fix there.

  [Test Plan]

   1. Open nautilus.
   2. Right-click on any file or directory and select 'Copy' from the context 
menu.
   3. Open gnome-terminal and right-click paste the contents of the clipboard.

  Expected result: path of the file/directory is pasted in the terminal.
  Actual result: pasted input is prefixed with "x-special/nautilus-clipboard
  copy file://"

  [Where problems could occur]

   * There are some workarounds listed in the upstream bug so fixing the root 
cause may break environments with those workarounds in place.
   * Reverting this change also limits functionality of the desktop icons 
extension shipped with Ubuntu. Namely: before the new clipboard API is used in 
desktop-icons (merge requests [1] and [2]) copying and pasting to/from the 
desktop extension to a nautilus will not be possible via keyboard shortcuts or 
context menu (dragging and dropping will remain to work).

  [1] 
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186
  [2] 
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195

  [Other Info]

  Original bug description:

  Until Ubuntu 18.10 Nautilus does copy all selected filenames in simple
  Text format and this way you cold paste the selected files as a list
  to other programs: for example into the texteditor gedit. This was a
  very useful function if you have, for example, to upload a file to
  webmail or other web-service. You cold copy the file within nautilus
  and paste it directliy to the selection dialog or webfield to upload
  the file.

  Or if you wanted a simple List of all your files in a folder you where
  able to select all files with nautilus, copy and paste into gedit.
  This is not possible anymore. The output of natilus looks now like
  this:

  x-special/nautilus-clipboard
  copy
  file:///home//Schreibtisch/new%20document.txt

  Until Ubuntu 18.10 this looks like this:

  /home//Schreibtisch/new document.txt

  Steps to reproduce:
  1. Select files with nautilus
  2. Press Ctrl+C
  3. open gedit
  4. press Ctrl+V

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.1-0ubuntu0.19.04.0
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 15:06:14 2019
  ExecutablePath: /usr/bin/nautilus
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1843588/+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 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

2021-10-25 Thread Marius Gedminas

I've seen this three times now on Ubuntu 21.10 (GNOME 40).  I don't
recall ever seeing it on Ubuntu 20.10.

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1532508/+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 1948641] Re: can not change dock bar position

Thanks for the bug report. I can't seem to reproduce any such bug in
that setting. Can you attach a video of the problem? You can record a
video using Shift+Ctrl+Alt+R and find the file in ~/Videos.

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

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

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

Title:
  can not change dock bar position

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

Bug description:
  
  dock bar is fixed at the bottom.

  when u want to change the pisition, is is still fixed at the bottom.

  method:

  settings->appearence->dock->position

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Mon Oct 25 15:45:45 2021
  DistUpgraded: 2021-10-22 13:55:14,850 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ca]
  InstallationDate: Installed on 2018-04-28 (1276 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Latitude E7240
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=794fdd3e-74af-4db0-8e0a-ca94eb02e241 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to impish on 2021-10-22 (3 days ago)
  dmi.bios.date: 02/01/2018
  dmi.bios.release: 65.25
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A25
  dmi.board.name: 08230Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA25:bd02/01/2018:br65.25:svnDellInc.:pnLatitudeE7240:pvr00:rvnDellInc.:rn08230Y:rvrA00:cvnDellInc.:ct9:cvr:sku05CA:
  dmi.product.name: Latitude E7240
  dmi.product.sku: 05CA
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1948641/+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 1948641] [NEW] can not change dock bar position

2021-10-25 Thread marszhang

Public bug reported:


dock bar is fixed at the bottom.

when u want to change the pisition, is is still fixed at the bottom.

method:

settings->appearence->dock->position

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Mon Oct 25 15:45:45 2021
DistUpgraded: 2021-10-22 13:55:14,850 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: impish
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ca]
InstallationDate: Installed on 2018-04-28 (1276 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. Latitude E7240
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=794fdd3e-74af-4db0-8e0a-ca94eb02e241 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to impish on 2021-10-22 (3 days ago)
dmi.bios.date: 02/01/2018
dmi.bios.release: 65.25
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A25
dmi.board.name: 08230Y
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA25:bd02/01/2018:br65.25:svnDellInc.:pnLatitudeE7240:pvr00:rvnDellInc.:rn08230Y:rvrA00:cvnDellInc.:ct9:cvr:sku05CA:
dmi.product.name: Latitude E7240
dmi.product.sku: 05CA
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug impish ubuntu

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

Title:
  can not change dock bar position

Status in xorg package in Ubuntu:
  New

Bug description:
  
  dock bar is fixed at the bottom.

  when u want to change the pisition, is is still fixed at the bottom.

  method:

  settings->appearence->dock->position

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Mon Oct 25 15:45:45 2021
  DistUpgraded: 2021-10-22 13:55:14,850 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ca]
  InstallationDate: Installed on 2018-04-28 (1276 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Latitude E7240
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=794fdd3e-74af-4db0-8e0a-ca94eb02e241 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to impish on 2021-10-22 (3 days ago)
  dmi.bios.date: 02/01/2018
  dmi.bios.release: 65.25
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A25
  dmi.board.name: 08230Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA25:bd02/01/2018:br65.25:svnDellInc.:pnLatitudeE7240:pvr00:rvnDellInc.:rn08230Y:rvrA00:cvnDellInc.:ct9:cvr:sku05CA:
  dmi.product.name: Latitude E7240
  dmi.product.sku: 05CA
  dmi.product.version: 00

[Desktop-packages] [Bug 1940545] Re: Update Mesa to mesa-21.1.7 on Ubuntu 20.04

2021-10-25 Thread Launchpad Bug Tracker

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

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

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

Title:
  Update Mesa to mesa-21.1.7 on Ubuntu 20.04

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  With the recent MR
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to
  Mesa, we (NVIDIA) have added ability to GBM to dynamically load the
  backends. So we request to upgrade mesa libs to its latest version
  (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our
  development.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1948616] Re: nautilus crashes when selecting bookmark in the dock

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

** This bug has been marked a duplicate of bug 1934579
   Nautilus crashes when opening places from the dock contextmenu

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

Title:
  nautilus crashes when selecting bookmark in the dock

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nautilus crashes on attempt to launch bookmarked location from the
  dock.

  Steps to reproduce.

  1. Open new Nautilus window from the dock.
  2. Right-click on Nautilus icon in the dock. There will be an option to open 
a new window and a list of bookmarks.
  3. Click on any bookmark to open new window at desired location
  4. Nautilus crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: nautilus 1:40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 24 22:30:34 2021
  GsettingsChanges:
   
  InstallationDate: Installed on 2021-10-21 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince40.4-2
   file-roller   3.40.0-2
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu2
   nautilus-share0.7.3-2ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1948616/+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 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken

2021-10-25 Thread Paul White

Can confirm. In order to see the previews you have to right-click on the
application icon and then click on 'All Windows' in order to see the
window preview. Previously the previews would be shown when left
clicking on the application icon.

The latest version of Dash to Dock released on 17th October retains the
expected functionality so an issue specific to Ubuntu Dock.

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

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

Title:
  Click actions "previews" and "minimize-or-previews" are broken

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

Bug description:
  Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or-
  previews" options no longer work as expected.

  For "previews":
  No previews are shown when clicking on the app icon.

  For "minimize-or-previews":
  When multiple windows of the same application are open and I click on the app 
icon, no previews are shown anymore.

  
  Schema: org.gnome.shell.extensions.dash-to-dock
  Name: click-action
  Value: "minimize-or-previews"
  Value: "previews"

  
  Description:  Ubuntu 21.10
  Release:  21.10

  gnome-shell-extension-ubuntu-dock:
Installed: 70~ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 11:32:51 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-21 (1090 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1947445/+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 1948362] Re: UnboundLocalError: local variable 't' referenced before assignment

2021-10-25 Thread yoloClin

Ran into this exact issue, and modifying line 198 to

```
 if vendor.find('8086') != -1 or vendor.lower().find('1002') != -1:
```

successfully allowed me to use the utility. Thanks @Lialosiu.

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

Title:
  UnboundLocalError: local variable 't' referenced before assignment

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  ```
  Traceback (most recent call last):
File "/usr/bin/prime-select", line 458, in 
  switcher.enable_profile(arg)
File "/usr/bin/prime-select", line 223, in enable_profile
  if not self._has_integrated_gpu():
File "/usr/bin/prime-select", line 198, in _has_integrated_gpu
  if t.find('8086') != -1 or t.lower().find('1002') != -1:
  UnboundLocalError: local variable 't' referenced before assignment
  ```

  at file `prime-select`, line 198

  https://git.launchpad.net/ubuntu/+source/nvidia-prime/tree/prime-
  select#n198

  that `t` should be `vendor` I think. :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1948362/+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 1948632] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all

2021-10-25 Thread akbar riyadi

Public bug reported:

only HDMI detected, no speaker or headphone hardware

 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.10.2-051002-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nli 988 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Mon Oct 25 15:06:53 2021
InstallationDate: Installed on 2021-10-21 (4 days ago)
InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nli 988 F pulseaudio
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2021
dmi.bios.release: 1.19
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: BSR7IPHK-68E4D-AVI-V19
dmi.board.name: GCG605WC40
dmi.board.vendor: AVITA
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: AVITA
dmi.chassis.version: Default string
dmi.ec.firmware.release: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrBSR7IPHK-68E4D-AVI-V19:bd09/06/2021:br1.19:efr1.0:svnAVITA:pnNE14A2:pvrDefaultstring:rvnAVITA:rnGCG605WC40:rvrDefaultstring:cvnAVITA:ct10:cvrDefaultstring:
dmi.product.family: CN6814G
dmi.product.name: NE14A2
dmi.product.sku: CN68E4C45M7ID-MB00B
dmi.product.version: Default string
dmi.sys.vendor: AVITA
modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-10-23T15:02:40.410508

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  only HDMI detected, no speaker or headphone hardware

   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.10.2-051002-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nli 988 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Oct 25 15:06:53 2021
  InstallationDate: Installed on 2021-10-21 (4 days ago)
  InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nli 988 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BSR7IPHK-68E4D-AVI-V19
  dmi.board.name: GCG605WC40
  dmi.board.vendor: AVITA
  dmi.board.version: Default string

[Desktop-packages] [Bug 1746656] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log()

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

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

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_log_handler() from wl_log()

Status in xorg-server package in Ubuntu:
  Confirmed
Status in xwayland package in Ubuntu:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1746656/+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 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.

2021-10-25 Thread Jerry Lee

These patches are used for newer Foxconn/Quectel modems :
* whose drivers are using the WWAN subsystem in the kernel 5.13. ( this OEM
project uses customized kernel )
* communicated to the ModemManager service via the MBIM protocol

These patches will not be used if the modem can't meet the above
requirements.

After checking Ubuntu certificated modems, there is no modem can meet
these 2 requirement to do the regression test.

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

Title:
Support manual firmware upgrading for Foxconn and Quectel modems.

Status in OEM Priority Project:
In Progress
Status in modemmanager package in Ubuntu:
Incomplete

Bug description:
[Impact]

The modem certification requires that different modem firmware is used for
different network carrier.
This needs the firmware upgrading capability during the modem certification
process.

The firmware upgrading was verified using the patched ModemManager v 1.16.6
with the following 2 modems:
* Foxconn SDX55 T99W175 5G sub6 PCIE Modem
* Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

[Test Plan]

[Where problems could occur]

The requested upstream patches are for these 2 specific modems.
This should not affect existing generic functions and other modems.

[Other Info]

The firmware and the upgrading utilities can be downloaded from the following
link:
* LP#1943774 for Quectel modems
* LP#1943780 for Foxconn modems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions

[Desktop-packages] [Bug 1948617] Re: gnome-shell crashed with SIGTRAP in /usr/lib/x86_64-linux-gnu/libc.so.6+1a476