date:20230307

** Changed in: mutter (Ubuntu Lunar)
   Status: In Progress => Fix Committed

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

Title:
  Ubuntu's GNOME desktop is higher latency than necessary

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  Triaged
Status in mutter source package in Kinetic:
  Triaged
Status in mutter source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Ubuntu's GNOME desktop is higher latency than necessary. It's stuck in
  triple buffering when it should be dropping to double buffering during
  light rendering.

  [ Test Plan ]

  1. Add this to /etc/environment:

   MUTTER_DEBUG=kms

  2. Reboot and log into a Wayland session.

  3. Open a Terminal and run:

   journalctl -f /usr/bin/gnome-shell | grep 'Swap buffers'

  4. Drag the Terminal window rapidly with the mouse (a high sample rate
  mouse will also help).

  Observed bug: "KMS: Swap buffers: 2 frames pending (triple-buffering)"
  Expected fix: "KMS: Swap buffers: 1 frames pending (double-buffering)"

  If you don't at first confirm the bug prior to the fix then try
  dragging the window to the top bar before wiggling it or opening the
  overview to make the render load higher. The fix will make the log
  messages return to double buffering much sooner and stay there more
  reliably.

  [ Where problems could occur ]

  Any part of the smoothness of the desktop experience could be impacted
  since the fix involves changing the frame clock for frame scheduling.

  [ Other Info ]

  Upstream fix:
  
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441/diffs?commit_id=17ea73d0570318926899c4e3e4821a8b7b21edae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2007262/+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 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller

2023-03-07 Thread Kai-Heng Feng

#9 doesn't seem to be a regression caused by pulseaudio.

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

Title:
  Fix HFP mSBC support on Realtek Bluetooth USB controller

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in pulseaudio source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in pulseaudio source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in pulseaudio source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  When a BT headset is connected Realtek BT USB controller, HFP profile can't 
play or record sound when mSBC codec is used.

  [Fix]
  At Linux kernel side, add a Realtek specific quirk to support mSBC.

  At PulseAudio side, send more data frames until the connected device
  sends response.

  [Test]
  Connect different headsets to the said controller, HFP can play and record 
sounds now.
  Also verified A2DP profile is unaffected.

  [Where problems could occur]
  The kernel part is Realtek specific, so the regression risk is very limited.

  The pulseaudio side only affects HFP profile, since the codeflow only
  changes when a mic is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller

2023-03-07 Thread Kai-Heng Feng

Verified on the following steps:
1) Enabled proposed pocket, upgrade pulseaudio and install oem kernel 
6.1.0-1008.8.
2) Reboot.
3) Pair and connect AirPods, play some audio to ensure that A2DP still works.
4) Switch to HFP and I can hear sound. Microphone also works too.
5) Keep switching between A2DP and HFP profile, both of them work all the time.

** Tags removed: verification-needed verification-needed-jammy 
verification-needed-kinetic
** Tags added: verification-done verification-done-jammy 
verification-done-kinetic

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

Title:
  Fix HFP mSBC support on Realtek Bluetooth USB controller

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in pulseaudio source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in pulseaudio source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in pulseaudio source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  When a BT headset is connected Realtek BT USB controller, HFP profile can't 
play or record sound when mSBC codec is used.

  [Fix]
  At Linux kernel side, add a Realtek specific quirk to support mSBC.

  At PulseAudio side, send more data frames until the connected device
  sends response.

  [Test]
  Connect different headsets to the said controller, HFP can play and record 
sounds now.
  Also verified A2DP profile is unaffected.

  [Where problems could occur]
  The kernel part is Realtek specific, so the regression risk is very limited.

  The pulseaudio side only affects HFP profile, since the codeflow only
  changes when a mic is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist

2023-03-07 Thread Aaron Rainbolt

** Also affects: software-properties (Ubuntu Lunar)
   Importance: Undecided
   Status: Triaged

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

Title:
  software-properties-{qt,kde} attempts to use KUrl but it doesn't exist

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Focal:
  Triaged
Status in software-properties source package in Jammy:
  Triaged
Status in software-properties source package in Kinetic:
  Triaged
Status in software-properties source package in Lunar:
  Triaged

Bug description:
  Release: Kubuntu 18.04
  Version: 0.96.24.32.1

  When clicking the "Import Key" button in the "Authentication" section
  of the panel it throws this error:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
 line 667, in add_key_clicked
  url = KUrl.fromPath(home)
  NameError: name 'KUrl' is not defined

  While this doesn't crash the program it causes nothing to happen when
  clicking the button. Running the program in a terminal reveals the
  error being printed to stderr.

  After debugging it appears KUrl doesn't exist anywhere and I'm not
  sure if's a python module that has changed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+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 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on

I've created https://github.com/snapcore/snapd/pull/12627 as a proposed
fix for the issue.

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

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if
  IBus is turned on

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  Test Case
  -
  From Ubuntu 23.04, install glib >= 2.75.3-3

  Test 1:
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu on Xorg
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  Test 2:
  Install the ibus-libpinyin package.
  Log out and log in again.
  Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)"
   to your input sources.
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu (on Wayland).
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  What Happens
  
  No text is inputted

  Other Info
  --
  You see the issue as soon as IBus has been 'turned on'. With the current 
g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 
session IBus is always turned on due to im-config 0.55-1. In a Wayland session 
you need to tell it to turn IBus on by either adding an IBus input method to 
your input sources or make use of the Screen Keyboard feature.

  And I've only seen the issue with the Firefox and Chromium snaps.

  Warning message if you start firefox from terminal:

  [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could
  not connect: Permission denied: 'glib warning', file
  /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167

  (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to
  ibus: Could not connect: Permission denied

  gnome-settings-daemon
  -
  gnome-settings-daemon 44 Beta makes the situation worse since it always turns 
IBus on in both Wayland and X11, but I reverted 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that 
we could continue with the update. See 
https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+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 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on

Okay. In a clean Lunar VM with glib 2.75.3 installed and ibus enabled as
described in the bug description, I could reproduce the input problems
in Firefox. I saw the following AppArmor denial in the dmesg logs:

[  +0.343553] audit: type=1400 audit(1678248386.012:62):
apparmor="DENIED" operation="connect" profile="snap.firefox.firefox"
name="/home/james/.cache/ibus/dbus-THbBfRNt" pid=2398 comm="pool-
firefox" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000

I edited /var/lib/snapd/apparmor/profiles/snap.firefox.firefox and added
the following rule:

@{HOME}/.cache/ibus/dbus-* rw,

After reloading the policy with "apparmor_parser -r
.../snap.firefox.firefox", keyboard input worked again. So that confirms
my guess about the cause of the problem. This is something we can fix
via a snapd update.

Longer term, we should get these snaps using ibus's portal interface,
which is both more secure (i.e. suitable to allow in the desktop
interface) and should be immune to future changes of this type.

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

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if
  IBus is turned on

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  Test Case
  -
  From Ubuntu 23.04, install glib >= 2.75.3-3

  Test 1:
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu on Xorg
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  Test 2:
  Install the ibus-libpinyin package.
  Log out and log in again.
  Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)"
   to your input sources.
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu (on Wayland).
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  What Happens
  
  No text is inputted

  Other Info
  --
  You see the issue as soon as IBus has been 'turned on'. With the current 
g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 
session IBus is always turned on due to im-config 0.55-1. In a Wayland session 
you need to tell it to turn IBus on by either adding an IBus input method to 
your input sources or make use of the Screen Keyboard feature.

  And I've only seen the issue with the Firefox and Chromium snaps.

  Warning message if you start firefox from terminal:

  [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could
  not connect: Permission denied: 'glib warning', file
  /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167

  (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to
  ibus: Could not connect: Permission denied

  gnome-settings-daemon
  -
  gnome-settings-daemon 44 Beta makes the situation worse since it always turns 
IBus on in both Wayland and X11, but I reverted 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that 
we could continue with the update. See 
https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+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 2008791] Re: Disk properties in Gnome Files (Nautilus) shows a black chart for disk usage on Ubuntu 22.04

The bug is confirmed for jammy, but not in lunar where the pie chart has
been replaced with a standard coloured progress bar.

** Also affects: yaru-theme (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: yaru-theme (Ubuntu Lunar)
   Importance: Low
   Status: Confirmed

** Changed in: yaru-theme (Ubuntu Lunar)
   Status: Confirmed => Invalid

** Changed in: yaru-theme (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: yaru-theme (Ubuntu Jammy)
   Importance: Undecided => Low

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

Title:
  Disk properties in Gnome Files (Nautilus) shows a black chart for disk
  usage on Ubuntu 22.04

Status in yaru-theme package in Ubuntu:
  Invalid
Status in yaru-theme source package in Jammy:
  Confirmed
Status in yaru-theme source package in Lunar:
  Invalid

Bug description:
  if I open the Properties window for a disk (not a plain folder) the
  pie chart intended to show disk usage is all black (screenshot
  attached). On previous versions it used to have different colors for
  "used" and "free" space.

  Testing a clean install on a virtual machine gives the same results so
  it's not an issue related to the upgrade process. I guess it's related
  to the theming features added to Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2008791/+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 2008791] Re: Disk properties in Gnome Files (Nautilus) shows a black chart for disk usage on Ubuntu 22.04

The missing style is called disk-space-display in nautilus:
src/resources/css/Adwaita.css


** No longer affects: nautilus (Ubuntu)

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

Title:
  Disk properties in Gnome Files (Nautilus) shows a black chart for disk
  usage on Ubuntu 22.04

Status in yaru-theme package in Ubuntu:
  Invalid
Status in yaru-theme source package in Jammy:
  Confirmed
Status in yaru-theme source package in Lunar:
  Invalid

Bug description:
  if I open the Properties window for a disk (not a plain folder) the
  pie chart intended to show disk usage is all black (screenshot
  attached). On previous versions it used to have different colors for
  "used" and "free" space.

  Testing a clean install on a virtual machine gives the same results so
  it's not an issue related to the upgrade process. I guess it's related
  to the theming features added to Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2008791/+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 2009637] Re: package libgl1-mesa-dri 22.3.6-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está también en el paq

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

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

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

Title:
  package libgl1-mesa-dri 22.3.6-1ubuntu1 failed to install/upgrade:
  intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so',
  que está también en el paquete libgl1-amber-dri:amd64 21.3.7-0ubuntu1

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Solved with a simple “apt --fix-broken install” but still…

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: libgl1-mesa-dri 22.3.6-1ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Tue Mar  7 15:25:16 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ErrorMessage: intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está también en el paquete 
libgl1-amber-dri:amd64 21.3.7-0ubuntu1
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [103c:84e7]
  InstallationDate: Installed on 2023-02-13 (22 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209)
  MachineType: HP HP Pavilion Laptop 15-cw0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic 
root=UUID=782cbb37-7870-44d8-aa55-53fdff89ddf8 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.20ubuntu2
   apt  2.5.6
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 22.3.6-1ubuntu1 failed to install/upgrade: 
intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está 
también en el paquete libgl1-amber-dri:amd64 21.3.7-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2021
  dmi.bios.release: 15.46
  dmi.bios.vendor: AMI
  dmi.bios.version: F.46
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 84E7
  dmi.board.vendor: HP
  dmi.board.version: 99.30
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 99.30
  dmi.modalias: 
dmi:bvnAMI:bvrF.46:bd01/04/2021:br15.46:efr99.30:svnHP:pnHPPavilionLaptop15-cw0xxx:pvr:rvnHP:rn84E7:rvr99.30:cvnHP:ct10:cvrChassisVersion:sku3PY37LA#ABM:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cw0xxx
  dmi.product.sku: 3PY37LA#ABM
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  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/mesa/+bug/2009637/+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 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on

This seems like the most likely culprit:

https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3005

This basically means that code that would have created an abstract
namespace socket in glib 2.74.x now creates a regular unix domain socket
in 2.75.x. We have AppArmor rules in snapd's desktop-legacy interface
granting access to the abstract namespace socket in $XDG_CACHE_HOME, but
nothing for the equivalent regular socket:

https://github.com/snapcore/snapd/blob/d5f47ca71fcd8a884072e75391a7e55d9ec9d145/interfaces/builtin/desktop_legacy.go#L142-L149

I still need to verify this is the actual cause, but if so it should be
relatively simple to update snapd's AppArmor rules to allow access to
this socket.

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

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if
  IBus is turned on

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  Test Case
  -
  From Ubuntu 23.04, install glib >= 2.75.3-3

  Test 1:
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu on Xorg
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  Test 2:
  Install the ibus-libpinyin package.
  Log out and log in again.
  Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)"
   to your input sources.
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu (on Wayland).
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  What Happens
  
  No text is inputted

  Other Info
  --
  You see the issue as soon as IBus has been 'turned on'. With the current 
g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 
session IBus is always turned on due to im-config 0.55-1. In a Wayland session 
you need to tell it to turn IBus on by either adding an IBus input method to 
your input sources or make use of the Screen Keyboard feature.

  And I've only seen the issue with the Firefox and Chromium snaps.

  Warning message if you start firefox from terminal:

  [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could
  not connect: Permission denied: 'glib warning', file
  /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167

  (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to
  ibus: Could not connect: Permission denied

  gnome-settings-daemon
  -
  gnome-settings-daemon 44 Beta makes the situation worse since it always turns 
IBus on in both Wayland and X11, but I reverted 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that 
we could continue with the update. See 
https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+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 581341] Re: Xnest application are not asked to redraw their windows

** Tags removed: lucid
** Tags added: jammy

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

Title:
  Xnest application are not asked to redraw their windows

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Run these commands in a command line window (bash):
  #---
  Xnest :1 &
  sleep 2
  DISPLAY=:1.0 gedit
  #---

  You will get a poor Xnest window with a gedit window in it, which
  works perfectly.

  But when moving another not-Xnest-window over it and then away again,
  the parts of gedit in the Xnest window are not redrawn automatically.
  only parts of it when moving or clicking around (which is normal
  behavior in such application).

  gedit is only an example, the problem happens with all applications,
  and also with metacity loaded in Xnest. Only xlogo (and maybe other
  test applications) seems to realize it has to update itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xnest 2:1.7.6-2ubuntu7
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic x86_64
  Architecture: amd64
  Date: Sun May 16 16:50:35 2010
  ExecutablePath: /usr/bin/Xnest
  SourcePackage: xorg-server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/581341/+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 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on

I think last time we had problems like this it was due to changes in the
location of the socket for ibus's private D-Bus bus. Looking into the
glib diffs for clues.

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

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if
  IBus is turned on

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  Test Case
  -
  From Ubuntu 23.04, install glib >= 2.75.3-3

  Test 1:
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu on Xorg
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  Test 2:
  Install the ibus-libpinyin package.
  Log out and log in again.
  Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)"
   to your input sources.
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu (on Wayland).
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  What Happens
  
  No text is inputted

  Other Info
  --
  You see the issue as soon as IBus has been 'turned on'. With the current 
g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 
session IBus is always turned on due to im-config 0.55-1. In a Wayland session 
you need to tell it to turn IBus on by either adding an IBus input method to 
your input sources or make use of the Screen Keyboard feature.

  And I've only seen the issue with the Firefox and Chromium snaps.

  Warning message if you start firefox from terminal:

  [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could
  not connect: Permission denied: 'glib warning', file
  /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167

  (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to
  ibus: Could not connect: Permission denied

  gnome-settings-daemon
  -
  gnome-settings-daemon 44 Beta makes the situation worse since it always turns 
IBus on in both Wayland and X11, but I reverted 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that 
we could continue with the update. See 
https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+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 2009564] Re: Touchpad disabling while typing does not work

Please report the bug to:

  https://gitlab.freedesktop.org/libinput/libinput/-/issues

and mention the machine model is Razer x Lambda.

** Summary changed:

- Touchpad disabling while typing does not work
+ [Razer x Lambda] Touchpad disabling while typing does not work

** No longer affects: mutter (Ubuntu)

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

Title:
  [Razer x Lambda] Touchpad disabling while typing does not work

Status in libinput package in Ubuntu:
  New

Bug description:
  It makes my laptop much less usable.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.85.05  Sat Jan 14 
00:49:50 UTC 2023
   GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  7 00:44:08 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi/9858, 5.19.0-32-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
   backport-iwlwifi/9858, 5.19.0-35-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
   nvidia/525.85.05, 5.15.0-56-generic, x86_64: installed
   nvidia/525.85.05, 5.19.0-32-generic, x86_64: installed
   nvidia/525.85.05, 5.19.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. Device [1a58:201f]
   NVIDIA Corporation Device [10de:24e0] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. Device [1a58:201f]
  InstallationDate: Installed on 2023-01-03 (62 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Razer x Lambda TensorBook (2022)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=4cd4fe61-a6ef-48c5-acc8-b96e7da91171 ro button.lid_init_state=open 
i915.enable_fbc=0 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2022
  dmi.bios.release: 1.0
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: CH580
  dmi.board.vendor: Razer x Lambda
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer x Lambda
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd07/29/2022:br1.0:efr1.0:svnRazerxLambda:pnTensorBook(2022):pvr8.04:rvnRazerxLambda:rnCH580:rvr4:cvnRazerxLambda:ct10:cvr:skuRZ09-0421NEL9:
  dmi.product.family: 1A58201F Razer x Lambda TensorBook
  dmi.product.name: TensorBook (2022)
  dmi.product.sku: RZ09-0421NEL9
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer x Lambda
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1

[Desktop-packages] [Bug 2008613] Re: gnome-shell crashed with SIGSEGV in meta_window_actor_queue_destroy(NULL) [ubuntu-d...@ubuntu.com/locations.js:370]

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

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_window_actor_queue_destroy(NULL) [ubuntu-
  d...@ubuntu.com/locations.js:370]

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

Bug description:
  Hello,

  just got this after updating to the new packages on 23.04 beta,

  Thank you

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 43.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-14.14-generic 6.1.6
  Uname: Linux 6.1.0-14-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 26 04:52:05 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-10-04 (144 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  JournalErrors:
   Feb 26 04:52:01 hostname evince[4624]: The peer-to-peer connection failed: 
Error while getting peer-to-peer dbus connection: Could not connect: Permission 
denied. Falling back to the session bus. Your application is probably missing 
--filesystem=xdg-run/gvfsd privileges.
   Feb 26 04:52:02 hostname evince[4624]: The peer-to-peer connection failed: 
Error while getting peer-to-peer dbus connection: Could not connect: Permission 
denied. Falling back to the session bus. Your application is probably missing 
--filesystem=xdg-run/gvfsd privileges.
   Feb 26 04:52:02 hostname evince[4624]: The peer-to-peer connection failed: 
Could not connect: Permission denied. Falling back to the session bus. Your 
application is probably missing --filesystem=xdg-run/gvfsd privileges.
   Feb 26 04:52:02 hostname evince[4624]: The peer-to-peer connection failed: 
Could not connect: Permission denied. Falling back to the session bus. Your 
application is probably missing --filesystem=xdg-run/gvfsd privileges.
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 43.2-6ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to lunar on 2022-11-18 (99 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/2008613/+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 2007124] Re: Move available config files from /etc to /usr

This bug was fixed in the package fontconfig - 2.14.1-3ubuntu3

---
fontconfig (2.14.1-3ubuntu3) lunar; urgency=medium

  * Implement the transition of available config files from /etc to
/usr after a decade of delay (LP: #2007124).

fontconfig (2.14.1-3ubuntu2) lunar; urgency=medium

  * debian/control:
- Make fontconfig-config break/replace kubuntu-settings-desktop
  << 1:23.04.3 to handle symlink conflict (LP: #2005124).

 -- Gunnar Hjalmarsson   Thu, 23 Feb 2023 15:54:28
+0100

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

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

Title:
  Move available config files from /etc to /usr

Status in fontconfig package in Ubuntu:
  Fix Released

Bug description:
  At the upgrade to fontconfig 2.10 a decade ago, the directory for
  storing available config files was changed from /etc/fonts/conf.avail
  to /usr/share/fontconfig/conf.avail. It was done upstream as well as
  in Debian, but Ubuntu delayed the transition for some reason. I think
  we should do that transition in Ubuntu too. That will get Ubuntu in
  sync with the upstream documentation and the delta to Debian gets
  reduced a little.

  The changes needed are straightforward. I put a proposed upload in
  this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/fontconfig

  and I would appreciate someone's eyes on it.

  So, what's the caveat? The only thing I can think of is that distros,
  system admins and individual users may have tweaked the font
  configuration by including symlinks which point to the moved files.
  While I don't have the impression that such symlinks are very frequent
  — custom conf files put directly in /etc/fonts/conf.d or equivalent
  places in $HOME seem to be more common — to the extent they exist,
  they will be silently disabled.

  Bug #2005124 revealed an example of a symlink which pointed to a file
  which will be moved if we do this. OTOH, in that case upstream added a
  symlink with the very same name, so we had to deal with that conflict.
  If the name of Kubuntu's link had been something else, we might not be
  aware of it yet.

  The changelog for this upload:

  https://launchpad.net/ubuntu/+source/fontconfig/2.10.1-0ubuntu1

  states that the transition will be done "later with another upload
  once the details are sorted". Are there other details which I have
  missed? If not, I suppose that the potential inconvenience is
  approximately as big today as it was 2012. And since next LTS release
  is more than one year ahead, this ought to be an appropriate time to
  make the change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2007124/+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 2005124] Re: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubu

This bug was fixed in the package fontconfig - 2.14.1-3ubuntu3

---
fontconfig (2.14.1-3ubuntu3) lunar; urgency=medium

  * Implement the transition of available config files from /etc to
/usr after a decade of delay (LP: #2007124).

fontconfig (2.14.1-3ubuntu2) lunar; urgency=medium

  * debian/control:
- Make fontconfig-config break/replace kubuntu-settings-desktop
  << 1:23.04.3 to handle symlink conflict (LP: #2005124).

 -- Gunnar Hjalmarsson   Thu, 23 Feb 2023 15:54:28
+0100

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

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

Title:
  package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade:
  trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which
  is also in package kubuntu-settings-desktop 1:23.04.2

Status in fontconfig package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in fontconfig package in Debian:
  Unknown

Bug description:
   I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: fontconfig-config 2.13.1-4.4ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Feb  4 05:59:53 2023
  DuplicateSignature:
   package:fontconfig-config:2.13.1-4.4ubuntu1
   Unpacking fontconfig-config (2.14.1-3ubuntu1) over (2.13.1-4.4ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-xn7IM4/015-fontconfig-config_2.14.1-3ubuntu1_amd64.deb 
(--unpack):
trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is 
also in package kubuntu-settings-desktop 1:23.04.2
  ErrorMessage: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', 
which is also in package kubuntu-settings-desktop 1:23.04.2
  InstallationDate: Installed on 2023-01-31 (3 days ago)
  InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230130)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 
3.11.1-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.19ubuntu3
   apt  2.5.5
  SourcePackage: fontconfig
  Title: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: 
trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in 
package kubuntu-settings-desktop 1:23.04.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124/+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 2009637] [NEW] package libgl1-mesa-dri 22.3.6-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está también en el p

2023-03-07 Thread Adolfo Jayme Barrientos

Public bug reported:

Solved with a simple “apt --fix-broken install” but still…

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: libgl1-mesa-dri 22.3.6-1ubuntu1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: pass
CompositorRunning: None
Date: Tue Mar  7 15:25:16 2023
DistUpgraded: Fresh install
DistroCodename: lunar
DistroVariant: ubuntu
ErrorMessage: intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está también en el paquete 
libgl1-amber-dri:amd64 21.3.7-0ubuntu1
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / Radeon 
Vega Mobile Series] [103c:84e7]
InstallationDate: Installed on 2023-02-13 (22 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209)
MachineType: HP HP Pavilion Laptop 15-cw0xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic 
root=UUID=782cbb37-7870-44d8-aa55-53fdff89ddf8 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.20ubuntu2
 apt  2.5.6
SourcePackage: mesa
Title: package libgl1-mesa-dri 22.3.6-1ubuntu1 failed to install/upgrade: 
intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está 
también en el paquete libgl1-amber-dri:amd64 21.3.7-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/04/2021
dmi.bios.release: 15.46
dmi.bios.vendor: AMI
dmi.bios.version: F.46
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 84E7
dmi.board.vendor: HP
dmi.board.version: 99.30
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 99.30
dmi.modalias: 
dmi:bvnAMI:bvrF.46:bd01/04/2021:br15.46:efr99.30:svnHP:pnHPPavilionLaptop15-cw0xxx:pvr:rvnHP:rn84E7:rvr99.30:cvnHP:ct10:cvrChassisVersion:sku3PY37LA#ABM:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-cw0xxx
dmi.product.sku: 3PY37LA#ABM
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
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

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


** Tags: amd64 apport-package lunar single-occurrence ubuntu

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

Title:
  package libgl1-mesa-dri 22.3.6-1ubuntu1 failed to install/upgrade:
  intentando sobreescribir `/usr/lib/x86_64-linux-gnu/dri/i915_dri.so',
  que está también en el paquete libgl1-amber-dri:amd64 21.3.7-0ubuntu1

Status in mesa package in Ubuntu:
  New

Bug description:
  Solved with a simple “apt --fix-broken install” but still…

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: libgl1-mesa-dri 22.3.6-1ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Tue Mar  7 15:25:16 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ErrorMessage: intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', que está también en el paquete 
libgl1-amber-dri:amd64 21.3.7-0ubuntu1
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [103c:84e7]
  InstallationDate: Installed on 2023-02-13 (22 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209)
  MachineType: HP HP Pavilion Laptop 15-cw0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic 
root=UUID=782cbb37-7870-44d8-aa55-53fdff89ddf8 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.20ubuntu2
   apt  2.5.6
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 22.3.6-1ubuntu1 failed to install/upgrade: 
intentando

[Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-03-07 Thread William

You select your kernel in the grub boot menu. There is an option for
alternative boot configurations. I have a dual boot environment set up
so grub comes up every time for me. I think you hit esc to bring it up
if it normally boots straight into windows. If you have any trouble it
should come up in a search pretty quick.

-- 
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 2009630] Re: package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1

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

** This bug has been marked a duplicate of bug 2006744
   libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file 
conflict

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

Title:
  package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade:
  trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which
  is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1

Status in mesa package in Ubuntu:
  New

Bug description:
  Happens while using firefox, terminal (apt upgrade) and sudoku. Not
  sure what exactly trigerred that.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: libgl1-mesa-dri 22.2.5-0ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Tue Mar  7 21:38:45 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  DpkgTerminalLog:
   Preparing to unpack .../0-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb ...
   Unpacking libgl1-mesa-dri:amd64 (22.3.6-1ubuntu1) over (22.2.5-0ubuntu1) ...
   [1mdpkg:[0m error processing archive 
/tmp/apt-dpkg-install-CwQPZK/0-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is 
also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package 
libgl1-amber-dri:amd64 21.3.7-0ubuntu1
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2023-03-07 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230301.1)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic 
root=UUID=78e3203a-6ffc-477c-a477-6808bd319007 ro quiet splash
  Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.19ubuntu3
   apt  2.5.5
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also 
in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  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/mesa/+bug/2009630/+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 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor

2023-03-07 Thread Dave Jones

I'm still seeing this behaviour (precisely as described at the top:
fades to black, switches off, then switches on to black a second or two
later) with the lunar daily image and the bootstrap 6.2 kernel, so it'll
likely be an issue in lunar.

I'll flash a jammy and kinetic image to a card in a bit and try and re-
confirm them there but kinetic certainly exhibited the issue last week
before I upgraded my devel system.

In case this is monitor specific, the monitor I'm using is a Benq
GW2270H running at 1080p.

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

Title:
  [raspi] Ubuntu 22.10 does not turn off monitor

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a
  strange behaviour of the screen saver.

  In settings -> energy -> power saving options I selected Screen Blank
  after 5 minutes. After 5 minutes of inactivity, the screen goes blank,
  the monitor says No Signal and turns off, but a few seconds after it
  turns on again, showing a completely black screen.

  The desired behaviour here is that Ubuntu sends no signal to the
  monitor, so the monitor goes into low-consumption mode. But this is
  not happening, the monitor is on and showing a black screen.

  I wonder how to solve this problem, especially given the current
  energy situation in Europe.

  This bug is related to the Ubuntu 22.04 LTS and 22.10 version.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7
  Uname: Linux 5.19.0-1009-raspi aarch64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  4 21:31:27 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  ImageMediaBuild: 20221018.1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  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/linux-raspi/+bug/1998716/+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 2009630] [NEW] package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libg

2023-03-07 Thread Alexander Bejarano

Public bug reported:

Happens while using firefox, terminal (apt upgrade) and sudoku. Not sure
what exactly trigerred that.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: libgl1-mesa-dri 22.2.5-0ubuntu1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
Date: Tue Mar  7 21:38:45 2023
DistUpgraded: Fresh install
DistroCodename: lunar
DistroVariant: ubuntu
DpkgTerminalLog:
 Preparing to unpack .../0-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb ...
 Unpacking libgl1-mesa-dri:amd64 (22.3.6-1ubuntu1) over (22.2.5-0ubuntu1) ...
 [1mdpkg:[0m error processing archive 
/tmp/apt-dpkg-install-CwQPZK/0-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb 
(--unpack):
  trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is 
also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1
ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', 
which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2023-03-07 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230301.1)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic 
root=UUID=78e3203a-6ffc-477c-a477-6808bd319007 ro quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.19ubuntu3
 apt  2.5.5
SourcePackage: mesa
Title: package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also 
in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
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

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


** Tags: amd64 apport-package lunar single-occurrence ubuntu

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

Title:
  package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade:
  trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which
  is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1

Status in mesa package in Ubuntu:
  New

Bug description:
  Happens while using firefox, terminal (apt upgrade) and sudoku. Not
  sure what exactly trigerred that.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: libgl1-mesa-dri 22.2.5-0ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Tue Mar  7 21:38:45 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  DpkgTerminalLog:
   Preparing to unpack .../0-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb ...
   Unpacking libgl1-mesa-dri:amd64 (22.3.6-1ubuntu1) over (22.2.5-0ubuntu1) ...
   [1mdpkg:[0m error processing archive 
/tmp/apt-dpkg-install-CwQPZK/0-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is 
also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package

Re: [Desktop-packages] [Bug 2009564] Re: Touchpad disabling while typing does not work

2023-03-07 Thread Stephen Casper

Thanks, Daniel

   - I assumed this bug was known -- others online have had it. But I
   wanted to still report it in hope that it will not always be an issue.
   - Neither setting org.gnome.desktop.peripherals.touchpad
   disable-while-typing nor any other solution I have found online for this
   works. Everything has invariably failed to make the touchpad shut off while
   typing.
   - I have been trying earlier today to log in with Xorg, and this is its
   own can of worms. I can't, and I'm not sure why. I don't have the option to
   with a little gear on startup/login. And when I try to
   edit /etc/gdm3/custom.conf and restart the computer, it won't start up
   unless I use ctrl+alt+f4 to open up a virtual console on startup and undo
   the change to /etc/gdm3/custom.conf.

In summary, nothing works. If some immediate solution comes to mind, great.
Else, I'll hope for an update soon. Thanks!

On Tue, Mar 7, 2023 at 4:30 AM Daniel van Vugt <2009...@bugs.launchpad.net>
wrote:

> I assume you mean:
>
>   org.gnome.desktop.peripherals.touchpad disable-while-typing true
>
> Does it work any better if you log into Ubuntu on Xorg instead?
>
> ** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
>
> ** Also affects: libinput (Ubuntu)
>Importance: Undecided
>Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2009564
>
> Title:
>   Touchpad disabling while typing does not work
>
> Status in libinput package in Ubuntu:
>   New
> Status in mutter package in Ubuntu:
>   New
>
> Bug description:
>   It makes my laptop much less usable.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: xorg 1:7.7+23ubuntu2
>   ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
>   Uname: Linux 5.19.0-35-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular
> file.
>   .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
>   .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular
> file.
>   .proc.driver.nvidia.registry: Binary: ""
>   .proc.driver.nvidia.suspend: suspend hibernate resume
>   .proc.driver.nvidia.suspend_depth: default modeset uvm
>   .proc.driver.nvidia.version:
>NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.85.05  Sat Jan 14
> 00:49:50 UTC 2023
>GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
>   ApportVersion: 2.20.11-0ubuntu82.3
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: pass
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Mar  7 00:44:08 2023
>   DistUpgraded: Fresh install
>   DistroCodename: jammy
>   DistroVariant: ubuntu
>   DkmsStatus:
>backport-iwlwifi/9858, 5.19.0-32-generic, x86_64: installed (WARNING!
> Diff between built and installed module!) (WARNING! Diff between built and
> installed module!) (WARNING! Diff between built and installed module!)
> (WARNING! Diff between built and installed module!) (WARNING! Diff between
> built and installed module!) (WARNING! Diff between built and installed
> module!)
>backport-iwlwifi/9858, 5.19.0-35-generic, x86_64: installed (WARNING!
> Diff between built and installed module!) (WARNING! Diff between built and
> installed module!) (WARNING! Diff between built and installed module!)
> (WARNING! Diff between built and installed module!) (WARNING! Diff between
> built and installed module!) (WARNING! Diff between built and installed
> module!)
>nvidia/525.85.05, 5.15.0-56-generic, x86_64: installed
>nvidia/525.85.05, 5.19.0-32-generic, x86_64: installed
>nvidia/525.85.05, 5.19.0-35-generic, x86_64: installed
>   ExtraDebuggingInterest: I just need to know a workaround
>   GraphicsCard:
>Intel Corporation Alder Lake-P Integrated Graphics Controller
> [8086:46a6] (rev 0c) (prog-if 00 [VGA controller])
>  Subsystem: Razer USA Ltd. Device [1a58:201f]
>NVIDIA Corporation Device [10de:24e0] (rev a1) (prog-if 00 [VGA
> controller])
>  Subsystem: Razer USA Ltd. Device [1a58:201f]
>   InstallationDate: Installed on 2023-01-03 (62 days ago)
>   InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
> (20220809.1)
>   MachineType: Razer x Lambda TensorBook (2022)
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic
> root=UUID=4cd4fe61-a6ef-48c5-acc8-b96e7da91171 ro
> button.lid_init_state=open i915.enable_fbc=0 quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/29/2022
>   dmi.bios.release: 1.0
>   dmi.bios.vendor: Razer
>

[Desktop-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on Xorg

2023-03-07 Thread Gunnar Hjalmarsson

** Description changed:

  Test Case
  -
  From Ubuntu 23.04, install glib >= 2.75.3-3
+ 
+ Test 1:
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu on Xorg
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.
  
+ Test 2:
+ Install the ibus-libpinyin package.
+ Log out and log in again.
+ Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)"
+  to your input sources.
+ Log out
+ Click your name on the login screen.
+ Click the gear button to choose Ubuntu (on Wayland).
+ Enter your password to finish logging in.
+ Open Firefox (or Chromium)
+ Try to enter text in the address bar.
+ 
  What Happens
  
- No text is input
+ No text is inputted
  
  Other Info
  --
- This issue appears to only affects the Xorg session.
+ You see the issue as soon as IBus has been 'turned on'. With the current 
g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 
session IBus is always turned on due to im-config 0.55-1. In a Wayland session 
you need to tell it to turn IBus on by either adding an IBus input method to 
your input sources or make use of the Screen Keyboard feature.
  
  And I've only seen the issue with the Firefox and Chromium snaps.
  
+ Warning message if you start firefox from terminal:
+ 
+ [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could not
+ connect: Permission denied: 'glib warning', file
+ /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167
+ 
+ (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to
+ ibus: Could not connect: Permission denied
+ 
  gnome-settings-daemon
  -
- It also affected the Wayland session with gnome-settings-daemon 44 Beta, but 
I reverted 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that 
we could continue with the update. See 
https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93
+ gnome-settings-daemon 44 Beta makes the situation worse since it always turns 
IBus on in both Wayland and X11, but I reverted 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that 
we could continue with the update. See 
https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93
  
  Before I did that, I tested disabling our patches but it didn't make a
  difference.
- 
- The issue happens with kinetic's gnome-settings-daemon 43; it just looks
- like the gnome-settings-daemon commit made the situation worse but that
- commit was reverted.

** Summary changed:

- glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on Xorg
+ glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

** Summary changed:

- glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps
+ glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is 
turned on

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

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if
  IBus is turned on

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  Test Case
  -
  From Ubuntu 23.04, install glib >= 2.75.3-3

  Test 1:
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu on Xorg
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  Test 2:
  Install the ibus-libpinyin package.
  Log out and log in again.
  Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)"
   to your input sources.
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu (on Wayland).
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  What Happens
  
  No text is inputted

  Other Info
  --
  You see the issue as soon as IBus has been 'turned on'. With the current 
g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 
session IBus is always turned on due to im-config 0.55-1. In a Wayland session 
you need to tell it to turn IBus on by either adding an IBus input method to 
your input sources or make use of the Screen Keyboard feature.

  And I've only seen the issue with the Firefox and Chromium snaps.

  Warning message if you start firefox from terminal:

  [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could
  not connect: Permission denied: 'glib warning', file
  /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167

  (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to
  ibus: Could not connect: Permission denied

  gnome-settings-daemon
  -
  gnome-settings-daemon 44 Beta makes the situation

[Desktop-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

2023-03-07 Thread Jeremy Bícha

** Description changed:

  Test Case
  -
+ From Ubuntu 23.04, install glib >= 2.75.3-3
+ Log out
+ Click your name on the login screen.
+ Click the gear button to choose Ubuntu on Xorg
+ Enter your password to finish logging in.
+ Open Firefox (or Chromium)
+ Try to enter text in the address bar.
  
+ What Happens
+ 
+ No text is input
  
- Original Bug Report
- ---
- While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I 
noticed that I could no longer enter text in the address bars for the Chromium 
or Firefox snaps.
+ Other Info
+ --
+ This issue appears to only affects the Xorg session.
  
- Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings-
+ It also affected the Wayland session with gnome-settings-daemon 44 Beta,
+ but I reverted https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/commit/27bc0889c so that we could continue with the update. See
  https://salsa.debian.org/gnome-team/gnome-settings-
  daemon/-/commit/baeeed93
  
  Before I did that, I tested disabling our patches but it didn't make a
  difference.
  
- I was unable to reproduce the issue on Debian Testing but there may have
- been differences in how snap was configured there.
- 
- I'm filing this bug since ideally we would not be diverging from
- upstream here.
+ The issue happens with kinetic's gnome-settings-daemon 43; it just looks
+ like the gnome-settings-daemon commit made the situation worse but that
+ commit was reverted.

** Description changed:

  Test Case
  -
  From Ubuntu 23.04, install glib >= 2.75.3-3
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu on Xorg
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.
  
  What Happens
  
  No text is input
  
  Other Info
  --
  This issue appears to only affects the Xorg session.
  
- It also affected the Wayland session with gnome-settings-daemon 44 Beta,
- but I reverted https://gitlab.gnome.org/GNOME/gnome-settings-
- daemon/-/commit/27bc0889c so that we could continue with the update. See
- https://salsa.debian.org/gnome-team/gnome-settings-
- daemon/-/commit/baeeed93
+ And I've only seen the issue with the Firefox and Chromium snaps.
+ 
+ gnome-settings-daemon
+ -
+ It also affected the Wayland session with gnome-settings-daemon 44 Beta, but 
I reverted 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that 
we could continue with the update. See 
https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93
  
  Before I did that, I tested disabling our patches but it didn't make a
  difference.
  
  The issue happens with kinetic's gnome-settings-daemon 43; it just looks
  like the gnome-settings-daemon commit made the situation worse but that
  commit was reverted.

** Summary changed:

- glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps
+ glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on Xorg

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

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on
  Xorg

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  Test Case
  -
  From Ubuntu 23.04, install glib >= 2.75.3-3
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu on Xorg
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  What Happens
  
  No text is input

  Other Info
  --
  This issue appears to only affects the Xorg session.

  And I've only seen the issue with the Firefox and Chromium snaps.

  gnome-settings-daemon
  -
  It also affected the Wayland session with gnome-settings-daemon 44 Beta, but 
I reverted 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that 
we could continue with the update. See 
https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

  The issue happens with kinetic's gnome-settings-daemon 43; it just
  looks like the gnome-settings-daemon commit made the situation worse
  but that commit was reverted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+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 2006070] Re: incredibly high memory usage

2023-03-07 Thread beadon

Ok, somewhat good news.  I have been watching the memory usage on the
machine as many applications start / stop , and am tracking the growth
and management.

A tool to tweak the behavior ---
One system parameter I had tweaked before reporting this issue was 
vm.swappiness , I had moved this down to 30, mostly because I'd like to get the 
best performance, while avoiding the use of swap space.  it had the intened 
effect, while using almost all available memory - generally a good thing (why 
have all this memory if you're not using it, right?).

Now, i've moved this back up to 60 (which I believe is the default for
the kernel options).  In response I am seeing better free-memory
management from the kernel.  The downside is that I am absolutely seeing
lower performance on and across web-pages and other applications as swap
is used a bit more.  The difference is measured in fractions of a
second, I could measure the difference but I'm not sure if this audience
would like to see those details (let me know if this is interesting).

For those at home --  edit:  /etc/sysctl.conf, modify or add the
parameter 'vm.swappiness = 60' and then on your terminal run 'sysctl
-p'.

I mention this on this bug thread because this parameter directly
effects the OOM killer behavior because the OOM killer appears to be
swapiness un-aware, and this is also the underlying behavior modifier
for the Chrome threads, and the Flatpak or gnome-software threads as
they grow in size.  I will continue to monitor for gnome-software
threads and memory usage, but this means the heavier memory usage is
effectively hidden by worse offenders (chrome likely being one of the
heaviest users for us all).


On Chrome -- 
Since Chrome is doing so much lately to manage their own threads, I hope this 
kerenel tuning parameter is kept in mind for memory management, it could save 
the team a lot of time building their own memory management utility/toolchain.  
There might even be some kind of alert / capability for the kernel to respond 
differently to certain applications depending on how aggressive they would like 
their own userspace managed.  (Kerenel development feature!)


One gnome-software --
I will keep tabs on the Flatpak memory usage.  In the mean time I have disabled 
snapd entirely.  I don't wish to manage my applications like this.  Apt is 
about as far as I want to go now, the interactions of many different pakage 
managers adds a lot of complexity.  I want to incentivize application 
develoeprs to use as few packaging systems as possible.  It's getting quite bad 
out there - there's are now whole businesses that have sprung up to convert the 
same binaries into different packaging formats and their dependencies.  It's 
really got to stop, it's such a waste of time and resources to 're-invent the 
wheel'.


On the root cause -- 
I would much prefer that we encourage developers to build statically compiled 
binaries, rather than build containers upon containers to manage what I see as 
effectively a problem stemming from resource sharing linked to library 
(mis)management.


I hope this is helpful to development here and across kernel
development.  I will continue to provide meaningful feedback as much as
possible.

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

Title:
  incredibly high memory usage

Status in GNOME Software:
  Unknown
Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  
  Please describe the issue you’re experiencing:
  gnome-software is consuming 6+ GB of RAM on my machine.  This is unacceptable 
and is affecting all other applications.
  Error message appearing in /var/log/syslog
  N/A -- other processes are fighting for memory, and OOM killer is more active.
  What Linux distribution are you using, and what kind of package (RPM, deb, 
flatpak, etc.) are you experiencing the problem with?
  Ubuntu 22.10
  apt
  flatpak

  
  I don't know how to replicate this issue, however it does appear to be a 
problem retaining memory.  See LSOF report below,  software is gnome-software 
43.0
   

  
  ```
  sudo lsof -p 750448 -n > ~/ramusage.txt
  cat ramusage.txt | perl -lane 'print "$F[6] $F[0] $F[1] $F[2] $F[3] $F[4] 
$F[5] $F[7] $F[8] $F[9] $F[10]"' | sort -rn > sorted-report.txt
  ```

  
  Top 10 filehandles are holding onto something like 6GB of RAM?!  What's going 
on here ?
  (open filehandles, sorted by bytes):

  ```
1 157191688 gnome-sof 750448 beadon 11u netlink 0t0 ROUTE
2 103546882 gnome-sof 750448 beadon DEL REG 259,2 
/usr/share/icons/hicolor/icon-theme.cache
3 103022860 gnome-sof 750448 beadon DEL REG 259,2 
/usr/share/glib-2.0/schemas/gschemas.compiled
4 61210892 gnome-sof 750448 beadon DEL REG 259,2 
/var/lib/flatpak/exports/share/icons/hicolor/icon-theme.cache
5 60828700 gnome-sof 750448 beadon DEL REG 259,2

[Desktop-packages] [Bug 581341] Re: Xnest application are not asked to redraw their windows

2023-03-07 Thread nacorn

This bug affects me. I am running xnest 2:21.1.3-2ubuntu2.7

When moving a window in the outer X server over the Xnest window, and
then moving it away again, the Xnest screen is redrawn (the window
manage draws the root widow background, window borders, title bar, and
window background) but the applications do not redraw their contents.

For example I have an xterm in the xnest server (white background).
When I do as described above I see the xterm with its white background,
but the contents is missing. If I move the mouse into the window then I
see the cursor but nothing else. If I move another window inside the
xnest server onto the xterm and then move it off again then the xterm
does redraw its contents (just the part that was "damaged" by the
obscuring window.

See images.tgz
tar xzf images.tgz

b1.png - Xnest with 2 xterms and fvwm
b2.png - Obscured by window in outer X server
b3.png - Obscuring window removed. Note that white xterm has no content now.
b4.png - Partially obscured by xterm in Xnest server,
b5.png - obscuring window removed. Note that white xterm has been partially
redrawn.

** Attachment added: "images.tgz"

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/581341/+attachment/5652496/+files/images.tgz

** Changed in: xorg-server (Ubuntu)
Status: Expired => Confirmed

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

Title:
Xnest application are not asked to redraw their windows

Status in xorg-server package in Ubuntu:
Confirmed

Bug description:
Run these commands in a command line window (bash):
#---
Xnest :1 &
sleep 2
DISPLAY=:1.0 gedit
#---

You will get a poor Xnest window with a gedit window in it, which
works perfectly.

But when moving another not-Xnest-window over it and then away again,
the parts of gedit in the Xnest window are not redrawn automatically.
only parts of it when moving or clicking around (which is normal
behavior in such application).

gedit is only an example, the problem happens with all applications,
and also with metacity loaded in Xnest. Only xlogo (and maybe other
test applications) seems to realize it has to update itself.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xnest 2:1.7.6-2ubuntu7
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
Architecture: amd64
Date: Sun May 16 16:50:35 2010
ExecutablePath: /usr/bin/Xnest
SourcePackage: xorg-server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/581341/+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 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

2023-03-07 Thread Jeremy Bícha

Gunnar, can you add a test case to the bug description?

I don't know how to reproduce this issue with a new Ubuntu 23.04 install
(using American English).

By the way, the issue still exists with glib 2.75.4-1 (currently in
Debian Experimental and not in Ubuntu yet).

** Description changed:

- While preparing the gnome-settings-daemon 44 Beta update for Ubuntu
- 23.04, I noticed that I could no longer enter text in the address bars
- for the Chromium or Firefox snaps.
+ Test Case
+ -
+ 
+ 
+ Original Bug Report
+ ---
+ While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I 
noticed that I could no longer enter text in the address bars for the Chromium 
or Firefox snaps.
  
  Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/commit/27bc0889c so that we could continue with the update. See
  https://salsa.debian.org/gnome-team/gnome-settings-
  daemon/-/commit/baeeed93
  
  Before I did that, I tested disabling our patches but it didn't make a
  difference.
  
  I was unable to reproduce the issue on Debian Testing but there may have
  been differences in how snap was configured there.
  
  I'm filing this bug since ideally we would not be diverging from
  upstream here.

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

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  Test Case
  -

  
  Original Bug Report
  ---
  While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I 
noticed that I could no longer enter text in the address bars for the Chromium 
or Firefox snaps.

  Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/commit/27bc0889c so that we could continue with the update.
  See https://salsa.debian.org/gnome-team/gnome-settings-
  daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

  I was unable to reproduce the issue on Debian Testing but there may
  have been differences in how snap was configured there.

  I'm filing this bug since ideally we would not be diverging from
  upstream here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+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 2008420] Re: '/usr/share/applications/default.list' content outdated

This bug was fixed in the package desktop-file-utils - 0.26-1ubuntu5

---
desktop-file-utils (0.26-1ubuntu5) lunar; urgency=medium

  * defaults.list: use the current .desktop for rhythmbox (lp: #2008420)

 -- Sebastien Bacher   Mon, 06 Mar 2023 13:07:27
+0100

** Changed in: desktop-file-utils (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  '/usr/share/applications/default.list' content outdated

Status in desktop-file-utils package in Ubuntu:
  Fix Released

Bug description:
  For Ubuntu 22.10 and 23.04, the contents of file
  /usr/share/applcations/default.list has file associations for audio
  file set as 'rhythmbox.desktop' as the application startup file to
  associate files to... That file was updated and changed names to
  'org.gnome.Rhythmbox3.desktop'...

  File '/usr/share/applications/defaults.list' needs to be updated to
  reflect that change.

  I know that the system that file belongs to, is underlying to
  nautilus, but I was unsure on what to file this issue against.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
  Uname: Linux 5.19.0-31-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 23 13:08:55 2023
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-02-23 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2008420/+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 2007742] Re: Can't update stage views actor

2023-03-07 Thread Jacob Ray Gilman

Same issue w/ my system locking up for about 30 seconds to 1 minute each
time it happens:

Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views 
actor [:0x55e06fa94310] is on because it needs an 
allocation.
Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views 
actor [:0x55e075f10b10] is on because it needs an 
allocation.
Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views 
actor [:0x55e06fce46c0] is on because it needs an 
allocation.
Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views 
actor [:0x55e07281faf0] is on because it needs an 
allocation.
Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views 
actor [:0x55e072823850] is on because it needs an 
allocation.
Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views 
actor [:0x55e07281e740] is on because it needs an 
allocation.
Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views 
actor [:0x55e0728226d0] is on because it needs an 
allocation.

My system is running Pop! OS 22.04 - it's not Ubuntu, but it is based on
it and I figured this would be useful.

jacob@jacob-hp-dev-one 
-- 
OS: Pop!_OS 22.04 LTS x86_64 
Host: Dev One Notebook PC 
Kernel: 6.1.11-76060111-generic 
Uptime: 23 hours, 26 mins 
Packages: 2289 (dpkg), 16 (flatpak), 6 (snap) 
Shell: bash 5.1.16 
Resolution: 1920x1080, 1920x1080 
DE: GNOME 42.5 
WM: Mutter 
WM Theme: Pop 
Theme: Pop-dark [GTK2/3] 
Icons: Pop [GTK2/3] 
Terminal: gnome-terminal 
CPU: AMD Ryzen 7 PRO 5850U with Radeon Graphics (16) @ 1.900GHz 
GPU: AMD ATI 03:00.0 Cezanne 
Memory: 17926MiB / 63630MiB

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

Title:
  Can't update stage views actor 

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

Bug description:
  These messages repeat:

  [  105.711276] ingenika gnome-shell[2919]: Can't update stage views actor 
[:0x55bba91da500] is on because it needs an 
allocation.
  [  105.711772] ingenika gnome-shell[2919]: Can't update stage views actor 
[:0x55bbac95c330] is on because it needs an 
allocation.
  [  105.711903] ingenika gnome-shell[2919]: Can't update stage views actor 
[:0x55bbae726860] is on because it needs an 
allocation.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  Uname: Linux 6.1.11-060111-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 17 21:54:39 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-08-22 (179 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-02-08 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2007742/+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 2008791] Re: Disk properties in Gnome Files (Nautilus) shows a black chart for disk usage on Ubuntu 22.04

2023-03-07 Thread Sebastien Bacher

Which Ubuntu release, theme and variant are you using?

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

** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Disk properties in Gnome Files (Nautilus) shows a black chart for disk
  usage on Ubuntu 22.04

Status in nautilus package in Ubuntu:
  Incomplete
Status in yaru-theme package in Ubuntu:
  New

Bug description:
  if I open the Properties window for a disk (not a plain folder) the
  pie chart intended to show disk usage is all black (screenshot
  attached). On previous versions it used to have different colors for
  "used" and "free" space.

  Testing a clean install on a virtual machine gives the same results so
  it's not an issue related to the upgrade process. I guess it's related
  to the theming features added to Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2008791/+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 2008791] Re: Disk properties in Gnome Files (Nautilus) shows a black chart for disk usage on Ubuntu 22.04

2023-03-07 Thread Marcus Aurelius

Despite affecting Nautilus from the user's perspective, on second
thought I think the bug is in yaru-theme.

** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Disk properties in Gnome Files (Nautilus) shows a black chart for disk
  usage on Ubuntu 22.04

Status in nautilus package in Ubuntu:
  New
Status in yaru-theme package in Ubuntu:
  New

Bug description:
  if I open the Properties window for a disk (not a plain folder) the
  pie chart intended to show disk usage is all black (screenshot
  attached). On previous versions it used to have different colors for
  "used" and "free" space.

  Testing a clean install on a virtual machine gives the same results so
  it's not an issue related to the upgrade process. I guess it's related
  to the theming features added to Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2008791/+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 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller

2023-03-07 Thread Timo Aaltonen

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: Confirmed => Won't Fix

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

Title:
  Fix HFP mSBC support on Realtek Bluetooth USB controller

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in pulseaudio source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in pulseaudio source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in pulseaudio source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  When a BT headset is connected Realtek BT USB controller, HFP profile can't 
play or record sound when mSBC codec is used.

  [Fix]
  At Linux kernel side, add a Realtek specific quirk to support mSBC.

  At PulseAudio side, send more data frames until the connected device
  sends response.

  [Test]
  Connect different headsets to the said controller, HFP can play and record 
sounds now.
  Also verified A2DP profile is unaffected.

  [Where problems could occur]
  The kernel part is Realtek specific, so the regression risk is very limited.

  The pulseaudio side only affects HFP profile, since the codeflow only
  changes when a mic is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 2009301] Re: package libxau-dev:amd64 1:1.0.9-1build5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

2023-03-07 Thread Timo Aaltonen

Your root disk is fairly full, so I assume it got filled up at some
point and the package got corrupted or something. Do as it suggests and
reinstall libxau-dev

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

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

Title:
  package libxau-dev:amd64 1:1.0.9-1build5 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in libxau package in Ubuntu:
  Invalid

Bug description:
  this is the fifth time it happens after few days of installing linux

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libxau-dev:amd64 1:1.0.9-1build5
  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
  CompositorRunning: None
  Date: Sun Mar  5 23:04:38 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DuplicateSignature:
   package:libxau-dev:amd64:1:1.0.9-1build5
   Setting up imagemagick-6-common (8:6.9.11.60+dfsg-1.3ubuntu0.22.04.1) ...
   dpkg: error processing package libxau-dev:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / 
Radeon 520 Mobile] [1028:06b2]
  InstallationDate: Installed on 2022-11-09 (115 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0bda:5684 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Unidentified System
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=f99443b7-ddd9-46e2-8c17-95b2826ad7f2 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: libxau
  Title: package libxau-dev:amd64 1:1.0.9-1build5 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2016
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 04D1V1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd10/06/2016:br1.2:svnDellInc.:pnUnidentifiedSystem:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct9:cvr:sku06B2:
  dmi.product.name: Unidentified System
  dmi.product.sku: 06B2
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/2009301/+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 2009598] Re: Error when I run "sudo apt upgrade"

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

** This bug has been marked a duplicate of bug 2006744
   libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file 
conflict

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

Title:
  Error when I run "sudo apt upgrade"

Status in mesa package in Ubuntu:
  New

Bug description:
  When I run sudo apt upgrade, I have this error :

  package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade:
  tentative de remplacement de « /usr/lib/x86_64-linux-
  gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber-
  dri:amd64 21.3.7-0ubuntu1

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: libgl1-mesa-dri 22.2.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Tue Mar  7 14:07:39 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ErrorMessage: tentative de remplacement de « 
/usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui appartient aussi au paquet 
libgl1-amber-dri:amd64 21.3.7-0ubuntu1
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2023-02-25 (9 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230216)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic 
root=UUID=3274a782-2ac3-4126-ae6f-61555798cd06 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.20ubuntu2
   apt  2.5.6
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: 
tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui 
appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2014
  dmi.bios.release: 1.11
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.11
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.54
  dmi.chassis.asset.tag: CNU422B518
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 21.84
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:br1.11:efr21.84:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:skuF9W54UP#UUZ:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.sku: F9W54UP#UUZ
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  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/mesa/+bug/2009598/+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 2009481] Re: FFE: mesa 23.0.1

2023-03-07 Thread Timo Aaltonen

works fine on my machines, but I've amended the request to use 23.0.1
which should be released in a day or two, unless the upstream CI is
acting up.

** Summary changed:

- FFE: mesa 23.0.0
+ FFE: mesa 23.0.1

** Description changed:

  Mesa 23.0.0 was released on Feb 23rd, and this is the planned branch to
  use for Ubuntu 23.04.
  
  This release includes improvements across the board, and packaging adds
  a package for mesa-drm-shim.
+ 
+ 23.0.1 should be released on week 10, so it's a good candidate for an
+ upload.

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

Title:
  FFE: mesa 23.0.1

Status in mesa package in Ubuntu:
  In Progress

Bug description:
  Mesa 23.0.0 was released on Feb 23rd, and this is the planned branch
  to use for Ubuntu 23.04.

  This release includes improvements across the board, and packaging
  adds a package for mesa-drm-shim.

  23.0.1 should be released on week 10, so it's a good candidate for an
  upload.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009481/+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 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor

2023-03-07 Thread Manuel Diewald

I was unable to reproduce this behavior on an up-to-date 22.04 and on
22.10 (5.19.0-1009-raspi) with gnome-shell 43.0-1ubuntu2 running on a
Pi4 device.

Do you still experience the issue with the latest kernel image and
firmware installed? Have you tried to reproduce the problem with a
different monitor?

** Changed in: linux-raspi (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  [raspi] Ubuntu 22.10 does not turn off monitor

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a
  strange behaviour of the screen saver.

  In settings -> energy -> power saving options I selected Screen Blank
  after 5 minutes. After 5 minutes of inactivity, the screen goes blank,
  the monitor says No Signal and turns off, but a few seconds after it
  turns on again, showing a completely black screen.

  The desired behaviour here is that Ubuntu sends no signal to the
  monitor, so the monitor goes into low-consumption mode. But this is
  not happening, the monitor is on and showing a black screen.

  I wonder how to solve this problem, especially given the current
  energy situation in Europe.

  This bug is related to the Ubuntu 22.04 LTS and 22.10 version.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7
  Uname: Linux 5.19.0-1009-raspi aarch64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  4 21:31:27 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  ImageMediaBuild: 20221018.1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  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/linux-raspi/+bug/1998716/+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 2009598] [NEW] Error when I run "sudo apt upgrade"

2023-03-07 Thread John Doe

Public bug reported:

When I run sudo apt upgrade, I have this error :

package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade:
tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so
», qui appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: libgl1-mesa-dri 22.2.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: unknown
CompositorRunning: None
Date: Tue Mar  7 14:07:39 2023
DistUpgraded: Fresh install
DistroCodename: lunar
DistroVariant: ubuntu
ErrorMessage: tentative de remplacement de « 
/usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui appartient aussi au paquet 
libgl1-amber-dri:amd64 21.3.7-0ubuntu1
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
InstallationDate: Installed on 2023-02-25 (9 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230216)
MachineType: Hewlett-Packard HP EliteBook 840 G1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic 
root=UUID=3274a782-2ac3-4126-ae6f-61555798cd06 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.20ubuntu2
 apt  2.5.6
SourcePackage: mesa
Title: package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: 
tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui 
appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/29/2014
dmi.bios.release: 1.11
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L71 Ver. 01.11
dmi.board.name: 198F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.54
dmi.chassis.asset.tag: CNU422B518
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.ec.firmware.release: 21.84
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:br1.11:efr21.84:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:skuF9W54UP#UUZ:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 840 G1
dmi.product.sku: F9W54UP#UUZ
dmi.product.version: A3009DD10203
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
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

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


** Tags: amd64 apport-package lunar single-occurrence ubuntu

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

Title:
  Error when I run "sudo apt upgrade"

Status in mesa package in Ubuntu:
  New

Bug description:
  When I run sudo apt upgrade, I have this error :

  package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade:
  tentative de remplacement de « /usr/lib/x86_64-linux-
  gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber-
  dri:amd64 21.3.7-0ubuntu1

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: libgl1-mesa-dri 22.2.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Tue Mar  7 14:07:39 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ErrorMessage: tentative de remplacement de « 
/usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui appartient aussi au paquet 
libgl1-amber-dri:amd64 21.3.7-0ubuntu1
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2023-02-25 (9 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230216)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcKernelCmdLine:

[Desktop-packages] [Bug 2009592] Re: gjs-console crashed with SIGABRT

2023-03-07 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1986455, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2009592/+attachment/5652398/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/2009592/+attachment/5652400/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2009592/+attachment/5652403/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2009592/+attachment/5652404/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/2009592/+attachment/5652405/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/2009592/+attachment/5652406/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/2009592/+attachment/5652407/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1986455

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gjs-console crashed with SIGABRT

Status in gjs package in Ubuntu:
  New

Bug description:
  Unknown action caused this crash

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gjs 1.75.2-2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  7 07:27:56 2023
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2022-12-02 (94 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221202)
  ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters 
--gapplication-service
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gjs
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgtk-4.so.1
   g_object_unref () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgjs.so.0
  Title: gjs-console crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

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

Re: [Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-03-07 Thread Robert Pearson

"Booting with linux-image-5.19.0-21-generic lists the audio
devices again."

So how do I do that?

On Tue, Mar 7, 2023 at 5:20 AM William <2007...@bugs.launchpad.net>
wrote:

> Booting with linux-image-5.19.0-35-generic appears to be the problem in
> 22.10. Booting with linux-image-5.19.0-21-generic lists the audio
> devices again.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>
>

-- 
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:

[Desktop-packages] [Bug 2009587] [NEW] Can't set sound output to Displayport screen - not listed anymore

2023-03-07 Thread Célian Godefroid

Public bug reported:

It's very recent, but I can't seem to set the audio output to my screens
as they are not listed anymore in the Sound settings panel.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar  7 12:37:41 2023
InstallationDate: Installed on 2022-05-31 (280 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.00
dmi.board.asset.tag: Default string
dmi.board.name: Z270 GAMING M7 (MS-7A57)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.00:bd12/06/2016:br5.12:svnMSI:pnMS-7A57:pvr1.0:rvnMSI:rnZ270GAMINGM7(MS-7A57):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7A57
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2009587

Title:
  Can't set sound output to Displayport screen - not listed anymore

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  It's very recent, but I can't seem to set the audio output to my
  screens as they are not listed anymore in the Sound settings panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  7 12:37:41 2023
  InstallationDate: Installed on 2022-05-31 (280 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.00
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270 GAMING M7 (MS-7A57)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.00:bd12/06/2016:br5.12:svnMSI:pnMS-7A57:pvr1.0:rvnMSI:rnZ270GAMINGM7(MS-7A57):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7A57
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

Re: [Desktop-packages] [Bug 2008433] Re: Request to enable WidevineCDM checking on ARM64

2023-03-07 Thread Nathan Teodosio

Ah, didn't know you were in Bionic. I'll build it in a PPA.

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

Title:
  Request to enable WidevineCDM checking on ARM64

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  If possible, could you please include a patch to enable widevinecdm
  checking on ARM64 linux? currently BUNDLE_WIDEVINE_CDM does not get
  set for arm64 linux (but does on amd64 linux) so chromium does not
  even check for widevine even if we have it available and placed in the
  directory manually.

  I am currently using the attached patch of my making when testing
  locally to correct this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2008433/+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 2000868] Re: backport required for virtio_gpu_dri.so

2023-03-07 Thread mohan43u

I'm not sure I can help here. I have been using kisak ppa with latest
mesa. I dont want to downgrade mesa packages.

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

Title:
  backport required for virtio_gpu_dri.so

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  xorg crashing when using modsetting with virtio_gpu_dri as graphics
  driver in kvm guest. Kindly look into this conversation

  https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/291#note_1701920

  I think we need to backport
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19655 to fix
  this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2000868/+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-03-07 Thread William

Booting with linux-image-5.19.0-35-generic appears to be the problem in
22.10. Booting with linux-image-5.19.0-21-generic lists the audio
devices again.

-- 
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 2008613] Re: gnome-shell crashed with SIGSEGV in meta_window_actor_queue_destroy(NULL) [ubuntu-d...@ubuntu.com/locations.js:370]

2023-03-07 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2008613

** Tags added: iso-testing

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_window_actor_queue_destroy(NULL) [ubuntu-
  d...@ubuntu.com/locations.js:370]

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Committed

Bug description:
  Hello,

  just got this after updating to the new packages on 23.04 beta,

  Thank you

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 43.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-14.14-generic 6.1.6
  Uname: Linux 6.1.0-14-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 26 04:52:05 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-10-04 (144 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  JournalErrors:
   Feb 26 04:52:01 hostname evince[4624]: The peer-to-peer connection failed: 
Error while getting peer-to-peer dbus connection: Could not connect: Permission 
denied. Falling back to the session bus. Your application is probably missing 
--filesystem=xdg-run/gvfsd privileges.
   Feb 26 04:52:02 hostname evince[4624]: The peer-to-peer connection failed: 
Error while getting peer-to-peer dbus connection: Could not connect: Permission 
denied. Falling back to the session bus. Your application is probably missing 
--filesystem=xdg-run/gvfsd privileges.
   Feb 26 04:52:02 hostname evince[4624]: The peer-to-peer connection failed: 
Could not connect: Permission denied. Falling back to the session bus. Your 
application is probably missing --filesystem=xdg-run/gvfsd privileges.
   Feb 26 04:52:02 hostname evince[4624]: The peer-to-peer connection failed: 
Could not connect: Permission denied. Falling back to the session bus. Your 
application is probably missing --filesystem=xdg-run/gvfsd privileges.
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 43.2-6ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to lunar on 2022-11-18 (99 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2008613/+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 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])

22.3.1+ includes these two commits:
intel: factor out dispatch PS enabling logic
intel: add missing restriction on fragment simd dispatch
They are not in 22.2.x

The other two commits:
intel/common/intel_genX_state.h: Add intel_set_ps_dispatch_state()
intel/blorp: Fix a hang caused by invalid dispatch enables on gfx7
are only in 23.0.

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

Title:
  Asynchronous wait on fence ... timed out
  (hint:intel_atomic_commit_ready [i915])

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Jammy:
  New
Status in mesa source package in Kinetic:
  New
Status in mesa source package in Lunar:
  New

Bug description:
  GUI hard lock during zoom session and gnome-terminal

  kern.log shows a mix of errors 
  __
  kernel: [ 3627.948545] Asynchronous wait on fence 
:00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready 
[i915])
  kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 
12:1:85db, in chrome [5521]
  kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped 
heartbeat on rcs0
  kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset 
due to GPU hang
  kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware 
i915/adlp_guc_70.1.1.bin version 70.1
  kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware 
i915/tgl_huc_7.9.3.bin version 7.9
  kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated
  kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled
  kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled
  ___

  I suspect this issue to be 
  upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755
  upstream commit: 
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217

  Reproducer: Although I don't have my own reproducer, the upstream mesa
  reproducer does trigger a hang on my machine.

  Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it
  loads, you will see pikachu. Press "S", he will go back.  My whole
  system freezes from this in Wayland, regardless of the browser.

  Kernel: 6.0.0-1008-oem
  Mesa: 22.2.5-0ubuntu0.1~22.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9
  Uname: Linux 6.0.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  8 21:40:19 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0b1a]
 Subsystem: Dell Device [1028:0b1a]
  InstallationDate: Installed on 2022-07-13 (211 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  MachineType: Dell Inc. Precision 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash 
mem_sleep_default=deep vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2022
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.1
  dmi.board.name: 03M8N5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A:
  dmi.product.family: Precision
  dmi.product.name: Precision 5570
  dmi.product.sku: 0B1A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau

[Desktop-packages] [Bug 2000868] Re: backport required for virtio_gpu_dri.so

22.2.5+ is now in jammy/kinetic/lunar updates.

mohan43u and others, can you can confirm it is fixed for you now?

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

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

Title:
  backport required for virtio_gpu_dri.so

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  xorg crashing when using modsetting with virtio_gpu_dri as graphics
  driver in kvm guest. Kindly look into this conversation

  https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/291#note_1701920

  I think we need to backport
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19655 to fix
  this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2000868/+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 2006645] Re: Death Stranding(Video Game) crashes consistenly when moving right control stick with map open

Lunar is now at 22.3.6-1ubuntu1, including this fix.

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

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

Title:
  Death Stranding(Video Game) crashes consistenly when moving right
  control stick with map open

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  New
Status in mesa source package in Kinetic:
  New

Bug description:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/7735#note_1674704

  99% sure it's this bug on Mesa's gitlab. Installing the kisak-mesa PPA
  fixed the issue for me. Any chance of a backport for the fix?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006645/+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 2009435] Re: Xorg freeze

** Package changed: xorg (Ubuntu) => nautilus (Ubuntu)

** Summary changed:

- Xorg freeze
+ Nautilus freeze

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

Title:
  Nautilus freeze

Status in nautilus package in Ubuntu:
  New

Bug description:
  Files application hangs when switched to from other application. Only
  occurs when mounted to internal HDD.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  6 08:50:17 2023
  DistUpgraded: 2022-09-30 11:53:10,478 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-67-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / 
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Sapphire Technology Limited Lexa PRO [Radeon RX 550] [1da2:e367]
  InstallationDate: Installed on 2020-10-24 (862 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=9db35888-ce9e-4ddd-96ab-979cf2de8c9e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-09-30 (156 days ago)
  dmi.bios.date: 11/13/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2006
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2006:bd11/13/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2009435/+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 2000409] Re: totem crashes on startup (assert !xcb_xlib_unknown_req_in_deq) in _XReply because XInitThreads is not called early enough by libx11 (patch included)

** Tags added: nvidia

** Summary changed:

- totem crashes on startup (assert !xcb_xlib_unknown_req_in_deq) in _XReply 
because XInitThreads is not called early enough by libx11 (patch included)
+ [nvidia] totem crashes on startup (assert !xcb_xlib_unknown_req_in_deq) in 
_XReply because XInitThreads is not called early enough by libx11 (patch 
included)

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

Title:
  [nvidia] totem crashes on startup (assert
  !xcb_xlib_unknown_req_in_deq) in _XReply because XInitThreads is not
  called early enough by libx11 (patch included)

Status in Totem:
  New
Status in totem package in Ubuntu:
  In Progress

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.10
  Release:  22.10
  Codename: kinetic

  totem 43.0-2ubuntu1
  proprietary nvidia-driver-525 525.60.11-0ubuntu0.22.10.1
  libx11-6   2:1.8.1-2

  Totem crashes (most of the time) when opening a video file. When it
  does crash, it crashes before playing the video at all.

  It doesn't crash often when being run under gdb, profilers, or other
  utilities that may slow down execution. That indicated it may be a
  threading issue or race condition, and after digging deeper the issue
  is evident from the assert message.

    [xcb] Unknown sequence number while processing queue
    [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
    [xcb] Aborting, sorry about that.

  A similar issue happened in SDL, where XInitThreads was *supposed* to
  be called but wasn't called early enough, specifically by the NVIDIA
  libGL implementation which I also happen to be using.

    https://github.com/libsdl-org/SDL-1.2/issues/753

  (Attempted to use apport to report this, but for some reason it
  doesn't want to upload or show me the report. I've included the gdb
  stack trace here.)

  andy@andy-i9:/var/crash$ gdb totem totem/CoreDump
  GNU gdb (Ubuntu 12.1-3ubuntu2) 12.1
  Copyright (C) 2022 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from totem...

  This GDB supports auto-downloading debuginfo from the following URLs:
  https://debuginfod.ubuntu.com
  Enable debuginfod for this session? (y or [n]) y
  Debuginfod has been enabled.
  To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
  Reading symbols from 
/home/andy/.cache/debuginfod_client/c3e79ca1f76831bf9e6750481740ad73e5fce85d/debuginfo...

  warning: Can't open file /memfd:/.glXX (deleted) during file-
  backed mapping note processing

  warning: Can't open file /run/user/1000/orcexec.iAL97R (deleted)
  during file-backed mapping note processing

  warning: Can't open file /memfd:pulseaudio (deleted) during file-
  backed mapping note processing

  warning: Can't open file /memfd:/.nvidia_drv.XX (deleted) during
  file-backed mapping note processing

  warning: Can't open file /home/andy/.local/share/gvfs-
  metadata/root-636ea0d4.log during file-backed mapping note processing

  warning: Can't open file /SYSV (deleted) during file-backed mapping 
note processing
  [New LWP 747582]
  [New LWP 747566]
  [New LWP 747568]
  [New LWP 747567]
  [New LWP 747570]
  [New LWP 747572]
  [New LWP 747583]
  [New LWP 747586]
  [New LWP 747578]
  [New LWP 747589]
  [New LWP 747588]
  [New LWP 747590]
  [New LWP 747584]
  [New LWP 747593]
  [New LWP 747587]
  [New LWP 747601]
  [New LWP 747581]
  [New LWP 747597]
  [New LWP 747606]
  [New LWP 747603]
  [New LWP 747579]
  [New LWP 747598]
  [New LWP 747592]
  [New LWP 747591]
  [New LWP 747599]
  [New LWP 747594]
  [New LWP 747596]
  [New LWP 747605]
  [New LWP 747595]
  [New LWP 747602]
  [New LWP 747585]
  [New LWP 747569]
  [New LWP 747600]
  [New LWP 747604]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  --Type  for more, q to quit, c to continue without paging--
  Core was generated by `totem C0109.MP4'.
  Program terminated with signal SIGABRT, Aborted.
  #0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=) at ./nptl/pthread_kill.c:44
  Download failed: Invalid argument.  Continuing without source file 
./nptl/./nptl/pthread_kill.c.
  44

[Desktop-packages] [Bug 2009523] Re: totem crashes almost at every start

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2000409, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 2000409
   totem crashes on startup (assert !xcb_xlib_unknown_req_in_deq) in _XReply 
because XInitThreads is not called early enough by libx11 (patch included)

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

Title:
  totem crashes almost at every start

Status in totem package in Ubuntu:
  New

Bug description:
  If I try to start totem, it crashes with that:

  [xcb] Unknown request in queue while dequeuing
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  totem: ../../src/xcb_io.c:175: dequeue_pending_request: Assertion 
`!xcb_xlib_unknown_req_in_deq' failed.
  Abgebrochen (Speicherabzug geschrieben)

  
  Apport starts collecting stuff about my system, but doesn't upload it.

  
  Ubuntu 22.10
  totem 43.0-2ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: totem 43.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  6 20:15:00 2023
  InstallationDate: Installed on 2022-12-27 (69 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/2009523/+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 2009564] Re: Touchpad disabling while typing does not work

I assume you mean:

  org.gnome.desktop.peripherals.touchpad disable-while-typing true

Does it work any better if you log into Ubuntu on Xorg instead?

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

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

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

Title:
  Touchpad disabling while typing does not work

Status in libinput package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  It makes my laptop much less usable.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.85.05  Sat Jan 14 
00:49:50 UTC 2023
   GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  7 00:44:08 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi/9858, 5.19.0-32-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
   backport-iwlwifi/9858, 5.19.0-35-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
   nvidia/525.85.05, 5.15.0-56-generic, x86_64: installed
   nvidia/525.85.05, 5.19.0-32-generic, x86_64: installed
   nvidia/525.85.05, 5.19.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. Device [1a58:201f]
   NVIDIA Corporation Device [10de:24e0] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. Device [1a58:201f]
  InstallationDate: Installed on 2023-01-03 (62 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Razer x Lambda TensorBook (2022)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=4cd4fe61-a6ef-48c5-acc8-b96e7da91171 ro button.lid_init_state=open 
i915.enable_fbc=0 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2022
  dmi.bios.release: 1.0
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: CH580
  dmi.board.vendor: Razer x Lambda
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer x Lambda
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd07/29/2022:br1.0:efr1.0:svnRazerxLambda:pnTensorBook(2022):pvr8.04:rvnRazerxLambda:rnCH580:rvr4:cvnRazerxLambda:ct10:cvr:skuRZ09-0421NEL9:
  dmi.product.family: 1A58201F Razer x Lambda TensorBook
  dmi.product.name: TensorBook (2022)
  dmi.product.sku: RZ09-0421NEL9
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer x Lambda
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1

[Desktop-packages] [Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

2023-03-07 Thread supremesyntax

If you force people into a snap package at least there should be no loss in 
functionality.
I have linked the snapd project so maybe someone from there could have a look.

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

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in Mozilla Firefox:
  New
Status in snapd:
  New
Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1849346/+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 2009576] Re: ubuntu lunar live test; gnome shell c(rashed (according to /var/crash)