[Desktop-packages] [Bug 2017337] Re: Multi touch broken on lunar (23.04) (xorg + wayland) for Focaltech touchpad

2023-04-22 Thread peeweek
** Package changed: ubuntu => libinput (Ubuntu)

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

Title:
  Multi touch broken on lunar (23.04) (xorg + wayland) for Focaltech
  touchpad

Status in libinput package in Ubuntu:
  New

Bug description:
  Multi touch broken on lunar (23.04) (xorg + wayland) for Focaltech
  touchpad

  Since the upgrade of my laptop (ASUS Zenbook UX303UB), multi touch has
  been acting erraticly in the following situations:

  - two finger scrolling
  - one finger clicks left mouse, other finger drags

  when two fingers are moving onto the surface, the cursor is fleeing to
  the right/top of the screen. (See attached screencast)

  The issue happens regardless of xorg/wayland.

  I enclosed a screencast video that demonstrates the issue. In this
  scenario, I am moving a window downwards using two methods:

  - Click and drag with one finger : working
  - Click the left click area with one finger, and drag using the other : not 
working, cursor is fleeing

  - When two fingers are present, and one of them is moving, I am experiencing 
the "fleeing cursor" issue


  Workaround : using left edge scrolling works as temporary workaround
  for scrolling, but click drag using a single finger is really
  cumbersome.

  Here is the output of the `xinput` command on Xorg:

  ```
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ FocalTechPS/2 FocalTech Touchpadid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Asus Wireless Radio Control id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Video Bus   id=9[slave  
keyboard (3)]
  ↳ Sleep Buttonid=10   [slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ```

  Here is the output of the `xinput` command on wayland:

  ```
  WARNING: running xinput against an Xwayland server. See the xinput man page 
for details.
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer  
(2)]
  ⎜   ↳ xwayland-pointer:15 id=6[slave  pointer  
(2)]
  ⎜   ↳ xwayland-relative-pointer:15id=7[slave  pointer  
(2)]
  ⎜   ↳ xwayland-pointer-gestures:15id=8[slave  pointer  
(2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  keyboard 
(3)]
  ↳ xwayland-keyboard:15id=9[slave  keyboard 
(3)]
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2017337/+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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-04-22 Thread zzq4343
>From my end, it appears that 5.19.0-40 breaks HDMI audio again, but
reverting to 5.19.0-38 fixes the problem.

In both cases, the HDMI audio device is showing, just the audio doesn't
work.

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 2017376] Re: App window is moved behind the dock and top bar

2023-04-22 Thread Islam
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  App window is moved behind the dock and top bar

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

Bug description:
  Randomly or sometimes after resuming for sleep, any app window will
  move to the top-left and goes behind the top bar of gnome-shell and
  behind the Ubuntu dock as shown in the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 23 00:43:44 2023
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-01-04 (108 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017376/+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 2017376] Re: App window is moved behind the dock and top bar

2023-04-22 Thread Islam
** Attachment added: "Screenshot from 2023-03-29 13-12-34.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017376/+attachment/5666967/+files/Screenshot%20from%202023-03-29%2013-12-34.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/2017376

Title:
  App window is moved behind the dock and top bar

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

Bug description:
  Randomly or sometimes after resuming for sleep, any app window will
  move to the top-left and goes behind the top bar of gnome-shell and
  behind the Ubuntu dock as shown in the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 23 00:43:44 2023
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-01-04 (108 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017376/+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 2017376] [NEW] App window is moved behind the dock and top bar

2023-04-22 Thread Islam
Public bug reported:

Randomly or sometimes after resuming for sleep, any app window will move
to the top-left and goes behind the top bar of gnome-shell and behind
the Ubuntu dock as shown in the attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 23 00:43:44 2023
DisplayManager: gdm3
GsettingsChanges:
 
InstallationDate: Installed on 2023-01-04 (108 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
RelatedPackageVersions: mutter-common 44.0-2ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago)

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


** Tags: amd64 apport-bug lunar

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

Title:
  App window is moved behind the dock and top bar

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Randomly or sometimes after resuming for sleep, any app window will
  move to the top-left and goes behind the top bar of gnome-shell and
  behind the Ubuntu dock as shown in the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 23 00:43:44 2023
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-01-04 (108 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017376/+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 2017355] Re: Ardour on Lunar crashes gnome-shell (for existing user)

2023-04-22 Thread Erich Eickmeyer
** Package changed: ardour (Ubuntu) => pipewire (Ubuntu)

** Changed in: pipewire (Ubuntu)
   Status: Won't Fix => New

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

Title:
  Ardour on Lunar crashes gnome-shell (for existing user)

Status in pipewire package in Ubuntu:
  New

Bug description:
  Thanks for all your work.

  I am running ardour with a low-latency kernel and via the command:
  pw-jack ardour
  which has been working in kinetic and ardour6. After upgrade to lunar and 
ardour7, this causes a crash of gnome-shell (aka the display) for my user but 
not for a new user.

  
  Recently, I upgraded to lunar from a partition that has been updated from 
hirsuite. I also installed lunar from scratch (iso) on another partition. (I 
have done this on 2 separate machines, both lenovo tiny, one m710q the other 
m720q.)

  If I create a new, empty user. I can run ardour without issues.

  However, when I try to run ardour from my home directory (with lots of
  legacy) which is mounted on another partition, when ardour runs, it
  takes down gnome-shell. Crash, then presented a login screen.

  There should be an automated submission of gnome-shell crashes for a
  machine with the characteristics of this machine (lenovo tiny) in the
  auto-submitted pool.

  I have tried, without success:

  rm /etc/ardour*
  rm /usr/share/ardour*
  rm .config/ardour*
  pw-jack ardour

  also I tried

  apt purge ardour ardour-data ardour-lv2-plugins ardour-video-timeline
  apt install ardour ardour-data ardour-lv2-plugins ardour-video-timeline
  pw-jack ardour

  but the problem persists.

  I would be glad to provide more info, but don't know how to catch
  gnome-shell as it crashes in a gdb session or some such.

  cheers,
~adrian

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ardour 1:7.3.0+ds0-1
  ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6
  Uname: Linux 6.2.0-1003-lowlatency x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 22 12:01:46 2023
  InstallationDate: Installed on 2021-11-14 (524 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: ardour
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2017355/+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 2017366] [NEW] Sound Not Working

2023-04-22 Thread Amit Gupta
Public bug reported:

Windows 11 - Hyper-V
Ubuntu 22.0.4

Tried various solutions!

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Sound Not Working

Status in software-properties package in Ubuntu:
  New

Bug description:
  Windows 11 - Hyper-V
  Ubuntu 22.0.4

  Tried various solutions!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2017366/+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 2017365] [NEW] vanilla-gnome-desktop depends on pulseaudio which results in a conflict

2023-04-22 Thread Thomas M Steenholdt
Public bug reported:

Installing vanilla-gnome-desktop on a fresh 23.04 install, fails with:

The following packages have unmet dependencies:
 pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be 
installed
 pipewire-audio : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be 
installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

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

** Package changed: pipewire (Ubuntu) => ubuntu-gnome-meta (Ubuntu)

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

Title:
  vanilla-gnome-desktop depends on pulseaudio which results in a
  conflict

Status in ubuntu-gnome-meta package in Ubuntu:
  New

Bug description:
  Installing vanilla-gnome-desktop on a fresh 23.04 install, fails with:

  The following packages have unmet dependencies:
   pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be 
installed
   pipewire-audio : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be 
installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/2017365/+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 2017196] Re: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire-alsa conflicts with pulseaudio

2023-04-22 Thread Thomas M Steenholdt
I realize that the conflict is probably intended and my issue is that
vanilla-gnome-desktop relies on pulseaudio still. I'll create a separate
bug, sorry.

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

Title:
  package pipewire-alsa (not installed) failed to install/upgrade:
  conflicting packages - not installing pipewire-alsa:amd64 [pipewire-
  alsa conflicts with pulseaudio]

Status in pipewire package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required
  software appeared to have downloaded. Committing Changes operated to
  about 84% at which point the system crashed. It was necessary to re-
  initiate the upgrade procedure. This time, the upgrade proceeded to
  about 95% when an error notification appeared on the screen. Further
  upgrades were not attempted.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: pipewire-alsa (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Apr 21 04:46:04 2023
  ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64
  InstallationDate: Installed on 2020-02-04 (1171 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: pipewire
  Title: package pipewire-alsa (not installed) failed to install/upgrade: 
conflicting packages - not installing pipewire-alsa:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2017196/+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 2017196] Re: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire-alsa conflicts with pulseaudio

2023-04-22 Thread Thomas M Steenholdt
I seem to hit the same dep issues on a freshly installed 23.04 system
when trying to install vanilla-gnome-desktop.

The following packages have unmet dependencies:
 pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be 
installed
 pipewire-audio : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be 
installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

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

Title:
  package pipewire-alsa (not installed) failed to install/upgrade:
  conflicting packages - not installing pipewire-alsa:amd64 [pipewire-
  alsa conflicts with pulseaudio]

Status in pipewire package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required
  software appeared to have downloaded. Committing Changes operated to
  about 84% at which point the system crashed. It was necessary to re-
  initiate the upgrade procedure. This time, the upgrade proceeded to
  about 95% when an error notification appeared on the screen. Further
  upgrades were not attempted.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: pipewire-alsa (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Apr 21 04:46:04 2023
  ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64
  InstallationDate: Installed on 2020-02-04 (1171 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: pipewire
  Title: package pipewire-alsa (not installed) failed to install/upgrade: 
conflicting packages - not installing pipewire-alsa:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2017196/+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 2017196] Re: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire-alsa conflicts with pulseaudio

2023-04-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package pipewire-alsa (not installed) failed to install/upgrade:
  conflicting packages - not installing pipewire-alsa:amd64 [pipewire-
  alsa conflicts with pulseaudio]

Status in pipewire package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required
  software appeared to have downloaded. Committing Changes operated to
  about 84% at which point the system crashed. It was necessary to re-
  initiate the upgrade procedure. This time, the upgrade proceeded to
  about 95% when an error notification appeared on the screen. Further
  upgrades were not attempted.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: pipewire-alsa (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Apr 21 04:46:04 2023
  ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64
  InstallationDate: Installed on 2020-02-04 (1171 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: pipewire
  Title: package pipewire-alsa (not installed) failed to install/upgrade: 
conflicting packages - not installing pipewire-alsa:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2017196/+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 2017196] Re: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire-alsa conflicts with pulseaudio

2023-04-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package pipewire-alsa (not installed) failed to install/upgrade:
  conflicting packages - not installing pipewire-alsa:amd64 [pipewire-
  alsa conflicts with pulseaudio]

Status in pipewire package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required
  software appeared to have downloaded. Committing Changes operated to
  about 84% at which point the system crashed. It was necessary to re-
  initiate the upgrade procedure. This time, the upgrade proceeded to
  about 95% when an error notification appeared on the screen. Further
  upgrades were not attempted.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: pipewire-alsa (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Apr 21 04:46:04 2023
  ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64
  InstallationDate: Installed on 2020-02-04 (1171 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: pipewire
  Title: package pipewire-alsa (not installed) failed to install/upgrade: 
conflicting packages - not installing pipewire-alsa:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2017196/+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 2013542] Re: [lunar] windows size/position is not saved for some apps

2023-04-22 Thread Jaromir Obr
It's a regression in 23.04 because it started after upgrade Ubuntu 22.10 => 
23.04.
I have the issue with VSCode and Skype. The issue worsened UX of the 
applications I need to work maximized with as I still need to maximize them 
manually.

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

Title:
  [lunar] windows size/position is not saved for some apps

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Lunar up to date, Ubuntu session, Wayland or X11

  1) open Synaptic not in full screen
  2) change window size to full screen
  3) close Synaptic
  4) open Synaptic
  5) its window is not maximized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013542/+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 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward

2023-04-22 Thread vatbier
@Butterfly

Hi kelebek333, can you add patches for 22.10 (kernel 5.19) and 23.04
(6.2) ?

In inttf-nvidia-patcher.sh (from 
https://www.if-not-true-then-false.com/2020/inttf-nvidia-patcher/ ) I see there 
are these newer patches:
  'kernel-5.16.patch'
  'kernel-5.17.patch'
  'kernel-5.18.patch'
  'kernel-6.0.patch'
  'kernel-6.2.patch'

Thanks in advance! Your ppa is much appreciated!
(Currently running your packages on Kubuntu 22.04)

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

Title:
  Nvidia 340.108 fails to install with kernels 5.5 onward

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Groovy:
  Fix Released

Bug description:
  SRU request:

  [Impact]

   * Installing the 340 driver will fail when running Linux 5.7 or
  newer.

  [Test Case]

   * Install nvidia-340 from -proposed.

   * Check that the modules was built and installed, using the
     following command:

     dkms status

  [Regression Potential]

   * The driver once built and installed could be not working and lead
  to have the desktop not starting for example. Check that you get a
  desktop loaded and decent performances

  

  Hi developers,

  thanks for your great work on porting legacy drivers to Ubuntu.

  Anyway I have to complain in not seeing Nvidia 340.108 driver for
  kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4,
  because Nvidia 340.108 fails to install with kernels 5.5 and 5.6.

  Archlinux already has a driver for Kernel 5.6 via AUR
  (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has
  one for kernel 5.5.

  So, the question is: when will we see a new version in repositories?

  Bye and have a nice day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

2023-04-22 Thread Luca Pavan
In my case, a simple > pulseaudio -k < on terminal fixes but surely I'd
prefer a solution rather than having to apply this command.

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

Title:
  Pulseaudio breaks HDMI audio on sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 2017224] Re: Cannot enable bluetooth in gnome-shell

2023-04-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Cannot enable bluetooth in gnome-shell

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 23.04, Bluetooth service is started but can't enable
  it in gnome-shell.

  Apr 21 11:34:15 ZB systemd[1]: Starting bluetooth.service - Bluetooth 
service...
  Apr 21 11:34:15 ZB systemd[1403]: ConfigurationDirectory 'bluetooth' already 
exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 
555)
  Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth daemon 5.66
  Apr 21 11:34:15 ZB bluetoothd[1403]: Starting SDP server
  Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/vcp.c:vcp_init() D-Bus 
experimental not enabled
  Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to 
init vcp plugin
  Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/mcp.c:mcp_init() D-Bus 
experimental not enabled
  Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to 
init mcp plugin
  Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/bap.c:bap_init() D-Bus 
experimental not enabled
  Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to 
init bap plugin
  Apr 21 11:34:15 ZB systemd[1]: Started bluetooth.service - Bluetooth service.
  Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth management interface 1.22 
initialized


  
  I installed the latest linux-firmware from the repo but it didn't help.

  # dmesg | grep -i bluetooth
  [ 18.861759] Bluetooth: Core ver 2.22
  [ 18.863617] NET: Registered PF_BLUETOOTH protocol family
  [ 18.863621] Bluetooth: HCI device and connection manager initialized
  [ 18.863628] Bluetooth: HCI socket layer initialized
  [ 18.863631] Bluetooth: L2CAP socket layer initialized
  [ 18.863638] Bluetooth: SCO socket layer initialized
  [ 19.146683] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
  [ 19.147702] Bluetooth: hci0: Device revision is 2
  [ 19.147707] Bluetooth: hci0: Secure boot is enabled
  [ 19.147709] Bluetooth: hci0: OTP lock is enabled
  [ 19.147712] Bluetooth: hci0: API lock is enabled
  [ 19.147714] Bluetooth: hci0: Debug lock is disabled
  [ 19.147716] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [ 19.150729] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
  [ 19.150841] Bluetooth: hci0: Boot Address: 0x24800
  [ 19.150843] Bluetooth: hci0: Firmware Version: 15-45.22
  [ 19.998952] Bluetooth: hci0: urb 8cd2a5b0 failed to resubmit (2)
  [ 20.015315] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [ 20.015321] Bluetooth: BNEP filters: protocol multicast
  [ 20.015329] Bluetooth: BNEP socket layer initialized
  [ 22.005627] Bluetooth: hci0: command 0xfc09 tx timeout
  [ 30.037760] Bluetooth: hci0: Failed to send firmware data (-110)
  [ 30.037855] Bluetooth: hci0: Intel reset sent to retry FW download
  [ 32.213626] Bluetooth: hci0: Failed to read MSFT supported features (-110)


  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: bluez 5.66-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 21 11:44:40 2023
  InstallationDate: Installed on 2023-01-04 (106 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  InterestingModules: bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago)
  dmi.bios.date: 04/22/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX435EG.315
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX435EG
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX435EG_UX435EG
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:

  mtime.conffile..etc.bluetooth.input.conf: 

[Desktop-packages] [Bug 2017224] Re: Cannot enable bluetooth in gnome-shell

2023-04-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Cannot enable bluetooth in gnome-shell

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 23.04, Bluetooth service is started but can't enable
  it in gnome-shell.

  Apr 21 11:34:15 ZB systemd[1]: Starting bluetooth.service - Bluetooth 
service...
  Apr 21 11:34:15 ZB systemd[1403]: ConfigurationDirectory 'bluetooth' already 
exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 
555)
  Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth daemon 5.66
  Apr 21 11:34:15 ZB bluetoothd[1403]: Starting SDP server
  Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/vcp.c:vcp_init() D-Bus 
experimental not enabled
  Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to 
init vcp plugin
  Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/mcp.c:mcp_init() D-Bus 
experimental not enabled
  Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to 
init mcp plugin
  Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/bap.c:bap_init() D-Bus 
experimental not enabled
  Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to 
init bap plugin
  Apr 21 11:34:15 ZB systemd[1]: Started bluetooth.service - Bluetooth service.
  Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth management interface 1.22 
initialized


  
  I installed the latest linux-firmware from the repo but it didn't help.

  # dmesg | grep -i bluetooth
  [ 18.861759] Bluetooth: Core ver 2.22
  [ 18.863617] NET: Registered PF_BLUETOOTH protocol family
  [ 18.863621] Bluetooth: HCI device and connection manager initialized
  [ 18.863628] Bluetooth: HCI socket layer initialized
  [ 18.863631] Bluetooth: L2CAP socket layer initialized
  [ 18.863638] Bluetooth: SCO socket layer initialized
  [ 19.146683] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
  [ 19.147702] Bluetooth: hci0: Device revision is 2
  [ 19.147707] Bluetooth: hci0: Secure boot is enabled
  [ 19.147709] Bluetooth: hci0: OTP lock is enabled
  [ 19.147712] Bluetooth: hci0: API lock is enabled
  [ 19.147714] Bluetooth: hci0: Debug lock is disabled
  [ 19.147716] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [ 19.150729] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
  [ 19.150841] Bluetooth: hci0: Boot Address: 0x24800
  [ 19.150843] Bluetooth: hci0: Firmware Version: 15-45.22
  [ 19.998952] Bluetooth: hci0: urb 8cd2a5b0 failed to resubmit (2)
  [ 20.015315] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [ 20.015321] Bluetooth: BNEP filters: protocol multicast
  [ 20.015329] Bluetooth: BNEP socket layer initialized
  [ 22.005627] Bluetooth: hci0: command 0xfc09 tx timeout
  [ 30.037760] Bluetooth: hci0: Failed to send firmware data (-110)
  [ 30.037855] Bluetooth: hci0: Intel reset sent to retry FW download
  [ 32.213626] Bluetooth: hci0: Failed to read MSFT supported features (-110)


  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: bluez 5.66-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 21 11:44:40 2023
  InstallationDate: Installed on 2023-01-04 (106 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  InterestingModules: bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago)
  dmi.bios.date: 04/22/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX435EG.315
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX435EG
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX435EG_UX435EG
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:

  mtime.conffile..etc.bluetooth.input.conf: 

[Desktop-packages] [Bug 2017341] Re: Can toggle Hexchat App Indicator from remote location

2023-04-22 Thread Islam
** Description changed:

- If I clicked on the title bar of opened window right under the Hexchat app 
indicator, it will toggle the appearance of Hexchat window as if clicking on 
the app indicator icon itself.
+ If I clicked on the title bar of opened window right under the Hexchat
+ app indicator, it will toggle the appearance of Hexchat window as if
+ clicking on the app indicator icon itself, and will prevent from closing
+ a browser tab for the first click.
+ 
  Please see the attached screencast of illustration.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 22 11:53:20 2023
  DisplayManager: gdm3
  GsettingsChanges:
-  
+ 
  InstallationDate: Installed on 2023-01-04 (107 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago)

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

Title:
  Can toggle Hexchat App Indicator from remote location

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  If I clicked on the title bar of opened window right under the Hexchat
  app indicator, it will toggle the appearance of Hexchat window as if
  clicking on the app indicator icon itself, and will prevent from
  closing a browser tab for the first click.

  Please see the attached screencast of illustration.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 22 11:53:20 2023
  DisplayManager: gdm3
  GsettingsChanges:

  InstallationDate: Installed on 2023-01-04 (107 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017341/+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 2017348] [NEW] Terminal configuration file for gnome desktop

2023-04-22 Thread Chenlin
Public bug reported:

When you repeatedly click on theoption in the terminal
configuration file, the terminal window will be reduced by one scroll
bar in length, which can continuously narrow the terminal

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-terminal 3.44.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 22 19:46:13 2023
ExecutablePath: /usr/libexec/gnome-terminal-server
InstallationDate: Installed on 2023-01-21 (91 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Terminal configuration file for gnome desktop

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When you repeatedly click on theoption in the
  terminal configuration file, the terminal window will be reduced by
  one scroll bar in length, which can continuously narrow the terminal

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-terminal 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 22 19:46:13 2023
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2023-01-21 (91 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2017348/+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 2016925] Re: Firefox window is visually corrupted after upgrading to Ubuntu 23.04

2023-04-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Firefox window is visually corrupted after upgrading to Ubuntu 23.04

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 22.10 to Ubuntu 23.04, every time I open
  firefox the windows is heavily visually corrupted. It seems to work
  fine under the corruption, but it is completely unusuable.

  The tar version of Firefox works fine. In the attached screenshot you
  can see the snap version of Firefox (corrupted) and the tar version of
  Firefox (working fine).

  I tried uninstalling (with --purge) and reinstalling and refreshing
  firefox to no avail.

  All other applications, including 3D games, are working fine. I am
  using an AMD RX5500 with default mesa drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: firefox 1:1snap1-0ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 18 18:04:26 2023
  InstallationDate: Installed on 2020-11-04 (895 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SnapChanges:
   IDEstado  Generado   Listo  Resumen
   1215  Done2023-04-18T17:42:17-03:00  2023-04-18T17:44:05-03:00  Eliminar 
snap "firefox"
   1216  Done2023-04-18T17:45:37-03:00  2023-04-18T17:47:25-03:00  Instalar 
snap "firefox"
   1217  Done2023-04-18T17:48:16-03:00  2023-04-18T17:48:30-03:00  Eliminar 
snap "firefox"
   1218  Done2023-04-18T17:48:39-03:00  2023-04-18T17:48:49-03:00  Instalar 
snap "firefox"
  SourcePackage: firefox
  UpgradeStatus: Upgraded to lunar on 2023-04-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016925/+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 2017341] Re: Can toggle Hexchat App Indicator from remote location

2023-04-22 Thread Islam
** Attachment added: "Screencast from 2023-04-22 11-51-53.webm"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017341/+attachment/5666780/+files/Screencast%20from%202023-04-22%2011-51-53.webm

** Also affects: gnome-shell-extension-appindicator (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Can toggle Hexchat App Indicator from remote location

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  If I clicked on the title bar of opened window right under the Hexchat app 
indicator, it will toggle the appearance of Hexchat window as if clicking on 
the app indicator icon itself.
  Please see the attached screencast of illustration.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 22 11:53:20 2023
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-01-04 (107 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017341/+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 2017341] [NEW] Can toggle Hexchat App Indicator from remote location

2023-04-22 Thread Islam
Public bug reported:

If I clicked on the title bar of opened window right under the Hexchat app 
indicator, it will toggle the appearance of Hexchat window as if clicking on 
the app indicator icon itself.
Please see the attached screencast of illustration.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 22 11:53:20 2023
DisplayManager: gdm3
GsettingsChanges:
 
InstallationDate: Installed on 2023-01-04 (107 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
RelatedPackageVersions: mutter-common 44.0-2ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago)

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

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


** Tags: amd64 apport-bug lunar

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

Title:
  Can toggle Hexchat App Indicator from remote location

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  If I clicked on the title bar of opened window right under the Hexchat app 
indicator, it will toggle the appearance of Hexchat window as if clicking on 
the app indicator icon itself.
  Please see the attached screencast of illustration.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 22 11:53:20 2023
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-01-04 (107 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017341/+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 2017173] Re: Ubuntu desktop settings unavailable

2023-04-22 Thread Michał Krassowski
You have control over the message displayed when Ubuntu dock cannot
load. GUI-only users would not be able to discover that this is due to
incompatible extensions issue.

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

Title:
  Ubuntu desktop settings unavailable

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

Bug description:
  I have just upgraded from 22.10 to 23.04.
  Now, in "Settings", the "Ubuntu Desktop" option shows:
  "No ubuntu settings found.
  Oops, something has gone wrong. Please report a bug in Launchpad."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2017173/+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 2017333] Re: Some Area in Top right corner of the screen is not clickable.

2023-04-22 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/2017333

Title:
  Some Area in Top right corner of the screen is not clickable.

Status in xorg package in Ubuntu:
  New

Bug description:
  
https://www.reddit.com/r/Ubuntu/comments/12tyiwf/top_right_area_is_not_clickable_in_ubuntu_2304_i/

  This link contains the visual representation and more details about
  the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 22 12:10:32 2023
  DistUpgraded: 2023-04-21 16:05:44,447 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:81ec]
 Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / 
R5 M330 / M430 / Radeon 520 Mobile] [103c:81ec]
  InstallationDate: Installed on 2022-04-01 (385 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: HP HP Notebook
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=358a40b6-0ed5-4812-8281-fbd535f676fd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago)
  dmi.bios.date: 12/17/2019
  dmi.bios.release: 15.48
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.48
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EC
  dmi.board.vendor: HP
  dmi.board.version: 61.61
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 61.61
  dmi.modalias: 
dmi:bvnInsyde:bvrF.48:bd12/17/2019:br15.48:efr61.61:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.61:cvnHP:ct10:cvrChassisVersion:skuW6T44PA#ACJ:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Notebook
  dmi.product.sku: W6T44PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2017333/+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 1992187] Re: hplip not working after install in 22.04, python error

2023-04-22 Thread Alberto Donato
I also hit this issue, it seems get_distro_std_name got renamed but the
code didn't get updated.

As a workaround, I managed to get it working with the following changes:


$ diff -u /usr/share/hplip/base/password.py.orig 
/usr/share/hplip/base/password.py   



--- /usr/share/hplip/base/password.py.orig  2023-04-22 08:56:30.569359088 
+0200
+++ /usr/share/hplip/base/password.py   2023-04-22 08:57:32.449282962 +0200
@@ -116,7 +116,7 @@
 # added replace() to remove the spaces in distro_name
 (os_name,_ver) = utils.get_distro_name() #.lower().replace(" ","")
 os_name = os_name.lower().replace(" ","")
-distro_name = get_distro_std_name(os_name)
+distro_name = get_distro_name()
 self.__authType = user_conf.get('authentication', 'su_sudo', '')
 if self.__authType != "su" and self.__authType != "sudo":
 try:
@@ -319,7 +319,7 @@
 def __get_password_utils_ui(self):
 (os_name,_ver) = utils.get_distro_name()
 os_name = os_name.lower().replace(" ","")
-distro_name = get_distro_std_name(os_name)
+distro_name = get_distro_name()
 if self.__authType == "sudo":
 AuthType, AuthCmd = 'sudo', 'sudo %s'
 else:

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

Title:
  hplip not working after install in 22.04, python error

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  after upgrade from 20.04 to 22.04.1 (not a new installation): new 
installation of hplip
  >sudo apt install hplip hplip-gui

  Install completes without error.

  Using hplip, e.g.
  >hp-setup

  manual detection of wireless printer using IP works, printer is
  listed, but on 'next' -> process hangs (wait/termination suggested,
  wait does not help)

  alternative: (hplip installs a suite of programs)
  >hp-check(verifies installation and contact to printer, scanner
  produces normal output ending prematurely with error message:

    Saving output in log file: /home/glassel/hp-check.log

  HP Linux Imaging and Printing System (ver. 3.22.2)
  Dependency/Version Check Utility ver. 15.1

  Copyright (c) 2001-18 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Note: hp-check can be run in three modes:
  1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied tarball (.tar.gz or
  .run) to determine if the proper dependencies are installed to successfully 
compile HPLIP.
  2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb, .rpm, etc) or an
  already built HPLIP supplied tarball has the proper dependencies installed to 
successfully run.
  3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the above cases (both
  compile- and run-time dependencies).

  Check types:
  a. EXTERNALDEP - External Dependencies
  b. GENERALDEP - General Dependencies (required both at compile and run time)
  c. COMPILEDEP - Compile time Dependencies
  d. [All are run-time checks]
  PYEXT SCANCONF QUEUES PERMISSION

  Status Types:
  OK
  MISSING   - Missing Dependency or Permission or Plug-in
  INCOMPAT  - Incompatible dependency-version or Plugin-version

  -Traceback (most recent call last):
    File "/usr/bin/hp-check", line 861, in 
  dep.core.init()
    File "/usr/share/hplip/installer/core_install.py", line 523, in init
  self.get_distro()
    File "/usr/share/hplip/installer/core_install.py", line 661, in get_distro
  if 'MX' in distro_release_name:
  NameError: name 'distro_release_name' is not defined

  further info:
  >apt-cache policy hplip
  hplip:
    Installed: 3.22.2+dfsg0-1+klbkjammy
    Candidate: 3.22.2+dfsg0-1+klbkjammy
    Version table:
   *** 3.22.2+dfsg0-1+klbkjammy 500
  500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu 
jammy/main amd64 Packages
  100 /var/lib/dpkg/status
   3.21.12+dfsg0-1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  > apt-cache policy hplip-gui
  hplip-gui:
    Installed: 3.22.2+dfsg0-1+klbkjammy
    Candidate: 3.22.2+dfsg0-1+klbkjammy
    Version table:
   *** 3.22.2+dfsg0-1+klbkjammy 500
  500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu 
jammy/main amd64 Packages
  500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu 
jammy/main i386 Packages
  100 

[Desktop-packages] [Bug 1992187] Re: hplip not working after install in 22.04, python error

2023-04-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  hplip not working after install in 22.04, python error

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  after upgrade from 20.04 to 22.04.1 (not a new installation): new 
installation of hplip
  >sudo apt install hplip hplip-gui

  Install completes without error.

  Using hplip, e.g.
  >hp-setup

  manual detection of wireless printer using IP works, printer is
  listed, but on 'next' -> process hangs (wait/termination suggested,
  wait does not help)

  alternative: (hplip installs a suite of programs)
  >hp-check(verifies installation and contact to printer, scanner
  produces normal output ending prematurely with error message:

    Saving output in log file: /home/glassel/hp-check.log

  HP Linux Imaging and Printing System (ver. 3.22.2)
  Dependency/Version Check Utility ver. 15.1

  Copyright (c) 2001-18 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Note: hp-check can be run in three modes:
  1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied tarball (.tar.gz or
  .run) to determine if the proper dependencies are installed to successfully 
compile HPLIP.
  2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb, .rpm, etc) or an
  already built HPLIP supplied tarball has the proper dependencies installed to 
successfully run.
  3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the above cases (both
  compile- and run-time dependencies).

  Check types:
  a. EXTERNALDEP - External Dependencies
  b. GENERALDEP - General Dependencies (required both at compile and run time)
  c. COMPILEDEP - Compile time Dependencies
  d. [All are run-time checks]
  PYEXT SCANCONF QUEUES PERMISSION

  Status Types:
  OK
  MISSING   - Missing Dependency or Permission or Plug-in
  INCOMPAT  - Incompatible dependency-version or Plugin-version

  -Traceback (most recent call last):
    File "/usr/bin/hp-check", line 861, in 
  dep.core.init()
    File "/usr/share/hplip/installer/core_install.py", line 523, in init
  self.get_distro()
    File "/usr/share/hplip/installer/core_install.py", line 661, in get_distro
  if 'MX' in distro_release_name:
  NameError: name 'distro_release_name' is not defined

  further info:
  >apt-cache policy hplip
  hplip:
    Installed: 3.22.2+dfsg0-1+klbkjammy
    Candidate: 3.22.2+dfsg0-1+klbkjammy
    Version table:
   *** 3.22.2+dfsg0-1+klbkjammy 500
  500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu 
jammy/main amd64 Packages
  100 /var/lib/dpkg/status
   3.21.12+dfsg0-1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  > apt-cache policy hplip-gui
  hplip-gui:
    Installed: 3.22.2+dfsg0-1+klbkjammy
    Candidate: 3.22.2+dfsg0-1+klbkjammy
    Version table:
   *** 3.22.2+dfsg0-1+klbkjammy 500
  500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu 
jammy/main amd64 Packages
  500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu 
jammy/main i386 Packages
  100 /var/lib/dpkg/status
   3.21.12+dfsg0-1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe i386 Packages

  ---

  I tried alternate ways to install hplip:
  hplip-3.22.6.run downloaded from hp

  this fails with an unmet dependency 'libcups2', but sudo apt install libcups2 
tells me it is
  installed (-dev version, too)

  A fresh install of cups did not help.

  Best regards ... Peter Glassel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1992187/+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