date:20230405

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/2015181/+attachment/5661394/+files/ThreadStacktrace.txt

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

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

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

Title:
  nautilus crashed with signal 7 in g_main_context_dispatch()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Just started gedit but no recent operations with nautilus.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  4 07:57:12 2023
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1099, 732)'
  InstallationDate: Installed on 2023-03-31 (3 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 7
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with signal 7 in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:
   
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.48.0-1ubuntu1
   nautilus-image-converter  0.4.0-2
   nautilus-share0.7.5-0.3
   python3-nautilus  4.0-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2015181/+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 2015181] Stacktrace.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/2015181/+attachment/5661392/+files/Stacktrace.txt

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

Title:
  nautilus crashed with signal 7 in g_main_context_dispatch()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Just started gedit but no recent operations with nautilus.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  4 07:57:12 2023
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1099, 732)'
  InstallationDate: Installed on 2023-03-31 (3 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 7
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with signal 7 in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:
   
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.48.0-1ubuntu1
   nautilus-image-converter  0.4.0-2
   nautilus-share0.7.5-0.3
   python3-nautilus  4.0-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2015181/+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 2015181] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/2015181/+attachment/5661393/+files/StacktraceSource.txt

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

Title:
  nautilus crashed with signal 7 in g_main_context_dispatch()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Just started gedit but no recent operations with nautilus.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  4 07:57:12 2023
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1099, 732)'
  InstallationDate: Installed on 2023-03-31 (3 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 7
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with signal 7 in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:
   
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.48.0-1ubuntu1
   nautilus-image-converter  0.4.0-2
   nautilus-share0.7.5-0.3
   python3-nautilus  4.0-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2015181/+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 2015181] nautilus crashed with signal 7 in g_main_context_dispatch()

StacktraceTop:
 nautilus_view_model_get_item_from_file (self=0x55bc174bd047, file=) at 
../src/nautilus-view-model.c:392
 on_clipboard_contents_received (source_object=, res=, user_data=) at ../src/nautilus-list-base.c:1316
 task_pool_manager_timeout (user_data=) at 
../../../gio/gtask.c:1471
 g_task_return_now (task=0x55b94d014ab0) at ../../../gio/gtask.c:1315
 g_main_context_invoke_full (context=0x0, priority=-1735093456, 
function=, data=, notify=0x5) at 
../../../glib/gmain.c:6448

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

Title:
  nautilus crashed with signal 7 in g_main_context_dispatch()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Just started gedit but no recent operations with nautilus.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  4 07:57:12 2023
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1099, 732)'
  InstallationDate: Installed on 2023-03-31 (3 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 7
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with signal 7 in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:
   
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.48.0-1ubuntu1
   nautilus-image-converter  0.4.0-2
   nautilus-share0.7.5-0.3
   python3-nautilus  4.0-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2015181/+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 2015405] Re: spice-vdagent crashed with SIGSEGV

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

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 #1965173, 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/2015405/+attachment/5661381/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 spice-vdagent in Ubuntu.
https://bugs.launchpad.net/bugs/2015405

Title:
  spice-vdagent crashed with SIGSEGV

Status in spice-vdagent package in Ubuntu:
  New

Bug description:
  Just launching an ubuntu 23.04 beta VM on libvirtd/qemu/KVM and this
  brings the reporting crash app as soon as loging into the desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: spice-vdagent 0.22.1-3
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  5 23:21:08 2023
  ExecutablePath: /usr/bin/spice-vdagent
  InstallationDate: Installed on 2023-03-31 (5 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
  ProcCmdline: /usr/bin/spice-vdagent
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x559a23cd00e0:mov(%r15),%rdi
   PC (0x559a23cd00e0) ok
   source "(%r15)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: spice-vdagent
  StacktraceTop:
   ()
   __libc_start_call_main (main=main@entry=0x559a23ccfe80, argc=argc@entry=1, 
argv=argv@entry=0x7ffce18a7c08) at ../sysdeps/nptl/libc_start_call_main.h:58
   __libc_start_main_impl (main=0x559a23ccfe80, argc=1, argv=0x7ffce18a7c08, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffce18a7bf8) at ../csu/libc-start.c:360
   ()
  Title: spice-vdagent crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2015405/+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 2015406] [NEW] Update gdm3 to 44.0

2023-04-05 Thread Jeremy Bícha

Public bug reported:

Impact
-
Ubuntu 23.04 is shipping GNOME 44, but one key component landed late.
This includes several fixes to the udev rules (used to determine whether 
Wayland is available and default) and other bugfixes. GDM 44 looks better for 
Ubuntu 23.04 users than 43.

https://gitlab.gnome.org/GNOME/gdm/-/blob/44.0/NEWS

Testing Done

I have been running gdm 44 on my computer since Monday, March 27 without seeing 
any new issues. I have restarted my system multiple times since then.

Why Wasn't this done sooner
---
gdm 44 was released during my spring break week.
I returned to work the Monday of Beta Freeze. It seemed unwise to push this 
update through at the last minute before Beta in case there were any issues.

** Affects: gdm3 (Ubuntu)
 Importance: Medium
 Status: In Progress


** Tags: lunar upgrade-software-version

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

Title:
  Update gdm3 to 44.0

Status in gdm3 package in Ubuntu:
  In Progress

Bug description:
  Impact
  -
  Ubuntu 23.04 is shipping GNOME 44, but one key component landed late.
  This includes several fixes to the udev rules (used to determine whether 
Wayland is available and default) and other bugfixes. GDM 44 looks better for 
Ubuntu 23.04 users than 43.

  https://gitlab.gnome.org/GNOME/gdm/-/blob/44.0/NEWS

  Testing Done
  
  I have been running gdm 44 on my computer since Monday, March 27 without 
seeing any new issues. I have restarted my system multiple times since then.

  Why Wasn't this done sooner
  ---
  gdm 44 was released during my spring break week.
  I returned to work the Monday of Beta Freeze. It seemed unwise to push this 
update through at the last minute before Beta in case there were any issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2015406/+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 2015403] [NEW] Feature Request: adsys 802.1X certificate auto-enrolment from Active Directory CA

2023-04-05 Thread Jaimes Joschko

Public bug reported:

Hi Team,

I'd like to make a feature request to support 802.1X certificate auto-
enrolment from Active Directory CA

Ideally, certificates for client ubuntu desktops could then be pushed
via GPOs from and managed by Active Directory CA

This feature would be for Ubuntu 22.04 LTS or later

Thanks for you time and consideration!

---
Cheers,
Jaimes Joschko

Canonical Support
---

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


** Tags: feature-request

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

Title:
  Feature Request: adsys 802.1X certificate auto-enrolment from Active
  Directory CA

Status in adsys package in Ubuntu:
  New

Bug description:
  Hi Team,

  I'd like to make a feature request to support 802.1X certificate auto-
  enrolment from Active Directory CA

  Ideally, certificates for client ubuntu desktops could then be pushed
  via GPOs from and managed by Active Directory CA

  This feature would be for Ubuntu 22.04 LTS or later

  Thanks for you time and consideration!

  ---
  Cheers,
  Jaimes Joschko

  Canonical Support
  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2015403/+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 2013236] Re: Failed to install bcmwl wireless driver during the install

2023-04-05 Thread Brian Murray

I tested this same scenario on Ubuntu 22.04.2 and while I still don't
have a wireless device available I did discover the following:

bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ ubuntu-drivers list
bcmwl-kernel-source
bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ ubuntu-drivers devices
== /sys/devices/pci:00/:00:02.4/:05:00.0 ==
modalias : pci:v14E4d43B1sv1043sd85BAbc02sc80i00
vendor   : Broadcom Inc. and subsidiaries
model: BCM4352 802.11ac Wireless Network Adapter
driver   : bcmwl-kernel-source - distro non-free
bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ apt-cache policy 
bcmwl-kernel-source
bcmwl-kernel-source:
  Installed: 6.30.223.271+bdcom-0ubuntu10~22.04.1
  Candidate: 6.30.223.271+bdcom-0ubuntu10~22.04.1
  Version table:
 *** 6.30.223.271+bdcom-0ubuntu10~22.04.1 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 
Packages
100 /var/lib/dpkg/status
 6.30.223.271+bdcom-0ubuntu8 500
500 http://us.archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages

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

Title:
  Failed to install bcmwl wireless driver during the install

Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 2013236] Re: Failed to install bcmwl wireless driver during the install

2023-04-05 Thread Brian Murray

I tried installing using the desktop legacy image and noticed that
`ubuntu-drivers` behaves the same way - recommending broadcom-sta-dkms
but then not installing it. Additionally, looking at the device I see
the following (which I also recall from the new installer):

05:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4352 
802.11ac Wireless Network Adapter [14e4:43b1] (rev 03)
Subsystem: ASUSTeK Computer Inc. BCM4352 802.11ac Wireless Network 
Adapter [1043:85ba]
Physical Slot: 0-5
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: bcma-pci-bridge
Kernel modules: bcma

While the bcma module might be in use I have not wireless devices setup.

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

Title:
  Failed to install bcmwl wireless driver during the install

Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 2013236] Re: Failed to install bcmwl wireless driver during the install

2023-04-05 Thread Brian Murray

After installing with the new desktop installer, rebooting, manually
installing broadcom-sta-dkms, and rebooting again no wireless adapter
was available.

Additionally, running 'ubuntu-drivers install' (before installing
broadcom-sta-dkms) indicated that all drivers were already installed.

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

Title:
  Failed to install bcmwl wireless driver during the install

Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 2012156] Re: xdg-desktop-portal-gtk crashed with SIGSEGV in fdo_find_notification()

2023-04-05 Thread Steve Beattie

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

** Information type changed from Private Security to Public

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

Title:
  xdg-desktop-portal-gtk crashed with SIGSEGV in fdo_find_notification()

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New

Bug description:
  Opening Brave and Firefox Same time

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: xdg-desktop-portal-gtk 1.14.1-1
  Uname: Linux 6.2.7-060207-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 19 05:32:41 2023
  ExecutablePath: /usr/libexec/xdg-desktop-portal-gtk
  InstallationDate: Installed on 2023-03-16 (2 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcCmdline: /usr/libexec/xdg-desktop-portal-gtk
  SegvAnalysis:
   Segfault happened at: 0x7f975a78f1da <__strcmp_sse42+26>:movdqu 
(%rdi),%xmm1
   PC (0x7f975a78f1da) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm1" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xdg-desktop-portal-gtk
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ffi_call () from /lib/x86_64-linux-gnu/libffi.so.8
  Title: xdg-desktop-portal-gtk crashed with SIGSEGV in ffi_call()
  UpgradeStatus: Upgraded to lunar on 2023-03-18 (0 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/xdg-desktop-portal-gtk/+bug/2012156/+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 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login

2023-04-05 Thread dann frazier

** Attachment added: "_usr_bin_gnome-shell.1002.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2015386/+attachment/5661328/+files/_usr_bin_gnome-shell.1002.crash

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

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

Title:
  gnome-shell crashes after "switching to" a new user from an existing
  login

Status in gnome-shell package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  When logged into a desktop session, I created a new user account and
  then tried to "switch to" it. A new gnome session started for that
  user (test1), but after a few seconds, gnome-shell appears to have
  crashed. This only seems to happen on the first attempt to "switch to"
  a new user.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0f.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.89.02  Wed Feb  1 
23:23:25 UTC 2023
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr  5 17:23:28 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  MachineType: NVIDIA DGX Station
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic 
root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0406
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-E-10G WS
  dmi.board.vendor: EMPTY
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: EMPTY
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000:
  dmi.product.family: DGX
  dmi.product.name: DGX Station
  dmi.product.sku: 920-22587-2510-000
  dmi.product.version: System Version
  dmi.sys.vendor: NVIDIA
  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.9
  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/gnome-shell/+bug/2015386/+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 2015386] [NEW] gnome-shell crashes after "switching to" a new user from an existing login

2023-04-05 Thread dann frazier

Public bug reported:

When logged into a desktop session, I created a new user account and
then tried to "switch to" it. A new gnome session started for that user
(test1), but after a few seconds, gnome-shell appears to have crashed.
This only seems to happen on the first attempt to "switch to" a new
user.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
Uname: Linux 5.15.0-69-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file.
.proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file.
.proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file.
.proc.driver.nvidia.gpus..0f.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.89.02  Wed Feb  1 23:23:25 
UTC 2023
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Apr  5 17:23:28 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
MachineType: NVIDIA DGX Station
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic 
root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2018
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0406
dmi.board.asset.tag: Default string
dmi.board.name: X99-E-10G WS
dmi.board.vendor: EMPTY
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: EMPTY
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000:
dmi.product.family: DGX
dmi.product.name: DGX Station
dmi.product.sku: 920-22587-2510-000
dmi.product.version: System Version
dmi.sys.vendor: NVIDIA
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.9
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

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

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


** Tags: amd64 apport-bug crash jammy ubuntu uec-images

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

Title:
  gnome-shell crashes after "switching to" a new user from an existing
  login

Status in gnome-shell package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  When logged into a desktop session, I created a new user account and
  then tried to "switch to" it. A new gnome session started for that
  user (test1), but after a few seconds, gnome-shell appears to have
  crashed. This only seems to happen on the first attempt to "switch to"
  a new user.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file.

[Desktop-packages] [Bug 2015129] Re: gstreamer 1.22.1 bugfix release

This bug was fixed in the package gstreamer1.0 - 1.22.1-1

---
gstreamer1.0 (1.22.1-1) experimental; urgency=medium

  * Team upload
  * New upstream bugfix release (LP: #2015129)

 -- Jeremy Bicha   Mon, 03 Apr 2023 16:03:42 -0400

** Changed in: gstreamer1.0 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  gstreamer 1.22.1 bugfix release

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Triaged
Status in gst-plugins-good1.0 package in Ubuntu:
  Triaged
Status in gstreamer1.0 package in Ubuntu:
  Fix Released

Bug description:
  Impact
  --
  This is a stable bugfix release

  See https://gstreamer.freedesktop.org/releases/1.22/#1.22.1 for more
  details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2015129/+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 2015373] Re: massive yellow screen color corruption

2023-04-05 Thread Dan

** Description changed:

  using the "try ubuntu" feature, this is what the entire experience looks
- like (see the 2nd attached screenshot in comment #2).
+ like (see the 2nd attached image in comment #2).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470.2
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  5 15:37:32 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104 [GeForce RTX 2060] [10de:1e89] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd TU104 [GeForce RTX 2060] 
[1458:402b]
  LiveMediaBuild: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: To Be Filled By O.E.M. A320M Pro4 R2.0
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.40
  dmi.board.name: A320M Pro4 R2.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.40:bd10/26/2022:br5.17:svnToBeFilledByO.E.M.:pnA320MPro4R2.0:pvrToBeFilledByO.E.M.:rvnASRock:rnA320MPro4R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: A320M Pro4 R2.0
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.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

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

Title:
  massive yellow screen color corruption

Status in xorg package in Ubuntu:
  New

Bug description:
  using the "try ubuntu" feature, this is what the entire experience
  looks like (see the 2nd attached image in comment #2).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470.2
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  5 15:37:32 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104 [GeForce RTX 2060] [10de:1e89] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd TU104 [GeForce RTX 2060] 
[1458:402b]
  LiveMediaBuild: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: To Be Filled By O.E.M. A320M Pro4 R2.0
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.40
  dmi.board.name: A320M Pro4 R2.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:

[Desktop-packages] [Bug 1997480] Re: maximized xwayland windows shift by 1 pixel when on top vs/ not on top

2023-04-05 Thread Joe Barnett

i think this is maybe fixed in lunar?  seems better at least with
initial testing

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

Title:
  maximized xwayland windows shift by 1 pixel when on top vs/ not on top

Status in xwayland package in Ubuntu:
  New

Bug description:
  on kinetic with a gnome wayland session, maximized X apps on the
  secondary screen run through xwayland appear to move position by ~ 1
  pixel when they are on top vs/ not on top.  running w/ 2 monitors,
  primary @ 175% scaling, secondary @ 100% scaling

  minimal example:
  maximize xterm and have it be the top window on secondary screen.  open 
another window on the primary screen.  drag it over to the secondary screen to 
overlap the xterm and see the window border jump by ~1 pixel

  actual example that is more noticable:
  maximize an intellij/pycharm/other jetbrains product and have it be the top 
window on the secondary screen.  hover over something that creates a popup (eg 
a folder in the left project tree pane with a name long enough to get cut off) 
and see the whole IDE dance around.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xwayland 2:22.1.3-2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Nov 22 10:50:47 2022
  InstallationDate: Installed on 2019-08-17 (1193 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xwayland
  UpgradeStatus: Upgraded to kinetic on 2022-09-22 (60 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1997480/+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 2015373] Re: massive yellow screen color corruption

2023-04-05 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  massive yellow screen color corruption

Status in xorg package in Ubuntu:
  New

Bug description:
  using the "try ubuntu" feature, this is what the entire experience
  looks like (see the 2nd attached screenshot in comment #2).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470.2
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  5 15:37:32 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104 [GeForce RTX 2060] [10de:1e89] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd TU104 [GeForce RTX 2060] 
[1458:402b]
  LiveMediaBuild: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: To Be Filled By O.E.M. A320M Pro4 R2.0
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.40
  dmi.board.name: A320M Pro4 R2.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.40:bd10/26/2022:br5.17:svnToBeFilledByO.E.M.:pnA320MPro4R2.0:pvrToBeFilledByO.E.M.:rvnASRock:rnA320MPro4R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: A320M Pro4 R2.0
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.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/xorg/+bug/2015373/+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 1849346]

2023-04-05 Thread Amin Bandali

I think we're hoping to tackle this for the next (Ubuntu) cycle.

-- 
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 2015373] [NEW] massive yellow screen color corruption

You have been subscribed to a public bug:

using the "try ubuntu" feature, this is what the entire experience looks
like (see the 2nd attached screenshot in comment #2).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.470.2
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  5 15:37:32 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU104 [GeForce RTX 2060] [10de:1e89] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd TU104 [GeForce RTX 2060] [1458:402b]
LiveMediaBuild: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223)
MachineType: To Be Filled By O.E.M. A320M Pro4 R2.0
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed 
maybe-ubiquity quiet splash ---
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P7.40
dmi.board.name: A320M Pro4 R2.0
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.40:bd10/26/2022:br5.17:svnToBeFilledByO.E.M.:pnA320MPro4R2.0:pvrToBeFilledByO.E.M.:rvnASRock:rnA320MPro4R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: A320M Pro4 R2.0
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.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

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


** Tags: amd64 apport-bug corruption jammy ubuntu
-- 
massive yellow screen color corruption
https://bugs.launchpad.net/bugs/2015373
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 2012733] Re: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions

This bug was fixed in the package mutter - 44.0-2ubuntu3

---
mutter (44.0-2ubuntu3) lunar; urgency=medium

  * debian/patches: Listen to XSettings changes to update decorations
(LP: #2012733)

 -- Marco Trevisan (Treviño)   Tue, 04 Apr 2023
22:26:20 +0200

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

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

Title:
  Unthemed and unscaled titlebars for server-side decorations in GNOME
  44 Xorg sessions

Status in Mutter:
  Fix Released
Status in Yaru Theme:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  Nvidia 530 (graphics ppa), dGPU mode, GS 44, Lunar

  X1 session:
  If I launch Synaptic or ChessX, eg., the title bar is Adwaita-styled (greyish 
+ icons).
  No issue with GNOME apps (and some other like FF or TB snaps, etc.).

  Wayland session:
  all is ok (except many other bugs!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2012733/+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 2012734] Re: no audio after update

2023-04-05 Thread malko

reboot with kernel 5.19.0-32-generic and the problem is gone, so it must
be at the kernel level

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

Title:
  no audio after update

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 22.10
  Release:  22.10

  
  during normal patching Ubuntu pushed from kernel 5.19.0-31 to 5.19.0-35. 
After this push, I lost audio from my AMD RX570 hdmi. I booted back to -31 
waiting for the next kernel push in the hopes the problem would be caught and 
addressed. It wasn't, and still persists in -38. The card info is below and was 
taken while booted into -38.

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]

  root@x:~# hwinfo --sound
  35: PCI 100.1: 0403 Audio device
  [Created at pci.386]
  Unique ID: NXNs.TsyFmhFLPLA
  Parent ID: mnDB.fA+tdbAkMSD
  SysFS ID: /devices/pci:00/:00:01.1/:01:00.1
  SysFS BusID: :01:00.1
  Hardware Class: sound
  Model: "ATI Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0xaaf0 "Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
  SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
  SubDevice: pci 0xaaf0
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xfcf6-0xfcf63fff (rw,non-prefetchable)
  IRQ: 86 (5 events)
  Module Alias: "pci:v1002dAAF0sv1458sdAAF0bc04sc0 3i00"
  Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #31 (PCI bridge)


  The errors I am getting during intialization are:

  [ 4.895282] hdaudio hdaudioC0D0: no AFG or MFG node found
  [ 4.895306] snd_hda_intel :01:00.1: no codecs initialized

  
  and if I try to validate the card

  root@x:~# aplay -l
  aplay: device_list:274: no soundcards found...

  I have tried passing numerous arguments to the module but to no avail.
  Booting back to -31 brings the card right back to fully functioning. I
  believe there has been an update to snd_hda_intel which is causing
  this issue and is most likely a regression situation. Can anyone
  assist? I have searched for a model to be passed specific to AMD
  cards, but can't find one. Any suggestions would be greatly
  appreciated. Additionally, I'm wondering if this should be directed to
  Ubuntu, or should it go to kernel.org the HD-Audio group? Again,
  thanks for your thoughts.

  options snd_hda_intel dmic_detect=0
  options snd_hda_intel model=generic
  options snd_hda_intel model=auto
  options snd_hda_intel probe_mask=1
  options snd-intel-dspcfg dsp_driver=1

  Under -31 the error messages are not displayed, sound works. If I
  again validate, I get the below:

  root@media2:~# aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [65Q825]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:gdm1585 F pipewire
  CasperMD5CheckResult: unknown
  Date: Fri Mar 24 07:45:50 2023
  InstallationDate: Installed on 2019-05-09 (1415 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2023-01-13 (69 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string

[Desktop-packages] [Bug 2012734] Re: no audio after update

2023-04-05 Thread malko

the output of uname -r
5.19.0-38-generic

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

Title:
  no audio after update

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 22.10
  Release:  22.10

  
  during normal patching Ubuntu pushed from kernel 5.19.0-31 to 5.19.0-35. 
After this push, I lost audio from my AMD RX570 hdmi. I booted back to -31 
waiting for the next kernel push in the hopes the problem would be caught and 
addressed. It wasn't, and still persists in -38. The card info is below and was 
taken while booted into -38.

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]

  root@x:~# hwinfo --sound
  35: PCI 100.1: 0403 Audio device
  [Created at pci.386]
  Unique ID: NXNs.TsyFmhFLPLA
  Parent ID: mnDB.fA+tdbAkMSD
  SysFS ID: /devices/pci:00/:00:01.1/:01:00.1
  SysFS BusID: :01:00.1
  Hardware Class: sound
  Model: "ATI Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0xaaf0 "Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
  SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
  SubDevice: pci 0xaaf0
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xfcf6-0xfcf63fff (rw,non-prefetchable)
  IRQ: 86 (5 events)
  Module Alias: "pci:v1002dAAF0sv1458sdAAF0bc04sc0 3i00"
  Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #31 (PCI bridge)


  The errors I am getting during intialization are:

  [ 4.895282] hdaudio hdaudioC0D0: no AFG or MFG node found
  [ 4.895306] snd_hda_intel :01:00.1: no codecs initialized

  
  and if I try to validate the card

  root@x:~# aplay -l
  aplay: device_list:274: no soundcards found...

  I have tried passing numerous arguments to the module but to no avail.
  Booting back to -31 brings the card right back to fully functioning. I
  believe there has been an update to snd_hda_intel which is causing
  this issue and is most likely a regression situation. Can anyone
  assist? I have searched for a model to be passed specific to AMD
  cards, but can't find one. Any suggestions would be greatly
  appreciated. Additionally, I'm wondering if this should be directed to
  Ubuntu, or should it go to kernel.org the HD-Audio group? Again,
  thanks for your thoughts.

  options snd_hda_intel dmic_detect=0
  options snd_hda_intel model=generic
  options snd_hda_intel model=auto
  options snd_hda_intel probe_mask=1
  options snd-intel-dspcfg dsp_driver=1

  Under -31 the error messages are not displayed, sound works. If I
  again validate, I get the below:

  root@media2:~# aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [65Q825]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:gdm1585 F pipewire
  CasperMD5CheckResult: unknown
  Date: Fri Mar 24 07:45:50 2023
  InstallationDate: Installed on 2019-05-09 (1415 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2023-01-13 (69 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS PRO WIFI-CF
  dmi.board.vendor:

[Desktop-packages] [Bug 2012734] Re: no audio after update

2023-04-05 Thread malko

Same problem here on ubuntu 22.04, since last update I can't output
sound through HDMI, the card is not listed anymore in any sound settings
app i tested (alasmixer, pavucontrol or system sound settings)

Here some commands output:

lspci | grep Audio
2d:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]
2f:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD 
Audio Controller

cat /proc/asound/cards
 1 [Microphone ]: USB-Audio - HD Pro Webcam C920
  HD Pro Webcam C920 at usb-:25:00.0-3.2, high speed
 2 [Generic]: HDA-Intel - HD-Audio Generic
  HD-Audio Generic at 0xfcc0 irq 80

aplay -l  
 Liste des périphériques matériels PLAYBACK 
carte 2 : Generic [HD-Audio Generic], périphérique 0 : ALC1220 Analog [ALC1220 
Analog]
  Sous-périphériques : 1/1
  Sous-périphérique #0 : subdevice #0
carte 2 : Generic [HD-Audio Generic], périphérique 1 : ALC1220 Digital [ALC1220 
Digital]
  Sous-périphériques : 1/1
  Sous-périphérique #0 : subdevice #0

So lscpi report the correctly the Ellesmere HDMI Audio which has
disappear from all other listings.

How can we fix that please

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

Title:
  no audio after update

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 22.10
  Release:  22.10

  
  during normal patching Ubuntu pushed from kernel 5.19.0-31 to 5.19.0-35. 
After this push, I lost audio from my AMD RX570 hdmi. I booted back to -31 
waiting for the next kernel push in the hopes the problem would be caught and 
addressed. It wasn't, and still persists in -38. The card info is below and was 
taken while booted into -38.

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]

  root@x:~# hwinfo --sound
  35: PCI 100.1: 0403 Audio device
  [Created at pci.386]
  Unique ID: NXNs.TsyFmhFLPLA
  Parent ID: mnDB.fA+tdbAkMSD
  SysFS ID: /devices/pci:00/:00:01.1/:01:00.1
  SysFS BusID: :01:00.1
  Hardware Class: sound
  Model: "ATI Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0xaaf0 "Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
  SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
  SubDevice: pci 0xaaf0
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xfcf6-0xfcf63fff (rw,non-prefetchable)
  IRQ: 86 (5 events)
  Module Alias: "pci:v1002dAAF0sv1458sdAAF0bc04sc0 3i00"
  Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #31 (PCI bridge)


  The errors I am getting during intialization are:

  [ 4.895282] hdaudio hdaudioC0D0: no AFG or MFG node found
  [ 4.895306] snd_hda_intel :01:00.1: no codecs initialized

  
  and if I try to validate the card

  root@x:~# aplay -l
  aplay: device_list:274: no soundcards found...

  I have tried passing numerous arguments to the module but to no avail.
  Booting back to -31 brings the card right back to fully functioning. I
  believe there has been an update to snd_hda_intel which is causing
  this issue and is most likely a regression situation. Can anyone
  assist? I have searched for a model to be passed specific to AMD
  cards, but can't find one. Any suggestions would be greatly
  appreciated. Additionally, I'm wondering if this should be directed to
  Ubuntu, or should it go to kernel.org the HD-Audio group? Again,
  thanks for your thoughts.

  options snd_hda_intel dmic_detect=0
  options snd_hda_intel model=generic
  options snd_hda_intel model=auto
  options snd_hda_intel probe_mask=1
  options snd-intel-dspcfg dsp_driver=1

  Under -31 the error messages are not displayed, sound works. If I
  again validate, I get the below:

  root@media2:~# aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [65Q825]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
Subdevices: 1/1
Subdevice #0:

[Desktop-packages] [Bug 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox

2023-04-05 Thread mario

It happen to me to.
I also removed snap as it doesn't support SSO i use in my daily work.
My /etc/apt/preferences.d/mozillateamppa:

Package: firefox*
Pin: release o=LP-PPA-mozillateam
Pin-Priority: 501:

So after each removal, i simply do:
sudo apt remove firefox && sudo apt install firefox, but indeed it's 
frustrating that we have to do such workarounds.

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

Title:
  Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
   I have looked on various forums including the search features of
  Launchpad, help.ubuntu..com, and Google for answers on this but not been
  able to.

  I have uninstalled the snap of firefox multiple times, installing the real
  Firefox from ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/, only for a
  few days later (once hours later) for snap to uninstall the real thing and
  install its snap version instead.

  I have tried a basic
 sudo snap remove firefox

  and when that didn't work
 sudo snap disable firefox
 sudo snap remove --purget firefox

  The former should be enough - that's a direct expression of my preferences,
  some thing like "You should have typed sudo snap remove --do-not-reinstall
  --disable-auto-ignore-preferences firefox"  would not resolve this bug.

  When installing using apt-get, the correct version is being installed, and
  snap afterwards does not show the presence of firefox:

  Get:1 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64
  xul-ext-ubufox all 3.4-0ubuntu1.17.10.1 [3,320 B]
  Get:2 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main
  amd64 firefox-locale-en amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [831 kB]
  Get:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main
  amd64 firefox amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [64.9 MB]

  Name   Version RevTracking
  Publisher  Notes
  authy  2.2.2   12 latest/stable
 twilio-authy   -
  bare   1.0 5  latest/stable
 canonical✓ base
  chromium   108.0.5359.94   2238   latest/stable
 canonical✓ -
  code   5235c6bb114latest/stable
 vscode✓classic
  core   16-2.57.6   14399  latest/stable
 canonical✓ core
  core18 202211032632   latest/stable
 canonical✓ base
  core20 202211231738   latest/stable
 canonical✓ base
  cups   2.4.2-4 836latest/stable
 openprinting✓  -
  gnome-3-28-18043.28.0-19-g98f9e67.98f9e67  161latest/stable
 canonical✓ -
  gnome-3-38-20040+git.6f39565   119latest/stable
 canonical✓ -
  gtk-common-themes  0.1-81-g442e511 1535
  latest/stable/…  canonical✓ -
  onlyoffice-desktopeditors  7.2.1   133latest/stable
 onlyoffice✓-
  snap-store 41.3-66-gfe1e325638
   latest/stable/…  canonical✓ -
  snapd  2.57.6  17883  latest/stable
 canonical✓ snapd

  
  /var/lib/snapd/seed/snaps contains (once firefox is removed):

  core18_1880.snap  gnome-3-34-1804_36.snap  gtk-common-themes_1506.snap
   snapd_8542.snap  snap-store_467.snap

  
https://ubuntuhandbook.org/index.php/2021/10/prevent-installing-firefox-snap-ubuntu-mate-21-10/
  claims that a similar issue affects Ubuntu MATE 21.04 and the solution was
  to type "sudo apt-mark manual firefox", which I have done, but that has not
  resolved the problem.

  I'm not here to explain why I wouldn't want the snap version, it is clearly
  a bug for snap to accept a command to uninstall something and then
  automatically reinstall it days later without the permission of the user,
  and especially galling that it removes the real version at the same time.

  I have lost data (passwords and history) because of this bug, because one
  of the many faults of the snap version is that it ignores the user's real
  ~/.mozilla profile and creates a shadow profile instead inside of the snap
  system.

  Please disable this behavior. It's obnoxious, it ignores EXPLICITY stated
  user preferences, and it causes the loss of data.

  I am unclear on what package is causing the behavior so for now marking it
  against Firefox, but it could be against some other piece of infrastructure
  related to snap:

   affects ubuntu/firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1999308/+subscriptions

[Desktop-packages] [Bug 2012733] Re: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions

This bug was fixed in the package yaru-theme - 23.04.3-0ubuntu1

---
yaru-theme (23.04.3-0ubuntu1) lunar; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * meson: Release 23.04.3
  * icons/meson: Explicitly list the icons pointing to wrong locations
  * icons/meson: Remove symbolic links for flavours
  * tweaks: Use consistent size for default decoration window buttons
(LP: #2012733, #2013271)
  * tweaks: Use consistent horizontal margin for window buttons
  * icons: Optimize symbolic icons
  * icons: Update rendered icons and symlinks

  [ Paul Kepinski ]
  * Add missing folds on libreoffice-oasis-formula icon

 -- Marco Trevisan (Treviño)   Tue, 04 Apr 2023
21:56:24 +0200

** Changed in: yaru-theme (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Unthemed and unscaled titlebars for server-side decorations in GNOME
  44 Xorg sessions

Status in Mutter:
  Fix Released
Status in Yaru Theme:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  Nvidia 530 (graphics ppa), dGPU mode, GS 44, Lunar

  X1 session:
  If I launch Synaptic or ChessX, eg., the title bar is Adwaita-styled (greyish 
+ icons).
  No issue with GNOME apps (and some other like FF or TB snaps, etc.).

  Wayland session:
  all is ok (except many other bugs!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2012733/+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 2013271] Re: GTK3 titlebar buttons are bigger than GTK4 titlebar buttons

This bug was fixed in the package yaru-theme - 23.04.3-0ubuntu1

---
yaru-theme (23.04.3-0ubuntu1) lunar; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * meson: Release 23.04.3
  * icons/meson: Explicitly list the icons pointing to wrong locations
  * icons/meson: Remove symbolic links for flavours
  * tweaks: Use consistent size for default decoration window buttons
(LP: #2012733, #2013271)
  * tweaks: Use consistent horizontal margin for window buttons
  * icons: Optimize symbolic icons
  * icons: Update rendered icons and symlinks

  [ Paul Kepinski ]
  * Add missing folds on libreoffice-oasis-formula icon

 -- Marco Trevisan (Treviño)   Tue, 04 Apr 2023
21:56:24 +0200

** Changed in: yaru-theme (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  GTK3 titlebar buttons are bigger than GTK4 titlebar buttons

Status in Yaru Theme:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  GTK3 titlebar buttons are bigger than GTK4 titlebar buttons

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/2013271/+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 2013236] Re: Failed to install bcmwl wireless driver during the install

2023-04-05 Thread Dimitri John Ledkov

are you sure the dkms module is still needed with the v6.2 kernel?

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

Title:
  Failed to install bcmwl wireless driver during the install

Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 2011837] Re: Nvidia with Wayland or Xorg issue

2023-04-05 Thread Luis Alvarado

Hi Daniel, I am trying but now the PC freezes even before booting to run
those commands. All I can say is that it was running Nvidia 525. I do
not know if it is fine if I simply reinstall everything again because it
freezes with an nvme AER error and I can not go to the terminal (This
happens even before booting to gnome). If I change tty it still shows
the error.

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

Title:
  Nvidia with Wayland or Xorg issue

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I will summarize here what I put at
  https://discourse.ubuntu.com/t/ubuntu-23-04-testing-week/34246/6

  On Ubuntu 23.04, if I install it, it works fine but there is a
  considerable lag for everything. This is when using Wayland. If I do
  not change the custom.conf gdm to not use wayland, I can get in but I
  can not interact with any windows. Context menus and sub menus open
  but do not do anything. The only way for me to get to the terminal was
  to open nautilus/files from the Dock, then right click any empty space
  and select terminal. The moment I did that I had a couple of seconds
  before it crashed the terminal. But was able to get a picture of the
  hardware after my 3rd attempt.

  If I do put in on xorg, then an image I posted on the 1st link happens
  and it stays there, does not matter if I change tty, it always shows
  and needed to reinstall 23.04 to be able to go back to wayland. But if
  I use wayland I can actually feel the lag and the interaction with
  windows and all. This started happening all today after applying all
  the latest updates for 23.04 (I did not update since I think since
  several days back).

  The hardware that I was using for testing is:

  CPU - 13900k
  MOBO - Asus Z790 Hero
  RAM: DDR5 128GB
  VID: Nvidia 4090 (Drivers were automatically installed during setup)
  SSD - SN850x

  It is a computer just for Ubuntu 23.04 testing right now.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.480
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.04
  LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 44.0-2ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  RelatedPackageVersions: mutter-common 44.0-2ubuntu2
  Tags:  lunar
  Uname: Linux 6.2.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011837/+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 1970424] Re: Have ubuntu-desktop-minimal depend on xdg-desktop-portal-gnome

2023-04-05 Thread Jeremy Bícha

** Description changed:

  Impact
  --
  Because ubuntu-desktop-minimal only recommends xdg-desktop-portal-gnome, it 
is easy for users to accidentally not have it installed. If it (Or another 
desktop portal backend are not installed), it breaks critical functionality for 
both the Firefox snap and Chromium snaps. It also breaks countless other snaps.
  
  Test Case
  -
- ubuntu-session and gnome-session should depend on xdg-desktop-portal-gnome
+ 1. ubuntu-session and gnome-session should depend on xdg-desktop-portal-gnome
  
- It should be possible to uninstall xdg-desktop-portal-gnome and keep
+ 2. It should be possible to uninstall xdg-desktop-portal-gnome and keep
  xdg-desktop-portal-gtk. (This allows someone to keep using GTK3 and
  avoid the libadwaita dialogs which may be easier for third party
  themes.)
+ 
+ After installing or uninstall portal packages, you should log out and
+ log back in to make sure the user services get stopped and started
+ correctly.
  
  What Could Go Wrong
  ---
  This just adds an additional dependency.
  
  I believe the portal backends currently open by default in the locale
  sort order, so xdg-desktop-portal-gnome is preferred if installed, then
  xdg-desktop-portal-gtk, then xdg-desktop-portal-kde, then xdg-desktop-
  portal-wlr. Which coincidentally is the order we would want.
  
  How This Was Fixed
  --
  ubuntu-desktop-minimal is a special germinate package and doesn't accept 
alternate dependencies. An alternate dependency is needed because we want to 
allow people to use a different portal backend and the easiest way to use a 
different portal backend is to install the backend you want and uninstall the 
ones you don't want.
  
  Therefore, we are handling this with a dependency in ubuntu-session. We
  are also doing this with gnome-session since that's a popular
  alternative for people who want a vanilla GNOME experience.
  
- 
  Original Bug Report
  ---
  With ubuntu 22.04 firefox comes as snap package by default.
  
  it is not possible to open any file dialog. save graphics as, save html
  page, import certificate never opens a file dialog.
  
  firefox is completly useless without that file dialog.
  
  (the root case is ubuntu uses snap)
  
  further: in snap store firefox has no icon and it's called firefox not
  "Firefox".

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

Title:
  Have ubuntu-desktop-minimal depend on xdg-desktop-portal-gnome

Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-session source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  Because ubuntu-desktop-minimal only recommends xdg-desktop-portal-gnome, it 
is easy for users to accidentally not have it installed. If it (Or another 
desktop portal backend are not installed), it breaks critical functionality for 
both the Firefox snap and Chromium snaps. It also breaks countless other snaps.

  Test Case
  -
  1. ubuntu-session and gnome-session should depend on xdg-desktop-portal-gnome

  2. It should be possible to uninstall xdg-desktop-portal-gnome and
  keep xdg-desktop-portal-gtk. (This allows someone to keep using GTK3
  and avoid the libadwaita dialogs which may be easier for third party
  themes.)

  After installing or uninstall portal packages, you should log out and
  log back in to make sure the user services get stopped and started
  correctly.

  What Could Go Wrong
  ---
  This just adds an additional dependency.

  I believe the portal backends currently open by default in the locale
  sort order, so xdg-desktop-portal-gnome is preferred if installed,
  then xdg-desktop-portal-gtk, then xdg-desktop-portal-kde, then xdg-
  desktop-portal-wlr. Which coincidentally is the order we would want.

  How This Was Fixed
  --
  ubuntu-desktop-minimal is a special germinate package and doesn't accept 
alternate dependencies. An alternate dependency is needed because we want to 
allow people to use a different portal backend and the easiest way to use a 
different portal backend is to install the backend you want and uninstall the 
ones you don't want.

  Therefore, we are handling this with a dependency in ubuntu-session.
  We are also doing this with gnome-session since that's a popular
  alternative for people who want a vanilla GNOME experience.

  Original Bug Report
  ---
  With ubuntu 22.04 firefox comes as snap package by default.

  it is not possible to open any file dialog. save graphics as, save
  html page, import certificate never opens a file dialog.

  firefox is completly useless without that file dialog.

  (the root case is ubuntu uses snap)

  further: in snap store firefox has no icon and it's called firefox not
  "Firefox".

To manage notifications about this bug go

[Desktop-packages] [Bug 2011415] Re: /usr/bin/software-properties-gtk:AttributeError:on_pktask_finish:net_status_changed

2023-04-05 Thread Robie Basak

Could you please confirm that this fix isn't relevant for releases after
Focal - ie. that the necessary API exists in Jammy onwards? It may be
that you implied this already, but the bug status isn't set separately
and I can't find anything that states this unambiguously so I want to
make sure it isn't being accidentally missed.

** Also affects: software-properties (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: software-properties (Ubuntu Focal)
   Status: New => Incomplete

** Changed in: software-properties (Ubuntu)
   Status: Fix Committed => Incomplete

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_pktask_finish:net_status_changed

Status in software-properties package in Ubuntu:
  Incomplete
Status in software-properties source package in Focal:
  Incomplete

Bug description:
  * Impact

  The change from the previous revision to handle connectivity change
  use an API not available on focal and trigger an exception

  * Test case

  - detach the system from ubuntu pro if it's attached
  - open software-properties
  - go the ubuntu pro tab
  - click on 'enable ubuntu pro'
  - while the dialog is open disconnect and reconnect the network
  - change the selection from manual token to PIN

  the UI should update and no error should be triggered

  Check also that the error reports stop for the new version (url
  referenced below)

  * Regression potential

  If the callback were not working as expected the UI could end up not
  responding to status change or not accepting the PIN or token entered,
  validate that the different methods still work as expected to register

  --

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2011415/+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 2010561] Re: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created

2023-04-05 Thread Lukas Märdian

First part is fixed in https://git.launchpad.net/network-
manager/commit/?h=netplan/lunar-gu=ed1837f

Second part is up for review in:
https://code.launchpad.net/~slyon/network-manager/+git/network-
manager/+merge/440401

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

Title:
The Netplan Everywhere NetworkManager fails to supply Netplan with
networking information until a connection is deleted and re-created

Status in netplan:
Triaged
Status in network-manager package in Ubuntu:
In Progress

Bug description:
Steps to reproduce:

1. Install Ubuntu Lunar or a flavor thereof onto physical hardware with a
WiFi adapter. (I used Lubuntu Lunar.)
2. Connect to WiFi and install all updates.
3. Enable the Netplan Everywhere PPA and install the updated NetworkManager
from it (further details at
https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-settings/32420?u=arraybolt3)
4. When the installation finishes, run "sudo netplan get".

Expected result: Networking information related to the WiFi connection
should appear in the "sudo netplan get" output.

Actual result: "sudo netplan get" returns the following:

** (process:4088): WARNING **: 12:41:41.394; Permissions for
/etc/netplan/01-network-manager-all.yaml are too open. Netplan configuration
should NOT be accessible by others.
network:
version: 2
renderer: NetworkManager

End of output. Additionally, the /etc/netplan folder does not contain
files that I would expect to be there that would contain the
networking info.

Additional information:

If I disconnect from WiFi, then delete my WiFi connection entirely in
nmtui, and *then* reconnect to the same WiFi network, "sudo netplan
get" returns the expected networking information. /etc/netplan is also
properly populated after doing this.

This bug seems like it will probably cause unintended behavior after
an upgrade from 23.04 (which uses normal NetworkManager) to 23.10
(which is supposed to be using the Netplan Everywhere NetworkManager).
People probably won't know to entirely delete the WiFi and other
connections and then reconnect them in order for the netplan output to
be usable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2010561/+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 2010561] Re: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created

** Merge proposal linked:

https://code.launchpad.net/~slyon/network-manager/+git/network-manager/+merge/440401

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

Title:
The Netplan Everywhere NetworkManager fails to supply Netplan with
networking information until a connection is deleted and re-created

Status in netplan:
Triaged
Status in network-manager package in Ubuntu:
In Progress

Bug description:
Steps to reproduce:

Expected result: Networking information related to the WiFi connection
should appear in the "sudo netplan get" output.

Actual result: "sudo netplan get" returns the following:

End of output. Additionally, the /etc/netplan folder does not contain
files that I would expect to be there that would contain the
networking info.

Additional information:

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2010561/+subscriptions

[Desktop-packages] [Bug 2015129] Re: gstreamer 1.22.1 bugfix release

This bug was fixed in the package gst-plugins-bad1.0 - 1.22.1-1ubuntu1

---
gst-plugins-bad1.0 (1.22.1-1ubuntu1) lunar; urgency=medium

  * Merge with Debian (LP: #2015129). Remaining changes:
- Don't build wpewebkit plugins
- Stop installing camerabin2 basecamerabin jpegformat - plugins which have
  moved to -good.
- Have gstreamer-plugins-bad-1.0.pc Require gstreamer-plugins-good-1.0 -
  the package we've moved the referenced plugins to. This maintains
  compatibility with upstream software and other distributions.
- Don't build the opencv binary packages on i386, avoiding a large tree
  of numeric-related dependencies for a binary package it's not required
  to support.
- d/control, d/gstreamer1.0-plugins-bad.install, d/rules:
  + Don't require these Build-Depends on i386:
- libltc-dev, libfreeaptx-dev, libopenh264-dev, libqrencode-dev,
  libzxingcore-dev, glslc, libdirectfb-dev, liblrdf0-dev, libneon27-dev

gst-plugins-bad1.0 (1.22.1-1) experimental; urgency=medium

  * Team upload

  [ Jeremy Bicha ]
  * New upstream bugfix release

  [ Laurent Bigonville ]
  * debian/rules: Explicitly disable wayland on non-linux architectures

gst-plugins-bad1.0 (1.22.0-4) unstable; urgency=medium

  * Team upload
  * debian/rules: Disable vulkan on non-linux architectures
  * Disable zxing element on architectures where opencv doesn't build

 -- Jeremy Bicha   Tue, 04 Apr 2023 10:00:40 -0400

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  gstreamer 1.22.1 bugfix release

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Triaged
Status in gst-plugins-good1.0 package in Ubuntu:
  Triaged
Status in gstreamer1.0 package in Ubuntu:
  Triaged

Bug description:
  Impact
  --
  This is a stable bugfix release

  See https://gstreamer.freedesktop.org/releases/1.22/#1.22.1 for more
  details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2015129/+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 2015347] [NEW] Regression: GTK statusbars look very weird on 200% scaling

2023-04-05 Thread Peter de Kraker

Public bug reported:

I don't know where I need to report this bug, but it's quite a serious
one.

On both livecd and installed version of Ubuntu 23.04 the statusbars of
some applications (for example libreoffice, Visual Studio Code, the
keychain dialog when logging in and more) are really small and weird
looking when using Gnome with 200% scaling.

https://pasteboard.co/S0idNZig1HEV.png

It looks like the legacy compatibility mode of GTK for these apps
doesn't take into account scaling. This worked properly on 22.10 and
earlier.

System:
Ubuntu 23.04 beta
NVIDIA RTX 3070Ti (nvidia drivers on install, nouveau I guess on livecd)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Schermafdruk van 2023-04-02 17-20-37.png"
   
https://bugs.launchpad.net/bugs/2015347/+attachment/5661187/+files/Schermafdruk%20van%202023-04-02%2017-20-37.png

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

Title:
  Regression: GTK statusbars look very weird on 200% scaling

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I don't know where I need to report this bug, but it's quite a serious
  one.

  On both livecd and installed version of Ubuntu 23.04 the statusbars of
  some applications (for example libreoffice, Visual Studio Code, the
  keychain dialog when logging in and more) are really small and weird
  looking when using Gnome with 200% scaling.

  https://pasteboard.co/S0idNZig1HEV.png

  It looks like the legacy compatibility mode of GTK for these apps
  doesn't take into account scaling. This worked properly on 22.10 and
  earlier.

  System:
  Ubuntu 23.04 beta
  NVIDIA RTX 3070Ti (nvidia drivers on install, nouveau I guess on livecd)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2015347/+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 2015345] [NEW] Intermittent problems with second monitor after xorg security updates

2023-04-05 Thread Nathan Wallach

Public bug reported:

I am running Ubuntu 22.04.2 LTS on a Dell 5410 laptop. Typically it is
connected to a Dell WD19 docking station with an attached monitor.

I have been having issues with using two monitors at once since a recent
security update to several xorg packages.

Since the update of:

Upgrade: xserver-xorg-core:amd64 (2:21.1.3-2ubuntu2,
2:21.1.3-2ubuntu2.9), xserver-xorg-legacy:amd64 (2:21.1.3-2ubuntu2,
2:21.1.3-2ubuntu2.9), xserver-common:amd64 (2:21.1.3-2ubuntu2,
2:21.1.3-2ubuntu2.9), xwayland:amd64 (2:22.1.1-1, 2:22.1.1-1ubuntu0.6),
xserver-xephyr:amd64 (2:21.1.3-2ubuntu2, 2:21.1.3-2ubuntu2.9)

sometimes only one monitor works at a time: the external one when the
docking station is attached and the internal screen when not. Several
times, after a reboot - only one monitor was available. When only one is
working the display settings show there only being one monitor.

Sometimes both work for a while, and then the problem starts. It is not
clear to me what triggers the problem. Once the bug triggers,
disconnecting the laptop from the docking station and reconnecting does
not seem to get the system back to using both monitors at once.
Detaching and the reattaching the monitor from the Docking station
helped once.

After a downgrade back to the versions - things seemed to work fine
again. I downgraded to the following package versions to avoid the issue

Downgrade: xserver-xorg-core:amd64 (2:21.1.3-2ubuntu2.9,
2:21.1.3-2ubuntu2), xserver-xorg-legacy:amd64 (2:21.1.3-2ubuntu2.9,
2:21.1.3-2ubuntu2), xserver-common:amd64 (2:21.1.3-2ubuntu2.9,
2:21.1.3-2ubuntu2), xwayland:amd64 (2:22.1.1-1ubuntu0.6, 2:22.1.1-1),
xserver-xephyr:amd64 (2:21.1.3-2ubuntu2.9, 2:21.1.3-2ubuntu2)

and after reinstalling the updates again experienced problems.

It seemed that things were fine when
xserver-xorg-core:amd64, xserver-common:amd64, xserver-xorg-legacy:amd64, 
server-xephyr:amd64 were all on version 2:21.1.3-2ubuntu2.7
and xwayland:amd64  was on version 2:22.1.1-1ubuntu0.5 but I am not sure about 
with  2:21.1.3-2ubuntu2.8 as I do not think the system was restarted after the 
update from  2:21.1.3-2ubuntu2.7 to 2:21.1.3-2ubuntu2.8.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  5 11:22:07 2023
DistUpgraded: 2023-03-09 23:44:15,474 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 
00 [VGA controller])
   Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:09a0]
InstallationDate: Installed on 2020-12-02 (853 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Latitude 5410
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic 
root=UUID=9835c982-ea8c-412d-bd72-92c8986e762a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to jammy on 2023-03-09 (26 days ago)
dmi.bios.date: 09/15/2022
dmi.bios.release: 1.17
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.17.0
dmi.board.name: 06KF2W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.0:bd09/15/2022:br1.17:svnDellInc.:pnLatitude5410:pvr:rvnDellInc.:rn06KF2W:rvrA00:cvnDellInc.:ct10:cvr:sku09A0:
dmi.product.family: Latitude
dmi.product.name: Latitude 5410
dmi.product.sku: 09A0
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.9
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

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


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

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

Title:
  Intermittent problems with second monitor after xorg security updates

Status in xorg package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 22.04.2 LTS on a Dell 5410 laptop. Typically it is
  connected to a Dell WD19 docking station with an attached monitor.

[Desktop-packages] [Bug 1998267] Autopkgtest regression report (glib2.0/2.72.4-0ubuntu2)

2023-04-05 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted glib2.0 (2.72.4-0ubuntu2) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

auto-multiple-choice/1.5.2-1willsync1 (arm64)
dbus/1.12.20-2ubuntu4.1 (armhf)
fwupd/1.7.9-1~22.04.1 (armhf)
golang-github-ostreedev-ostree-go/0.0+git20190702.759a8c1-4 (s390x)
gvfs/1.48.2-0ubuntu1 (ppc64el)
mutter/42.5-0ubuntu1 (amd64)
udisks2/2.9.4-1ubuntu2 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#glib2.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Jammy:
  Fix Committed
Status in glib2.0 source package in Kinetic:
  Won't Fix
Status in glib2.0 source package in Lunar:
  Fix Released

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  (requires a core snap running the updated glib).

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

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

2023-04-05 Thread alfuraldrid84

gnome-control-center freeze

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

Title:
  gnome-control-center

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

Bug description:
  gnome-control-center logs fix

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  4 18:21:28 2023
  InstallationDate: Installed on 2023-03-12 (23 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2023-04-05 Thread alfuraldrid84

gnome-system-monitor freeze

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

Title:
  gnome-system-monitor

Status in gnome-system-monitor package in Ubuntu:
  Incomplete

Bug description:
  gnome-system-monitor fix bug

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-system-monitor 42.0-1
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  4 18:25:40 2023
  InstallationDate: Installed on 2023-03-12 (23 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-system-monitor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/2015267/+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 2006500] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported()

** Changed in: gnome-control-center
   Status: Unknown => Fix Released

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

Title:
  gnome-control-center crashed with SIGSEGV in
  cc_display_config_manager_get_night_light_supported()

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed

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

  gnome-control-center crashed when i try change refresh rate to other
  value than 60 Hz. Its crash after I tap keep changes

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-control-center 1:44~alpha-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  7 19:59:50 2023
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2023-02-07 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209)
  JournalErrors: lut 07 19:59:50 hostname kernel: show_signal_msg: 4 callbacks 
suppressed
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0x55a5f2b496d4:mov(%rdi),%rax
   PC (0x55a5f2b496d4) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke()
  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/gnome-control-center/+bug/2006500/+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 2010561] Re: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created

2023-04-05 Thread Lukas Märdian

** Changed in: network-manager (Ubuntu)
Status: New => In Progress

** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)

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

Title:
The Netplan Everywhere NetworkManager fails to supply Netplan with
networking information until a connection is deleted and re-created

Status in netplan:
Triaged
Status in network-manager package in Ubuntu:
In Progress

Bug description:
Steps to reproduce:

Expected result: Networking information related to the WiFi connection
should appear in the "sudo netplan get" output.

Actual result: "sudo netplan get" returns the following:

End of output. Additionally, the /etc/netplan folder does not contain
files that I would expect to be there that would contain the
networking info.

Additional information:

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2010561/+subscriptions

[Desktop-packages] [Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()

This seems to fix it:
https://gitlab.gnome.org/GNOME/gjs/-/merge_requests/834

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

Title:
  gnome-shell crashed on logout with SIGSEGV in
  js::gc::Cell::storeBuffer() from
  js::gc::PostWriteBarrierImpl()

Status in gjs:
  New
Status in Spidermonkey Javascript engine:
  New
Status in OEM Priority Project:
  Confirmed
Status in gjs package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mozjs102 package in Ubuntu:
  Invalid
Status in mozjs91 package in Ubuntu:
  Invalid
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4
  https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7

  Description: Ubuntu 22.04 LTS
  Release: 22.04

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 20 16:06:35 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1649813447
  InstallationDate: Installed on 2022-05-05 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in g_object_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1974293/+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 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()

** Changed in: gjs (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gjs (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: mozjs102 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: mozjs91 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: gjs (Ubuntu)
Milestone: None => ubuntu-23.04

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

Title:
  gnome-shell crashed on logout with SIGSEGV in
  js::gc::Cell::storeBuffer() from
  js::gc::PostWriteBarrierImpl()

Status in gjs:
  New
Status in Spidermonkey Javascript engine:
  New
Status in OEM Priority Project:
  Confirmed
Status in gjs package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mozjs102 package in Ubuntu:
  Invalid
Status in mozjs91 package in Ubuntu:
  Invalid
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4
  https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7

  Description: Ubuntu 22.04 LTS
  Release: 22.04

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 20 16:06:35 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1649813447
  InstallationDate: Installed on 2022-05-05 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in g_object_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1974293/+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 2013271] Re: GTK3 titlebar buttons are bigger than GTK4 titlebar buttons

** Changed in: yaru
   Status: New => Fix Released

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

Title:
  GTK3 titlebar buttons are bigger than GTK4 titlebar buttons

Status in Yaru Theme:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Committed

Bug description:
  GTK3 titlebar buttons are bigger than GTK4 titlebar buttons

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/2013271/+subscriptions


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

[Desktop-packages] [Bug 2013107] Re: [lunar] GNOME does not display high contrast app icons

** Changed in: yaru
   Status: New => Fix Released

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

Title:
  [lunar] GNOME does not display high contrast app icons

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/2013107/+subscriptions


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

[Desktop-packages] [Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()

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

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


On 2023-04-05T08:20:49+00:00 Daniel van Vugt wrote:

Steps to reproduce:

1. Log into gnome-shell (currently version 44 using mozjs102).
2. Wait or use it for a while (long enough for some GC to have occurred I 
guess).
3. Log out.

https://launchpad.net/bugs/1974293
https://gitlab.gnome.org/GNOME/gjs/-/issues/472


Actual results:

#0  __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
tid = 
ret = 0
pd = 
old_mask = {__val = {11}}
ret = 
#1  __pthread_kill_internal (signo=11, threadid=) at 
./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=, signo=signo@entry=11) at 
./nptl/pthread_kill.c:89
#3  0x7f464d03c406 in __GI_raise (sig=sig@entry=11) at 
../sysdeps/posix/raise.c:26
ret = 
#4  0x56282c4afaea in dump_gjs_stack_on_signal_handler (signo=11) at 
../src/main.c:495
sa = {__sigaction_handler = {sa_handler = 0x56282c4af730 
, sa_sigaction = 0x56282c4af730 
}, sa_mask = {__val = {0 }}, 
sa_flags = 0, sa_restorer = 0x0}
i = 
#5  0x7f464d03c4b0 in  () at 
/lib/x86_64-linux-gnu/libc.so.6
#6  0x7f464ad8d344 in js::gc::Cell::storeBuffer() const (this=, this=) at /usr/src/mozjs102-102.9.0-1/js/src/gc/Cell.h:357
buffer = 0x0
#7  js::gc::PostWriteBarrierImpl(void*, JSObject*, JSObject*) 
(next=, prev=, cellp=) at 
/usr/src/mozjs102-102.9.0-1/js/src/gc/StoreBuffer.h:646
buffer = 0x0
#8  js::gc::PostWriteBarrier(js::SavedFrame**, js::SavedFrame*, 
js::SavedFrame*) (next=, prev=, vp=) at /usr/src/mozjs102-102.9.0-1/js/src/gc/StoreBuffer.h:658
#9  js::InternalBarrierMethods::postBarrier(js::SavedFrame**, js::SavedFrame*, js::SavedFrame*) 
(next=, prev=, vp=0x7f4630022da0) at 
/usr/src/mozjs102-102.9.0-1/js/src/gc/Barrier.h:350
#10 js::InternalBarrierMethods::postBarrier(js::SavedFrame**, js::SavedFrame*, js::SavedFrame*) 
(vp=0x7f4630022da0, prev=, next=) at 
/usr/src/mozjs102-102.9.0-1/js/src/gc/Barrier.h:349
#11 0x7f464d91f721 in js::BarrierMethods::postWriteBarrier(JSObject**, JSObject*, JSObject*) (next=0x0, 
prev=, vp=0x7f4630022da0) at 
/usr/include/mozjs-102/js/RootingAPI.h:795
p = 0x7f4630022da0
#12 JS::Heap::postWriteBarrier(JSObject* const&, JSObject* const&) 
(next=, prev=@0x7f4630022da0: 0x1c8a30a483a0, 
this=0x7f4630022da0, this=, prev=, 
next=)
at /usr/include/mozjs-102/js/RootingAPI.h:376
p = 0x7f4630022da0
#13 JS::Heap::~Heap() (this=0x7f4630022da0, this=) at 
/usr/include/mozjs-102/js/RootingAPI.h:338
p = 0x7f4630022da0
#14 mozilla::detail::VectorImpl, 0ul, 
js::SystemAllocPolicy, false>::destroy(JS::Heap*, 
JS::Heap*) (aEnd=0x7f4630022da8, aBegin=) at 
/usr/include/mozjs-102/mozilla/Vector.h:65
p = 0x7f4630022da0
#15 mozilla::Vector, 0ul, js::SystemAllocPolicy>::~Vector() 
(this=0x56282d2db9d8, this=) at 
/usr/include/mozjs-102/mozilla/Vector.h:901
#16 JS::GCVector, 0ul, js::SystemAllocPolicy>::~GCVector() 
(this=0x56282d2db9d8, this=) at 
/usr/include/mozjs-102/js/GCVector.h:43
#17 GjsContextPrivate::~GjsContextPrivate() (this=0x56282d2db960, 
this=) at 
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gjs/context.cpp:487
#18 0x7f464d9211e3 in gjs_context_finalize(GObject*) 
(object=0x56282d2dbae0) at 
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gjs/context.cpp:500
gjs = 
#19 0x7f464e02ee4c in g_object_unref (_object=0x56282d2dbae0) at 
../../../gobject/gobject.c:3938
weak_locations = 
nqueue = 0x56282d8fc5c0
object = 0x56282d2dbae0
old_ref = 
__func__ = "g_object_unref"
#20 0x7f464dc2508d in _shell_global_destroy_gjs_context (self=) at ../src/shell-global.c:752
_pp = 
_ptr = 
#21 0x56282c4af00f in main (argc=, argv=) at 
../src/main.c:776
context = 0x56282cd4e780
debug_flags_string = 0x56282d06c7b0 
"backtrace-aborts:backtrace-math-errors:backtrace-crashes-all:backtrace-all"
error = 0x0
shell_debug = 
ecode = 0
(gdb)


Expected results:

No crash.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1974293/comments/51


** Changed in: mozjs
   Status: Unknown => New

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

Title:
  gnome-shell crashed on logout with SIGSEGV in
  js::gc::Cell::storeBuffer() from
  js::gc::PostWriteBarrierImpl()

Status in gjs:
  New
Status in Spidermonkey Javascript engine:
  New
Status in OEM Priority Project:
  Confirmed
Status in gjs

[Desktop-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

2023-04-05 Thread Alex Robinson

On an Ubuntu 22.04 (newly updated from 18.04) box I got Firefox and
Chromium browser back to using the good, system SaveAs dialog box
instead of the horrid (((search box focus grabber and almost impossible
to change file name from the default))) dialog box by doing this:

sudo snap install snapd

This version of snapd, 2.38.3, apparently overrides the apt-installed
snapd version 2.38.

That the snap version of snapd wasn't installed ("snap list" did not
list it) was the glaring difference between the bad box and a laptop
that did not have the problem.

I should note: widget.use-xdg-desktop-portal.file-picker needs to be put
back to the default, 2, from 0.

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Invalid
Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()

Tracking upstream in
https://bugzilla.mozilla.org/show_bug.cgi?id=1826512

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

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

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

Title:
  gnome-shell crashed on logout with SIGSEGV in
  js::gc::Cell::storeBuffer() from
  js::gc::PostWriteBarrierImpl()

Status in gjs:
  New
Status in Spidermonkey Javascript engine:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in gjs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mozjs102 package in Ubuntu:
  Confirmed
Status in mozjs91 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4
  https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7

  Description: Ubuntu 22.04 LTS
  Release: 22.04

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 20 16:06:35 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1649813447
  InstallationDate: Installed on 2022-05-05 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in g_object_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1974293/+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 1981148] Re: Focusing the filename in GTK's portal file dialog triggers search

2023-04-05 Thread Alex Robinson

On an Ubuntu 22.04 (newly updated from 18.04) box I got Firefox and
Chromium browser back to using the good, system SaveAs dialog box
instead of the horrid (((search box focus grabber and almost impossible
to change file name from the default))) dialog box by doing this:

`sudo snap install snapd`

This version of snapd, 2.38.3, apparently overrides the apt-installed
snapd version 2.38.

That the snap version of snapd wasn't installed ("`snap list`" did not
list it) was the glaring difference between the bad box and a laptop
that did not have the problem.

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

Title:
  Focusing the filename in GTK's portal file dialog triggers search

Status in firefox package in Ubuntu:
  Confirmed
Status in lubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed

Bug description:
  I'm still wondering why my Ubuntu forces the snap version of Firefox
  onto me, despite apt-pinning, but OK, I guess being frustrated about
  that would be a lost cause.

  In any case:
  The snap version of Firefox that my Ubuntu has decided to install despite my 
apt-pinning has a bug in the saving dialog.

  I've recorded a video and left it online, here:
  https://anonfiles.com/X4ec15w7y3/simplescreenrecorder-2022-07-10_15.57.54_mkv

  Following protocol:

  1) $ lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  2) $ apt-cache policy firefox
  firefox:
Installed: 1:1snap1-0ubuntu2
Candidate: 1:1snap1-0ubuntu2
Version table:
   *** 1:1snap1-0ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
   102.0.1+build1-0ubuntu0.18.04.1 999
  500 http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu 
bionic/main amd64 Packages
  500 
https://ppa.launchpadcontent.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main 
amd64 Packages

  (note how Ubuntu doesn't give a damn about the pin priority, but
  whatever)

  
  3) I'm trying to save a downloaded document. 
   3.1) Firefox opens the save dialogue.
   3.2) I would like to enter a filename into the filename bar

  4) following 3.1:
   4.2) When I try to change the filename, the focus immediately jumps to the 
search bar and the dialogue for some reason tries to search for the entered 
letters on the drive. I can click back to focus on the filename bar, sometimes 
I can manage to type one or two letters, before the focus jumps, again.


  This does not happen with the version I installed using apt, but which
  repeatedly gets removed by the Ubuntu updating process, to install the
  snap version, which sadly never seems to work without problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Sun Jul 10 16:00:53 2022
  InstallationDate: Installed on 2022-03-07 (125 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981148/+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 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()

Looks closest to:

  https://bugzilla.mozilla.org/show_bug.cgi?id=1508618
  https://bugzilla.mozilla.org/show_bug.cgi?id=1511580

which were resolved several years ago by
https://hg.mozilla.org/releases/mozilla-beta/rev/ef2cd013fe73 so that
doesn't really help us now.

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

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

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

Title:
  gnome-shell crashed on logout with SIGSEGV in
  js::gc::Cell::storeBuffer() from
  js::gc::PostWriteBarrierImpl()

Status in gjs:
  New
Status in OEM Priority Project:
  Confirmed
Status in gjs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mozjs102 package in Ubuntu:
  Confirmed
Status in mozjs91 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4
  https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7

  Description: Ubuntu 22.04 LTS
  Release: 22.04

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 20 16:06:35 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1649813447
  InstallationDate: Installed on 2022-05-05 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in g_object_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1974293/+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 2012733] Re: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions

** Tags added: fixed-in-mutter-44.1 fixed-upstream

** Changed in: yaru-theme (Ubuntu)
   Status: In Progress => Fix Committed

** Tags added: fixed-in-yaru-23.04.2-0ubuntu2

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

Title:
  Unthemed and unscaled titlebars for server-side decorations in GNOME
  44 Xorg sessions

Status in Mutter:
  Fix Released
Status in Yaru Theme:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed
Status in yaru-theme package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  Nvidia 530 (graphics ppa), dGPU mode, GS 44, Lunar

  X1 session:
  If I launch Synaptic or ChessX, eg., the title bar is Adwaita-styled (greyish 
+ icons).
  No issue with GNOME apps (and some other like FF or TB snaps, etc.).

  Wayland session:
  all is ok (except many other bugs!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2012733/+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 2012733] Re: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  Unthemed and unscaled titlebars for server-side decorations in GNOME
  44 Xorg sessions

Status in Mutter:
  Fix Released
Status in Yaru Theme:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed
Status in yaru-theme package in Ubuntu:
  In Progress

Bug description:
  Hi,

  Nvidia 530 (graphics ppa), dGPU mode, GS 44, Lunar

  X1 session:
  If I launch Synaptic or ChessX, eg., the title bar is Adwaita-styled (greyish 
+ icons).
  No issue with GNOME apps (and some other like FF or TB snaps, etc.).

  Wayland session:
  all is ok (except many other bugs!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2012733/+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 1886728] Re: OpenVPN OTP replaces the ordinary password

** Changed in: network-manager
   Status: New => Fix Released

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

Title:
  OpenVPN OTP replaces the ordinary password

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  When OpenVPN has One-time password (OTP) enabled, and the user
  connects, a dialog asks the user to enter the One-time password (OTP)
  and press ok. This action replaces the ordinary "long term" password
  with the OTP. This causes annoyance as the next login will fail
  because the password is wrong and the user has to enter both the
  password and the OTP the next time they log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  8 01:07:18 2020
  InstallationDate: Installed on 2020-03-23 (106 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to focal on 2020-05-11 (57 days ago)

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

Please remove the 'kisak' PPA from your system as it is unsupported and
likely to cause graphics bugs. Once removed, feel free to report new
bugs about any problems you encounter.

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

** Changed in: ubuntu
   Status: Incomplete => Invalid

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

Title:
  gnome-shell

Status in Ubuntu:
  Invalid

Bug description:
  gnome-shell fix

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  4 18:22:35 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-03-12 (23 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2015264/+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 2015255] Re: [Lenovo Legion 5 17ACH6H] Backlight regulation don't work

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

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 1944094, 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.


** Summary changed:

- Backlight regulation don't work
+ [Lenovo Legion 5 17ACH6H] Backlight regulation don't work

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

** This bug has been marked a duplicate of bug 1944094
   Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD

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

Title:
  [Lenovo Legion 5 17ACH6H] Backlight regulation don't work

Status in linux package in Ubuntu:
  New

Bug description:
  Hello.
  I trying different fresh live USB: 20.04, 22.04, 22.10 and 23.04-beta
  Only 23.04-beta can't adjust brightness level of display backlight on my 
laptop (lenovo legion 5 17ach6h).
  Processor: AMD Ryzen™ 7 5800H with Radeon™ Graphics × 16
  Graphics: AMD Radeon™ Graphics / AMD Radeon™ Graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.480
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  4 14:17:45 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:24dd] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GA104M [GeForce RTX 3070 Mobile / Max-Q] [17aa:3a4e]
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:3a4e]
  LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
  MachineType: LENOVO 82JY
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2022
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN59WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 5 17ACH6H
  dmi.ec.firmware.release: 1.59
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN59WW:bd11/21/2022:br1.59:efr1.59:svnLENOVO:pn82JY:pvrLegion517ACH6H:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegion517ACH6H:skuLENOVO_MT_82JY_BU_idea_FM_Legion517ACH6H:
  dmi.product.family: Legion 5 17ACH6H
  dmi.product.name: 82JY
  dmi.product.sku: LENOVO_MT_82JY_BU_idea_FM_Legion 5 17ACH6H
  dmi.product.version: Legion 5 17ACH6H
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.1-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/linux/+bug/2015255/+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 2015273] Re: Errors in syslog cant update stage views actor because it needs an allocation

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

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 2007742, 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 2007742
   Can't update stage views actor  (regarding MetaWindowGroup, 
MetaWindowActorX11, MetaSurfaceActorX11)

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

Title:
  Errors in syslog cant update stage views actor because it needs an
  allocation

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  switch from wayland to xorg and error started.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  4 08:37:09 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-03-18 (17 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015273/+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 2015228] Re: Bluetooth not working rfkill Soft blocked: yes

Try pressing the wireless key (Fn+PrtScr) to toggle the soft block.

** Summary changed:

- Bluetooth not working rfkill Soft blocked: yes
+ Dell Inspiron 7577 Bluetooth not working rfkill Soft blocked: yes

** Package changed: bluez (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Dell Inspiron 7577 Bluetooth not working rfkill Soft blocked: yes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi Devs,

  Hope you're all keeping well.

  The problem I have is similar to:
  https://answers.launchpad.net/ubuntu/+question/699306

  Basically Bluetooth doesn't work on installed Ubuntu 22.04.2 neither
  the laptop (Dell Inspirion 7577) internal device (Intel 8265) or a USB
  dongle (not sure it was recommended for raspberry pi and works on
  desktop with 22.04 just fine: 0a12:0001 Cambridge Silicon Radio, Ltd
  Bluetooth Dongle (HCI mode).

  It works fine in a live USB image on the same laptop.

  I get the following with rfkill:

  rfkill list all 
  1: hci1: Bluetooth
Soft blocked: yes
Hard blocked: no
  2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  3: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

  - Unblocking with rfkill doesn't work
  - Restarting bluetooth doesn't work
  - Getting another device doesn't work

  I recall having issues with WiFi around the time I got the laptop, and
  recall changing settings for that - but I couldn't tell you what they
  were (~2017 ish). Plus I believe I've reinstalled since then due to an
  SSD failure. It has been upgraded from LTS to LTS since 18.04 though.

  Any thoughts, ideas, or questions, I'm more than happy to try
  anything, or even help as much as possible to help get this resolved,
  its been going on for a couple of years now and mainly ignored it
  because I was mostly fine without, but I really need it to work now
  and appreciate any help on this.

  Thanks so much in advance, love you all for the work you do.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Apr  4 12:47:27 2023
  InstallationDate: Installed on 2020-04-09 (1089 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7577
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic 
root=UUID=761c1e7a-7759-4f7d-a985-33c7654bccad ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to jammy on 2023-01-12 (82 days ago)
  dmi.bios.date: 03/18/2022
  dmi.bios.release: 1.17
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.17.0
  dmi.board.name: 0XCNGT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.0:bd03/18/2022:br1.17:svnDellInc.:pnInspiron7577:pvr:rvnDellInc.:rn0XCNGT:rvrA00:cvnDellInc.:ct10:cvr:sku07FA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7577
  dmi.product.sku: 07FA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015228/+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 2006500] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported()