[Desktop-packages] [Bug 2049504] Re: Loading application details window hanged in Ubuntu Software app

2024-01-19 Thread Zahar Lenok
Ubuntu 20

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

Title:
  Loading application details window hanged in Ubuntu Software app

Status in gnome-software package in Ubuntu:
  New

Bug description:
  see attached screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2049504/+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 1961508] Re: Dock displaying over window after resuming from blank screen

2024-01-19 Thread ExploreWiki
I reported this issue back on the 2022-02-20. I can't believe it is
still happening. I have also gotten used to re-maxing the windows!

If there is anything we can do to fix this bug, please just let us know!

Currently this bug affects 82 other people, and that's only the people
who have a launchpad account...

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

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-desktop package in Fedora:
  Confirmed

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-02-18 (328 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: wayland-session third-party-packages kinetic
  Uname: Linux 5.19.0-28-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+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 2040108] Re: error "contains an invalid sample specification."

2024-01-19 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  error "contains an invalid sample specification."

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  After upgrade network audio stop working.
  On the client side in log i see:
  "CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series' contains an invalid 
sample specification."
  Microphone sink work, but playback not. I tried as client ubuntu 23.04 and 
23.10, so I suppose issue in zeroconf-publish
  Just specifying env PULSE_SERVER play sound fine.

  Also will be great if zeroconf-publish can filter what to export, at
  least disable microphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio-module-zeroconf 1:16.1+dfsg1-2ubuntu4
  Uname: Linux 6.2.16-060216-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vova   1822 F wireplumber
   /dev/snd/controlC2:  vova   1822 F wireplumber
   /dev/snd/controlC1:  vova   1822 F wireplumber
   /dev/snd/seq:vova   1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Oct 22 17:04:30 2023
  InstallationDate: Installed on 2023-04-01 (204 days ago)
  InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230401)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to mantic on 2023-10-15 (7 days ago)
  dmi.bios.date: 08/09/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: FEb
  dmi.board.asset.tag: Default string
  dmi.board.name: B550 AORUS ELITE V2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFEb:bd08/09/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSELITEV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSELITEV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B550 MB
  dmi.product.name: B550 AORUS ELITE V2
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2040108/+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 2042972] Re: Apps take minutes to launch

2024-01-19 Thread Launchpad Bug Tracker
[Expired for xdg-desktop-portal (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xdg-desktop-portal (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Apps take minutes to launch

Status in xdg-desktop-portal package in Ubuntu:
  Expired

Bug description:
  After booting, sometimes I am not able to quickly open apps, it takes
  more than 5 mins to launch and in most of them dark mode is not shown.
  It used to come back to normal but now it stays the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 00:11:58 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TigerLake-H GT1 [UHD Graphics] [1043:13fc]
   NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GA107M [GeForce RTX 3050 Mobile] 
[1043:13fc]
  InstallationDate: Installed on 2023-10-29 (9 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=5188fb64-a6dc-4300-a704-0666d8ca03ba ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2023
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: FX506HCB.313
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX506HCB
  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.ec.firmware.release: 3.11
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX506HCB.313:bd03/03/2023:br5.19:efr3.11:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506HCB_FX506HCB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506HCB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS TUF Gaming F15
  dmi.product.name: ASUS TUF Gaming F15 FX506HCB_FX506HCB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/2042972/+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 2049960] [NEW] polkitd.postinst script refers to non-existent /usr/libexec/polkitd

2024-01-19 Thread Daniel Richard G.
Public bug reported:

I am seeing this on Ubuntu noble with polkitd 123-3.

After debootstrap'ing a minimal system, I run

# apt-get install linux-generic

which pulls in polkitd as a dependency. In the output, I see the
following:

Setting up polkitd (123-3) ...
Creating group 'polkitd' with GID 994.
Creating user 'polkitd' (polkit) with UID 994 and GID 994.
Running in chroot, ignoring request.
 * Reloading system message bus config...   
Failed to open connection to "system" message bus: Failed to connect to 
socket /run/dbus/system_bus_socket: No such file or directory
invoke-rc.d: initscript dbus, action "reload" failed.
start-stop-daemon: unable to stat /usr/libexec/polkitd (No such file or 
directory)

There is indeed no file there:

# ls -l /usr/libexec/polkitd
ls: cannot access '/usr/libexec/polkitd': No such file or directory

The binary appears to be installed at /usr/lib/polkit-1/polkitd .

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  polkitd.postinst script refers to non-existent /usr/libexec/polkitd

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  I am seeing this on Ubuntu noble with polkitd 123-3.

  After debootstrap'ing a minimal system, I run

  # apt-get install linux-generic

  which pulls in polkitd as a dependency. In the output, I see the
  following:

  Setting up polkitd (123-3) ...
  Creating group 'polkitd' with GID 994.
  Creating user 'polkitd' (polkit) with UID 994 and GID 994.
  Running in chroot, ignoring request.
   * Reloading system message bus config... 
  Failed to open connection to "system" message bus: Failed to connect to 
socket /run/dbus/system_bus_socket: No such file or directory
  invoke-rc.d: initscript dbus, action "reload" failed.
  start-stop-daemon: unable to stat /usr/libexec/polkitd (No such file or 
directory)

  There is indeed no file there:

  # ls -l /usr/libexec/polkitd
  ls: cannot access '/usr/libexec/polkitd': No such file or directory

  The binary appears to be installed at /usr/lib/polkit-1/polkitd .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2049960/+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 1988754] Re: libreoffice writer crashes when edit the page break

2024-01-19 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Confirmed => In Progress

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

Title:
  libreoffice writer crashes when edit the page break

Status in LibreOffice:
  In Progress
Status in libreoffice package in Ubuntu:
  New

Bug description:
  LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 
22.04.1 and also in LinuxMint 21.
  I have tried also using LibreOffice from ppa and it still crashes.

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

2024-01-19 Thread Mattkse
Fix posted at: https://gerrit.libreoffice.org/c/core/+/162317

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

Title:
  libreoffice writer crashes when edit the page break

Status in LibreOffice:
  In Progress
Status in libreoffice package in Ubuntu:
  New

Bug description:
  LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 
22.04.1 and also in LinuxMint 21.
  I have tried also using LibreOffice from ppa and it still crashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1988754/+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 2047737] Re: Nautilus crashes when opening folders that contain files with js or json extensions

2024-01-19 Thread airtonix
This isn't specific to ubuntu btw. it happens on Fedora 38 too.

so far i've found that any `.json` or `.js` file will cause any instance
of the gnome filebrowser (nautilus, a file picker modal, etc) to crash
itself and any app that uses it.

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

Title:
  Nautilus crashes when opening folders that contain files with js or
  json extensions

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  After attempting to open a folder that contains js or json files the app 
crashes.
  when testing from terminal I get a segmentation fault and no other error info.
  even enabling G_MESSAGES_DEBUG=all did not provide additional info.
  removing nautilus extensions, resetting xdg-mime for js/json, and disabling 
nautilus features (search, file count, etc ...) did not fix the problem either.

  additional info
  $ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:42.6-0ubuntu1
Candidate: 1:42.6-0ubuntu1
Version table:
   *** 1:42.6-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:42.2-0ubuntu2.1 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:42.0-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.6-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 30 14:50:09 2023
  InstallationDate: Installed on 2023-02-14 (319 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.3-0ubuntu3.1
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2047737/+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 2048931] Re: [noble] extension pref dialog turns hidden

2024-01-19 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: New => Fix Released

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

Title:
  [noble] extension pref dialog turns hidden

Status in gjs:
  Fix Released
Status in GNOME Shell:
  Fix Released
Status in gjs package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I get this after:
  1) open Extensions app
  2) open a pref
  3) prefs window after a quarter of second gets hidden
  4) no way to access this window

  JS ERROR: Gio.IOErrorEnum: GDBus.Error:org.gnome.gjs.JSError.Error: Already 
showing a prefs dialog
  asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
  
_init/GLib.MainLoop.prototype.runAsync/https://bugs.launchpad.net/gjs/+bug/2048931/+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 2049958] [NEW] package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/bluetooth/obexd' before installing new version: Input/outpu

2024-01-19 Thread phillip bolton-frank
Public bug reported:

bug found during software update launched from bootable usb

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bluez-obexd 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckMismatches: ./casper/minimal.squashfs
CasperMD5CheckResult: fail
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
Date: Sat Jan 20 00:18:32 2024
DuplicateSignature:
 package:bluez-obexd:5.68-0ubuntu1
 Unpacking bluez-obexd (5.68-0ubuntu1.1) over (5.68-0ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-MsVzUs/045-bluez-obexd_5.68-0ubuntu1.1_amd64.deb 
(--unpack):
  unable to make backup link of './usr/lib/bluetooth/obexd' before installing 
new version: Input/output error
ErrorMessage: unable to make backup link of './usr/lib/bluetooth/obexd' before 
installing new version: Input/output error
InterestingModules: rfcomm bnep btusb bluetooth
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.22.0ubuntu1
 apt  2.7.3
SourcePackage: bluez
Title: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to 
make backup link of './usr/lib/bluetooth/obexd' before installing new version: 
Input/output error
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2018
dmi.bios.release: 5.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 306
dmi.board.asset.tag: Default string
dmi.board.name: GL553VW
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:bvnAmericanMegatrendsInc.:bvr306:bd09/26/2018:br5.6:svnASUSTeKCOMPUTERINC.:pnGL553VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
dmi.product.family: GL
dmi.product.name: GL553VW
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: D0:57:7B:12:13:2F  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:1345 acl:0 sco:0 events:90 errors:0
TX bytes:3835 acl:0 sco:0 commands:90 errors:0

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


** Tags: amd64 apport-package mantic need-duplicate-check

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

Title:
  package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to
  make backup link of './usr/lib/bluetooth/obexd' before installing new
  version: Input/output error

Status in bluez package in Ubuntu:
  New

Bug description:
  bug found during software update launched from bootable usb

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: bluez-obexd 5.68-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckMismatches: ./casper/minimal.squashfs
  CasperMD5CheckResult: fail
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  Date: Sat Jan 20 00:18:32 2024
  DuplicateSignature:
   package:bluez-obexd:5.68-0ubuntu1
   Unpacking bluez-obexd (5.68-0ubuntu1.1) over (5.68-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-MsVzUs/045-bluez-obexd_5.68-0ubuntu1.1_amd64.deb 
(--unpack):
unable to make backup link of './usr/lib/bluetooth/obexd' before installing 
new version: Input/output error
  ErrorMessage: unable to make backup link of './usr/lib/bluetooth/obexd' 
before installing new version: Input/output error
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: bluez
  Title: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to 

[Desktop-packages] [Bug 1953210] Re: package libvdpau1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of packag

2024-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package libvdpau1 (not installed) failed to install/upgrade: trying to
  overwrite shared '/etc/vdpau_wrapper.cfg', which is different from
  other instances of package libvdpau1:amd64

Status in libvdpau package in Ubuntu:
  Confirmed

Bug description:
  not a programmer

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libvdpau1 (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Fri Dec  3 22:36:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DuplicateSignature:
   package:libvdpau1:(not installed)
   Unpacking libvdpau1:amd64 (1.3-1ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-CYOEuz/155-libvdpau1_1.3-1ubuntu2_amd64.deb (--unpack):
trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different 
from other instances of package libvdpau1:amd64
  ErrorMessage: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is 
different from other instances of package libvdpau1:amd64
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GK104 [GeForce GTX 770] [1458:3603]
  InstallationDate: Installed on 2021-09-25 (69 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic 
root=UUID=4e954e5c-691e-4c0b-a835-8de78a6f578d ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: libvdpau
  Title: package libvdpau1 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other 
instances of package libvdpau1:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd06/05/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:skuAll:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIHERO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1953210/+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 1952536] Re: package libvdpau1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of packag

2024-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package libvdpau1 (not installed) failed to install/upgrade: trying to
  overwrite shared '/etc/vdpau_wrapper.cfg', which is different from
  other instances of package libvdpau1:amd64

Status in libvdpau package in Ubuntu:
  Confirmed

Bug description:
  sudo apt-get -f install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
libvdpau1 mesa-vdpau-drivers mesa-vdpau-drivers:i386
  The following NEW packages will be installed:
libvdpau1
  The following packages will be upgraded:
mesa-vdpau-drivers mesa-vdpau-drivers:i386
  2 upgraded, 1 newly installed, 0 to remove and 83 not upgraded.
  262 not fully installed or removed.
  Need to get 6,161 kB of archives.
  After this operation, 92.2 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://in.archive.ubuntu.com/ubuntu focal/main amd64 libvdpau1 amd64 
1.3-1ubuntu2 [25.6 kB]
  Get:2 http://in.archive.ubuntu.com/ubuntu focal-updates/main amd64 
mesa-vdpau-drivers amd64 21.0.3-0ubuntu0.3~20.04.4 [2,946 kB]
  Get:3 http://in.archive.ubuntu.com/ubuntu focal-updates/main i386 
mesa-vdpau-drivers i386 21.0.3-0ubuntu0.3~20.04.4 [3,189 kB]
  Fetched 6,161 kB in 17s (354 kB/s)
 
  (Reading database ... 202522 files and directories currently installed.)
  Preparing to unpack .../libvdpau1_1.3-1ubuntu2_amd64.deb ...
  Unpacking libvdpau1:amd64 (1.3-1ubuntu2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libvdpau1_1.3-1ubuntu2_amd64.deb (--unpack):
   trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from 
other instances of package libvdpau1:amd64
  Preparing to unpack .../mesa-vdpau-drivers_21.0.3-0ubuntu0.3~20.04.4_i386.deb 
...
  Unpacking mesa-vdpau-drivers:i386 (21.0.3-0ubuntu0.3~20.04.4) over 
(21.0.3-0ubuntu0.3~20.04.3) ...
  Preparing to unpack 
.../mesa-vdpau-drivers_21.0.3-0ubuntu0.3~20.04.4_amd64.deb ...
  Unpacking mesa-vdpau-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.4) over 
(21.0.3-0ubuntu0.3~20.04.3) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libvdpau1_1.3-1ubuntu2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  souti@souti-roy:~$ 


  this is what I am geting

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libvdpau1 (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  AptOrdering:
   libvdpau1:amd64: Install
   mesa-vdpau-drivers:i386: Install
   mesa-vdpau-drivers:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Nov 28 03:40:39 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgTerminalLog:
   Preparing to unpack .../libvdpau1_1.3-1ubuntu2_amd64.deb ...
   Unpacking libvdpau1:amd64 (1.3-1ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libvdpau1_1.3-1ubuntu2_amd64.deb (--unpack):
trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different 
from other instances of package libvdpau1:amd64
  DuplicateSignature:
   package:libvdpau1:(not installed)
   Unpacking libvdpau1:amd64 (1.3-1ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libvdpau1_1.3-1ubuntu2_amd64.deb (--unpack):
trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different 
from other instances of package libvdpau1:amd64
  ErrorMessage: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is 
different from other instances of package libvdpau1:amd64
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1840]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon HD 7670M [103c:1840]
  InstallationDate: Installed on 2021-11-10 (17 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic 
root=UUID=751fb0a9-8974-4aa0-9790-7c9ccb9e30a5 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: 

[Desktop-packages] [Bug 2017881] Re: package Wine-stabel (not installed) failed to install/upgrade: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of pack

2024-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package Wine-stabel (not installed) failed to install/upgrade: trying
  to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from
  other instances of package libvdpau1:amd64

Status in libvdpau package in Ubuntu:
  Confirmed

Bug description:
  Preparing to unpack .../271-libosmesa6_21.2.6-0ubuntu0.1~20.04.2_amd64.deb ...
  Unpacking libosmesa6:amd64 (21.2.6-0ubuntu0.1~20.04.2) ...
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-2rmjbX/158-libvdpau1_1.3-1ubuntu2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libvdpau1 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-71.78~20.04.1-generic 5.15.92
  Uname: Linux 5.15.0-71-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Thu Apr 27 11:57:41 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ErrorMessage: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is 
different from other instances of package libvdpau1:amd64
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] 
[1025:1191]
  InstallationDate: Installed on 2022-09-08 (230 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0408:a031 Quanta Computer, Inc. VGA WebCam
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A315-51
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-71-generic 
root=UUID=c0cb241c-4819-491c-a922-b8c009cd21fe ro quiet splash vt.handoff=7
  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: libvdpau
  Title: package libvdpau1 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other 
instances of package libvdpau1:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2017
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Venusaur_KL
  dmi.board.vendor: SKL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd10/16/2017:br0.0:efr1.1:svnAcer:pnAspireA315-51:pvrV1.06:rvnSKL:rnVenusaur_KL:rvrV1.06:cvnChassisManufacturer:ct10:cvrChassisVersion:sku:
  dmi.product.family: Aspire 3
  dmi.product.name: Aspire A315-51
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

2024-01-19 Thread Sebastien Bacher
The version in Noble includes the fix but we should SRU the stable
update to mantic

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Fix Released

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

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

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

Bug description:
  Random crash while moving between elements in control panel sidebar.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 14:35:50 2023
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2023-07-15 (47 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230712.1)
  JournalErrors:
   Aug 31 14:35:50 hostname gnome-control-c[3007]: Finalizing 
AdwPreferencesPage 0x5613c09ca1e0, but it still has children left:
  - GtkCenterBox 
0x5613c160b4a0
   Aug 31 14:35:50 hostname gnome-control-c[3007]: failed to get enum property 
'auth-mode'
   Aug 31 14:35:50 hostname gnome-control-c[3007]: Failed fetch permissions 
from flatpak permission store: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for location
   Aug 31 14:35:50 hostname gnome-control-c[3007]: Failed fetch permissions 
from flatpak permission store: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
  ProcCmdline: /usr/bin/gnome-control-center
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f2b46ca45a2 :lock 
xadd %eax,(%rdi)
   PC (0x7f2b46ca45a2) ok
   source "%eax" ok
   destination "(%rdi)" (0x5612c2a70918) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_atomic_ref_count_dec () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_atomic_ref_count_dec()
  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-control-center/+bug/2033656/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

2024-01-19 Thread Steve Langasek
All older source packages listed in this bug report have been removed,
and yet:

$ reverse-depends src:nvidia-graphics-drivers-460
Reverse-Depends
===
* libnvidia-decode-455  (for libnvidia-decode-460)
* libnvidia-encode-455  (for libnvidia-encode-460)
* nvidia-headless-455 [amd64]   (for nvidia-headless-460)
* nvidia-kernel-common-455 [amd64]

Packages without architectures listed are reverse-dependencies in: amd64, i386
$

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

2024-01-19 Thread Steve Langasek
Same for 515-server:

$ reverse-depends src:nvidia-graphics-drivers-515-server
Reverse-Depends
===
* libnvidia-decode-510-server   (for libnvidia-decode-515-server)
* libnvidia-encode-510-server   (for libnvidia-encode-515-server)

Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, i386
$

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2049923] Re: gnome-terminal freezing, then crashing

2024-01-19 Thread Egmont Koblinger
What do you mean by "split windows out from tabs"? Do you mean right-
clicking on the tab and choosing "Detach Terminal"?

Do I understand correctly that the freeze and crash always happens right
after opening a new window or detaching a tab? Does the new window
appear before the freeze or not?

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

Title:
  gnome-terminal freezing, then crashing

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  First: It's very hard to reproduce, but it happens to me about once per week.
  If often open new windows or split windows out from tabs. And then it 
happens. First it becomes unresponsive, and then after about 2-3 seconds it 
simply closes all instances.

  
  [328830.780749] gnome-terminal-[117706]: segfault at 460742 ip 
7fdb2fb45611 sp 7ffdb8c5fda0 error 4 in 
libgtk-3.so.0.2406.32[7fdb2f883000+38f000] likely on CPU 4 (core 4, socket 0)

  [328830.780761] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89
  44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85
  c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6
  48 89

  [329377.925310] gnome-terminal-[120116]: segfault at 2f0774 ip
  7f86af745611 sp 7ffc9943c5c0 error 4 in
  libgtk-3.so.0.2406.32[7f86af483000+38f000] likely on CPU 2 (core 2,
  socket 0)

  [329377.925324] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89
  44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85
  c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6
  48 89

  unfortunately, apport isn't automatically creating a crash report.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-terminal 3.49.92-2ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 16:48:43 2024
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to mantic on 2023-10-17 (94 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2049923/+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 2049907] Re: tracker-extract-3 crash with SIGSYS when upgrading from 22.04 to 24.04

2024-01-19 Thread Brian Murray
This is failing to retrace due to the fact that there are mixture of
packages from Noble and Jammy. It'd be interesting to look at the
timestamp of the crash versus where we were in the upgrade process but I
suspect it was somewhere in the middle.  Subsequently, I think we should
probably just turn off whatever runs tracker-extract while the upgrade
is in progress. (There is code in ubuntu-release-upgrader to do similar
things.)

Here's part of apport's output:

Get:1 http://192.168.10.7/ubuntu noble/main amd64 libgcc-s1 amd64 
13.2.0-9ubuntu1 [63.1 kB]
Get:2 http://192.168.10.7/ubuntu noble/main amd64 gvfs-libs amd64 1.52.2-1 [107 
kB]
Get:3 http://192.168.10.7/ubuntu noble/main amd64 gvfs amd64 1.52.2-1 [115 kB]
Get:4 http://ddebs.ubuntu.com noble/main amd64 gvfs-dbgsym amd64 1.52.2-1 [394 
kB]
Get:5 http://ddebs.ubuntu.com noble/main amd64 gvfs-libs-dbgsym amd64 1.52.2-1 
[403 kB]
Fetched 1082 kB in 0s (0 B/s)
Extracting downloaded debs...
E: Can not find version '3.3.3-0ubuntu0.20.04.1' of package 'tracker-miners'
E: Unable to find a source package for tracker-miners
dpkg-source: warning: -sn is not a valid option for 
Dpkg::Source::Package::V3::Quilt
gpgv: Signature made Fri 10 Nov 2023 12:08:46 AM PST
gpgv:using RSA key 50C4A0DDCF31E452CEB19B516569D855A744BE93
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify inline signature for 
/tmp/tmpl2x1cdty/tracker-miners_3.3.3-0ubuntu0.20.04.1.dsc: no acceptable 
signature found
--- stack trace ---
#0  0x7f4e079ca909 in ?? ()
No symbol table info available.
#1  0x0006 in ?? ()
No symbol table info available.
#2  0x in ?? ()
No symbol table info available.
--- source code stack trace ---
#0  0x7f4e079ca909 in ?? ()
#1  0x0006 in ?? ()
#2  0x in ?? ()


** Summary changed:

- tracker-extract-3 crash with SIGSYS when upgrading from 22.04 to 24.04
+ tracker-extract-3 crashes routinely during distribution upgrades

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

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

Title:
  tracker-extract-3 crashes routinely during distribution upgrades

Status in tracker-miners package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Very similar behavior as this existing bug:
  https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1983859

  Almost copy-paste of original report:

  When upgrading Ubuntu Desktop from 22.04 to 24.04, there's often
  (pretty much always) a crash from tracker-extract, as described in the
  following error report:

  https://errors.ubuntu.com/oops/7a86fbf0-b52b-11ee-b9e4-fa163e171f02

  The crash occurs during the upgrade, which means it's fairly hard to
  investigate exactly what's going on as apport fails to extract a stack
  trace, the binaries being overwritten during the upgrade.

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

2024-01-19 Thread Kumar KALIAPPAN
It seems the issue has been addressed by Gnome
(https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2647). Do
you know if Ubuntu plans to release an update for gnome-control-center?

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2647
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2647

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

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

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

Bug description:
  Random crash while moving between elements in control panel sidebar.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 14:35:50 2023
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2023-07-15 (47 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230712.1)
  JournalErrors:
   Aug 31 14:35:50 hostname gnome-control-c[3007]: Finalizing 
AdwPreferencesPage 0x5613c09ca1e0, but it still has children left:
  - GtkCenterBox 
0x5613c160b4a0
   Aug 31 14:35:50 hostname gnome-control-c[3007]: failed to get enum property 
'auth-mode'
   Aug 31 14:35:50 hostname gnome-control-c[3007]: Failed fetch permissions 
from flatpak permission store: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for location
   Aug 31 14:35:50 hostname gnome-control-c[3007]: Failed fetch permissions 
from flatpak permission store: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
  ProcCmdline: /usr/bin/gnome-control-center
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f2b46ca45a2 :lock 
xadd %eax,(%rdi)
   PC (0x7f2b46ca45a2) ok
   source "%eax" ok
   destination "(%rdi)" (0x5612c2a70918) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_atomic_ref_count_dec () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_atomic_ref_count_dec()
  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-control-center/+bug/2033656/+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 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble

2024-01-19 Thread Brian Murray
** Tags added: rls-nn-incoming

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

Title:
  Unable to contact snap store on Xubuntu from Jammy to Noble

Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  When running `do-release-upgrade -d` on Jammy Xubuntu, the upgrade
  fails consistently at the `Installing the firefox snap` step.

  This was first detected on Jenkins [1], then reproduced locally with
  `auto-upgrade-testing`, then finally by manually running a `do-
  release-upgrade -d` in a VM.

  [1]: https://platform-qa-jenkins.ps5.ubuntu.com/view/upgrade-
  list/job/upgrade_ubuntu-jammy-noble-xubuntu-amd64_qemu/7/consoleFull
  (Jenkins full log attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.17
  ProcVersionSignature: User Name 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Fri Nov 17 18:24:22 2023
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+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 2046633] Re: Don't include 'nmcli -f all con' output in bug report (for privacy)

2024-01-19 Thread Marc Deslauriers
** Information type changed from Public Security to Public

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

Title:
  Don't include 'nmcli -f all con' output in bug report (for privacy)

Status in network-manager package in Ubuntu:
  New

Bug description:
  The apport bug reporting hooks for this package
  (/usr/share/apport/package/hooks/source_network-manager{,-applet}.py)
  include the output of `nmcli -f all con`.  This lists all wifi SSIDs
  that the user has ever connected to, and the date of last connection.
  I think this is a privacy problem, as it tends to reveal the user's
  recent whereabouts, and it's posted publicly on launchpad.  (Imagine
  for instance an entry for "LoveMotelGuestWifi" at a time when the user
  had said they were at the office...)

  It is disclosed to the user before the report is sent, but only if
  they think to expand that item in the "Send / Don't send" dialog
  (which is not descriptively labeled), and there is no way to opt out
  of it.  You can delete it manually from launchpad afterward, which is
  what I am going to do with this bug report, but I doubt most people
  would know to do that.

  This info should probably not be included at all, or if it is, it
  should be sanitized.  Also, it might be a good idea to purge launchpad
  of all such files.

  (Marking this as "security" in case you consider this kind of a
  privacy leak to be something the security team should handle.  If not,
  feel free to demote it to an ordinary bug.)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Dec 16 14:38:45 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-03 (1657 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.1.13 dev enxa0cec8c4f782 proto dhcp src 192.168.1.60 
metric 100 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.1.0/24 dev enxa0cec8c4f782 proto kernel scope link src 192.168.1.60 
metric 100 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-12-14 (3 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-04T11:07:36.415303
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2046633/+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 2047595] Re: sound control panel security

2024-01-19 Thread Marc Deslauriers
** Package changed: ubuntu-meta (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  sound control panel security

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The controls in the upper right hand corner, which consist of WiFi Bar, Sound 
Bar, and Battery Bar icons are unlocked when the machine is locked. This will 
enable anyone, who has physical access to the machine to change, disable or 
rearrange any settings available in this interface; 
  1. WiFi-- add or remove access points, disconnect WiFi, change power modes, 
styles, keyboard, etc. Power Modes. 
  2. Sounds, disable or modify sounds, lighting settings 
  3. Change or modify battery schemes. Power off machines, or sleep / Hibernate 
machine, etc. 
   
  lsb_release -rd  Ubuntu 23.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2047595/+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 2047595] Re: sound control panel security

2024-01-19 Thread Marc Deslauriers
What desktop environment are you using?

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

Title:
  sound control panel security

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The controls in the upper right hand corner, which consist of WiFi Bar, Sound 
Bar, and Battery Bar icons are unlocked when the machine is locked. This will 
enable anyone, who has physical access to the machine to change, disable or 
rearrange any settings available in this interface; 
  1. WiFi-- add or remove access points, disconnect WiFi, change power modes, 
styles, keyboard, etc. Power Modes. 
  2. Sounds, disable or modify sounds, lighting settings 
  3. Change or modify battery schemes. Power off machines, or sleep / Hibernate 
machine, etc. 
   
  lsb_release -rd  Ubuntu 23.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2047595/+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 2024377] Re: Adsys can't fetch GPOs

2024-01-19 Thread Tony Galyan
Hi all, is there any update on the fix being backported to 22.04? I'm
also having this issue and am locked into 22.04.

Thanks!

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

Title:
  Adsys can't fetch GPOs

Status in adsys package in Ubuntu:
  Fix Released

Bug description:
  Bad, maybe no understandable english ahead.

  Can't find anything related to this on Github, Canonical Forums,
  Reddit or StackOverflow.

  On Ubuntu 22.04, I've followed the Wiki tutorial and verified all
  steps on Integration Ubuntu Desktop whitepaper. Currently using SSSD
  backend, I can log with Active Directory users however when adsys is
  installed I can't fetch GPOs. In this version the error is:

  ERROR Error from server: error while updating policy: can't get
  policies for "ubuntu": can't download all gpos and assets: one or more
  error while fetching GPOs and assets: can't download "ubuntuRoot":
  can't check if ubuntuRoot needs refreshing: no GPT.INI file: cannot
  open
  
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
  invalid argument

  It happens when using "adsysctl update -m" or "adsysctl update
  usern...@domain.com.br /tmp/krb5c_getentId_randomdnumber" and just
  "adsysctl update" too.

  I've upgrade the machine to 22.10 and the error changed to:

  ERROR Error from server: error while updating policy: can't get policies for 
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
  Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
  Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP 
client internal error: NT_STATUS_INVALID_PARAMETER
  Failed to open session: (1, 'LDAP client internal error: 
NT_STATUS_INVALID_PARAMETER').

  After upgrade to 23.04 the error persist same as the above.

  Full info 22.04 (- verbose):

  INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates 
/root /etc /usr/sbin]".
  We will only use the defaults, env variables or flags.
  DEBUG Connecting as [[2504:109556]]
  DEBUG New request /service/UpdatePolicy
  DEBUG Requesting with parameters: IsComputer: true, All: false, Target: 
ubuntu, Krb5Cc:
  DEBUG NormalizeTargetName for "ubuntu", type "computer"
  DEBUG Check if grpc request peer is authorized
  DEBUG Authorized as being administrator
  DEBUG GetPolicies for "ubuntu", type "computer"
  DEBUG Getting gpo list with arguments: "--objectclass computer 
ldap://addc01.domain.com.br ubuntu"
  DEBUG GPO "ubuntuRoot" for "ubuntu" available at 
"smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}"
  DEBUG Analyzing "assets"
  DEBUG Analyzing "ubuntuRoot"
  INFO No assets directory with GPT.INI file found on AD, skipping assets 
download
  ERROR Error from server: error while updating policy: can't get policies for 
"ubuntu": can't download all gpos and assets: one or more error while fetching 
GPOs and assets: can't download "ubuntuRoot": can't check if ubuntuRoot needs 
refreshing: no GPT.INI file: cannot open 
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
 invalid argument

  Full info 23.04 (- verbose):

  INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates 
/root /etc /usr/sbin]".
  DEBUG Connecting as [[58811:006019]]
  DEBUG New request /service/UpdatePolicy
  DEBUG Requesting with parameters: IsComputer: true, All: false, Target: 
ubuntu, Krb5Cc:
  DEBUG NormalizeTargetName for "ubuntu", type "computer"
  DEBUG Check if grpc request peer is authorized
  DEBUG Authorized as being administrator
  DEBUG GetPolicies for "ubuntu", type "computer"
  DEBUG Getting gpo list with arguments: "--objectclass computer 
ldap://addc01.domain.com.br ubuntu"
  ERROR Error from server: error while updating policy: can't get policies for 
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
  Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
  Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP 
client internal error: NT_STATUS_INVALID_PARAMETER
  Failed to open session: (1, 'LDAP client internal error: 
NT_STATUS_INVALID_PARAMETER')

  Additional info:

  Domain Controller and machine are on the same subnet without firewall on any 
level;
  Domain Controller is a Windows Server 2019 updated to the last security 
version;
  Both machine and user are on the same OU with "no heritage" enabled and just 
one policy added to permit usern...@domain.com.br to become root;
  The info header directory is "/home/jzprates" on both logs because I've 
collected them using the local account using "sudo adsysctl update -m -";
  If I disable Adsys login on pam-auth-update, Ubuntu creates a homedir and 
enter correctly with domain 

[Desktop-packages] [Bug 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble

2024-01-19 Thread Brian Murray
Looking at the log files this is happening when installing the firefox
deb so the problem is likely there.

06:31:33 Selecting previously unselected package firefox.
06:31:33 Preparing to unpack .../26-firefox_1%3a1snap1-0ubuntu5_amd64.deb ...
06:31:33 => Installing the firefox snap
06:31:33 ==> Checking connectivity with the snap store
06:32:06 ===> Unable to contact the store, trying every minute for the next 30 
minutes
06:47:28 ===> Still unable to contact the store, trying for another 20 minutes
07:02:51 ===> Still unable to contact the store, trying for another 10 minutes
07:16:00 Build timed out (after 60 minutes). Marking the build as failed.

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

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

** Changed in: firefox (Ubuntu)
   Importance: Undecided => High

** Tags added: cuqa-automated-testing

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

Title:
  Unable to contact snap store on Xubuntu from Jammy to Noble

Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  When running `do-release-upgrade -d` on Jammy Xubuntu, the upgrade
  fails consistently at the `Installing the firefox snap` step.

  This was first detected on Jenkins [1], then reproduced locally with
  `auto-upgrade-testing`, then finally by manually running a `do-
  release-upgrade -d` in a VM.

  [1]: https://platform-qa-jenkins.ps5.ubuntu.com/view/upgrade-
  list/job/upgrade_ubuntu-jammy-noble-xubuntu-amd64_qemu/7/consoleFull
  (Jenkins full log attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.17
  ProcVersionSignature: User Name 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Fri Nov 17 18:24:22 2023
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2024-01-19 Thread geole0
*** This bug is a duplicate of bug 2043958 ***
https://bugs.launchpad.net/bugs/2043958

Hello
The bug 2043958 say
This problem was most recently seen with package version 45.1-1ubuntu1, the 
problem page at 
https://errors.ubuntu.com/problem/c4d852b67163763f6ebf416e212eb366999c17b8 
contains more details,
But but my bug say
DistroRelease: Ubuntu 24.04
Package: gnome-shell 45.3-1ubuntu1
and 45.3 is not like 45.1

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  New noble version

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Jan 18 12:22:32 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2024-01-18 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240116)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7e9568201e5d <__GI_getenv+77>:   cmp
(%rbx),%r12b
   PC (0x7e9568201e5d) ok
   source "(%rbx)" (0x621392096246) not located in a known VMA region (needed 
readable region)!
   destination "%r12b" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_getenv (name=0x7e956533813e "FONTCONFIG_SYSROOT") at 
./stdlib/getenv.c:31
   FcConfigCreate () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   FcInit () from /lib/x86_64-linux-gnu/libfontconfig.so.1
  Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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

2024-01-19 Thread geole0
*** This bug is a duplicate of bug 2043958 ***
https://bugs.launchpad.net/bugs/2043958

Hello
The bug 2043958 say
This problem was most recently seen with package version 45.1-1ubuntu1, the 
problem page at 
https://errors.ubuntu.com/problem/c4d852b67163763f6ebf416e212eb366999c17b8 
contains more details,
But  but my bug say
DistroRelease: Ubuntu 24.04
Package: gnome-shell 45.3-1ubuntu1
and 45.3 is not likd 45.1

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  New noble version

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Jan 18 12:22:32 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2024-01-18 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240116)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7e9568201e5d <__GI_getenv+77>:   cmp
(%rbx),%r12b
   PC (0x7e9568201e5d) ok
   source "(%rbx)" (0x621392096246) not located in a known VMA region (needed 
readable region)!
   destination "%r12b" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_getenv (name=0x7e956533813e "FONTCONFIG_SYSROOT") at 
./stdlib/getenv.c:31
   FcConfigCreate () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   FcInit () from /lib/x86_64-linux-gnu/libfontconfig.so.1
  Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2049752/+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 2024424] Re: Right-click menu on dock doesn't scroll when it is long

2024-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Confirmed

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

Title:
  Right-click menu on dock doesn't scroll when it is long

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

Bug description:
  When you right-click on a "Favourite" in the dock, it shows a small
  menu relating to that app. For example, right-click on Nautilus to
  show the options "All Windows", "New Window", and the various Nautilus
  shortcuts.

  However, when the menu is long (I have many Nautilus shortcuts, so
  this happens with me), the top of the menu, which is the most
  important bit (for me, anyway, as I want "New Window") disappears
  above the screen.

  The attached screenshot shows the very top-left of my monitor after
  I've right-clicked on the Nautilus shortcut. As you can see, the top
  part of the menu has disappeared off the top.

  Unfortunately, this menu cannot be scrolled; there's no scrollbar, and
  the mouse wheel does nothing.

  The menu needs to be scrollable.

  More information:

  $ lsb_release -rd
  Description: Ubuntu 22.04.2 LTS
  Release: 22.04

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:42.6-0ubuntu1
Candidate: 1:42.6-0ubuntu1
Version table:
   *** 1:42.6-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:42.2-0ubuntu2.1 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:42.0-1ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.6-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 20 07:55:21 2023
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2022-08-28 (295 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2024424/+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 2049923] [NEW] gnome-terminal freezing, then crashing

2024-01-19 Thread Ralf Hildebrandt
Public bug reported:

First: It's very hard to reproduce, but it happens to me about once per week.
If often open new windows or split windows out from tabs. And then it happens. 
First it becomes unresponsive, and then after about 2-3 seconds it simply 
closes all instances.


[328830.780749] gnome-terminal-[117706]: segfault at 460742 ip 
7fdb2fb45611 sp 7ffdb8c5fda0 error 4 in 
libgtk-3.so.0.2406.32[7fdb2f883000+38f000] likely on CPU 4 (core 4, socket 0)

[328830.780761] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89 44
24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85 c0 74
05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6 48 89

[329377.925310] gnome-terminal-[120116]: segfault at 2f0774 ip
7f86af745611 sp 7ffc9943c5c0 error 4 in
libgtk-3.so.0.2406.32[7f86af483000+38f000] likely on CPU 2 (core 2,
socket 0)

[329377.925324] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89 44
24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85 c0 74
05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6 48 89

unfortunately, apport isn't automatically creating a crash report.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-terminal 3.49.92-2ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 19 16:48:43 2024
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to mantic on 2023-10-17 (94 days ago)

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


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

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

Title:
  gnome-terminal freezing, then crashing

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  First: It's very hard to reproduce, but it happens to me about once per week.
  If often open new windows or split windows out from tabs. And then it 
happens. First it becomes unresponsive, and then after about 2-3 seconds it 
simply closes all instances.

  
  [328830.780749] gnome-terminal-[117706]: segfault at 460742 ip 
7fdb2fb45611 sp 7ffdb8c5fda0 error 4 in 
libgtk-3.so.0.2406.32[7fdb2f883000+38f000] likely on CPU 4 (core 4, socket 0)

  [328830.780761] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89
  44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85
  c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6
  48 89

  [329377.925310] gnome-terminal-[120116]: segfault at 2f0774 ip
  7f86af745611 sp 7ffc9943c5c0 error 4 in
  libgtk-3.so.0.2406.32[7f86af483000+38f000] likely on CPU 2 (core 2,
  socket 0)

  [329377.925324] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89
  44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85
  c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6
  48 89

  unfortunately, apport isn't automatically creating a crash report.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-terminal 3.49.92-2ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 16:48:43 2024
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to mantic on 2023-10-17 (94 days ago)

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

2024-01-19 Thread darinsmiller
Canonical occasionally breaks sound compatibility between kernel release
(but I yet to figure out why).  However, the XanMod kernel quite rarely
breaks Lenovo sound compatibility, thus I suggest you give that kernel a
whirl: https://xanmod.org/  (It's quite easy to install and remove if
needed).

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

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

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

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

  uname -r
  5.11.0-44-generic

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

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


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


[Desktop-packages] [Bug 1958019]

2024-01-19 Thread cam
Probably time to bisect and then report back to Cirrus Logic.

On 1/18/24 16:53, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #806 from Howard Chu (h...@highlandsun.com) ---
> (In reply to Cameron Berkenpas from comment #805)
>> I believe support for the 16ACHg6 was added quite a ways back.
> Yes, it was added in 5.18. It is broken in 6.x. That's why I still only run
> 5.19 on my machine. The comment below says it actually stopped working in
> 6.6.
> I can't confirm that it worked in any earlier 6.x kernels, I had no luck with
> it.
>> On 1/18/24 05:36, bugzilla-dae...@kernel.org wrote:
>>> --- Comment #804 from shenanig...@duck.com ---
>>> (In reply to Howard Chu from comment #791)
 (In reply to Miggy from comment #790)
> It seems the sound no longer works for the legion 7 16achg6 on kernel
>> 6.6.
> It's been working great for the last year on all kernels, but 6.6 just
> doesn't work.
>
> I'm not sure if anyone else is having similar issues? Manjaro Linux here.
 I had no luck with sound on Ubuntu's 6.2 either. I dropped back to 5.19 to
 get sound working again.
>>> I have been lurking on this thread for a while. This thread has been up and
>>> still active since 2020, I don't even know where / which suggestions I need
>>> to
>>> start following.
>>>
>>> I have 16ACHg6 too, (Alsa says that) it's running Realtek ALC287. I have a
>>> fresh install of Ubuntu 22.04 with kernel 6.5.0-14-generic, I have updated
>> my
>>> BIOS and internal speakers hasn't been working at all since the first day.
>>> External speakers (headphone, Bluetooth speakers) work just fine though.
>>> Still
>>> no luck with 16ACHg6 then ?
>>>

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

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

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

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

  uname -r
  5.11.0-44-generic

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

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


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


[Desktop-packages] [Bug 1958019]

2024-01-19 Thread hyc
(In reply to Cameron Berkenpas from comment #805)
> I believe support for the 16ACHg6 was added quite a ways back.

Yes, it was added in 5.18. It is broken in 6.x. That's why I still only run 
5.19 on my machine. The comment below says it actually stopped working in 6.6. 
I can't confirm that it worked in any earlier 6.x kernels, I had no luck with 
it.
> 
> On 1/18/24 05:36, bugzilla-dae...@kernel.org wrote:
> > --- Comment #804 from shenanig...@duck.com ---
> > (In reply to Howard Chu from comment #791)
> >> (In reply to Miggy from comment #790)
> >>> It seems the sound no longer works for the legion 7 16achg6 on kernel
> 6.6.
> >>> It's been working great for the last year on all kernels, but 6.6 just
> >>> doesn't work.
> >>>
> >>> I'm not sure if anyone else is having similar issues? Manjaro Linux here.
> >> I had no luck with sound on Ubuntu's 6.2 either. I dropped back to 5.19 to
> >> get sound working again.
> > I have been lurking on this thread for a while. This thread has been up and
> > still active since 2020, I don't even know where / which suggestions I need
> > to
> > start following.
> >
> > I have 16ACHg6 too, (Alsa says that) it's running Realtek ALC287. I have a
> > fresh install of Ubuntu 22.04 with kernel 6.5.0-14-generic, I have updated
> my
> > BIOS and internal speakers hasn't been working at all since the first day.
> > External speakers (headphone, Bluetooth speakers) work just fine though.
> > Still
> > no luck with 16ACHg6 then ?
> >

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

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

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

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

  uname -r
  5.11.0-44-generic

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

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


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


[Desktop-packages] [Bug 1958019]

2024-01-19 Thread cam
I believe support for the 16ACHg6 was added quite a ways back.

On 1/18/24 05:36, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> shenanig...@duck.com changed:
>
> What|Removed |Added
> 
>   CC||shenanig...@duck.com
>
> --- Comment #804 from shenanig...@duck.com ---
> (In reply to Howard Chu from comment #791)
>> (In reply to Miggy from comment #790)
>>> It seems the sound no longer works for the legion 7 16achg6 on kernel 6.6.
>>> It's been working great for the last year on all kernels, but 6.6 just
>>> doesn't work.
>>>
>>> I'm not sure if anyone else is having similar issues? Manjaro Linux here.
>> I had no luck with sound on Ubuntu's 6.2 either. I dropped back to 5.19 to
>> get sound working again.
> I have been lurking on this thread for a while. This thread has been up and
> still active since 2020, I don't even know where / which suggestions I need
> to
> start following.
>
> I have 16ACHg6 too, (Alsa says that) it's running Realtek ALC287. I have a
> fresh install of Ubuntu 22.04 with kernel 6.5.0-14-generic, I have updated my
> BIOS and internal speakers hasn't been working at all since the first day.
> External speakers (headphone, Bluetooth speakers) work just fine though.
> Still
> no luck with 16ACHg6 then ?
>

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

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

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

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

  uname -r
  5.11.0-44-generic

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

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


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


[Desktop-packages] [Bug 1958019]

2024-01-19 Thread shenanigans
(In reply to Howard Chu from comment #791)
> (In reply to Miggy from comment #790)
> > It seems the sound no longer works for the legion 7 16achg6 on kernel 6.6.
> > It's been working great for the last year on all kernels, but 6.6 just
> > doesn't work.
> > 
> > I'm not sure if anyone else is having similar issues? Manjaro Linux here.
> 
> I had no luck with sound on Ubuntu's 6.2 either. I dropped back to 5.19 to
> get sound working again.

I have been lurking on this thread for a while. This thread has been up
and still active since 2020, I don't even know where / which suggestions
I need to start following.

I have 16ACHg6 too, (Alsa says that) it's running Realtek ALC287. I have
a fresh install of Ubuntu 22.04 with kernel 6.5.0-14-generic, I have
updated my BIOS and internal speakers hasn't been working at all since
the first day. External speakers (headphone, Bluetooth speakers) work
just fine though. Still no luck with 16ACHg6 then ?

-- 
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 2049907] [NEW] tracker-extract-3 crash with SIGSYS when upgrading from 22.04 to 24.04

2024-01-19 Thread Skia
Public bug reported:

Very similar behavior as this existing bug:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1983859

Almost copy-paste of original report:

When upgrading Ubuntu Desktop from 22.04 to 24.04, there's often (pretty
much always) a crash from tracker-extract, as described in the following
error report:

https://errors.ubuntu.com/oops/7a86fbf0-b52b-11ee-b9e4-fa163e171f02

The crash occurs during the upgrade, which means it's fairly hard to
investigate exactly what's going on as apport fails to extract a stack
trace, the binaries being overwritten during the upgrade.

** Affects: tracker-miners (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  tracker-extract-3 crash with SIGSYS when upgrading from 22.04 to 24.04

Status in tracker-miners package in Ubuntu:
  New

Bug description:
  Very similar behavior as this existing bug:
  https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1983859

  Almost copy-paste of original report:

  When upgrading Ubuntu Desktop from 22.04 to 24.04, there's often
  (pretty much always) a crash from tracker-extract, as described in the
  following error report:

  https://errors.ubuntu.com/oops/7a86fbf0-b52b-11ee-b9e4-fa163e171f02

  The crash occurs during the upgrade, which means it's fairly hard to
  investigate exactly what's going on as apport fails to extract a stack
  trace, the binaries being overwritten during the upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/2049907/+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 2037604] Re: Backport packages for 22.04.4 HWE stack

2024-01-19 Thread Timo Aaltonen
Thanks a lot for these, so we're good on AMD platforms.

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

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Committed
Status in rust-bindgen source package in Jammy:
  Invalid
Status in rust-clang-sys source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  [Test case]
  We want to cover at least 2-3 different, widely used and already previously 
supported GPU generations from both AMD and Intel which are supported by this 
release, as those are the ones that cover most bases; nouveau users tend to 
switch to the NVIDIA blob after installation. No need to test ancient GPU's 
supported by mesa-amber. And best to focus on the newer generations (~5y and 
newer) as the older ones are less likely to break at this point.
  - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
  - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2)

  Install the new packages and run some tests:
  - check that the desktop is still using hw acceleration and hasn't fallen 
back to swrast/llvmpipe
  - run freely available benchmarks that torture the GPU (Unigine 
Heaven/Valley/Superposition)
  - run some games from Steam if possible

  and in each case check that there is no gfx corruption happening or
  worse.

  Note that upstream releases have already been tested for OpenGL and
  Vulkan conformance by their CI.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2049895] [NEW] Distorted mouse poitner in the remote window

2024-01-19 Thread Simon Sadetsky
Public bug reported:

Distorted mouse poitner in the remote window (see the photo attched)

The bug is reproducable with Wayland only. Whith xorg all works fine on
the same machine. I experience it more than a year.

I'm using fraqtional scale 125%.

$ gsettings get org.gnome.mutter experimental-features
['x11-randr-fractional-scaling', 'scale-monitor-framebuffer']

Video is AMD integrated Radeon 4750G.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-remote-desktop 42.9-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 19 15:35:25 2024
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-remote-desktop
UpgradeStatus: Upgraded to jammy on 2022-06-05 (592 days ago)

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


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

** Attachment added: "bug photo"
   
https://bugs.launchpad.net/bugs/2049895/+attachment/5740761/+files/1705668457716.JPEG

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

Title:
  Distorted mouse poitner in the remote window

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

Bug description:
  Distorted mouse poitner in the remote window (see the photo attched)

  The bug is reproducable with Wayland only. Whith xorg all works fine
  on the same machine. I experience it more than a year.

  I'm using fraqtional scale 125%.

  $ gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling', 'scale-monitor-framebuffer']

  Video is AMD integrated Radeon 4750G.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-remote-desktop 42.9-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 15:35:25 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-remote-desktop
  UpgradeStatus: Upgraded to jammy on 2022-06-05 (592 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2049895/+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 2049883] [NEW] Can't switch language layout by mouse if set Ctrl+Space keyboard combination

2024-01-19 Thread Oleksandr Bratashov
Public bug reported:

I've set up a custom Ctrl+Space keyboard combination to switch language.
But now I can't switch the language by mouse in the top menu - the indicator is 
always on the 'En' layout.

OS: Ubuntu 22.04

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

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

Title:
  Can't switch language layout by mouse if set Ctrl+Space keyboard
  combination

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

Bug description:
  I've set up a custom Ctrl+Space keyboard combination to switch language.
  But now I can't switch the language by mouse in the top menu - the indicator 
is always on the 'En' layout.

  OS: Ubuntu 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2049883/+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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot

2024-01-19 Thread Simon Chopin
** Changed in: glibc (Ubuntu)
   Importance: Undecided => Critical

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

** Changed in: glibc (Ubuntu)
 Assignee: (unassigned) => Simon Chopin (schopin)

** Tags added: foundations-todo

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

Title:
  pango1.0: FTBFS against glibc 2.39 snapshot

Status in glibc package in Ubuntu:
  Triaged
Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Hi,

  The package pango1.0 failed to build during the recent full archive
  test rebuild against a snapshot of the the development branch for the
  upcoming glibc 2.39, expected to land in Noble. This was subsequently
  confirmed locally against a more recent snapshot.

  Full logs for the FTBFS: 
https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz
  Full report: 
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html
  PPA with glibc snapshot: 
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc

  Snippet showing the failure:

  === 22/27 
  test: test-fonts
  start time:   10:25:39
  duration: 0.11s
  result:   exit status 1
  command:  G_TEST_SRCDIR=/<>/tests 
srcdir=/<>/tests LC_ALL=en_US.UTF-8 
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango 
G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k 
--tap
  --- stdout ---
  TAP version 13
  # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d
  1..4
  # Start of fontsets tests
  ok 1 /fontsets/cantarell2
  # Contents don't match expected contents
  # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100
  # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 2 /fontsets/mono2
  ok 3 /fontsets/cantarell
  # Contents don't match expected contents
  # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100
  # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 4 /fontsets/mono
  # End of fontsets tests
  --- stderr ---

  (test program exited with status code 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+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 2049493] Re: Newer rustc version needed in jammy to build chromium updates

2024-01-19 Thread Nathan Teodosio
The build with the manual removal of the -Z flags failed[1] with
multiple undefined references such as

--->
obj/third_party/rust/cxx/v1/lib/libcxx_lib.rlib(libcxx_lib.cxx.fbfe687f763ab24e-cgu.0.rcgu.o):cxx.fbfe687f763ab24e-cgu.0:function
 < as core::fmt::Debug>::fmt: error: undefined reference to '::fmt'
obj/third_party/rust/cxx/v1/lib/libcxx_lib.rlib(libcxx_lib.cxx.fbfe687f763ab24e-cgu.0.rcgu.o):cxx.fbfe687f763ab24e-cgu.0:function
 < as core::fmt::Display>::fmt: error: undefined reference to '::fmt'
obj/third_party/rust/cxx/v1/lib/libcxx_lib.rlib(libcxx_lib.cxx.fbfe687f763ab24e-cgu.0.rcgu.o):cxx.fbfe687f763ab24e-cgu.0:function
 < as core::fmt::LowerHex>::fmt: error: undefined reference to 
'core::fmt::numfmt'
<---

The builds with RUSTC_BOOTSTRAP=1 were silently reset after hours of
progress (an old mysterious bug) and therefore we'll find out their
actual result only on Monday.

[1]
https://launchpadlibrarian.net/710066046/buildlog_snap_ubuntu_jammy_armhf_chromium-
rust_BUILDING.txt.gz

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

Title:
  Newer rustc version needed in jammy to build chromium updates

Status in chromium-browser package in Ubuntu:
  New
Status in rustc package in Ubuntu:
  New

Bug description:
  The next chromium version is making rustc mandatory to build. Chromium
  is a snap built from core22 so using the jammy packages, the build is
  currently failing because it needs libprofiler_builtins.rlib which
  isn't available.

  Upstream provides toolchain builds that can be used but only for amd64 so 
currently the snap is failing to build on arm
  https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta

  The version upstream is using is 1.75 but it's possible that a lower
  version would be enough for now if libprofiler was enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot

2024-01-19 Thread Simon Chopin
I'm currently focused on cataloguing failures, but I'll try to
investigate it if nobody has picked it up by then.

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

Title:
  pango1.0: FTBFS against glibc 2.39 snapshot

Status in glibc package in Ubuntu:
  New
Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Hi,

  The package pango1.0 failed to build during the recent full archive
  test rebuild against a snapshot of the the development branch for the
  upcoming glibc 2.39, expected to land in Noble. This was subsequently
  confirmed locally against a more recent snapshot.

  Full logs for the FTBFS: 
https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz
  Full report: 
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html
  PPA with glibc snapshot: 
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc

  Snippet showing the failure:

  === 22/27 
  test: test-fonts
  start time:   10:25:39
  duration: 0.11s
  result:   exit status 1
  command:  G_TEST_SRCDIR=/<>/tests 
srcdir=/<>/tests LC_ALL=en_US.UTF-8 
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango 
G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k 
--tap
  --- stdout ---
  TAP version 13
  # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d
  1..4
  # Start of fontsets tests
  ok 1 /fontsets/cantarell2
  # Contents don't match expected contents
  # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100
  # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 2 /fontsets/mono2
  ok 3 /fontsets/cantarell
  # Contents don't match expected contents
  # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100
  # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 4 /fontsets/mono
  # End of fontsets tests
  --- stderr ---

  (test program exited with status code 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+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 2049881] [NEW] pango1.0: FTBFS against glibc 2.39 snapshot

2024-01-19 Thread Simon Chopin
Public bug reported:

Hi,

The package pango1.0 failed to build during the recent full archive test
rebuild against a snapshot of the the development branch for the
upcoming glibc 2.39, expected to land in Noble. This was subsequently
confirmed locally against a more recent snapshot.

Full logs for the FTBFS: 
https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz
Full report: 
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html
PPA with glibc snapshot: 
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc

Snippet showing the failure:

=== 22/27 
test: test-fonts
start time:   10:25:39
duration: 0.11s
result:   exit status 1
command:  G_TEST_SRCDIR=/<>/tests 
srcdir=/<>/tests LC_ALL=en_US.UTF-8 
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango 
G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k 
--tap
--- stdout ---
TAP version 13
# random seed: R02Sd064b2e790c11a865b61afd5b0b7909d
1..4
# Start of fontsets tests
ok 1 /fontsets/cantarell2
# Contents don't match expected contents
# --- /tmp/.OQTQH2  2024-01-19 11:25:39.214546169 +0100
# +++ /tmp/.OSTQH2  2024-01-19 11:25:39.214546169 +0100
# @@ -4,7 +4,7 @@
#  DejaVu Sans 20
#  Noto Sans CJK JP 20
#  Droid Sans Japanese 20
# -Cantarell 20
# +Cantarell 20 @wght=400
#  Amiri 20
#  DejaVu Sans Bold 20
#  Font Awesome 5 Free Solid Heavy 20
#
not ok 2 /fontsets/mono2
ok 3 /fontsets/cantarell
# Contents don't match expected contents
# --- /tmp/.X3URH2  2024-01-19 11:25:39.234546069 +0100
# +++ /tmp/.FJURH2  2024-01-19 11:25:39.234546069 +0100
# @@ -4,7 +4,7 @@
#  DejaVu Sans 20
#  Noto Sans CJK JP 20
#  Droid Sans Japanese 20
# -Cantarell 20
# +Cantarell 20 @wght=400
#  Amiri 20
#  DejaVu Sans Bold 20
#  Font Awesome 5 Free Solid Heavy 20
#
not ok 4 /fontsets/mono
# End of fontsets tests
--- stderr ---

(test program exited with status code 1)

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

** Affects: pango1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: test-rebuild-glibc-noble

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

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

Title:
  pango1.0: FTBFS against glibc 2.39 snapshot

Status in glibc package in Ubuntu:
  New
Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Hi,

  The package pango1.0 failed to build during the recent full archive
  test rebuild against a snapshot of the the development branch for the
  upcoming glibc 2.39, expected to land in Noble. This was subsequently
  confirmed locally against a more recent snapshot.

  Full logs for the FTBFS: 
https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz
  Full report: 
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html
  PPA with glibc snapshot: 
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc

  Snippet showing the failure:

  === 22/27 
  test: test-fonts
  start time:   10:25:39
  duration: 0.11s
  result:   exit status 1
  command:  G_TEST_SRCDIR=/<>/tests 
srcdir=/<>/tests LC_ALL=en_US.UTF-8 
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango 
G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k 
--tap
  --- stdout ---
  TAP version 13
  # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d
  1..4
  # Start of fontsets tests
  ok 1 /fontsets/cantarell2
  # Contents don't match expected contents
  # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100
  # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 2 /fontsets/mono2
  ok 3 /fontsets/cantarell
  # Contents don't match expected contents
  # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100
  # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100
  # 

[Desktop-packages] [Bug 2023572] Re: SRU gjs 1.72.4 to jammy

2024-01-19 Thread Ernst Persson
Still sitting in "kept back" :-)

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

Title:
  SRU gjs 1.72.4 to jammy

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]

  That's the GNOME 42 stable update, including some fixes:
  https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  The test plan that will be used is documented at
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

  [ Regression potential ]

  Gjs is fundamental part of the ubuntu desktop, so any failure of it
  may cause the desktop not even to boot (because it's being used by gdm
  too).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+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 1982693] Re: USB-Audio device UMC204HD disappears after suspend

2024-01-19 Thread Kerem B
I have in the meantime switched to a new PC and this problem doesn't
occur any more. Sorry I cannot be of help.

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

Title:
  USB-Audio device UMC204HD disappears after suspend

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Coming back from sleep, Behringer UMC204HD is not in the list of
  devices in Settings > Sound. It comes back if I unplug and plug back
  in.

  I tried with/without a USB hub in between, I tried setting
  "usbcore.autosuspend=-1". No help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 24 15:04:57 2022
  InstallationDate: Installed on 2022-04-21 (93 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U192k successful
  Symptom_Card: HD Webcam C525 - HD Webcam C525
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [USB-Audio - UMC204HD 192k, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.H0
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M PRO-VH (MS-7996)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.H0:bd06/16/2018:br5.12:svnMSI:pnMS-7996:pvr1.0:rvnMSI:rnH110MPRO-VH(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7996
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1982693/+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 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x

2024-01-19 Thread Olivier Gayot
The last two autopkgtest runs in the infrastructure are green despite
the trigger and they both show:

258s Unpacking wpasupplicant (2:2.10-21) ...

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

Title:
  Test suite often fails with "systemd units changed without reload" on
  s390x

Status in netplan:
  Invalid
Status in netplan.io package in Ubuntu:
  Triaged
Status in wpa package in Ubuntu:
  New

Bug description:
  The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
  often fails with

  AssertionError: systemd units changed without reload

  Looking at the history of autopkgtest runs, it looks like that the
  error does not always occur during execution of a specific test. I've
  seen occurrences of this error during the following test-cases:

  test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
  test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
  test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL

  Example [1]:

  781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
  781s --
  781s Traceback (most recent call last):
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line 
189, in test_dhcp6
  781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in 
generate_and_settle
  781s self.fail('systemd units changed without reload')
  781s AssertionError: systemd units changed without reload

  [1] https://autopkgtest.ubuntu.com/results/autopkgtest-
  noble/noble/s390x/n/netplan.io/20240105_144627_cb35e@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2048388/+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 2049434] Re: Nautilus crashes when trying to open file options in administrator mode

2024-01-19 Thread Bug Watch Updater
** Changed in: nautilus
   Status: Unknown => Fix Released

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

Title:
  Nautilus crashes when trying to open file options in administrator
  mode

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 23.10
  nautilus 1:45~rc-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 16 00:46:25 2024
  InstallationDate: Installed on 2024-01-11 (4 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/2049434/+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 2049434] Re: Nautilus crashes when trying to open file options in administrator mode

2024-01-19 Thread Sebastien Bacher
Thanks!

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #3111
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/3111

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

Title:
  Nautilus crashes when trying to open file options in administrator
  mode

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 23.10
  nautilus 1:45~rc-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 16 00:46:25 2024
  InstallationDate: Installed on 2024-01-11 (4 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/2049434/+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 2049434] Re: Nautilus crashes when trying to open file options in administrator mode

2024-01-19 Thread Sebastien Bacher
The issue is known upstream as
https://gitlab.gnome.org/GNOME/nautilus/-/issues/3111 and was fixed in
the 45.1 update so will be resolved in Ubuntu once the fix for bug
#2048892 lands

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

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

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

** Also affects: nautilus via
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/3111
   Importance: Unknown
   Status: Unknown

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

Title:
  Nautilus crashes when trying to open file options in administrator
  mode

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 23.10
  nautilus 1:45~rc-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 16 00:46:25 2024
  InstallationDate: Installed on 2024-01-11 (4 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/2049434/+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 2049855] Re: /usr/bin/nautilus:11:fast_validate:g_utf8_validate:g_utf8_validate:get_real_name:nautilus_get_user_names

2024-01-19 Thread Sebastien Bacher
*** This bug is a duplicate of bug 2049434 ***
https://bugs.launchpad.net/bugs/2049434

** This bug has been marked a duplicate of bug 2049434
   Nautilus crashes when trying to open file options in administrator mode

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

Title:
  
/usr/bin/nautilus:11:fast_validate:g_utf8_validate:g_utf8_validate:get_real_name:nautilus_get_user_names

Status in nautilus package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2049855/+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 2049855] [NEW] /usr/bin/nautilus:11:fast_validate:g_utf8_validate:g_utf8_validate:get_real_name:nautilus_get_user_names

2024-01-19 Thread errors.ubuntu.com bug bridge
Public bug reported:

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

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


** Tags: lunar mantic noble

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

Title:
  
/usr/bin/nautilus:11:fast_validate:g_utf8_validate:g_utf8_validate:get_real_name:nautilus_get_user_names

Status in nautilus package in Ubuntu:
  New

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

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