[Desktop-packages] [Bug 1961460] Re: My laptop shuts off randomly after displaying a black screen

2022-02-18 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (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/1961460

Title:
  My laptop shuts off randomly after displaying a black screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.4 LTS
  N: Unable to locate package pkgname
  My latop screen turns black randomly and it has to do something with graphics 
driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 19 07:06:41 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 (Whiskey Lake) 
[1025:129a]
 Subsystem: Acer Incorporated [ALI] GP108BM [GeForce MX250] [1025:129a]
  InstallationDate: Installed on 2022-02-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Acer Swift SF314-55G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=8e45e071-d3dc-4ff9-9a0b-b18cd73b8609 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2018
  dmi.bios.release: 1.7
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Default string
  dmi.board.name: MILLER_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.07
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.07:bd12/24/2018:br1.7:efr1.8:svnAcer:pnSwiftSF314-55G:pvrV1.07:rvnWL:rnMILLER_WL:rvrV1.07:cvnAcer:ct10:cvrV1.07:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-55G
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1961460/+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 1961460] [NEW] My laptop shuts off randomly after displaying a black screen

2022-02-18 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Ubuntu 20.04.4 LTS
N: Unable to locate package pkgname
My latop screen turns black randomly and it has to do something with graphics 
driver.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 19 07:06:41 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] UHD Graphics 620 (Whiskey Lake) 
[1025:129a]
   Subsystem: Acer Incorporated [ALI] GP108BM [GeForce MX250] [1025:129a]
InstallationDate: Installed on 2022-02-18 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: Acer Swift SF314-55G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=8e45e071-d3dc-4ff9-9a0b-b18cd73b8609 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/24/2018
dmi.bios.release: 1.7
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.07
dmi.board.asset.tag: Default string
dmi.board.name: MILLER_WL
dmi.board.vendor: WL
dmi.board.version: V1.07
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.07
dmi.ec.firmware.release: 1.8
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.07:bd12/24/2018:br1.7:efr1.8:svnAcer:pnSwiftSF314-55G:pvrV1.07:rvnWL:rnMILLER_WL:rvrV1.07:cvnAcer:ct10:cvrV1.07:sku:
dmi.product.family: Swift 3
dmi.product.name: Swift SF314-55G
dmi.product.sku: 
dmi.product.version: V1.07
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu
-- 
My laptop shuts off randomly after displaying a black screen
https://bugs.launchpad.net/bugs/1961460
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg 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 1961456] [NEW] [iMac7, 1, Realtek ALC889A, Speaker, Internal] Sound is distorted

2022-02-18 Thread Eugene Golovin
Public bug reported:

Sound quality is poor. Like I am listening to very low bitrate audio.
Changing levels in alsa doesnt help. Deaf sound like under water.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  beatleman757 F pulseaudio
  beatleman   7666 F qashctl
 /dev/snd/pcmC0D0p:   beatleman757 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 19 03:36:30 2022
InstallationDate: Installed on 2022-02-18 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
Symptom_Card: Встроенное аудио - HDA Intel
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [iMac7,1, Realtek ALC889A, Speaker, Internal] Sound is distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/05/08
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: IM71.88Z.007A.B03.0803051705
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F42386C8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42386C8
dmi.modalias: 
dmi:bvnAppleInc.:bvrIM71.88Z.007A.B03.0803051705:bd03/05/08:br0.1:svnAppleInc.:pniMac7,1:pvr1.0:rvnAppleInc.:rnMac-F42386C8:rvrPVT:cvnAppleInc.:ct13:cvrMac-F42386C8:skuSystemSKU#:
dmi.product.family: Mac
dmi.product.name: iMac7,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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

Title:
  [iMac7,1, Realtek ALC889A, Speaker, Internal] Sound is distorted

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound quality is poor. Like I am listening to very low bitrate audio.
  Changing levels in alsa doesnt help. Deaf sound like under water.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  beatleman757 F pulseaudio
beatleman   7666 F qashctl
   /dev/snd/pcmC0D0p:   beatleman757 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 19 03:36:30 2022
  InstallationDate: Installed on 2022-02-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Встроенное аудио - HDA Intel
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [iMac7,1, Realtek ALC889A, Speaker, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/08
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM71.88Z.007A.B03.0803051705
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F42386C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42386C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM71.88Z.007A.B03.0803051705:bd03/05/08:br0.1:svnAppleInc.:pniMac7,1:pvr1.0:rvnAppleInc.:rnMac-F42386C8:rvrPVT:cvnAppleInc.:ct13:cvrMac-F42386C8:skuSystemSKU#:
  dmi.product.family: Mac
  dmi.product.name: iMac7,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1961456/+subscriptions


-- 
Mailing list: 

[Desktop-packages] [Bug 1961453] [NEW] ubuntu-dock crashes nautilus

2022-02-18 Thread Lex Ross
Public bug reported:

Right-clicking on nautilus pinned to the dock displays nautilus bookmars
shall at least one nautilus window is open. This is very convenient and
is expected behaviour from Unity dock.

Clicking on the bookmark however crashes nautilus with segmentation
fault. Confirmed on Ubuntu 20.04 and 22.04 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-ubuntu-dock 72~ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu77
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 18 18:26:01 2022
InstallationDate: Installed on 2021-10-21 (120 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to jammy on 2022-02-18 (0 days ago)

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


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

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

Title:
  ubuntu-dock crashes nautilus

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

Bug description:
  Right-clicking on nautilus pinned to the dock displays nautilus
  bookmars shall at least one nautilus window is open. This is very
  convenient and is expected behaviour from Unity dock.

  Clicking on the bookmark however crashes nautilus with segmentation
  fault. Confirmed on Ubuntu 20.04 and 22.04 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 18 18:26:01 2022
  InstallationDate: Installed on 2021-10-21 (120 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to jammy on 2022-02-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1961453/+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 1961452] [NEW] [Wayland] Super + nubmer doesn't switch windows

2022-02-18 Thread Lex Ross
Public bug reported:

In Wayland session using Super+ number key does not switch to the window
if the app is not pinned to the dock. Espetially when the Settings is
unpinned and is being launched as well as GNOME Terminal. It mostly
affects the Super+8 and Super+9. Even the Trash can be affected by this.

Under X.org session everything works fine. Except that the numbers are
not displayed on holding the Super key and aren't displayed properly no
matter what the session is, X.org or Wayland.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-ubuntu-dock 72~ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu77
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 18 18:11:12 2022
InstallationDate: Installed on 2021-10-21 (120 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to jammy on 2022-02-18 (0 days ago)

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


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

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

Title:
  [Wayland] Super + nubmer doesn't switch windows

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

Bug description:
  In Wayland session using Super+ number key does not switch to the
  window if the app is not pinned to the dock. Espetially when the
  Settings is unpinned and is being launched as well as GNOME Terminal.
  It mostly affects the Super+8 and Super+9. Even the Trash can be
  affected by this.

  Under X.org session everything works fine. Except that the numbers are
  not displayed on holding the Super key and aren't displayed properly
  no matter what the session is, X.org or Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 18 18:11:12 2022
  InstallationDate: Installed on 2021-10-21 (120 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to jammy on 2022-02-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1961452/+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 1711538] Re: Tap-to-click does not work on the GDM login screen

2022-02-18 Thread Lex Ross
Same thing with Ubuntu 22.04

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

Title:
  Tap-to-click does not work on the GDM login screen

Status in gnome-control-center:
  New
Status in GNOME Settings Daemon:
  Won't Fix
Status in gdm3 package in Ubuntu:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Tap-to-click does not work in GDM login

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.25.90.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Aug 18 16:16:56 2017
  InstallationDate: Installed on 2017-05-04 (105 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1711538/+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 1961444] [NEW] Wrong Energy value for an Asus Stylus

2022-02-18 Thread AdlerHorst
Public bug reported:

Stylus: ELAN25B2:00 04F3:25B1
All hardware: https://linux-hardware.org/?probe=1055dc7082 

Not a bug but it would be nice if the two clicks on the stylus (Right
and Left click)  could be configured with other keys or clicks.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu77
Architecture: amd64
CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb
CasperMD5CheckResult: fail
Date: Fri Feb 18 21:58:54 2022
DisplayManager: gdm3
GsettingsChanges:
 
InstallationDate: Installed on 2021-08-15 (187 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 LANGUAGE=de_CH:de
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_CH.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 41.3-1ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy third-party-packages

** Attachment added: "Stylus Energie.png"
   
https://bugs.launchpad.net/bugs/1961444/+attachment/5561927/+files/Stylus%20Energie.png

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

Title:
  Wrong Energy value for an Asus Stylus

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Stylus: ELAN25B2:00 04F3:25B1
  All hardware: https://linux-hardware.org/?probe=1055dc7082 

  Not a bug but it would be nice if the two clicks on the stylus (Right
  and Left click)  could be configured with other keys or clicks.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb
  CasperMD5CheckResult: fail
  Date: Fri Feb 18 21:58:54 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2021-08-15 (187 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANGUAGE=de_CH:de
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 41.3-1ubuntu5
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961444/+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 1960508] Re: glib2.0-0:i386 breaks installation due to unconfigured libmount1:i386

2022-02-18 Thread Eli Fichnová
This bug made it into pop!_OS 21.10

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

Title:
  glib2.0-0:i386 breaks installation due to unconfigured libmount1:i386

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  After running "sudo apt upgrade" and approving the listed packages,
  the following error occurred after unpacking a number of packages:

  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:  

   
   libglib2.0-0:i386 depends on libmount1 (>= 2.35.2-7~); however:  

   
Package libmount1:i386 is not configured yet.

  output from "dpkg-reconfigure libmount1:i386":

  /usr/sbin/dpkg-reconfigure: libmount1:i386 is broken or not fully
  installed

  output from "sudo apt install libmount1:i386":

  Reading package lists... Done 

   
  Building dependency tree... Done  

   
  Reading state information... Done 

   
  libmount1:i386 is already the newest version (2.36.1-8ubuntu2.2).
  ...

  output from "sudo apt reinstall libmount1:i386":

  E: Internal Error, No file name for libmount1:i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1960508/+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 1960508] Re: glib2.0-0:i386 breaks installation due to unconfigured libmount1:i386

2022-02-18 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: glib2.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  glib2.0-0:i386 breaks installation due to unconfigured libmount1:i386

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  After running "sudo apt upgrade" and approving the listed packages,
  the following error occurred after unpacking a number of packages:

  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:  

   
   libglib2.0-0:i386 depends on libmount1 (>= 2.35.2-7~); however:  

   
Package libmount1:i386 is not configured yet.

  output from "dpkg-reconfigure libmount1:i386":

  /usr/sbin/dpkg-reconfigure: libmount1:i386 is broken or not fully
  installed

  output from "sudo apt install libmount1:i386":

  Reading package lists... Done 

   
  Building dependency tree... Done  

   
  Reading state information... Done 

   
  libmount1:i386 is already the newest version (2.36.1-8ubuntu2.2).
  ...

  output from "sudo apt reinstall libmount1:i386":

  E: Internal Error, No file name for libmount1:i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1960508/+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 1600142] Re: System Monitor CPU graph shows random colors only for 4 CPU cores

2022-02-18 Thread Jeremy Bicha
** Changed in: gnome-system-monitor (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  System Monitor CPU graph shows random colors only for 4 CPU cores

Status in libgtop:
  Fix Released
Status in gnome-system-monitor package in Ubuntu:
  Fix Released

Bug description:
  On Linux Mint 18 Cinnamon 64-bit (and on Mint 17 series as well) System 
Monitor CPU graph has random colours for 4 cores only. My AMD FX-series CPU has 
8 cores and core 5 to 8 graph is shown in red for each mentioned core 
separately. There is no option to choose a different colour for each CPU core 
(it would be nice to have).
  The problem is that I can not distinguish which core does what if half of 
them is shown in the same colour. It kind of defeats the purpose of having a 
separate graph for each core. Yes, one might argue it is not that important but 
still - if it is there, I would like to use that option. Multi-core CPUs with 
more than just 4 cores are widespread.
  Having more contrast in those graphs for all cores would solve my problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgtop/+bug/1600142/+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 1953052] Re: In Jammy sound level reset after reboot

2022-02-18 Thread Igor V. Kovalenko
Please have a look which apps are using audio devices: 'lsof /dev/snd/*

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center 1:41.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  wayland-session jammy
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare 

[Desktop-packages] [Bug 1957944] Re: CSD do not distinguish focused and unfocused FF windows

2022-02-18 Thread Bug Watch Updater
Launchpad has imported 2 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1756170.

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 2022-02-18T14:39:51+00:00 Kai Groner wrote:

Created attachment 9264555
ff-csd-focus-bug.png

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:97.0)
Gecko/20100101 Firefox/97.0

Steps to reproduce:

Using ubuntu (21.10, GNOME desktop, wayland)
Launch firefox
Enable a colorways theme
Open two windows


Actual results:

I am unable to distinguish if a window has focus by the title bar
appearance.


Expected results:

I should be able to distinguish if a window has focus by the title bar
appearance.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1957944/comments/5


On 2022-02-18T14:48:46+00:00 Kai Groner wrote:

Also reported here
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1957944

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1957944/comments/6


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

Title:
  CSD do not distinguish focused and unfocused FF windows

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

Bug description:
  After the FF 96 upgrade I can't distinguish focused and unfocused FF
  windows from their client side decorations.

  Previously the distinction was subtle, but not impossible.

  The attached image shows two windows, the one on the left has focus.
  The only way you can tell this is that the scrollbar is faded in the
  unfocused window.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: firefox 96.0+build2-0ubuntu0.21.10.1
  Uname: Linux 5.14.0-051400-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BuildID: 20220106144528
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 14 13:15:27 2022
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (941 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=96.0/20220106144528 (In use)
   Profile0 (Default) - LastVersion=96.0/20220106144528 (In use)
   Profile2 - LastVersion=71.0/20191205203726 (Out of date)
  RebootRequiredPkgs: Error: path contained symlinks.
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to impish on 2021-10-31 (75 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.90
  dmi.board.name: B450M Steel Legend
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Desktop-packages] [Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-02-18 Thread Dave Jones
@xnox Ah, that makes sense, thanks. I'll propose some seed updates in a
bit.

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1957944] Re: CSD do not distinguish focused and unfocused FF windows

2022-02-18 Thread Olivier Tilloy
Thanks Kai!

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

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

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

Title:
  CSD do not distinguish focused and unfocused FF windows

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

Bug description:
  After the FF 96 upgrade I can't distinguish focused and unfocused FF
  windows from their client side decorations.

  Previously the distinction was subtle, but not impossible.

  The attached image shows two windows, the one on the left has focus.
  The only way you can tell this is that the scrollbar is faded in the
  unfocused window.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: firefox 96.0+build2-0ubuntu0.21.10.1
  Uname: Linux 5.14.0-051400-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BuildID: 20220106144528
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 14 13:15:27 2022
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (941 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=96.0/20220106144528 (In use)
   Profile0 (Default) - LastVersion=96.0/20220106144528 (In use)
   Profile2 - LastVersion=71.0/20191205203726 (Out of date)
  RebootRequiredPkgs: Error: path contained symlinks.
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to impish on 2021-10-31 (75 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.90
  dmi.board.name: B450M Steel Legend
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1957944/+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 1957944] Re: CSD do not distinguish focused and unfocused FF windows

2022-02-18 Thread Kai Groner
https://bugzilla.mozilla.org/show_bug.cgi?id=1756170

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

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

Title:
  CSD do not distinguish focused and unfocused FF windows

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  After the FF 96 upgrade I can't distinguish focused and unfocused FF
  windows from their client side decorations.

  Previously the distinction was subtle, but not impossible.

  The attached image shows two windows, the one on the left has focus.
  The only way you can tell this is that the scrollbar is faded in the
  unfocused window.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: firefox 96.0+build2-0ubuntu0.21.10.1
  Uname: Linux 5.14.0-051400-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BuildID: 20220106144528
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 14 13:15:27 2022
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (941 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=96.0/20220106144528 (In use)
   Profile0 (Default) - LastVersion=96.0/20220106144528 (In use)
   Profile2 - LastVersion=71.0/20191205203726 (Out of date)
  RebootRequiredPkgs: Error: path contained symlinks.
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to impish on 2021-10-31 (75 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.90
  dmi.board.name: B450M Steel Legend
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1957944/+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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-02-18 Thread Dimitri John Ledkov
systemd stuff did either partition or fs but not both.

we used the cloud initramfs implementation on the desktop, because yes,
it doesn't do cloud-init.

probably moving that out of the common seed will help.

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1958002] Re: Nouveau drivers are not suspending the system when the laptop lid is closed. Reopening the lid causes a black screen.

2022-02-18 Thread Marc Deslauriers
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Nouveau drivers are not suspending the system when the laptop lid is
  closed. Reopening the lid causes a black screen.

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

Bug description:
  When using open-source video drivers, the laptop doesn't suspend when
  the lid is closed. Reopening the lid causes a black screen, and the
  system has to be manually shut down and restarted. This wasn't an
  issue before, and is currently not an issue with proprietary Nvidia
  drivers. I'm not sure if the system is locking if the lid is closed,
  as it doesn't suspend and I'm only presented with a black screen upon
  reopening the lid.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-46-generic x86_64
  NonfreeKernelModules: socwatch2_15 vtsspp sep5 socperf3 pax
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 14 23:37:42 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:827f]
 Subsystem: Hewlett-Packard Company GP108M [GeForce MX150] [103c:827f]
  InstallationDate: Installed on 2022-01-02 (12 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 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 15-bl1XX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2017
  dmi.bios.release: 15.20
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827F
  dmi.board.vendor: HP
  dmi.board.version: 95.03
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.20:bd06/28/2017:br15.20:efr95.3:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:sku2TY42UAR#ABL:rvnHP:rn827F:rvr95.03:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-bl1XX
  dmi.product.sku: 2TY42UAR#ABL
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1958002/+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 1959591] Re: Out-of-bounds read during processing of a password-protected PDF file

2022-02-18 Thread Marc Deslauriers
** Changed in: poppler (Ubuntu)
   Status: New => Confirmed

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

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

Title:
  Out-of-bounds read during processing of a password-protected PDF file

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  Out-of-bounds read during processing of a password-protected PDF file

  # Description
  During processsing of the attached pdf file via
  ```
  pdftotext -upw USERPASS -opw OWNERPASS $PWD/testcase /tmp/out.txt
  ```
  a out-of-bounds read happens. Since I was unable to reproduce this bug
  on the most recent upstream commit 
(b3f93644de4941bdbd532a7d8f82cd652dfbeadf), I report it here.

  This bug allows an attacker to perform a denial of service and
  possibly opens up other attack vectors.

  To reproduce the crash, we provide the following script alongside the 
crashing input:
  - ./reproduce-ubuntu.sh: Reproduce crash via a Ubuntu 20.04 docker container

  If you need further details, we are happy to answer all questions.

  # apt show poppler-utils
  Package: poppler-utils
  Version: 0.86.1-0ubuntu1
  Priority: optional
  Section: utils
  Source: poppler
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian freedesktop.org maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 754 kB
  Provides: pdftohtml, xpdf-utils
  Depends: libpoppler97 (= 0.86.1-0ubuntu1), libc6 (>= 2.14), libcairo2 (>= 
1.12.0), libfreetype6 (>= 2.2.1), liblcms2-2 (>= 2.2+git20110628), libstdc++6 
(>= 5.2)
  Conflicts: pdftohtml
  Breaks: xpdf-common, xpdf-utils (<< 1:0)
  Replaces: pdftohtml, xpdf-reader, xpdf-utils (<< 3.02-2~)
  Homepage: http://poppler.freedesktop.org/
  Task: print-server, ubuntu-desktop-minimal, ubuntu-desktop, kubuntu-desktop, 
xubuntu-core, xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop-core, 
ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, 
ubuntu-mate-desktop, ubuntu-budgie-desktop
  Download-Size: 174 kB
  APT-Manual-Installed: no
  APT-Sources: http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  Description: PDF utilities (based on Poppler)

  # valgrind Ubuntu
  ==1== Memcheck, a memory error detector
  ==1== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
  ==1== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
  ==1== Command: pdftotext -upw USERPASS -opw OWNERPASS /testcase /tmp/out.txt
  ==1==
  Syntax Error (409): Dictionary key must be a name object
  Syntax Error (796): Illegal character <29> in hex string
  Syntax Error (798): Illegal character <14> in hex string
  Syntax Error (799): Illegal character  in hex string
  Syntax Error (800): Illegal character  in hex string
  Syntax Error (801): Illegal character <8a> in hex string
  Syntax Error (860): Illegal character <58> in hex string
  Unimplemented Feature: Unsupported version/revision (1/0) of Standard 
security handler
  ==1== Invalid read of size 8
  ==1==at 0x498F758: FilterStream::getDict() (in 
/usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0)
  ==1==by 0x4A0B4A9: Parser::makeStream(Object&&, unsigned char const*, 
CryptAlgorithm, int, int, int, int, bool) (in 
/usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0)
  ==1==by 0x4A0BE3D: Parser::getObj(bool, unsigned char const*, 
CryptAlgorithm, int, int, int, int, bool) (in 
/usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0)
  ==1==by 0x49EE0AE: Hints::readTables(BaseStream*, Linearization*, XRef*, 
SecurityHandler*) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0)
  ==1==by 0x4A0C949: PDFDoc::checkLinearization() (in 
/usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0)
  ==1==by 0x4A0E4A9: PDFDoc::getPage(int) (in 
/usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0)
  ==1==by 0x4A0E88C: PDFDoc::displayPage(OutputDev*, int, double, double, 
int, bool, bool, bool, bool (*)(void*), void*, bool (*)(Annot*, void*), void*, 
bool) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0)
  ==1==by 0x4A0E9E1: PDFDoc::displayPages(OutputDev*, int, int, double, 
double, int, bool, bool, bool, bool (*)(void*), void*, bool (*)(Annot*, void*), 
void*) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0)
  ==1==by 0x10C57F: main (pdftotext.cc:400)
  ==1==  Address 0x60005ad8fc0 is not stack'd, malloc'd or (recently) free'd
  ==1==
  ==1==
  ==1== Process terminating with default action of signal 11 (SIGSEGV): dumping 
core
  ==1==  General Protection Fault
  ==1==at 0x498F758: FilterStream::getDict() (in 
/usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0)
  ==1==by 0x4A0B4A9: Parser::makeStream(Object&&, unsigned char const*, 
CryptAlgorithm, int, int, int, int, bool) (in 
/usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0)
  ==1==by 0x4A0BE3D: Parser::getObj(bool, unsigned char const*, 
CryptAlgorithm, int, int, int, 

[Desktop-packages] [Bug 1957944] Re: CSD do not distinguish focused and unfocused FF windows

2022-02-18 Thread Olivier Tilloy
Okay, that sounds like a problem that's specific to the use of Colorways
(https://support.mozilla.org/en-US/kb/personalize-firefox-colorways).

Could you please file an upstream bug at
https://bugzilla.mozilla.org/enter_bug.cgi, and share the link to it
here?

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

Title:
  CSD do not distinguish focused and unfocused FF windows

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  After the FF 96 upgrade I can't distinguish focused and unfocused FF
  windows from their client side decorations.

  Previously the distinction was subtle, but not impossible.

  The attached image shows two windows, the one on the left has focus.
  The only way you can tell this is that the scrollbar is faded in the
  unfocused window.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: firefox 96.0+build2-0ubuntu0.21.10.1
  Uname: Linux 5.14.0-051400-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BuildID: 20220106144528
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 14 13:15:27 2022
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (941 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=96.0/20220106144528 (In use)
   Profile0 (Default) - LastVersion=96.0/20220106144528 (In use)
   Profile2 - LastVersion=71.0/20191205203726 (Out of date)
  RebootRequiredPkgs: Error: path contained symlinks.
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to impish on 2021-10-31 (75 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.90
  dmi.board.name: B450M Steel Legend
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1957944/+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 1961010] Re: firefox doesn't let its user control how or when it upgrades

2022-02-18 Thread Olivier Tilloy
> Are "Security updates" in update-manager different from the
> "security pocket" that Firefox updates occur in?

They shouldn't be. "Security updates" are defined as anything that is
delivered through the security pocket.

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

Title:
  firefox doesn't let its user control how or when it upgrades

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  The Firefox package does not act like ordinary packages.  When it is
  running, it forcibly downloads upgraded binary versions of itself and
  then forces the user to restart Firefox and run the new version.
  There used to be a Firefox setting by which the user could control
  this, but it has been deliberately removed.

  This is problematic in many ways.  The first way is that it undermines
  the user's control over their own environment.  The essential element
  of free software is that users control it, it does not control them.
  If there is behavior that is undesirable, they can fix it, not just be
  subjected to the arbitrary decisions of a distant corporation.  For
  example, some users require that they have a copy of the source code
  that matches each binary package they are running.  Firefox's covert
  upgrades undermine this local user policy, installing binaries that
  have no local matching source code.  Other users may be using plugins
  or other applications that do not work with later versions of Firefox.
  It is not Firefox's decision when to upgrade -- it is the user's or
  system operator's.

  The second problem is that restarting one's browser has many side effects.  
For example, if one window or tab is in a video conference, forcing a restart 
of Firefox ejects the user from their video conference.  If a video or audio 
file is merely playing in another window or tab, it is
  interrupted and not necessarily resumed after restart in the right place.  
Cookies and permissions (e.g. for NoScript) are not carried forward after a 
restart, when they are set to persist only for one session.

  If the Mozilla Corporation has firmly and permanently decided that it
  doesn't believe in the freedom of the end-users of its software, then
  Ubuntu should ship a patched version that DOES give its end-users
  freedom, by restoring the setting to disable automated updates.
  Firefox would continue to be able to be updated by the usual update-
  manager GUI (which IS under the control of the user), apt-get, or by
  the user explicitly installing new versions via dpkg or by building
  from source code.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 97.0+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gnu2520 F pulseaudio
   /dev/snd/controlC1:  gnu2520 F pulseaudio
   /dev/snd/controlC0:  gnu2520 F pulseaudio
  BuildID: 20220202182137
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 15 22:55:07 2022
  ForcedLayersAccel: False
  IncompatibleExtensions:
   Global Menu Bar integration - globalm...@ubuntu.com
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2020-05-04 (652 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 209.16.159.254 dev enp6s0 proto static metric 100 
   75.101.100.0/24 dev enp6s0 proto kernel scope link src 75.101.100.46 metric 
100 
   169.254.0.0/16 dev enp6s0 scope link metric 1000 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   209.16.159.0/24 dev enp6s0 proto kernel scope link src 209.16.159.252 metric 
100
  MostRecentCrashID: bp-f3d4806a-b277-49a1-b452-902072161127
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=97.0/20220202182137 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-f3d4806a-b277-49a1-b452-902072161127
   bp-4da20c64-dde1-4304-9118-238562160914
   bp-16b8bc44-ebd0-46e0-a272-95feb2160908
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F25
  dmi.board.asset.tag: Default string
  

[Desktop-packages] [Bug 1961303] Re: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error

2022-02-18 Thread Olivier Tilloy
Relevant excerpt from DpkgTerminalLog.txt:

  ==> Installing the chromium snap
  error: snap "chromium" has "install-snap" change in progress

Can you share the output of `snap changes` ?

If you try to reinstall chromium (`sudo apt reinstall chromium-
browser`), does it succeed?

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

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

Title:
  package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to
  install/upgrade: new chromium-browser package pre-installation script
  subprocess returned error exit status 10

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I tried to install Chromium browser using terminal and I got this error.
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  N: Unable to locate package pkgname

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Feb 17 16:28:10 2022
  Dependencies:
   
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2022-02-16 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: chromium-browser
  Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to 
install/upgrade: new chromium-browser package pre-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1961303/+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 1838249] ProcCpuinfoMinimal.txt

2022-02-18 Thread davide soresinetti
apport information

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

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

Title:
  crash on startup

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  libreoffice --norestore --safe-mode
  dbus[16783]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2754.
  This is normally a bug in some application using the D-Bus library.

D-Bus not built with -rdynamic so unable to print a backtrace

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3ba93)[0x7f62a2538a93]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3bca3)[0x7f62a2538ca3]
  /lib/x86_64-linux-gnu/libc.so.6(+0x43f60)[0x7f62a2329f60]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f62a2329ed7]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f62a230b535]
  /lib/x86_64-linux-gnu/libdbus-1.so.3(+0xb78d)[0x7f62a19e578d]
  /lib/x86_64-linux-gnu/libdbus-1.so.3(_dbus_strdup+0x0)[0x7f62a1a07380]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_iter_append_basic+0x369)[0x7f62a19f8a79]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args_valist+0x154)[0x7f62a19f93d4]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args+0x99)[0x7f62a19f9669]
  
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3(avahi_record_browser_new+0x17c)[0x7f629d11ac9c]
  /usr/lib/x86_64-linux-gnu/libcups.so.2(+0x28f1e)[0x7f62a0537f1e]
  /usr/lib/x86_64-linux-gnu/libcups.so.2(cupsGetDests2+0x94)[0x7f62a05380b4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2e97a17)[0x7f62a53f0a17]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3e6f8)[0x7f62a253b6f8]
  /lib/x86_64-linux-gnu/libpthread.so.0(+0x9182)[0x7f62a1a34182]
  /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f62a2403b1f]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-10-29 (273 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: libreoffice-core 1:6.2.5-0ubuntu0.19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Tags:  disco
  Uname: Linux 5.0.0-21-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-25 (95 days ago)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2018-10-29 (1207 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: libreoffice-core 1:7.2.5-0ubuntu0.21.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-28-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-12-27 (52 days ago)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1838249/+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 1838249] Re: crash on startup

2022-02-18 Thread davide soresinetti
apport information

** Tags added: impish wayland-session

** Description changed:

  libreoffice --norestore --safe-mode
  dbus[16783]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2754.
  This is normally a bug in some application using the D-Bus library.
  
D-Bus not built with -rdynamic so unable to print a backtrace
  
  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3ba93)[0x7f62a2538a93]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3bca3)[0x7f62a2538ca3]
  /lib/x86_64-linux-gnu/libc.so.6(+0x43f60)[0x7f62a2329f60]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f62a2329ed7]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f62a230b535]
  /lib/x86_64-linux-gnu/libdbus-1.so.3(+0xb78d)[0x7f62a19e578d]
  /lib/x86_64-linux-gnu/libdbus-1.so.3(_dbus_strdup+0x0)[0x7f62a1a07380]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_iter_append_basic+0x369)[0x7f62a19f8a79]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args_valist+0x154)[0x7f62a19f93d4]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args+0x99)[0x7f62a19f9669]
  
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3(avahi_record_browser_new+0x17c)[0x7f629d11ac9c]
  /usr/lib/x86_64-linux-gnu/libcups.so.2(+0x28f1e)[0x7f62a0537f1e]
  /usr/lib/x86_64-linux-gnu/libcups.so.2(cupsGetDests2+0x94)[0x7f62a05380b4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2e97a17)[0x7f62a53f0a17]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3e6f8)[0x7f62a253b6f8]
  /lib/x86_64-linux-gnu/libpthread.so.0(+0x9182)[0x7f62a1a34182]
  /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f62a2403b1f]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-10-29 (273 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: libreoffice-core 1:6.2.5-0ubuntu0.19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Tags:  disco
  Uname: Linux 5.0.0-21-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-25 (95 days ago)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu71
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.10
+ InstallationDate: Installed on 2018-10-29 (1207 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ Package: libreoffice-core 1:7.2.5-0ubuntu0.21.10.1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=it_IT.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
+ Tags:  impish wayland-session
+ Uname: Linux 5.13.0-28-generic x86_64
+ UpgradeStatus: Upgraded to impish on 2021-12-27 (52 days ago)
+ UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo 
wireshark
+ _MarkForUpload: True

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

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

Title:
  crash on startup

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  libreoffice --norestore --safe-mode
  dbus[16783]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2754.
  This is normally a bug in some application using the D-Bus library.

D-Bus not built with -rdynamic so unable to print a backtrace

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3ba93)[0x7f62a2538a93]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3bca3)[0x7f62a2538ca3]
  /lib/x86_64-linux-gnu/libc.so.6(+0x43f60)[0x7f62a2329f60]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f62a2329ed7]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f62a230b535]
  /lib/x86_64-linux-gnu/libdbus-1.so.3(+0xb78d)[0x7f62a19e578d]
  /lib/x86_64-linux-gnu/libdbus-1.so.3(_dbus_strdup+0x0)[0x7f62a1a07380]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_iter_append_basic+0x369)[0x7f62a19f8a79]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args_valist+0x154)[0x7f62a19f93d4]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args+0x99)[0x7f62a19f9669]
  
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3(avahi_record_browser_new+0x17c)[0x7f629d11ac9c]
  

[Desktop-packages] [Bug 1012858]

2022-02-18 Thread K-it-m
Somewhat nice that after nearly 10 years something has been done about
this.

Yet I strongly suspect that this "cures" just one of the symptoms of a deeper 
issue, 
namely some busy waiting whenever a network connection is a attempted but the 
network or the addressed server is (temporarily) unavailable.

See also bug 1107251, bug 683651, bug 562977, and likely several more.

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

Title:
  "Sending of message failed" dialog needs 100% of one CPU as long as it
  is open.

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Priority: Low
  How to reproduce:
   - Attach a large file to a message to make the sending process need enough 
time for the third step.
   - press the "send" button
   - Interrupt the internet connection before the sending of the message can be 
completed
  Problem:
   The Dialog that pops up now telling the message could not be sent creates 
100% CPU load for one CPU.
  What was to be expected:
   The dialog pops up and does not need any CPU power until a button is clicked.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: thunderbird 14.0~b1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
  Uname: Linux 3.4.0-5-generic x86_64
  ApportVersion: 2.2.2-0ubuntu2
  Architecture: amd64
  Date: Wed Jun 13 22:49:39 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/thunderbird/thunderbird-bin
  LocalLibraries: 
/home/gunter/.thunderbird/fskw3xe2.default/extensions/mintr...@tn123.ath.cx/lib/tray_x86_64-gcc3.so
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2022-02-18 Thread hyc
(In reply to henry.hormaza from comment #555)
> (In reply to Howard Chu from comment #554)
> > (In reply to Lucas Tanure from comment #539)
> > > Hi, 
> > > 
> > > We are waiting for this patch series to be merged:
> > > 
> > > https://lkml.org/lkml/2022/1/21/471
> > > 
> > > Thanks
> > > Lucas
> > 
> > Hi, just wanted to confirm, adding these patches on top of 5.17-rc4 works
> > for me on my 2021 Legion 7 (AMD). This is running Ubuntu 21.04. I grabbed
> > the kernel source from the Ubuntu tree, as linked here

> I've tried with that kernel direct from kernel.org but couldn't find the SPI
> multi..., is there any previous step I'm missing?, I read something about a
> patch, but I don't know which one is ( I have the same laptop than you )

The patch in the comment I replied to, comment #539.

That's why I replied to that specific comment.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

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

2022-02-18 Thread roberttopopescu
(In reply to Howard Chu from comment #554)
> (In reply to Lucas Tanure from comment #539)
> > Hi, 
> > 
> > We are waiting for this patch series to be merged:
> > 
> > https://lkml.org/lkml/2022/1/21/471
> > 
> > Thanks
> > Lucas
> 
> Hi, just wanted to confirm, adding these patches on top of 5.17-rc4 works
> for me on my 2021 Legion 7 (AMD). This is running Ubuntu 21.04. I grabbed
> the kernel source from the Ubuntu tree, as linked here
> 
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.17-rc4/
> 
> And built following the instructions here 
> 
> https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
> 
> In the editconfigs step you have to navigate in menuconfig to Device Drivers
> /
> X86 Platform Specific Device Drivers /
> I2C and SPI multi instantiate pseudo device driver
> 
> and select that module. Then Exit/Save the config and build. It takes a few
> minutes to build, but the process goes smoothly.
> 
> Thanks for getting this working!

Heyy, did it worked for Legion 16achg6? Now speakers work properly? if
yes can you post step by step how to do that please? i would realy
appreciate that!

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

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

2022-02-18 Thread henry.hormaza
(In reply to Howard Chu from comment #554)
> (In reply to Lucas Tanure from comment #539)
> > Hi, 
> > 
> > We are waiting for this patch series to be merged:
> > 
> > https://lkml.org/lkml/2022/1/21/471
> > 
> > Thanks
> > Lucas
> 
> Hi, just wanted to confirm, adding these patches on top of 5.17-rc4 works
> for me on my 2021 Legion 7 (AMD). This is running Ubuntu 21.04. I grabbed
> the kernel source from the Ubuntu tree, as linked here
> 
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.17-rc4/
> 
> And built following the instructions here 
> 
> https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
> 
> In the editconfigs step you have to navigate in menuconfig to Device Drivers
> /
> X86 Platform Specific Device Drivers /
> I2C and SPI multi instantiate pseudo device driver
> 
> and select that module. Then Exit/Save the config and build. It takes a few
> minutes to build, but the process goes smoothly.
> 
> Thanks for getting this working!

I've tried with that kernel direct from kernel.org but couldn't find the
SPI multi..., is there any previous step I'm missing?, I read something
about a patch, but I don't know which one is ( I have the same laptop
than you )

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-02-18 Thread Dave Jones
Hmmm, I wonder if this is in the seeds, given we *finally* got around to
using the platform seeds to build the impish image (the intention was to
do this in hirsute, and they were ready but for some reason they were
never activated on that release).

Ah ha! Here's the culprit:

https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/platform/tree/raspi-common

Now I wonder why that was added ...

https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/platform/commit/raspi-
common?id=66ab1060453f5cdc8db8af901910282de20411bc

Ohhh. I wonder if this is required to grow the partition on the desktop
images. Those don't use cloud-init at all, instead there's a
"x-systemd.growfs" tag in the fstab, but perhaps this package was
required to operate that? I thought that was systemd-growfs though...
Either way, it seems like something that could be added to the desktop
seed specifically instead of the raspi-common seed.

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: cloud-init (Ubuntu)
 Assignee: Dave Jones (waveform) => (unassigned)

** Changed in: cloud-init (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1953052] Re: In Jammy sound level reset after reboot

2022-02-18 Thread corrado venturini
On a different Jammy install on a different desktop the problem dos
still occur.

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center 1:41.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  wayland-session jammy
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev 

[Desktop-packages] [Bug 1924859] Re: VMware not grabbing Alt+Tab input in Wayland sessions

2022-02-18 Thread Kamen Stoykov
I'm using Ubuntu 21.10 and I'm experiencing the same issue

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

Title:
  VMware not grabbing Alt+Tab input in Wayland sessions

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  I am currently running VMware workstation pro 16.1. When pressing
  alt+tab to toggle the windows in the guest OS, the input is instead
  applied to the host OS and not the guest. When switching from Wayland
  to Xorg the problem is resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: 
Error executing command as another user: Request dismissed
  Date: Sat Apr 17 15:48:45 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASRock Incorporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [1849:0112]
   NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GM206 [GeForce GTX 
960] [1462:3202]
  InstallationDate: Installed on 2021-04-16 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic 
root=UUID=739968f7-1aa4-47f1-8d68-55af0ffb428d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 07/11/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.30
  dmi.board.name: Z77 OC Formula
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/11/2013:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77OCFormula:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1924859/+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 1961392] [NEW] NetworkManager blocks wifi connection after standby with multiple users logged in

2022-02-18 Thread Arvid Jasper
Public bug reported:

I frequently have multiple users logged in on my laptop. When starting
from standby and logging in to the current user, wifi connection is
regularly blocked. NetworkManager appears to try connecting from the
other user which seems decisively quicker. This is throwing an error
message with the uid of the user apparently already trying to connect.
Actually, all non-used wifis are shown as "connection in progress",
while "connect" to the actual wifi network is not clickable.
NetworkManager on the other user cannot connect though because finishing
the connection apparently requires being logged in at that exact moment.
Wifi connection is not achievable therefore in the current user.

Logging back in to the other user to solve this wifi issue is doable in
my case, but only since it is me controlling both accounts. In any case
it is a tedious procedure. I guess it just wasn't ever tested during
development?

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu3
ProcVersionSignature: Ubuntu 5.11.0-49.55-generic 5.11.22
Uname: Linux 5.11.0-49-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.4
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Feb 18 09:07:23 2022
InstallationDate: Installed on 2020-06-08 (619 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
 default via 192.168.2.1 dev wlp4s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp4s0 scope link metric 1000 
 192.168.2.0/24 dev wlp4s0 proto kernel scope link src 192.168.2.104 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 LANGUAGE=
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to hirsute on 2021-10-19 (121 days ago)
modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
 [connection]
 wifi.powersave = 2
mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2021-11-26T16:07:47.831184
nmcli-dev:
 DEVICE  TYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTIONCON-UUID   
   CON-PATH   
 wlp4s0  wifi  connectedfull  full  
/org/freedesktop/NetworkManager/Devices/3  Drogenfahndung#5  
e7791f87-6e62-4f04-a8bc-d2cac21ccbaa  
/org/freedesktop/NetworkManager/ActiveConnection/5 
 enp2s0  ethernet  unavailable  none  none  
/org/freedesktop/NetworkManager/Devices/2  ---- 
   -- 
 lo  loopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

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

Title:
  NetworkManager blocks wifi connection after standby with multiple
  users logged in

Status in network-manager package in Ubuntu:
  New

Bug description:
  I frequently have multiple users logged in on my laptop. When starting
  from standby and logging in to the current user, wifi connection is
  regularly blocked. NetworkManager appears to try connecting from the
  other user which seems decisively quicker. This is throwing an error
  message with the uid of the user apparently already trying to connect.
  Actually, all non-used wifis are shown as "connection in progress",
  while "connect" to the actual wifi network is not clickable.
  NetworkManager on the other user cannot connect though because
  finishing the connection apparently requires being logged in at that
  exact moment. Wifi connection is not achievable therefore in the
  current user.

  Logging back in to the other user to solve this wifi issue is doable
  in my case, but only since it is me controlling both accounts. In any
  case it is a tedious procedure. I guess it just wasn't ever tested
  during development?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-49.55-generic 5.11.22
  Uname: Linux 5.11.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Feb 18 09:07:23 2022
  InstallationDate: Installed on 2020-06-08 (619 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)