date:20230930

[Desktop-packages] [Bug 1958019]

2023-09-30 Thread realmamitler

I was wondering how do I apply any patches? I'm on a legion 7i gen 7 and
was wondering how to add patches because I wanted to try out if any
patch works for my system, thank you.

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support

2023-09-30 Thread Launchpad Bug Tracker

This bug was fixed in the package mesa - 23.2.1-1ubuntu2

---
mesa (23.2.1-1ubuntu2) mantic; urgency=medium

  * d/p/v3d-v3dv-support-for-HW-7.1.x.patch
- [FFe] Raspberry Pi 5 (LP: #2037642)

 -- Juerg Haefliger   Fri, 29 Sep 2023
08:27:32 +0200

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

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

Title:
  [FFe] Raspberry Pi 5 support

Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Triaged
Status in linux-raspi package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Triaged
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2037795] Re: gnome-shell crashed with SIGSEGV in clutter_stage_process_event()

2023-09-30 Thread Apport retracing service

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

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 #2035096, 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/2037795/+attachment/5705550/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 2035096
   gnome-shell crashed with SIGSEGV in clutter_stage_emit_event()

** 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2037795

Title:
  gnome-shell crashed with SIGSEGV in clutter_stage_process_event()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I was prompted to restart in order to complete a software updated.
  After (rebooting and) entering my password at login, the desktop
  appeared but the moues was unable to move. After ~5s I was kicked back
  to the login window, logged in again and everything was fine.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 30 16:27:34 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-28 (2 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   clutter_stage_process_event () from 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-clutter-13.so.0
   _clutter_stage_process_queued_events () from 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-clutter-13.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-clutter-13.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_stage_process_event()
  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/gnome-shell/+bug/2037795/+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 2037794] [NEW] [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound at all

2023-09-30 Thread Jose Miguel Sanchez Vargas

Public bug reported:

Not sound at all

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 30 15:00:02 2023
InstallationDate: Installed on 2023-08-28 (33 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UX482EA.311
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX482EA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX482EA.311:bd10/21/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX482EA_UX482EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX482EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX482EA_UX482EA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

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

Title:
  [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Not sound at all

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 30 15:00:02 2023
  InstallationDate: Installed on 2023-08-28 (33 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX482EA.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX482EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX482EA.311:bd10/21/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX482EA_UX482EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX482EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX482EA_UX482EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2037794/+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 2037503] Re: [jammy]backport #1453 from upstream

2023-09-30 Thread Erkin Alp Güney

related freeze exception from upstream:
https://gitlab.gnome.org/Teams/Releng/freeze-breaks/-/issues/101

** Tags added: jammy

** Bug watch added: gitlab.gnome.org/Teams/Releng/freeze-breaks/-/issues #101
   https://gitlab.gnome.org/Teams/Releng/freeze-breaks/-/issues/101

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

Title:
  [jammy]backport #1453 from upstream

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

Bug description:
  In some cases, it was possible for a profile to be set (directly, or
  through a hold) even though it wasn't supported. Don't assert in those
  cases.

  The bug in question makes the gnome-control-center crash if an unsupported
  power profile is set using, say, powerprofilesctl.
  Should be trivial to cherry-pick without breaking other components.
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453

  I had to wait for this long because I expected a 42.x backport in the
  backports repository of .1 release, but no one bothered to do such a
  backport.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+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 2037766] Re: firefox snap crashes when playing video REGRESSION

2023-09-30 Thread StevenT

This morning I saw that there was a update to the gnome-42-2204 snap
(rev. 141) available, so I refreshed it and then tried to play a video
in firefox 118.0.1-1 again. Happily, firefox played videos with the
hardware acceleration option enabled and did not crash. I've yet to try
it whiled logged into a wayland session and will do that later today and
will report if I receive any errors

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

Title:
  firefox snap crashes when playing video REGRESSION

Status in firefox package in Ubuntu:
  New

Bug description:
  Newest snap version of Firefox instantly crashes when attempting to
  play a video with the setting, "Use hardware acceleration when
  available" is enabled. Disabling the hardware acceleration setting
  allows videos to play albeit with occasional stuttering and high CPU
  utilization.

  Older version of snap Firefox with identical settings and hardware
  acceleration enabled played videos well.

  System:
Host: neons Kernel: 6.2.0-33-generic arch: x86_64 bits: 64 compiler: N/A
Desktop: GNOME v: 42.9 Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
  CPU:
Info: dual core AMD Athlon II X2 245 [MCP] arch: K10 speed (MHz): avg: 800
  min/max: 800/2900
  Graphics:
Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: VISIONTEK
  driver: radeon v: kernel arch: TeraScale-2 bus-ID: 01:00.0 temp: 60.0 C
Display: x11 server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.1 driver: X:
  loaded: radeon unloaded: fbdev,modesetting,vesa dri: r600 gpu: radeon
  resolution: 1600x900~60Hz
API: OpenGL v: 4.5 Mesa 23.0.4-0ubuntu1~22.04.1 renderer: AMD CEDAR (DRM
  2.50.0 / 6.2.0-33-generic LLVM 15.0.7) direct-render: Yes

  $ snap list firefox --all
  Name VersionRev   Tracking   Publisher  Notes
  firefox  118.0.1-1  3206  latest/stable  mozilla✓   -
  firefox  116.0.3-2  3026  latest/stable  mozilla✓   disabled

  When started from the command-line, the 118.0.1-1 version spams the
  following output when playing a video before crashing:

  EE ../src/gallium/drivers/r600/r600_shader.c:193 r600_pipe_shader_create - 
translation from TGSI failed !
  EE ../src/gallium/drivers/r600/r600_state_common.c:961 r600_shader_select - 
Failed to build shader variant (type=1) -1

  This goes on for several lines until it gets here:

  libva info: VA-API version 1.19.0
  libva info: Trying to open 
/snap/firefox/3206/gnome-platform/usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so

  Then it spams a few more shader lines and then gets here:

  libva info: va_openDriver() returns 0
  ATTENTION: default value of option mesa_glthread overridden by environment.
  out of memory: 0x000773594008 bytes requested
  ExceptionHandler::GenerateDump cloned child 8049
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.

  At which point the Firefox window disappears and the Firefox crash
  handler pop up.

  Terminal output from 116.0.3-2 when playing same video

  [Parent 8438, Main Thread] WARNING: OnCloseSessionDone error: Timeout
  was reached: 'glib warning', file
  /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167

  ** (firefox:8438): WARNING **: 16:29:24.338: OnCloseSessionDone error: 
Timeout was reached
  libva info: VA-API version 1.7.0
  libva info: Trying to open 
/snap/firefox/3026/gnome-platform/usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
  libva info: Found init function __vaDriverInit_1_7
  ATTENTION: default value of option mesa_glthread overridden by environment.
  libva info: va_openDriver() returns 0
  ATTENTION: default value of option mesa_glthread overridden by environment.

  The same latest release of Firefox downloaded directly from
  mozilla.org does not have this problem and works as expected with no
  issues.

  Chromium snap is also installed and up-to-date, but does not crash
  with hardware acceleration enabled and plays videos as expected.

  Expectations:
  1. New version of Firefox snap should have at least the same performance 
profile as an older version, or the same version of the non-snap release
  2. Even if a hardware acceleration setting is not attainable because of the 
limitation of said hardware, the program should gracefully downgrade to 
software rendering and not crash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037766/+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 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers

2023-09-30 Thread Gunnar Hjalmarsson

Added yelp as affected package too, since you hit this bug if you browse
the desktop guide on X11/NVIDIA.

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

** Changed in: yelp (Ubuntu)
   Status: New => Triaged

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

Title:
  Unable to setup Google Online Accounts with Nvidia drivers

Status in Webkit:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in webkit2gtk package in Ubuntu:
  Incomplete
Status in yelp package in Ubuntu:
  Triaged
Status in webkit2gtk package in Debian:
  Confirmed

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL

[Desktop-packages] [Bug 2037228] Re: Firefox doesn't work after 23.10 upgrade

2023-09-30 Thread Rick

It looks like my issue is related to this bug 
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036765

I followed the steps in this post to fix my firefox
https://discourse.ubuntu.com/t/ubuntu-23-10-beta-testing/38861/9
snap refresh --channel=latest/stable/ubuntu-23.10 firefox


Firefox however semi broke again yesterday (clicking the icon didn't open it)
$ firefox
Content snap command-chain for 
/snap/firefox/3166/gnome-platform/command-chain/desktop-launch not found: 
ensure slot is connected

$ snap refresh
fixed firefox this time for me

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

Title:
  Firefox doesn't work after 23.10 upgrade

Status in firefox package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  Firefox doesn’t work after upgrading from 23.04 to 23.10 beta.
  The Firefox icon disappeared from my sidebar during the upgrade process.
  'snap list' shows firefox stable is installed, trying to run the command 
firefox says: 
  Command '/usr/bin/firefox' requires the firefox snap to be installed. Please 
install it with: snap install firefox

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu Mantic Minotaur (development branch)
  Release:23.10

  
  $ apt-cache policy firefox
  firefox:
Installed: 1:1snap1-0ubuntu3
Candidate: 1:1snap1-0ubuntu3
Version table:
   *** 1:1snap1-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037228/+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 2037773] Re: Rebuild against latest webkit2gtk

2023-09-30 Thread Gunnar Hjalmarsson

Ok, thanks. Then we can drop the rebuild idea, so closing this bug. I
also added yelp to bug #2023322.

** Changed in: yelp (Ubuntu)
   Status: In Progress => Invalid

** Changed in: yelp (Ubuntu)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)

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

Title:
  Rebuild against latest webkit2gtk

Status in yelp package in Ubuntu:
  Invalid

Bug description:
  Please see this email thread:

  https://lists.ubuntu.com/archives/ubuntu-devel-
  discuss/2023-September/019607.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037773/+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 2037773] Re: Rebuild against latest webkit2gtk

2023-09-30 Thread Jack Howarth

Actually, I just checked gnome-online-accounts in the gnome-control-
center under X11 nvidia and it is also broken for the Google login.
Clicking the Google Account under the Online Accounts options, produces
and empty window whereas under Wayland nvidia, the sign in content is
displayed. So
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2023322
appears to be the same issue and remains unresolved in 23.10.

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

Title:
  Rebuild against latest webkit2gtk

Status in yelp package in Ubuntu:
  In Progress

Bug description:
  Please see this email thread:

  https://lists.ubuntu.com/archives/ubuntu-devel-
  discuss/2023-September/019607.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037773/+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 2037773] Re: Rebuild against latest webkit2gtk

2023-09-30 Thread Jack Howarth

I still see the bug with your build. One correction though. Apparently
my proposed fix of changing...

* debian/control.in: Bump Standards-Version to 4.6.2

is insufficient. It seems that my previous workaround of changing
/usr/share/applications/yelp.desktop to contain...

Exec=env WEBKIT_DISABLE_COMPOSITING_MODE=1 yelp %u

rather than

Exec=yelp %u

survives closing yelp and reinstalling the packages. After a reboot,
with that change no longer in the desktop file for yelp, the bug
returns.

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

Title:
  Rebuild against latest webkit2gtk

Status in yelp package in Ubuntu:
  In Progress

Bug description:
  Please see this email thread:

  https://lists.ubuntu.com/archives/ubuntu-devel-
  discuss/2023-September/019607.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037773/+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 2037773] Re: Rebuild against latest webkit2gtk

2023-09-30 Thread Jack Howarth

FYI, I see that same bug, with no content in the Help application, for
both the 6.5.0-5.5 and 6.5.0-6.6 kernels. Only resorting to the
change...

Exec=env WEBKIT_DISABLE_COMPOSITING_MODE=1 yelp %u

or using Wayland suppresses the bug.

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

Title:
  Rebuild against latest webkit2gtk

Status in yelp package in Ubuntu:
  In Progress

Bug description:
  Please see this email thread:

  https://lists.ubuntu.com/archives/ubuntu-devel-
  discuss/2023-September/019607.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037773/+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 2037773] Re: Rebuild against latest webkit2gtk

2023-09-30 Thread Jack Howarth

FYI, I am running mantic on a workstation with secure boot enabled for
the second drive containing Windows 11 in case that might have some
impact on the bug. The linux debs that are installed are...

ii  linux-base4.5ubuntu9
  all  Linux image base package
ii  linux-firmware20230919.git3672ccab-0ubuntu2 
  amd64Firmware for Linux kernel drivers
ii  linux-generic-hwe-22.04   6.5.0.6.8 
  amd64Complete Generic Linux kernel and headers
ii  linux-headers-6.5.0-5 6.5.0-5.5 
  all  Header files related to Linux kernel version 6.5.0
ii  linux-headers-6.5.0-5-generic 6.5.0-5.5 
  amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP
ii  linux-headers-6.5.0-6 6.5.0-6.6 
  all  Header files related to Linux kernel version 6.5.0
ii  linux-headers-6.5.0-6-generic 6.5.0-6.6 
  amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP
ii  linux-headers-generic-hwe-22.04   6.5.0.6.8 
  amd64Generic Linux kernel headers
ii  linux-image-6.5.0-5-generic   6.5.0-5.5 
  amd64Signed kernel image generic
ii  linux-image-6.5.0-6-generic   6.5.0-6.6 
  amd64Signed kernel image generic
ii  linux-image-generic-hwe-22.04 6.5.0.6.8 
  amd64Generic Linux kernel image
ii  linux-libc-dev:amd64  6.5.0-6.6 
  amd64Linux Kernel Headers for development
ii  linux-modules-6.5.0-5-generic 6.5.0-5.5 
  amd64Linux kernel extra modules for version 6.5.0 on 64 bit 
x86 SMP
ii  linux-modules-6.5.0-6-generic 6.5.0-6.6 
  amd64Linux kernel extra modules for version 6.5.0 on 64 bit 
x86 SMP
ii  linux-modules-extra-6.5.0-5-generic   6.5.0-5.5 
  amd64Linux kernel extra modules for version 6.5.0 on 64 bit 
x86 SMP
ii  linux-modules-extra-6.5.0-6-generic   6.5.0-6.6 
  amd64Linux kernel extra modules for version 6.5.0 on 64 bit 
x86 SMP
ii  linux-modules-nvidia-535-6.5.0-5-generic  6.5.0-5.5 
  amd64Linux kernel nvidia modules for version 6.5.0-5
ii  linux-modules-nvidia-535-6.5.0-6-generic  6.5.0-6.6 
  amd64Linux kernel nvidia modules for version 6.5.0-6
ii  linux-modules-nvidia-535-generic-hwe-22.046.5.0-6.6 
  amd64Extra drivers for nvidia-535 for the generic-hwe-22.04 
flavour
ii  linux-objects-nvidia-535-6.5.0-5-generic  6.5.0-5.5 
  amd64Linux kernel nvidia modules for version 6.5.0-5 (objects)
ii  linux-objects-nvidia-535-6.5.0-6-generic  6.5.0-6.6 
  amd64Linux kernel nvidia modules for version 6.5.0-6 (objects)
ii  linux-signatures-nvidia-6.5.0-5-generic   6.5.0-5.5 
  amd64Linux kernel signatures for nvidia modules for version 
6.5.0-5-generic
ii  linux-signatures-nvidia-6.5.0-6-generic   6.5.0-6.6 
  amd64Linux kernel signatures for nvidia modules for version 
6.5.0-6-generic
ii  linux-sound-base  1.0.25+dfsg-0ubuntu7  
  all  base package for ALSA and OSS sound systems
ii  linux-tools-6.5.0-5   6.5.0-5.5 
  amd64Linux kernel version specific tools for version 6.5.0-5
ii  linux-tools-6.5.0-5-generic   6.5.0-5.5 
  amd64Linux kernel version specific tools for version 6.5.0-5
ii  linux-tools-6.5.0-6   6.5.0-6.6 
  amd64Linux kernel version specific tools for version 6.5.0-6
ii  linux-tools-6.5.0-6-generic   6.5.0-6.6 
  amd64Linux kernel version specific tools for version 6.5.0-6
ii  linux-tools-common6.5.0-6.6 
  all  Linux kernel version specific tools for version 6.5.0

and the nvidia kernel is installed with the signatures package and the
prebuilt modules rather than using dkms.

ii  libnvidia-cfg1-535:amd64  535.104.05-0ubuntu4   
  amd64NVIDIA binary OpenGL/GLX configuration library
ii  libnvidia-common-535

[Desktop-packages] [Bug 2037773] Re: Rebuild against latest webkit2gtk

2023-09-30 Thread Jack Howarth

** Attachment added: "yelp nvidia bug.png"
   
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037773/+attachment/5705507/+files/yelp%20nvidia%20bug.png

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

Title:
  Rebuild against latest webkit2gtk

Status in yelp package in Ubuntu:
  In Progress

Bug description:
  Please see this email thread:

  https://lists.ubuntu.com/archives/ubuntu-devel-
  discuss/2023-September/019607.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037773/+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 2037696] Re: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common

2023-09-30 Thread Launchpad Bug Tracker

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

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

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

Title:
  package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to
  install/upgrade: conflicting packages - not installing libreoffice-
  common

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I wanted to upgrade the ubuntu. But these bugs are coming on update.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-common 1:6.0.7-0ubuntu0.18.04.13
  ProcVersionSignature: Ubuntu 5.4.0-163.180-generic 5.4.246
  Uname: Linux 5.4.0-163-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Sep 25 00:08:48 2023
  ErrorMessage: conflicting packages - not installing libreoffice-common
  InstallationDate: Installed on 2023-08-21 (35 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to 
install/upgrade: conflicting packages - not installing libreoffice-common
  UpgradeStatus: Upgraded to focal on 2023-09-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2037696/+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 1923363] Re: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

2023-09-30 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-settings - 23.10.5

---
ubuntu-settings (23.10.5) mantic; urgency=medium

  * ubuntu-raspi-settings: Add macb ethernet driver to the eth0 rename list
to support Raspberry Pi 5 (LP: #2037642)
  * ubuntu-raspi-settings: Use uaccess instead of group membership to control
access to GPIO devices (LP: #1923363)
  * ubuntu-settings, ubuntu-raspi-settings-desktop: Override lintian warnings
about netplan configuration mode and growroot.service

 -- Dave Jones   Fri, 22 Sep 2023 11:13:46
+0100

** Changed in: ubuntu-settings (Ubuntu Mantic)
   Status: Triaged => Fix Released

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

Title:
  Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

Status in cloud-init package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Invalid
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in user-setup package in Ubuntu:
  Invalid
Status in cloud-init source package in Impish:
  Won't Fix
Status in ubiquity source package in Impish:
  Invalid
Status in ubuntu-settings source package in Impish:
  Won't Fix
Status in user-setup source package in Impish:
  Invalid
Status in cloud-init source package in Jammy:
  Confirmed
Status in ubiquity source package in Jammy:
  Invalid
Status in ubuntu-settings source package in Jammy:
  Confirmed
Status in user-setup source package in Jammy:
  Invalid
Status in cloud-init source package in Kinetic:
  Won't Fix
Status in ubiquity source package in Kinetic:
  Invalid
Status in ubuntu-settings source package in Kinetic:
  Won't Fix
Status in user-setup source package in Kinetic:
  Invalid
Status in cloud-init source package in Lunar:
  Won't Fix
Status in ubiquity source package in Lunar:
  Invalid
Status in ubuntu-settings source package in Lunar:
  Won't Fix
Status in user-setup source package in Lunar:
  Invalid
Status in cloud-init source package in Mantic:
  Fix Released
Status in ubiquity source package in Mantic:
  Invalid
Status in ubuntu-settings source package in Mantic:
  Fix Released
Status in user-setup source package in Mantic:
  Invalid

Bug description:
  We're attempting to make the GPIO system on the Raspberry Pi images
  work "out of the box" on the new image. By default, GPIO kernel
  devices are made available to members of the "dialout" group which the
  initial user is added to by default on our server images. However,
  we've noticed that this isn't the case on the desktop images.

  The regression potential is minimal; the group already exists and
  we're simply adding the freshly created user to a new group and not
  removing any existing memberships. The group in question ("dialout")
  is also rarely used these days except for providing access to serial
  consoles, and as mentioned above is already a default membership on
  the server images. The change has been tested on the desktop image
  successfully.

  A test build of the updated image will be made under
  https://launchpad.net/~waveform/+archive/ubuntu/ubiquity and I'll
  attach a debdiff shortly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1923363/+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 2037642] Re: [FFe] Raspberry Pi 5 support

2023-09-30 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-settings - 23.10.5

---
ubuntu-settings (23.10.5) mantic; urgency=medium

  * ubuntu-raspi-settings: Add macb ethernet driver to the eth0 rename list
to support Raspberry Pi 5 (LP: #2037642)
  * ubuntu-raspi-settings: Use uaccess instead of group membership to control
access to GPIO devices (LP: #1923363)
  * ubuntu-settings, ubuntu-raspi-settings-desktop: Override lintian warnings
about netplan configuration mode and growroot.service

 -- Dave Jones   Fri, 22 Sep 2023 11:13:46
+0100

** Changed in: ubuntu-settings (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [FFe] Raspberry Pi 5 support

Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Triaged
Status in linux-raspi package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Committed
Status in pipewire package in Ubuntu:
  Triaged
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2037773] Re: Rebuild against latest webkit2gtk

2023-09-30 Thread Gunnar Hjalmarsson

@Jack: I don't see a yelp issue in a 23.10 Xorg session with NVIDIA. But
I uploaded yelp to this PPA:

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

Can you please install yelp from there and confirm that it makes a
difference for you compared with yelp 42.2-1 in the archive?

** Changed in: yelp (Ubuntu)
   Status: New => In Progress

** Changed in: yelp (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Rebuild against latest webkit2gtk

Status in yelp package in Ubuntu:
  In Progress

Bug description:
  Please see this email thread:

  https://lists.ubuntu.com/archives/ubuntu-devel-
  discuss/2023-September/019607.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037773/+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 2003283] Re: Ubuntu22.04 Remote Desktop doesn't support to display the screen of the second monitor

2023-09-30 Thread m...@papersolve.com

I just set this up and can confirm, it only sees one monitor (the
"primary"). Very weird. No problem using x0tigervncserver to see them
both.

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

Title:
  Ubuntu22.04 Remote Desktop doesn't support to display the screen of
  the second monitor

Status in gnome-remote-desktop package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 Remote Desktop can only show the screen of the main
  monitor but not for the second monitor. It did work in Ubuntu 20.04
  without any problem on the same computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.1
  Uname: Linux 6.1.4-060104-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 19 11:03:30 2023
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2023-01-10 (8 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  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-remote-desktop/+bug/2003283/+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 2037773] [NEW] Rebuild against latest webkit2gtk

2023-09-30 Thread Gunnar Hjalmarsson

Public bug reported:

Please see this email thread:

https://lists.ubuntu.com/archives/ubuntu-devel-
discuss/2023-September/019607.html

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

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

Title:
  Rebuild against latest webkit2gtk

Status in yelp package in Ubuntu:
  New

Bug description:
  Please see this email thread:

  https://lists.ubuntu.com/archives/ubuntu-devel-
  discuss/2023-September/019607.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037773/+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 2003283] Re: Ubuntu22.04 Remote Desktop doesn't support to display the screen of the second monitor

2023-09-30 Thread Launchpad Bug Tracker

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

** Changed in: gnome-remote-desktop (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ubuntu22.04 Remote Desktop doesn't support to display the screen of
  the second monitor

Status in gnome-remote-desktop package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 Remote Desktop can only show the screen of the main
  monitor but not for the second monitor. It did work in Ubuntu 20.04
  without any problem on the same computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.1
  Uname: Linux 6.1.4-060104-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 19 11:03:30 2023
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2023-01-10 (8 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  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-remote-desktop/+bug/2003283/+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 1923363] Re: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

2023-09-30 Thread Steve Langasek

it does now

** Changed in: ubuntu-settings (Ubuntu Mantic)
   Status: Confirmed => Triaged

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

Title:
  Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

Status in cloud-init package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Invalid
Status in ubuntu-settings package in Ubuntu:
  Triaged
Status in user-setup package in Ubuntu:
  Invalid
Status in cloud-init source package in Impish:
  Won't Fix
Status in ubiquity source package in Impish:
  Invalid
Status in ubuntu-settings source package in Impish:
  Won't Fix
Status in user-setup source package in Impish:
  Invalid
Status in cloud-init source package in Jammy:
  Confirmed
Status in ubiquity source package in Jammy:
  Invalid
Status in ubuntu-settings source package in Jammy:
  Confirmed
Status in user-setup source package in Jammy:
  Invalid
Status in cloud-init source package in Kinetic:
  Won't Fix
Status in ubiquity source package in Kinetic:
  Invalid
Status in ubuntu-settings source package in Kinetic:
  Won't Fix
Status in user-setup source package in Kinetic:
  Invalid
Status in cloud-init source package in Lunar:
  Won't Fix
Status in ubiquity source package in Lunar:
  Invalid
Status in ubuntu-settings source package in Lunar:
  Won't Fix
Status in user-setup source package in Lunar:
  Invalid
Status in cloud-init source package in Mantic:
  Fix Released
Status in ubiquity source package in Mantic:
  Invalid
Status in ubuntu-settings source package in Mantic:
  Triaged
Status in user-setup source package in Mantic:
  Invalid

Bug description:
  We're attempting to make the GPIO system on the Raspberry Pi images
  work "out of the box" on the new image. By default, GPIO kernel
  devices are made available to members of the "dialout" group which the
  initial user is added to by default on our server images. However,
  we've noticed that this isn't the case on the desktop images.

  The regression potential is minimal; the group already exists and
  we're simply adding the freshly created user to a new group and not
  removing any existing memberships. The group in question ("dialout")
  is also rarely used these days except for providing access to serial
  consoles, and as mentioned above is already a default membership on
  the server images. The change has been tested on the desktop image
  successfully.

  A test build of the updated image will be made under
  https://launchpad.net/~waveform/+archive/ubuntu/ubiquity and I'll
  attach a debdiff shortly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1923363/+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 1923363] Re: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

2023-09-30 Thread Dimitri John Ledkov

Does this have FFe?

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

Title:
  Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

Status in cloud-init package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Invalid
Status in ubuntu-settings package in Ubuntu:
  Confirmed
Status in user-setup package in Ubuntu:
  Invalid
Status in cloud-init source package in Impish:
  Won't Fix
Status in ubiquity source package in Impish:
  Invalid
Status in ubuntu-settings source package in Impish:
  Won't Fix
Status in user-setup source package in Impish:
  Invalid
Status in cloud-init source package in Jammy:
  Confirmed
Status in ubiquity source package in Jammy:
  Invalid
Status in ubuntu-settings source package in Jammy:
  Confirmed
Status in user-setup source package in Jammy:
  Invalid
Status in cloud-init source package in Kinetic:
  Won't Fix
Status in ubiquity source package in Kinetic:
  Invalid
Status in ubuntu-settings source package in Kinetic:
  Won't Fix
Status in user-setup source package in Kinetic:
  Invalid
Status in cloud-init source package in Lunar:
  Won't Fix
Status in ubiquity source package in Lunar:
  Invalid
Status in ubuntu-settings source package in Lunar:
  Won't Fix
Status in user-setup source package in Lunar:
  Invalid
Status in cloud-init source package in Mantic:
  Fix Released
Status in ubiquity source package in Mantic:
  Invalid
Status in ubuntu-settings source package in Mantic:
  Confirmed
Status in user-setup source package in Mantic:
  Invalid

Bug description:
  We're attempting to make the GPIO system on the Raspberry Pi images
  work "out of the box" on the new image. By default, GPIO kernel
  devices are made available to members of the "dialout" group which the
  initial user is added to by default on our server images. However,
  we've noticed that this isn't the case on the desktop images.

  The regression potential is minimal; the group already exists and
  we're simply adding the freshly created user to a new group and not
  removing any existing memberships. The group in question ("dialout")
  is also rarely used these days except for providing access to serial
  consoles, and as mentioned above is already a default membership on
  the server images. The change has been tested on the desktop image
  successfully.

  A test build of the updated image will be made under
  https://launchpad.net/~waveform/+archive/ubuntu/ubiquity and I'll
  attach a debdiff shortly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1923363/+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 1990341] Autopkgtest regression report (ubuntu-drivers-common/1:0.9.7.1.2)

2023-09-30 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted ubuntu-drivers-common (1:0.9.7.1.2) for 
lunar have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-drivers-common/1:0.9.7.1.2 (ppc64el)


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/lunar/update_excuses.html#ubuntu-drivers-common

[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 ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341

Title:
  [SRU] Support to install nvidia driver by allowing list

Status in OEM Priority Project:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Confirmed
Status in ubuntu-drivers-common source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

   * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
  OEM/ODM for production.

  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
  to use a specific nvidia version to development/production.

  NVIDIA and OEN/ODM will announce the next generation combination at
  the same time usually when the factory ready to ship the product.

  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.

  [ Test Plan ]

   * Steps to make sure it works:

  1. pick a cutting edge nvidia graphic.
  2. remove nv-525 from the pool by removing restricted in jammy-updates and 
jammy-security
  3. check the nv support status:
  ```
  $ ubuntu-drivers list
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta
  ```
  4. modify custom file
  ```
  $ cat /etc/custom_supported_gpus.json
  {
    "chips": [
  {
    "devid": "0x24BA",
    "name": "TEST 24BA",
    "branch": "580.1234",
    "features": [
  "runtimepm"
    ]
  },
  {
    "devid": "0x25BC",
    "name": "TEST 25BC",
    "branch": "510",
    "features": [
  "runtimepm"
    ]
  }
    ]
  }
  ```
  5. make sure the hook works
  ```
  $ ubuntu-drivers list
  nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta

  [ Where problems could occur ]

   * This feature only impact target system has a custom file
  "/etc/custom_supported_gpus.json". And it won't generate automatically
  which should not impact normal users

  [ Other Info ]

   * the patches are picked from
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
   * Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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: b43 driver conflicts with bcmwl driver for some Broadcom devices

2023-09-30 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-drivers-common - 1:0.9.7.6

---
ubuntu-drivers-common (1:0.9.7.6) mantic; urgency=medium

  [ Dimitri John Ledkov ]
  * Add broadcom-sta-dkms to allowlist. (LP: #2013236)
In Lunar it was identified that both bcmwl and broadcom-sta-dkms are
identical and maintained in the archive twice. They were merged,
taking the Debian name as the new default one. However, allowlist was
forgotten to be updated in ubuntu-drivers to actually offer default
install of broadcom-sta-dkms.

 -- Alberto Milone   Fri, 29 Sep 2023
15:19:31 +

** Changed in: ubuntu-drivers-common (Ubuntu Mantic)
   Status: Triaged => Fix Released

-- 
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:
  b43 driver conflicts with bcmwl driver for some Broadcom devices

Status in broadcom-sta package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Lunar:
  New
Status in linux-firmware source package in Lunar:
  Invalid
Status in ubuntu-drivers-common source package in Lunar:
  Incomplete
Status in broadcom-sta source package in Mantic:
  New
Status in linux-firmware source package in Mantic:
  Invalid
Status in ubuntu-drivers-common source package in Mantic:
  Fix Released

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

  Workaround
  --
  You'll first need to blacklist the b43 driver by adding a blacklist file to 
/etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run 
"update-initramfs -u". Then install the bcmwl-kernel-source package. After a 
reboot your wireless device should be available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+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 2037642] Re: [FFe] Raspberry Pi 5 support

2023-09-30 Thread Dimitri John Ledkov

I cannot tell if
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1923363 has FFe
or not for the uaccess addition on udev rules.

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

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

Title:
  [FFe] Raspberry Pi 5 support

Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Triaged
Status in linux-raspi package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Committed
Status in pipewire package in Ubuntu:
  Triaged
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Triaged

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers

2023-09-30 Thread Jack Howarth

So I assume the blank windows in the Help application under X11 using
the nvidia drivers on Mantic would be resolved if the yelp package were
rebuilt with...

debian/control.in: Bump Standards-Version to 4.6.2

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

Title:
  Unable to setup Google Online Accounts with Nvidia drivers

Status in Webkit:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in webkit2gtk package in Ubuntu:
  Incomplete
Status in webkit2gtk package in Debian:
  Confirmed

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2

[Desktop-packages] [Bug 2037767] ThreadStacktrace.txt

2023-09-30 Thread Apport retracing service

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

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

** Changed in: file-roller (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- file-roller crashed with SIGSEGV in ???()
+ file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event()

** Tags removed: need-amd64-retrace

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

Title:
  file-roller crashed with SIGSEGV in
  egg_tree_multi_drag_button_release_event()

Status in file-roller package in Ubuntu:
  New

Bug description:
  Archive Manager (file-roller) often crashes when I open Qt source
  archives. I usually build (most of) Qt modules myself from the source
  archive "qt-everywhere-src-X.Y.Z.tar.xz". When I open the archive to
  select the directories I wish to extract, Archive Manager often
  crashes so I have to try again some times to succeed. Steps to
  reproduce the issue: 1) Download the file
  https://download.qt.io/official_releases/qt/6.5/6.5.3/single/qt-
  everywhere-src-6.5.3.tar.xz, 2) Open it with Archive Manager, 3)
  Browse the directories. The application will eventually crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: file-roller 43.0-1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 19:13:52 2023
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2023-05-16 (136 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230516)
  ProcCmdline: /usr/bin/file-roller 
/home/username/Downloads/qt-everywhere-src-6.5.3.tar.xz
  SegvAnalysis:
   Segfault happened at: 0x563107aa36c0:mov(%rbx),%rsi
   PC (0x563107aa36c0) ok
   source "(%rbx)" (0x20006) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: file-roller
  StacktraceTop:
   ??? ()
   ??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: file-roller crashed with SIGSEGV in ???()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users vboxusers 
wireshark
  separator:

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

2023-09-30 Thread Apport retracing service

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

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

Title:
  file-roller crashed with SIGSEGV in
  egg_tree_multi_drag_button_release_event()

Status in file-roller package in Ubuntu:
  New

Bug description:
  Archive Manager (file-roller) often crashes when I open Qt source
  archives. I usually build (most of) Qt modules myself from the source
  archive "qt-everywhere-src-X.Y.Z.tar.xz". When I open the archive to
  select the directories I wish to extract, Archive Manager often
  crashes so I have to try again some times to succeed. Steps to
  reproduce the issue: 1) Download the file
  https://download.qt.io/official_releases/qt/6.5/6.5.3/single/qt-
  everywhere-src-6.5.3.tar.xz, 2) Open it with Archive Manager, 3)
  Browse the directories. The application will eventually crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: file-roller 43.0-1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 19:13:52 2023
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2023-05-16 (136 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230516)
  ProcCmdline: /usr/bin/file-roller 
/home/username/Downloads/qt-everywhere-src-6.5.3.tar.xz
  SegvAnalysis:
   Segfault happened at: 0x563107aa36c0:mov(%rbx),%rsi
   PC (0x563107aa36c0) ok
   source "(%rbx)" (0x20006) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: file-roller
  StacktraceTop:
   ??? ()
   ??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: file-roller crashed with SIGSEGV in ???()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users vboxusers 
wireshark
  separator:

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

2023-09-30 Thread Apport retracing service

** Attachment added: "StacktraceTop.txt"
   
https://bugs.launchpad.net/bugs/2037767/+attachment/5705460/+files/StacktraceTop.txt

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

Title:
  file-roller crashed with SIGSEGV in
  egg_tree_multi_drag_button_release_event()

Status in file-roller package in Ubuntu:
  New

Bug description:
  Archive Manager (file-roller) often crashes when I open Qt source
  archives. I usually build (most of) Qt modules myself from the source
  archive "qt-everywhere-src-X.Y.Z.tar.xz". When I open the archive to
  select the directories I wish to extract, Archive Manager often
  crashes so I have to try again some times to succeed. Steps to
  reproduce the issue: 1) Download the file
  https://download.qt.io/official_releases/qt/6.5/6.5.3/single/qt-
  everywhere-src-6.5.3.tar.xz, 2) Open it with Archive Manager, 3)
  Browse the directories. The application will eventually crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: file-roller 43.0-1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 19:13:52 2023
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2023-05-16 (136 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230516)
  ProcCmdline: /usr/bin/file-roller 
/home/username/Downloads/qt-everywhere-src-6.5.3.tar.xz
  SegvAnalysis:
   Segfault happened at: 0x563107aa36c0:mov(%rbx),%rsi
   PC (0x563107aa36c0) ok
   source "(%rbx)" (0x20006) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: file-roller
  StacktraceTop:
   ??? ()
   ??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: file-roller crashed with SIGSEGV in ???()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users vboxusers 
wireshark
  separator:

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

2023-09-30 Thread Apport retracing service

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

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

Title:
  file-roller crashed with SIGSEGV in
  egg_tree_multi_drag_button_release_event()

Status in file-roller package in Ubuntu:
  New

Bug description:
  Archive Manager (file-roller) often crashes when I open Qt source
  archives. I usually build (most of) Qt modules myself from the source
  archive "qt-everywhere-src-X.Y.Z.tar.xz". When I open the archive to
  select the directories I wish to extract, Archive Manager often
  crashes so I have to try again some times to succeed. Steps to
  reproduce the issue: 1) Download the file
  https://download.qt.io/official_releases/qt/6.5/6.5.3/single/qt-
  everywhere-src-6.5.3.tar.xz, 2) Open it with Archive Manager, 3)
  Browse the directories. The application will eventually crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: file-roller 43.0-1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 19:13:52 2023
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2023-05-16 (136 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230516)
  ProcCmdline: /usr/bin/file-roller 
/home/username/Downloads/qt-everywhere-src-6.5.3.tar.xz
  SegvAnalysis:
   Segfault happened at: 0x563107aa36c0:mov(%rbx),%rsi
   PC (0x563107aa36c0) ok
   source "(%rbx)" (0x20006) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: file-roller
  StacktraceTop:
   ??? ()
   ??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: file-roller crashed with SIGSEGV in ???()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users vboxusers 
wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2037767/+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 2037767] [NEW] file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event()

2023-09-30 Thread Eric Carvalho

Public bug reported:

Archive Manager (file-roller) often crashes when I open Qt source
archives. I usually build (most of) Qt modules myself from the source
archive "qt-everywhere-src-X.Y.Z.tar.xz". When I open the archive to
select the directories I wish to extract, Archive Manager often crashes
so I have to try again some times to succeed. Steps to reproduce the
issue: 1) Download the file
https://download.qt.io/official_releases/qt/6.5/6.5.3/single/qt-
everywhere-src-6.5.3.tar.xz, 2) Open it with Archive Manager, 3) Browse
the directories. The application will eventually crash.

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: file-roller 43.0-1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 29 19:13:52 2023
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2023-05-16 (136 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230516)
ProcCmdline: /usr/bin/file-roller 
/home/username/Downloads/qt-everywhere-src-6.5.3.tar.xz
SegvAnalysis:
 Segfault happened at: 0x563107aa36c0:  mov(%rbx),%rsi
 PC (0x563107aa36c0) ok
 source "(%rbx)" (0x20006) not located in a known VMA region (needed 
readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ??? ()
 ??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: file-roller crashed with SIGSEGV in ???()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users vboxusers wireshark
separator:

** Affects: file-roller (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash mantic

** Information type changed from Private to Public

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

Title:
  file-roller crashed with SIGSEGV in
  egg_tree_multi_drag_button_release_event()

Status in file-roller package in Ubuntu:
  New

Bug description:
  Archive Manager (file-roller) often crashes when I open Qt source
  archives. I usually build (most of) Qt modules myself from the source
  archive "qt-everywhere-src-X.Y.Z.tar.xz". When I open the archive to
  select the directories I wish to extract, Archive Manager often
  crashes so I have to try again some times to succeed. Steps to
  reproduce the issue: 1) Download the file
  https://download.qt.io/official_releases/qt/6.5/6.5.3/single/qt-
  everywhere-src-6.5.3.tar.xz, 2) Open it with Archive Manager, 3)
  Browse the directories. The application will eventually crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: file-roller 43.0-1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 19:13:52 2023
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2023-05-16 (136 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230516)
  ProcCmdline: /usr/bin/file-roller 
/home/username/Downloads/qt-everywhere-src-6.5.3.tar.xz
  SegvAnalysis:
   Segfault happened at: 0x563107aa36c0:mov(%rbx),%rsi
   PC (0x563107aa36c0) ok
   source "(%rbx)" (0x20006) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: file-roller
  StacktraceTop:
   ??? ()
   ??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: file-roller crashed with SIGSEGV in ???()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users vboxusers 
wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2037767/+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 1799262] Re: OpenVPN doesn't respect dns servers in settings

2023-09-30 Thread -

Same issue on Ubuntu 23.04, as described by
https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/1799262/comments/9

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

Title:
  OpenVPN doesn't respect dns servers in settings

Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  Hello! After upgrading to Ubuntu 18.10 OpenVPN doesn't respect dns
  servers in settings. It trying to resolve internal host with default
  DNS server except resolving with dns servers from connection settings.
  On Ubuntu 18.04 all works fine

  1) 18.10
  2) 1.8.6-1ubuntu1
  3) OpenVPN uses DNS servers for resolving from connection settings
  4) Resolving used by default DNS server

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager-openvpn 1.8.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 19:46:17 2018
  InstallationDate: Installed on 2018-09-24 (28 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1799262/+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 2037766] [NEW] firefox snap crashes when playing video REGRESSION

2023-09-30 Thread StevenT

Public bug reported:

Newest snap version of Firefox instantly crashes when attempting to play
a video with the setting, "Use hardware acceleration when available" is
enabled. Disabling the hardware acceleration setting allows videos to
play albeit with occasional stuttering and high CPU utilization.

Older version of snap Firefox with identical settings and hardware
acceleration enabled played videos well.

System:
  Host: neons Kernel: 6.2.0-33-generic arch: x86_64 bits: 64 compiler: N/A
  Desktop: GNOME v: 42.9 Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
CPU:
  Info: dual core AMD Athlon II X2 245 [MCP] arch: K10 speed (MHz): avg: 800
min/max: 800/2900
Graphics:
  Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: VISIONTEK
driver: radeon v: kernel arch: TeraScale-2 bus-ID: 01:00.0 temp: 60.0 C
  Display: x11 server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.1 driver: X:
loaded: radeon unloaded: fbdev,modesetting,vesa dri: r600 gpu: radeon
resolution: 1600x900~60Hz
  API: OpenGL v: 4.5 Mesa 23.0.4-0ubuntu1~22.04.1 renderer: AMD CEDAR (DRM
2.50.0 / 6.2.0-33-generic LLVM 15.0.7) direct-render: Yes

$ snap list firefox --all
Name VersionRev   Tracking   Publisher  Notes
firefox  118.0.1-1  3206  latest/stable  mozilla✓   -
firefox  116.0.3-2  3026  latest/stable  mozilla✓   disabled

When started from the command-line, the 118.0.1-1 version spams the
following output when playing a video before crashing:

EE ../src/gallium/drivers/r600/r600_shader.c:193 r600_pipe_shader_create - 
translation from TGSI failed !
EE ../src/gallium/drivers/r600/r600_state_common.c:961 r600_shader_select - 
Failed to build shader variant (type=1) -1

This goes on for several lines until it gets here:

libva info: VA-API version 1.19.0
libva info: Trying to open 
/snap/firefox/3206/gnome-platform/usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so

Then it spams a few more shader lines and then gets here:

libva info: va_openDriver() returns 0
ATTENTION: default value of option mesa_glthread overridden by environment.
out of memory: 0x000773594008 bytes requested
ExceptionHandler::GenerateDump cloned child 8049
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.

At which point the Firefox window disappears and the Firefox crash
handler pop up.

Terminal output from 116.0.3-2 when playing same video

[Parent 8438, Main Thread] WARNING: OnCloseSessionDone error: Timeout
was reached: 'glib warning', file
/build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167

** (firefox:8438): WARNING **: 16:29:24.338: OnCloseSessionDone error: Timeout 
was reached
libva info: VA-API version 1.7.0
libva info: Trying to open 
/snap/firefox/3026/gnome-platform/usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_1_7
ATTENTION: default value of option mesa_glthread overridden by environment.
libva info: va_openDriver() returns 0
ATTENTION: default value of option mesa_glthread overridden by environment.

The same latest release of Firefox downloaded directly from mozilla.org
does not have this problem and works as expected with no issues.

Chromium snap is also installed and up-to-date, but does not crash with
hardware acceleration enabled and plays videos as expected.

Expectations:
1. New version of Firefox snap should have at least the same performance 
profile as an older version, or the same version of the non-snap release
2. Even if a hardware acceleration setting is not attainable because of the 
limitation of said hardware, the program should gracefully downgrade to 
software rendering and not crash.

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


** Tags: core22 crash firefox gnome-42-2204 mesa snap

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

Title:
  firefox snap crashes when playing video REGRESSION

Status in firefox package in Ubuntu:
  New

Bug description:
  Newest snap version of Firefox instantly crashes when attempting to
  play a video with the setting, "Use hardware acceleration when
  available" is enabled. Disabling the hardware acceleration setting
  allows videos to play albeit with occasional stuttering and high CPU
  utilization.

  Older version of snap Firefox with identical settings and hardware
  acceleration enabled played videos well.

  System:
Host: neons Kernel: 6.2.0-33-generic arch: x86_64 bits: 64 compiler: N/A
Desktop: GNOME v: 42.9 Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
  CPU:
Info: dual core AMD Athlon II X2 245 [MCP] arch: K10 speed (MHz): avg: 800
  min/max: 800/2900
  Graphics:
Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor:

[Desktop-packages] [Bug 2037569] Re: udev issues with mantic beta

2023-09-30 Thread Dan Bungert

after exploring udisks2/libblockdev/libfdisk, I have three possible proposals 
for resolution:
 
1. hack udisks2 udisks_linux_partition_table_update
  * calling bd_part_get_disk_spec is always going to be a loop, unless
* watches have been inhibited
* or calling bd_part_get_disk_spec causes
  ID_PART_TABLE_TYPE to be set
  * disable everything under `if (!part_type && num_parts > 0)`, log
and bail
2. add read-only API in libblockdev so we open the dev RO in libfdisk
3. add vtoc support to libfdisk + enable the s390 bits in libblockdev

only option 1 sounds plausible to me, though, for a Mantic timeframe.

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

Title:
  udev issues with mantic beta

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in libblockdev package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  While installing mantic beta (on s390x, LPAR and z/VM - but this might not be 
architecture specific) I faced issues with udev.
  In my installation I've updated the installer to "edge/lp-2009141" (subiquity 
 22.02.2+git1762.1b1ee6f4  5164).

  During my installations I first noticed bad response times in case of
  dealing with devices (like enabling new devices with chzdev). chzdev
  is used during the installation, hence the installation procedure is
  also affected by this. (I mainly notice this issue in case of DASD
  ECKD disk enablements.)

  But even after after a successful (but due to this issue less snappier) 
installation, means after the post-install reboot, in the installed system I 
can find several udev related processes, like:
69448 root  20   0   31280  11944   2560 S  39.2   0.0   2:51.67 
(udev-worker)
  509 root  20   0   31276  13812   4600 S  20.6   0.0   2:07.76 
systemd-udevd
  893 root  20   0  469016  13544  10496 R  17.3   0.0   1:43.53 
udisksd  
1 root  20   0  168664  12748   8396 S  16.3   0.0   1:40.47 
systemd  
  which is not only unusual, but (as one can see) they consume quite some 
resources.
  Even the remote ssh into that system is impacted by this high load.

  So far I only see this in mantic.
  I tried 20.04.3 as well as lunar, but both do not seem to be affected by this 
udev problem.
  I neither face the bad response on device enablement, nor can see any udev 
related processes still running after post-install-reboot in the installed 
system.

  (Sometimes I could also see a growing log file 'syslog').

  I cannot say yet what is causing this, but since I see 'systemd-udevd'
  as prominent process in top, I'll first of all mark this as affecting
  systemd-udevd (or systemd).

  I've attached the outcome of some more investigations I did ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+subscriptions


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

[Desktop-packages] [Bug 1958019]

[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support

[Desktop-packages] [Bug 2037795] Re: gnome-shell crashed with SIGSEGV in clutter_stage_process_event()

[Desktop-packages] [Bug 2037794] [NEW] [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound at all

[Desktop-packages] [Bug 2037503] Re: [jammy]backport #1453 from upstream

[Desktop-packages] [Bug 2037766] Re: firefox snap crashes when playing video REGRESSION

[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers

[Desktop-packages] [Bug 2037228] Re: Firefox doesn't work after 23.10 upgrade

[Desktop-packages] [Bug 2037773] Re: Rebuild against latest webkit2gtk

[Desktop-packages] [Bug 2037773] Re: Rebuild against latest webkit2gtk

[Desktop-packages] [Bug 2037773] Re: Rebuild against latest webkit2gtk

[Desktop-packages] [Bug 2037773] Re: Rebuild against latest webkit2gtk

[Desktop-packages] [Bug 2037773] Re: Rebuild against latest webkit2gtk

[Desktop-packages] [Bug 2037773] Re: Rebuild against latest webkit2gtk

[Desktop-packages] [Bug 2037696] Re: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common

[Desktop-packages] [Bug 1923363] Re: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support

[Desktop-packages] [Bug 2037773] Re: Rebuild against latest webkit2gtk

[Desktop-packages] [Bug 2003283] Re: Ubuntu22.04 Remote Desktop doesn't support to display the screen of the second monitor

[Desktop-packages] [Bug 2037773] [NEW] Rebuild against latest webkit2gtk

[Desktop-packages] [Bug 2003283] Re: Ubuntu22.04 Remote Desktop doesn't support to display the screen of the second monitor

[Desktop-packages] [Bug 1923363] Re: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

[Desktop-packages] [Bug 1923363] Re: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

[Desktop-packages] [Bug 1990341] Autopkgtest regression report (ubuntu-drivers-common/1:0.9.7.1.2)

[Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices

[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support

[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers

[Desktop-packages] [Bug 2037767] ThreadStacktrace.txt

[Desktop-packages] [Bug 2037767] StacktraceSource.txt

[Desktop-packages] [Bug 2037767] StacktraceTop.txt

[Desktop-packages] [Bug 2037767] Stacktrace.txt

[Desktop-packages] [Bug 2037767] [NEW] file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event()

[Desktop-packages] [Bug 1799262] Re: OpenVPN doesn't respect dns servers in settings

[Desktop-packages] [Bug 2037766] [NEW] firefox snap crashes when playing video REGRESSION

[Desktop-packages] [Bug 2037569] Re: udev issues with mantic beta

35 matches

Site Navigation

Mail list logo

Footer information