[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland

2023-10-31 Thread Ante Karamatić
Another +1 on -proposed mutter. It solves the problem for me too.

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy
  load in Wayland

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Committed
Status in linux source package in Mantic:
  Triaged
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems,
  sometimes when the screen locks, sometimes when launching particular
  apps.

  [ Workaround ]

  Add this to /etc/environment:

    MUTTER_DEBUG_KMS_THREAD_TYPE=user

  and then reboot.

  [ Test Plan ]

  Not all Ryzen systems (including one I just purchased) are able to
  reproduce the bug. We have no choice but to leave final verification
  to the community. Anyone affected should try locking their screen and
  verify they are not instantly returned to the login screen.

  [ Where problems could occur ]

  Anywhere in frame scheduling and particularly for mouse cursor
  movement since that's what the real-time thread exists to optimize.

  [ Original Description ]

  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  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: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  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/linux/+bug/2034619/+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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode

2023-10-31 Thread Kai-Chuan Hsieh
Here is fccunlock package for the Dell platform.

http://dell.archive.canonical.com/dists/jammy-somerville/public/binary-
amd64/Packages

Package: oem-fix-misc-intel-fccunlock
Priority: optional
Section: misc
Installed-Size: 116
Maintainer: Commercial Engineering 
Architecture: amd64
Version: 5
Filename: 
pool/public/o/oem-fix-misc-intel-fccunlock/oem-fix-misc-intel-fccunlock_5_amd64.deb
Size: 25304
SHA256: 7d582be18039443bfcccfd4c54ef3c95396d8429f5b63b476fde85697375ad1c
SHA1: 58fc9cbee65caa02514b0f0c9064cd9187451cfd
MD5sum: 91215c90ef0de45155b586e2698ee9ac
Description: This is a fccunlock application used for unlocking 7560 R+ and 
FM350 modem.
Description-md5: 994674e9a65d631a0b92e571f9867bae
Modaliases: oem(pci:v14C3d4D75sv*sd*bc*sc*i*, 
pci:v8086d7560sv*sd*bc*sc*i*)

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

Title:
  Fibcom FM350-GL not able connect to network with 5G mode

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  Fibcom FM350-GL can support 5G network
  (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu
  22.04, system can only connect to mobile network with 4G mode.


General  | path: /org/freedesktop/ModemManager1/Modem/0
 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e

Hardware | manufacturer: generic
 |model: MBIM [14C3:4D75]
 |firmware revision: 81600..00.29.18.01_GC
 |   C01
 | h/w revision: V1.0.6
 |supported: gsm-umts, lte
 |  current: gsm-umts, lte
 | equipment id: 352750140002001

System   |   device: 
/sys/devices/pci:00/:00:1c.0/:73:00.0
 |  drivers: mtk_t7xx
 |   plugin: generic
 | primary port: wwan0mbim0
 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 
(mbim)

Status   |   unlock retries: sim-pin (3), sim-pin2 (3)
 |state: connected
 |  power state: on
 |  access tech: lte
 |   signal quality: 74% (recent)

Modes|supported: allowed: 3g, 4g; preferred: none
 |  current: allowed: 3g, 4g; preferred: none

IP   |supported: ipv4, ipv6, ipv4v6

3GPP | imei: 352750140002001
 |enabled locks: sim, fixed-dialing
 |  operator id: 46692
 |operator name: Chunghwa Telecom
 | registration: home

3GPP EPS | ue mode of operation: csps-2
 |  initial bearer path: /org/freedesktop/ModemManager1/Bearer/0

SIM  | primary sim path: /org/freedesktop/ModemManager1/SIM/0

Bearer   |paths: /org/freedesktop/ModemManager1/Bearer/1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-06-15 (26 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: modemmanager 1.18.6-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9
  Tags:  jammy
  Uname: Linux 5.17.0-9012-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1981190/+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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode

2023-10-31 Thread Michael J Brancato
How did you get the FCC Unlock to enable the modem?

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

Title:
  Fibcom FM350-GL not able connect to network with 5G mode

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  Fibcom FM350-GL can support 5G network
  (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu
  22.04, system can only connect to mobile network with 4G mode.


General  | path: /org/freedesktop/ModemManager1/Modem/0
 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e

Hardware | manufacturer: generic
 |model: MBIM [14C3:4D75]
 |firmware revision: 81600..00.29.18.01_GC
 |   C01
 | h/w revision: V1.0.6
 |supported: gsm-umts, lte
 |  current: gsm-umts, lte
 | equipment id: 352750140002001

System   |   device: 
/sys/devices/pci:00/:00:1c.0/:73:00.0
 |  drivers: mtk_t7xx
 |   plugin: generic
 | primary port: wwan0mbim0
 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 
(mbim)

Status   |   unlock retries: sim-pin (3), sim-pin2 (3)
 |state: connected
 |  power state: on
 |  access tech: lte
 |   signal quality: 74% (recent)

Modes|supported: allowed: 3g, 4g; preferred: none
 |  current: allowed: 3g, 4g; preferred: none

IP   |supported: ipv4, ipv6, ipv4v6

3GPP | imei: 352750140002001
 |enabled locks: sim, fixed-dialing
 |  operator id: 46692
 |operator name: Chunghwa Telecom
 | registration: home

3GPP EPS | ue mode of operation: csps-2
 |  initial bearer path: /org/freedesktop/ModemManager1/Bearer/0

SIM  | primary sim path: /org/freedesktop/ModemManager1/SIM/0

Bearer   |paths: /org/freedesktop/ModemManager1/Bearer/1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-06-15 (26 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: modemmanager 1.18.6-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9
  Tags:  jammy
  Uname: Linux 5.17.0-9012-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1981190/+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 2042367] [NEW] eglinfo device platform eglInitialize failed

2023-10-31 Thread Dean Wheatley
Public bug reported:

On an Intel NUC13RNGi9 system with 13900K processor with integrated
Intel UHD 770 Graphics, the command "eglinfo" fails to initialize the
Device platform:

$ eglinfo
...

Device platform:
eglinfo: eglInitialize failed


The other platforms (X11, Wayland, GBM) initialize.

The reason I am reporting is I'm trying to fix an issue in my system
where:

EGLDisplay display = eglGetDisplay(EGL_DEFAULT_DISPLAY)

is returning EGL_NO_DISPLAY

on my system, and I think it's due to the Device platform failing to
initialize.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  1 09:42:40 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:a780] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:3033]
InstallationDate: Installed on 2023-10-30 (1 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: Intel(R) Client Systems NUC13RNGi9
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/04/2023
dmi.bios.release: 5.27
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SBRPL579.0056.2023.0204.0233
dmi.board.name: NUC13SBBi9
dmi.board.vendor: Intel Corporation
dmi.board.version: M58736-304
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 44.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrSBRPL579.0056.2023.0204.0233:bd02/04/2023:br5.27:efr44.0:svnIntel(R)ClientSystems:pnNUC13RNGi9:pvrM89920-304:rvnIntelCorporation:rnNUC13SBBi9:rvrM58736-304:cvnIntelCorporation:ct35:cvr2.0:skuRNUC13RNGi9:
dmi.product.family: RN
dmi.product.name: NUC13RNGi9
dmi.product.sku: RNUC13RNGi9
dmi.product.version: M89920-304
dmi.sys.vendor: Intel(R) Client Systems
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.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-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

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

Title:
  eglinfo device platform eglInitialize failed

Status in xorg package in Ubuntu:
  New

Bug description:
  On an Intel NUC13RNGi9 system with 13900K processor with integrated
  Intel UHD 770 Graphics, the command "eglinfo" fails to initialize the
  Device platform:

  $ eglinfo
  ...

  Device platform:
  eglinfo: eglInitialize failed

  
  The other platforms (X11, Wayland, GBM) initialize.

  The reason I am reporting is I'm trying to fix an issue in my system
  where:

  EGLDisplay display = eglGetDisplay(EGL_DEFAULT_DISPLAY)

  is returning EGL_NO_DISPLAY

  on my system, and I think it's due to the Device platform failing to
  initialize.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 09:42:40 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:a780] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:3033]
  InstallationDate: Installed on 2023-10-30 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Intel(R) Client Systems NUC13RNGi9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2023
  

[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain

2023-10-31 Thread Dave Jones
Is this fixed in noble now? No. Is this due to be fixed; I've not heard
anything, but happy to be corrected if this is on a roadmap somewhere?

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

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  Fix Released
Status in NetworkManager:
  New
Status in netplan.io package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Incomplete
Status in netplan.io source package in Jammy:
  Triaged
Status in network-manager source package in Jammy:
  Incomplete
Status in netplan.io source package in Kinetic:
  Fix Released
Status in network-manager source package in Kinetic:
  Incomplete

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users 
can simply setup Ubuntu Server headless by putting the wifi configuration 
details in cloudinit/netplan's "network-config" on the FAT partition of the SD 
card: 
https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so 
may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

2023-10-31 Thread Erich Eickmeyer
Thank you for reporting this and helping make Ubuntu better. Could you
please boot into a Ubuntu kernel (not third party kernel) and execute
the following command only once, as it will automatically gather
debugging information, in a terminal:

apport-collect 2011385

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

2023-10-31 Thread Erich Eickmeyer
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We need some more information from you before we can
start working on this bug.

Please include the information requested from the "Reporting Sound Bugs"
section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate
attachments.

This information can be gathered for you automatically by using the following 
command only once:
apport-collect -p alsa-base 2011385

** Also affects: linux-hwe-5.19 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 1806242] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C

2023-10-31 Thread Andreas Hasenack
I still get this error in Ubuntu Lunar, with kernel 6.2.0-35-generic.

Sample:
$ sudo dmesg -T|grep Atomic
[qua nov  1 05:52:03 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=78023 end=78024) time 305 us, min 1783, max 1799, 
scanline start 1753, end 1804
[qua nov  1 06:15:56 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=161109 end=161110) time 209 us, min 1783, max 1799, 
scanline start 1775, end 1811
[qua nov  1 22:22:34 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=50827 end=50828) time 270 us, min 1783, max 1799, 
scanline start 1767, end 1812
[qua nov  1 22:32:50 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=90592 end=90593) time 278 us, min 1783, max 1799, 
scanline start 1768, end 1814
[qua nov  1 22:35:42 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=100359 end=100360) time 168 us, min 1783, max 1799, 
scanline start 1779, end 1807
[qua nov  1 23:29:19 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=259865 end=259866) time 276 us, min 1783, max 1799, 
scanline start 1770, end 1817
[qui nov  2 03:54:09 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=317370 end=317371) time 264 us, min 1783, max 1799, 
scanline start 1756, end 1801
[qui nov  2 03:57:36 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe A (start=331393 end=331394) time 279 us, min 1783, max 1799, 
scanline start 1769, end 1816
[qui nov  2 04:00:05 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe C (start=317726 end=317727) time 255 us, min 2146, max 2159, 
scanline start 2140, end 2173
[qui nov  2 04:48:44 2023] i915 :00:02.0: [drm] *ERROR* Atomic update 
failure on pipe C (start=492825 end=492826) time 272 us, min 2146, max 2159, 
scanline start 2123, end 2159

Hardware is a lenovo x1 10th gen, with intel "alderlake gen12" according
to intel_gpu_top, and I'm running xorg (not wayland).


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

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

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

Title:
  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe A/B/C

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have this error and arbitrary freezes on the system

  My System:

  Hardware:
  Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 
0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate 
ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: 
Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 
Gigabit + Intel Device a370

  Software:
  OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, 
Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, 
Screen Resolution: 1920x1980

  dmesg output:

  Dec  2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, 
min 894, max 899, scanline start 845, end 903
  Dec  2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup 
failure, AE_NOT_FOUND (20170831/psargs-364)
  Dec  2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized 
for Method [BRT6]
  Dec  2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method 
[BRT6]:  (2 arguments defined for method invocation)
  Dec  2 16:08:50 G5 kernel: [ 2534.448073]   Arg0:   a83faa08 
   Integer 0001
  Dec  2 16:08:50 G5 kernel: [ 2534.448076]   Arg1:   35246c42 
   Integer 
  Dec  2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution 
failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution 
failed \EV5, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution 
failed \SMEE, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution 
failed \SMIE, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution 
failed \NEVT, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution 
failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event 
[0x86]
  Dec  2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event 
[0x86]
 

[Desktop-packages] [Bug 2039460] Re: Please merge network-manager-applet 1.34.0-1 from Debian unstable

2023-10-31 Thread Bryce Harrington
Hi Nathan,

In your changelog entry, it shows 'UNRELEASED' as the distro, but that should 
be 'noble' now. 
It would also be worthwhile to mention this bug # in the changelog, so it 
should look like:


+network-manager-applet (1.34.0-1ubuntu1) noble; urgency=medium
+
+  * Merge with Debian (LP: #2039460). Remaining changes:
+- d/control:
+  + Build-Depend on on dh-sequence-translations


I would also recommend that you set up a PPA and upload the package
there, to verify the build against Noble.

Please re-subscribe sponsors once this is fixed up.  Thanks!

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

Title:
  Please merge network-manager-applet 1.34.0-1 from Debian unstable

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

Bug description:
  Builds successfully in Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/2039460/+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 2042301] Re: Windows are slow to open shortly after login under X11 session

2023-10-31 Thread Dimitrij Mijoski
** Description changed:

  On Ubuntu 23.10 after I install the Nvidia driver v535 I get noticeable
  latency of about 10-15 seconds after I click on any application, be it
  Nautilus, Terminal, Firefox. The problem lasts for about one minute.
  More precise steps:
  
  1. Install Nvidia drivers (using sudo ubuntu-drivers install)
  2. Reboot
  3. Login to X11 session (which becomes the default when Nvidia drivers are 
installed)
  4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons
  5. The mouse cursor turns to circle. After 10-15 seconds, some window will 
appear
  
  After about one minute opening any of these apps will open immediately,
  as expected. If I logout and login to Wayland the issue is not present.
  If I logout and login into X11 the issue can be reproduced, so it is not
  related to boot but to login. If I uninstall nvidia drivers the issue is
  gone.
  
  It might be an issue with mutter or gnome-shell.
  
  $ apt list nvidia-driver-535 mutter gnome-shell
  Listing... Done
  gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic]
  mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic]
  nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed]
  
  The following might be related. If I open the GUI app Logs I see the 
following error:
  Failed to start xdg-desktop-portal.service - Portal service.
  
  If I write the following command:
  
  $ journalctl --user --unit=xdg-desktop-portal
  
  I get:
  
  Oct 31 18:19:20 my-pc-hostname systemd[39536]: Starting 
xdg-desktop-portal.service - Portal service...
- Oct 31 18:20:10 my-pc-hostname xdg-desktop-por[44027]: Failed to create 
settings proxy: Error calling StartServiceByName for 
org.freedesktop.impl.portal.desktop.gnome: Timeout was r>
- Oct 31 18:20:35 my-pc-hostname xdg-desktop-por[44027]: Failed to create file 
chooser proxy: Error calling StartServiceByName for 
org.freedesktop.impl.portal.desktop.gnome: Timeout w>
+ Oct 31 18:20:10 lenovo-legion-5 xdg-desktop-por[44027]: Failed to create 
settings proxy: Error calling StartServiceByName for 
org.freedesktop.impl.portal.desktop.gnome: Timeout was reached
+ Oct 31 18:20:35 lenovo-legion-5 xdg-desktop-por[44027]: Failed to create file 
chooser proxy: Error calling StartServiceByName for 
org.freedesktop.impl.portal.desktop.gnome: Timeout was reached
  Oct 31 18:20:35 my-pc-hostname xdg-desktop-por[44027]: No skeleton to export
  Oct 31 18:20:50 my-pc-hostname systemd[39536]: xdg-desktop-portal.service: 
start operation timed out. Terminating.
  Oct 31 18:20:50 my-pc-hostname systemd[39536]: xdg-desktop-portal.service: 
Failed with result 'timeout'.
  Oct 31 18:20:50 my-pc-hostname systemd[39536]: Failed to start 
xdg-desktop-portal.service - Portal service.
  Oct 31 18:21:21 my-pc-hostname systemd[39536]: Starting 
xdg-desktop-portal.service - Portal service...
  Oct 31 18:21:21 my-pc-hostname systemd[39536]: Started 
xdg-desktop-portal.service - Portal service.
  Oct 31 18:23:46 my-pc-hostname systemd[39536]: Stopping 
xdg-desktop-portal.service - Portal service...
  Oct 31 18:23:46 my-pc-hostname systemd[39536]: Stopped 
xdg-desktop-portal.service - Portal service.
  
  So during one login and logout the service fails to start at first, but
  succeeds to start later.

** Description changed:

  On Ubuntu 23.10 after I install the Nvidia driver v535 I get noticeable
  latency of about 10-15 seconds after I click on any application, be it
  Nautilus, Terminal, Firefox. The problem lasts for about one minute.
  More precise steps:
  
  1. Install Nvidia drivers (using sudo ubuntu-drivers install)
  2. Reboot
  3. Login to X11 session (which becomes the default when Nvidia drivers are 
installed)
  4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons
  5. The mouse cursor turns to circle. After 10-15 seconds, some window will 
appear
  
  After about one minute opening any of these apps will open immediately,
  as expected. If I logout and login to Wayland the issue is not present.
  If I logout and login into X11 the issue can be reproduced, so it is not
  related to boot but to login. If I uninstall nvidia drivers the issue is
  gone.
  
  It might be an issue with mutter or gnome-shell.
  
  $ apt list nvidia-driver-535 mutter gnome-shell
  Listing... Done
  gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic]
  mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic]
  nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed]
  
  The following might be related. If I open the GUI app Logs I see the 
following error:
  Failed to start xdg-desktop-portal.service - Portal service.
  
  If I write the following command:
  
  $ journalctl --user --unit=xdg-desktop-portal
  
  I get:
  
  Oct 31 18:19:20 my-pc-hostname systemd[39536]: Starting 
xdg-desktop-portal.service - Portal service...
- Oct 31 18:20:10 lenovo-legion-5 xdg-desktop-por[44027]: Failed to create 
settings proxy: Error calling 

[Desktop-packages] [Bug 2042301] Re: Windows are slow to open shortly after login under X11 session

2023-10-31 Thread Dimitrij Mijoski
** Also affects: xdg-desktop-portal (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  On Ubuntu 23.10 after I install the Nvidia driver v535 I get noticeable
  latency of about 10-15 seconds after I click on any application, be it
  Nautilus, Terminal, Firefox. The problem lasts for about one minute.
  More precise steps:
  
  1. Install Nvidia drivers (using sudo ubuntu-drivers install)
  2. Reboot
  3. Login to X11 session (which becomes the default when Nvidia drivers are 
installed)
  4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons
  5. The mouse cursor turns to circle. After 10-15 seconds, some window will 
appear
  
  After about one minute opening any of these apps will open immediately,
  as expected. If I logout and login to Wayland the issue is not present.
  If I logout and login into X11 the issue can be reproduced, so it is not
  related to boot but to login. If I uninstall nvidia drivers the issue is
  gone.
  
  It might be an issue with mutter or gnome-shell.
  
  $ apt list nvidia-driver-535 mutter gnome-shell
  Listing... Done
  gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic]
  mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic]
  nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed]
  
  The following might be related. If I open the GUI app Logs I see the 
following error:
  Failed to start xdg-desktop-portal.service - Portal service.
  
  If I write the following command:
  
  $ journalctl --user --unit=xdg-desktop-portal
  
  I get:
  
  Oct 31 18:19:20 my-pc-hostname systemd[39536]: Starting 
xdg-desktop-portal.service - Portal service...
  Oct 31 18:20:10 my-pc-hostname xdg-desktop-por[44027]: Failed to create 
settings proxy: Error calling StartServiceByName for 
org.freedesktop.impl.portal.desktop.gnome: Timeout was r>
  Oct 31 18:20:35 my-pc-hostname xdg-desktop-por[44027]: Failed to create file 
chooser proxy: Error calling StartServiceByName for 
org.freedesktop.impl.portal.desktop.gnome: Timeout w>
  Oct 31 18:20:35 my-pc-hostname xdg-desktop-por[44027]: No skeleton to export
  Oct 31 18:20:50 my-pc-hostname systemd[39536]: xdg-desktop-portal.service: 
start operation timed out. Terminating.
  Oct 31 18:20:50 my-pc-hostname systemd[39536]: xdg-desktop-portal.service: 
Failed with result 'timeout'.
  Oct 31 18:20:50 my-pc-hostname systemd[39536]: Failed to start 
xdg-desktop-portal.service - Portal service.
  Oct 31 18:21:21 my-pc-hostname systemd[39536]: Starting 
xdg-desktop-portal.service - Portal service...
  Oct 31 18:21:21 my-pc-hostname systemd[39536]: Started 
xdg-desktop-portal.service - Portal service.
  Oct 31 18:23:46 my-pc-hostname systemd[39536]: Stopping 
xdg-desktop-portal.service - Portal service...
  Oct 31 18:23:46 my-pc-hostname systemd[39536]: Stopped 
xdg-desktop-portal.service - Portal service.
  
  So during one login and logout the service fails to start at first, but
- succeeds to tart later.
+ succeeds to start later.

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

Title:
  Windows are slow to open shortly after login under X11 session

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in xdg-desktop-portal package in Ubuntu:
  New

Bug description:
  On Ubuntu 23.10 after I install the Nvidia driver v535 I get
  noticeable latency of about 10-15 seconds after I click on any
  application, be it Nautilus, Terminal, Firefox. The problem lasts for
  about one minute. More precise steps:

  1. Install Nvidia drivers (using sudo ubuntu-drivers install)
  2. Reboot
  3. Login to X11 session (which becomes the default when Nvidia drivers are 
installed)
  4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons
  5. The mouse cursor turns to circle. After 10-15 seconds, some window will 
appear

  After about one minute opening any of these apps will open
  immediately, as expected. If I logout and login to Wayland the issue
  is not present. If I logout and login into X11 the issue can be
  reproduced, so it is not related to boot but to login. If I uninstall
  nvidia drivers the issue is gone.

  It might be an issue with mutter or gnome-shell.

  $ apt list nvidia-driver-535 mutter gnome-shell
  Listing... Done
  gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic]
  mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic]
  nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed]

  The following might be related. If I open the GUI app Logs I see the 
following error:
  Failed to start xdg-desktop-portal.service - Portal service.

  If I write the following command:

  $ journalctl --user --unit=xdg-desktop-portal

  I get:

  Oct 31 18:19:20 my-pc-hostname systemd[39536]: Starting 
xdg-desktop-portal.service - Portal service...
  Oct 31 18:20:10 my-pc-hostname 

[Desktop-packages] [Bug 2041845] Re: Notifies about some ancient downgrades on every boot

2023-10-31 Thread Mykola Yaroshenko
That's it.

pkcon offline-status
Status: Success
Updated google-chrome-stable-113.0.5672.126-1.amd64
Updated mdadm-4.2-0ubuntu2.amd64
Updated google-chrome-stable-113.0.5672.126-1.amd64
Updated mdadm-4.2-0ubuntu2.amd64

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

Title:
  Notifies about some ancient downgrades on every boot

Status in gnome-software package in Ubuntu:
  Incomplete
Status in packagekit package in Ubuntu:
  Incomplete

Bug description:
  Preparing for upgrade from 22.04 to 23.04 some packages were
  downgraded (or just marked as such?) and now update-notifier reminds
  me about them on every boot, this makes me likely to miss important
  upgrades available, because I tend now to dismiss it without looking.

  google-chrome-stable was upgraded many times since then, but I still
  get notifications about that 113.0... version. Btw, it says about
  downgrade from the current version!

  It's update-notifier/lunar,now 3.192.64 amd64

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: update-notifier 3.192.64
  ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 30 14:47:30 2023
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2016-11-26 (2529 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  SourcePackage: update-notifier
  UpgradeStatus: Upgraded to lunar on 2023-06-11 (140 days ago)
  upstart.update-notifier-release.log: вівторок, 14 серпня 2018 21:28:26 +0300 
new release available

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2041845/+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 2041845] Re: Notifies about some ancient downgrades on every boot

2023-10-31 Thread Mykola Yaroshenko
> you may want to see if pkcon get-updates shows the same issue.
pkcon get-updates
Getting updates [=] 
Loading cache   [=] 
Finished[=] 
There are no updates available at this time.

However notification says about installed updates, not available. For
some reason it just doesn't forget about it over time. I also have
`unattended-upgrades` installed, for which those notifications would
make sense - if it was something new.

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

Title:
  Notifies about some ancient downgrades on every boot

Status in gnome-software package in Ubuntu:
  Incomplete
Status in packagekit package in Ubuntu:
  Incomplete

Bug description:
  Preparing for upgrade from 22.04 to 23.04 some packages were
  downgraded (or just marked as such?) and now update-notifier reminds
  me about them on every boot, this makes me likely to miss important
  upgrades available, because I tend now to dismiss it without looking.

  google-chrome-stable was upgraded many times since then, but I still
  get notifications about that 113.0... version. Btw, it says about
  downgrade from the current version!

  It's update-notifier/lunar,now 3.192.64 amd64

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: update-notifier 3.192.64
  ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 30 14:47:30 2023
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2016-11-26 (2529 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  SourcePackage: update-notifier
  UpgradeStatus: Upgraded to lunar on 2023-06-11 (140 days ago)
  upstart.update-notifier-release.log: вівторок, 14 серпня 2018 21:28:26 +0300 
new release available

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2041845/+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 1951586] Re: Need option to specify wifi regulatory domain

2023-10-31 Thread Utkarsh Gupta
Is this fixed in Noble?

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

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  Fix Released
Status in NetworkManager:
  New
Status in netplan.io package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Incomplete
Status in netplan.io source package in Jammy:
  Triaged
Status in network-manager source package in Jammy:
  Incomplete
Status in netplan.io source package in Kinetic:
  Fix Released
Status in network-manager source package in Kinetic:
  Incomplete

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users 
can simply setup Ubuntu Server headless by putting the wifi configuration 
details in cloudinit/netplan's "network-config" on the FAT partition of the SD 
card: 
https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so 
may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions


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


Re: [Desktop-packages] [Bug 2023322] Re: GTK internal browser does not render with Nvidia drivers

2023-10-31 Thread Bart Burroughs
browser works now but sign in does not work. I enter my google credentials
and it just spins forever but never signs in to the account. Luckily I
bypassed this a long time ago just creating a direct app link to google
calendar so really don't need it but it is too bad Ubuntu can't seem to get
this fixed

On Thu, Oct 26, 2023 at 1:00 AM Daniel van Vugt <2023...@bugs.launchpad.net>
wrote:

> Verified working in webkit2gtk 2.42.1-2.
>
> Tested Nvidia 535 with both X11 and Wayland, in both Online Accounts and
> Ubuntu Desktop Guide.
>
>
> ** Changed in: webkit2gtk (Ubuntu)
>Status: In Progress => Fix Released
>
> ** Changed in: yelp (Ubuntu)
>Status: Triaged => Invalid
>
> ** Changed in: gnome-control-center (Ubuntu)
>Status: Triaged => Invalid
>
> ** Changed in: gnome-online-accounts (Ubuntu)
>Status: Triaged => Invalid
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2027737).
> https://bugs.launchpad.net/bugs/2023322
>
> Title:
>   GTK internal browser does not render with Nvidia drivers
>
> Status in Webkit:
>   Confirmed
> Status in gnome-control-center package in Ubuntu:
>   Invalid
> Status in gnome-online-accounts package in Ubuntu:
>   Invalid
> Status in webkit2gtk package in Ubuntu:
>   Fix Released
> Status in yelp package in Ubuntu:
>   Invalid
> Status in webkit2gtk package in Debian:
>   Fix Released
>
> Bug description:
>   When I go into Settings > Online Accounts > Google, I get to the
>   prompt for email address, once in a while it stops accepting input
>   there. But often I can get to the password screen. Once I do, I can't
>   type anything or paste anything.
>
>   This is a fresh install of Ubuntu 23.04 and I have installed all
>   updates.
>
>   Nothing in /var/crash
>
>   Jun 08 11:15:59 CCW-HAL systemd[3523]:
> vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU
> time.
>   Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion
> 'closure->ref_count > 0' failed
>   Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion
> 'closure->ref_count > 0' failed
>   Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion
> 'closure->ref_count > 0' failed
>   Jun 08 11:16:29 CCW-HAL systemd[3523]: Started
> app-gnome-org.gnome.Terminal-10924.scope - Application launched by
> gnome-shell.
>   Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552]
> Activating via systemd: service name='org.gnome.Terminal'
> unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000
> pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined")
>   Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting
> gnome-terminal-server.service - GNOME Terminal Server...
>   Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552]
> Successfully activated service 'org.gnome.Terminal'
>   Jun 08 11:16:29 CCW-HAL systemd[3523]: Started
> gnome-terminal-server.service - GNOME Terminal Server.
>   Jun 08 11:16:29 CCW-HAL systemd[3523]: Started
> vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process
> 10955 launched by gnome-terminal-server process 10931.
>   Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account:
> Child process exited with code 1
>   Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]:
> GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock
> if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found
> default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is
> not thread-safe and should not be used after threads are createdGLib-GIO:
> _g_io_module_get_default: Found default implementation dconf
> (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all
> providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: -
> windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: -
> imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos
> providerGLib-GIO: _g_io_module_get_default: Found default implementation
> gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account:
> Dialog was dismissed
>   Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not
> map pid: Could not determine pid namespace: Could not find instance-id in
> process's /.flatpak-info
>   Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session
> opened for user root(uid=0) by (uid=0)
>   Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts
> --report /etc/cron.hourly)
>   Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session
> closed for user root
>   Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at
> 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU
> 2 (core 2, socket 0)
>   Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at
> 0x55bd22ad9ab2.
>   Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window 

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

2023-10-31 Thread Utkarsh Gupta
** Also affects: mesa (Ubuntu Noble)
   Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
   Status: Fix Released

** Also affects: ubuntu-settings (Ubuntu Noble)
   Importance: Undecided
 Assignee: Dave Jones (waveform)
   Status: Fix Released

** Also affects: pipewire (Ubuntu Noble)
   Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
   Status: Invalid

** Also affects: linux-meta-raspi (Ubuntu Noble)
   Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
   Status: Fix Released

** Also affects: linux-raspi (Ubuntu Noble)
   Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
   Status: Fix Released

** Also affects: libcamera (Ubuntu Noble)
   Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
   Status: Triaged

** Also affects: rpi-eeprom (Ubuntu Noble)
   Importance: Undecided
 Assignee: Dave Jones (waveform)
   Status: Fix Released

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

Title:
  [FFe] Raspberry Pi 5 support

Status in Release Notes for Ubuntu:
  Fix Released
Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Invalid
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in libcamera source package in Noble:
  Triaged
Status in linux-meta-raspi source package in Noble:
  Fix Released
Status in linux-raspi source package in Noble:
  Fix Released
Status in mesa source package in Noble:
  Fix Released
Status in pipewire source package in Noble:
  Invalid
Status in rpi-eeprom source package in Noble:
  Fix Released
Status in ubuntu-settings source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

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

  [ Test Plan ]

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

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

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

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

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

  [ Other Info ]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+subscriptions


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


[Desktop-packages] [Bug 2042350] Re: When switching workspaces with mouse, no dot in indicator

2023-10-31 Thread Marc Deslauriers
Reproduced this on mantic also.

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

Title:
  When switching workspaces with mouse, no dot in indicator

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

Bug description:
  When switching between workspaces with ctrl-alt-arrow, there is an
  indicator that pops up with a bright dot highlighting which workspace
  is being switched to. When switching between workspaces by scrolling
  the mouse wheel over the "show applications" icon, the indicator pops
  up but doesn't draw the bright dot to indicate which workspace is
  becoming active.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.2.1
  ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
  Uname: Linux 6.1.0-1025-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 13:07:17 2023
  InstallationDate: Installed on 2023-10-24 (7 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  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/2042350/+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 2042350] [NEW] When switching workspaces with mouse, no dot in indicator

2023-10-31 Thread Marc Deslauriers
Public bug reported:

When switching between workspaces with ctrl-alt-arrow, there is an
indicator that pops up with a bright dot highlighting which workspace is
being switched to. When switching between workspaces by scrolling the
mouse wheel over the "show applications" icon, the indicator pops up but
doesn't draw the bright dot to indicate which workspace is becoming
active.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.2.1
ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
Uname: Linux 6.1.0-1025-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 31 13:07:17 2023
InstallationDate: Installed on 2023-10-24 (7 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  When switching workspaces with mouse, no dot in indicator

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

Bug description:
  When switching between workspaces with ctrl-alt-arrow, there is an
  indicator that pops up with a bright dot highlighting which workspace
  is being switched to. When switching between workspaces by scrolling
  the mouse wheel over the "show applications" icon, the indicator pops
  up but doesn't draw the bright dot to indicate which workspace is
  becoming active.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.2.1
  ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
  Uname: Linux 6.1.0-1025-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 13:07:17 2023
  InstallationDate: Installed on 2023-10-24 (7 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  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/2042350/+subscriptions


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


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

2023-10-31 Thread Utkarsh Gupta
Wait, I think this is already fixed in Noble, isn't it? In that case, if
someone could confirm, could they adjust the bug status for Noble?

** Also affects: gnome-shell (Ubuntu Noble)
   Importance: High
   Status: Triaged

** Also affects: gnome-themes-extra (Ubuntu Noble)
   Importance: Undecided
   Status: Invalid

** Also affects: yaru-theme (Ubuntu Noble)
   Importance: Undecided
   Status: Won't Fix

** Changed in: gnome-themes-extra (Ubuntu Noble)
   Status: Invalid => New

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

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

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

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

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


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


[Desktop-packages] [Bug 2036817]

2023-10-31 Thread julien2412
(In reply to Eric from comment #31)
> How are you running version 24.2.0.0 of LibreOffice? I thought 7.6.2.x was
> the latest?
Yes 7.6.2 is the last non dev and non beta release.

Now there are alpha versions (master branch which corresponds nowadays to 
"24.2") here:
https://dev-builds.libreoffice.org/daily/master/

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

Title:
  soffice.bin crashed with SIGSEGV in
  
com::sun::star::uno::Reference::operator->()

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Occurred when exiting Calc/

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 20 13:44:57 2023
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2023-09-17 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2)
  ProcAttrCurrent: libreoffice-soffice (complain)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi
   PC (0x7f4aee4abf8e) ok
   source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned 
int, com::sun::star::uno::Reference const&) () 
from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::OAccessibleContextWrapper::disposing() () from 
/usr/lib/libreoffice/program/libmergedlo.so
   cppu::WeakComponentImplHelperBase::dispose() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
   cppu::WeakComponentImplHelperBase::release() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
  Title: soffice.bin crashed with SIGSEGV in 
comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()
  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/df-libreoffice/+bug/2036817/+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 2036817]

2023-10-31 Thread Erbenton
How are you running version 24.2.0.0 of LibreOffice? I thought 7.6.2.x
was the latest?

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

Title:
  soffice.bin crashed with SIGSEGV in
  
com::sun::star::uno::Reference::operator->()

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Occurred when exiting Calc/

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 20 13:44:57 2023
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2023-09-17 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2)
  ProcAttrCurrent: libreoffice-soffice (complain)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi
   PC (0x7f4aee4abf8e) ok
   source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned 
int, com::sun::star::uno::Reference const&) () 
from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::OAccessibleContextWrapper::disposing() () from 
/usr/lib/libreoffice/program/libmergedlo.so
   cppu::WeakComponentImplHelperBase::dispose() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
   cppu::WeakComponentImplHelperBase::release() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
  Title: soffice.bin crashed with SIGSEGV in 
comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()
  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/df-libreoffice/+bug/2036817/+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 2036817]

2023-10-31 Thread Michael Weghorn
(In reply to Eric from comment #28)
> LibreOffice 7.6.2.1 on opensuse Tumbleweed. This just crashed when i closed
> it. It's a simple spreadsheet I am attaching, but the crash happens randomly
> at close, not every time.

Didn't crash for me in a quick test, but that doesn't necessarily say
much as you say it's random. In any case, unless this is known to be
related to the issue originally described here, I think this should be
handled in a separate bug report, ideally with some more details on what
might help to trigger it.

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: df79eedf6989ab4c2913a23a7e72079bd719168b
CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded

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

Title:
  soffice.bin crashed with SIGSEGV in
  
com::sun::star::uno::Reference::operator->()

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Occurred when exiting Calc/

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 20 13:44:57 2023
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2023-09-17 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2)
  ProcAttrCurrent: libreoffice-soffice (complain)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi
   PC (0x7f4aee4abf8e) ok
   source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned 
int, com::sun::star::uno::Reference const&) () 
from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::OAccessibleContextWrapper::disposing() () from 
/usr/lib/libreoffice/program/libmergedlo.so
   cppu::WeakComponentImplHelperBase::dispose() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
   cppu::WeakComponentImplHelperBase::release() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
  Title: soffice.bin crashed with SIGSEGV in 
comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()
  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/df-libreoffice/+bug/2036817/+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 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)

2023-10-31 Thread hifron
In Krita there could be seen(and set) various colour profiles ICC
standards for images(could be seen on Create New Image).

If some vague generated colour profile for unsupported monitors or
hardware vendors uninterested for such GNOME thing(may be different in
other DE?) is lack of corporate funding interest on this area, but at
least CMYK colour profile standard means that such image should looked
same on monitor as printed, but todays advanced monitors support
sometimes 10bit colours or 8+2computed and also not only advanced SRGB
~100% coverage of colours, but it is also towards 100% DCI-P3 coverage
of possible colours and such thing should colour profile support and if
"generated" don't, problem occurs(or shit images). Now is also OKLCH
colour standard instead of RGB in CSS web.

More on advancement on this area in articles:
https://evilmartians.com/chronicles/oklch-a-color-picker-made-to-help-think-perceptively
and
https://evilmartians.com/chronicles/oklch-in-css-why-quit-rgb-hsl

Adobe software is maybe long standard in this area(maybe with web apps),
but industry is much wider...

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

Title:
  Images are washed out or colors are skewed in some apps (particularly
  Image Viewer and Chrome)

Status in Eye of GNOME:
  New
Status in GNOME Shell:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in colord package in Ubuntu:
  Confirmed
Status in eog package in Ubuntu:
  Confirmed
Status in inkscape package in Ubuntu:
  Confirmed

Bug description:
  Images are washed out or colors are skewed in some apps, notably
  Chrome/Chromium and Image Viewer (eog).

  Workaround:

  1. Settings > Colour > turn off the toggle switch for your monitor.

  2. Restart any affected apps.

  Originally reported in
  https://bugzilla.gnome.org/show_bug.cgi?id=675645

To manage notifications about this bug go to:
https://bugs.launchpad.net/eog/+bug/938751/+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 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception

2023-10-31 Thread Bug Watch Updater
** Changed in: linux
   Status: Unknown => New

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

Title:
  22.04.3, zen 4 7840, screen turn white exception

Status in Linux:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  New
Status in mesa source package in Jammy:
  New
Status in linux source package in Lunar:
  New
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New
Status in linux source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in mesa source package in Mantic:
  New
Status in linux source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  Invalid
Status in mesa source package in Noble:
  New

Bug description:
  My screen suddenly turned completely white, then only the bottom half
  was white, but I can still operate the application window. When moving
  the application window, the bottom half of the screen turns the Ubuntu
  theme color.

  Only lock and unlock the screen or turn off the screen can fix the
  situation.

  There are some photo about the exception attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3
  Uname: Linux 6.5.0-1006-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 12:26:24 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3818]
  InstallationDate: Installed on 2023-10-30 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: LENOVO 83AM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem 
root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2023
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MKCN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76479 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: XiaoXinPro 14 APH8
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8:
  dmi.product.family: XiaoXinPro 14 APH8
  dmi.product.name: 83AM
  dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8
  dmi.product.version: XiaoXinPro 14 APH8
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.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-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2042054/+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 2042042] Re: Browser does not remember workspace after leaving full screen video

2023-10-31 Thread Daniel LaSalle
After more testing it seems that regardless on which workspace the
browser was in before going into full screen that it will end up on the
opposite workspace after getting unmaximized.

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

Title:
  Browser does not remember workspace after leaving full screen video

Status in xorg package in Ubuntu:
  New

Bug description:
  Using 2x screens in portrait mode, if I display my browser on the
  right-side panel of workspace 1, watch a video and full screen it,
  after I  off the video the browser will now be displayed on the
  left-side panel of workspace 1.

  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
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Mon Oct 30 23:06:47 2023
  DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / 
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
  InstallationDate: Installed on 2023-04-14 (199 days ago)
  InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu--mate-root ro ipv6.disable=1 pcie_aspm=off 
ipv6.disable=1 pcie_aspm=off
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (17 days ago)
  dmi.bios.date: 03/13/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6063
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.cron.daily.apport: [deleted]
  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.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/xorg/+bug/2042042/+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 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception

2023-10-31 Thread Mario Limonciello
It's unclear if this is a BIOS, mesa or kernel bug at this time, but
it's certainly not an Xorg bug as it was reproduced in Wayland.

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

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2954
   https://gitlab.freedesktop.org/drm/amd/-/issues/2954

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/amd/-/issues/2954
   Importance: Unknown
   Status: Unknown

** Also affects: linux-oem-6.5 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mesa (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.5 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-6.5 (Ubuntu)
   Status: New => Invalid

** Also affects: mesa (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.5 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: mesa (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.5 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: mesa (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.5 (Ubuntu Noble)
   Importance: Undecided
   Status: Invalid

** Changed in: linux-oem-6.5 (Ubuntu Mantic)
   Status: New => Invalid

** Changed in: linux-oem-6.5 (Ubuntu Lunar)
   Status: New => Invalid

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

Title:
  22.04.3, zen 4 7840, screen turn white exception

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  New
Status in mesa source package in Jammy:
  New
Status in linux source package in Lunar:
  New
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New
Status in linux source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in mesa source package in Mantic:
  New
Status in linux source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  Invalid
Status in mesa source package in Noble:
  New

Bug description:
  My screen suddenly turned completely white, then only the bottom half
  was white, but I can still operate the application window. When moving
  the application window, the bottom half of the screen turns the Ubuntu
  theme color.

  Only lock and unlock the screen or turn off the screen can fix the
  situation.

  There are some photo about the exception attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3
  Uname: Linux 6.5.0-1006-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 12:26:24 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3818]
  InstallationDate: Installed on 2023-10-30 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: LENOVO 83AM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem 
root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2023
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MKCN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76479 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: XiaoXinPro 14 APH8
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8:
  dmi.product.family: XiaoXinPro 14 APH8
  dmi.product.name: 83AM
  

[Desktop-packages] [Bug 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception

2023-10-31 Thread Mario Limonciello
** Package changed: xorg (Ubuntu) => mesa (Ubuntu)

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

Title:
  22.04.3, zen 4 7840, screen turn white exception

Status in mesa package in Ubuntu:
  New

Bug description:
  My screen suddenly turned completely white, then only the bottom half
  was white, but I can still operate the application window. When moving
  the application window, the bottom half of the screen turns the Ubuntu
  theme color.

  Only lock and unlock the screen or turn off the screen can fix the
  situation.

  There are some photo about the exception attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3
  Uname: Linux 6.5.0-1006-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 12:26:24 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3818]
  InstallationDate: Installed on 2023-10-30 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: LENOVO 83AM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem 
root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2023
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MKCN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76479 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: XiaoXinPro 14 APH8
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8:
  dmi.product.family: XiaoXinPro 14 APH8
  dmi.product.name: 83AM
  dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8
  dmi.product.version: XiaoXinPro 14 APH8
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.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-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2042054/+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 2007704] Re: Nautilus-admin does not install Edit as Administrator

2023-10-31 Thread Sebastien Bacher
** Package changed: nautilus (Ubuntu) => nautilus-admin (Ubuntu)

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

Title:
  Nautilus-admin does not install Edit as Administrator

Status in nautilus-admin package in Ubuntu:
  New

Bug description:
  After installing the nautilus-admin package, the Edit as Administrator
  feature does not show up in the right-click context menu. I am able to
  workaround with sudo nautilus, but it's not as nice.

  This is Ubuntu 22.04.1 LTS in a UTM VM on a macOS Ventura M2 Mac Mini.

  nautilus-admin version 1.1.9-3.1

  This login is with Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.2-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic aarch64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 17 14:49:43 2023
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' 
b"'list-view'"
  InstallationDate: Installed on 2023-02-14 (2 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
arm64 (20220809)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.3-0ubuntu2
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6
   python3-nautilus  1.2.3-3.1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus-admin/+bug/2007704/+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 2041845] Re: Notifies about some ancient downgrades on every boot

2023-10-31 Thread Julian Andres Klode
The messages in the screenshot seem to be from gnome-software which is a
third party software in universe and not part of the Ubuntu user
experience.

It's not clear why it would show downgrades to packages no longer in the
cache. gnome-software uses PackageKit so you may want to see if pkcon
get-updates shows the same issue.

** Package changed: update-notifier (Ubuntu) => gnome-software (Ubuntu)

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

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

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

Title:
  Notifies about some ancient downgrades on every boot

Status in gnome-software package in Ubuntu:
  Incomplete
Status in packagekit package in Ubuntu:
  Incomplete

Bug description:
  Preparing for upgrade from 22.04 to 23.04 some packages were
  downgraded (or just marked as such?) and now update-notifier reminds
  me about them on every boot, this makes me likely to miss important
  upgrades available, because I tend now to dismiss it without looking.

  google-chrome-stable was upgraded many times since then, but I still
  get notifications about that 113.0... version. Btw, it says about
  downgrade from the current version!

  It's update-notifier/lunar,now 3.192.64 amd64

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: update-notifier 3.192.64
  ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 30 14:47:30 2023
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2016-11-26 (2529 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  SourcePackage: update-notifier
  UpgradeStatus: Upgraded to lunar on 2023-06-11 (140 days ago)
  upstart.update-notifier-release.log: вівторок, 14 серпня 2018 21:28:26 +0300 
new release available

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2041845/+subscriptions


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


Re: [Desktop-packages] [Bug 1990005] Re: Visible columns option missing function

2023-10-31 Thread Eugenio
ok, I'll try with version 22.10 even if it's not LTS


cordiali saluti


THS INFORMATICA
Eugenio D. Giannotti
(+39)  *339 888 16 82*


Il giorno mar 31 ott 2023 alle ore 15:12 Bug Watch Updater <
1990...@bugs.launchpad.net> ha scritto:

> ** Changed in: nautilus
>Status: Unknown => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1990005
>
> Title:
>   Visible columns option missing function
>
> Status in Nautilus:
>   Fix Released
> Status in nautilus package in Ubuntu:
>   Fix Released
>
> Bug description:
>   In Ubuntu 20.04 nautilus setting Preferences > List Columns was
> affecting display on ALL the folders and was possible to remove the column
> 'Star'
>   while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible
> Columns' affect only the current folder and can't remove the 'Star' column.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.10
>   Package: nautilus 1:43~rc-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
>   Uname: Linux 5.19.0-15-generic x86_64
>   ApportVersion: 2.23.0-0ubuntu2
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Sep 16 20:00:16 2022
>   GsettingsChanges:
>b'org.gnome.nautilus.preferences' b'default-folder-viewer'
> b"'list-view'"
>b'org.gnome.nautilus.window-state' b'initial-size' b'(1064, 734)'
>   InstallationDate: Installed on 2022-09-08 (8 days ago)
>   InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908)
>   SourcePackage: nautilus
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   usr_lib_nautilus:
>file-roller   43~alpha-1
>nautilus-extension-gnome-terminal 3.45.90-1ubuntu1
>python3-nautilus  4.0~alpha-2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nautilus/+bug/1990005/+subscriptions
>
>

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

Title:
  Visible columns option missing function

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

Bug description:
  In Ubuntu 20.04 nautilus setting Preferences > List Columns was affecting 
display on ALL the folders and was possible to remove the column 'Star'
  while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible Columns' 
affect only the current folder and can't remove the 'Star' column.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 16 20:00:16 2022
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1064, 734)'
  InstallationDate: Installed on 2022-09-08 (8 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43~alpha-1
   nautilus-extension-gnome-terminal 3.45.90-1ubuntu1
   python3-nautilus  4.0~alpha-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1990005/+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 2041845] [NEW] Notifies about some ancient downgrades on every boot

2023-10-31 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Preparing for upgrade from 22.04 to 23.04 some packages were downgraded
(or just marked as such?) and now update-notifier reminds me about them
on every boot, this makes me likely to miss important upgrades
available, because I tend now to dismiss it without looking.

google-chrome-stable was upgraded many times since then, but I still get
notifications about that 113.0... version. Btw, it says about downgrade
from the current version!

It's update-notifier/lunar,now 3.192.64 amd64

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: update-notifier 3.192.64
ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 30 14:47:30 2023
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2016-11-26 (2529 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
SourcePackage: update-notifier
UpgradeStatus: Upgraded to lunar on 2023-06-11 (140 days ago)
upstart.update-notifier-release.log: вівторок, 14 серпня 2018 21:28:26 +0300 
new release available

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug lunar wayland-session
-- 
Notifies about some ancient downgrades on every boot
https://bugs.launchpad.net/bugs/2041845
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-software in Ubuntu.

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


[Desktop-packages] [Bug 1975638] Re: Broken background portal autostart in 1.14.3

2023-10-31 Thread Mantas Kriaučiūnas
It seems bug #2018440 (No such interface
“org.freedesktop.portal.Background”) is a duplicate, right?

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

Title:
  Broken background portal autostart in 1.14.3

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Jammy:
  Fix Released

Bug description:
  - Impact

  With 1.14.3 the background portal creates a broken autostart file (it
  sends an incorrectly quoted app ID to implementations). This means
  apps like EasyEffects or Pika Backup cannot rely on the background
  portal to create a working autostart file. Please update to xdg-
  desktop-portal 1.14.4 https://github.com/flatpak/xdg-desktop-
  portal/releases/tag/1.14.4 which fixes this issue.

  - Test Case

  1. Install ASHPD Demo
  https://flathub.org/apps/details/com.belmoussaoui.ashpd.demo from
  Flathub

  2. Within the app make a background portal request with auto start
  enabled (you must accept the prompt from GNOME Shell)

  3. Note the contents of
  ~/.config/autostart/com.belmoussaoui.ashpd.demo.desktop is a desktop
  file, however the exec key’s value has an app id with quotes, making
  it invalid.

  4. After logging out and in or restarting, the app will not already be
  running, even though it previously asked the portal API for it to be
  auto started.

  The same steps can be repeated with EasyEffects from Flathub instead
  of ASHPD Demo, note the EasyEffects switch is named "Start Service at
  Login" within EasyEffects' preferences menu.

  When the bug is fixed, the created desktop file for auto start is
  valid and the app will start after login.

  - Regression potential

  The update is a new minor version including the fix for that bug and
  translation updates (which are going to be imported by launchpad but
  not part of the deb on Ubuntu)

  The codepath change is specific to flatpak commandline parsing so
  check that flatpaks still start correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1975638/+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 2018440] Re: No such interface “org.freedesktop.portal.Background”

2023-10-31 Thread Mantas Kriaučiūnas
Maybe someone could backport xdg-desktop-portal 1.16 to Ubuntu 22.04,
like some other features were backported, see bug #1975638 (Broken
background portal autostart in 1.14.3) for example?

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

Title:
  No such interface “org.freedesktop.portal.Background”

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

Bug description:
  Hello,

  Having an issue with PikaBackup's background process. Using the
  flatpak. Running linux mint 21.1; but the package is from Ubuntu

  xdg-desktop-portal - 1.14.4-1ubuntu2~22.04.1
  xdg-desktop-portal-gtk - 1.14.0-1build1
  flatpak - 1.12.7-1

  Output of flatpak run -v when trying to configure scheduled backups

  ```
  pika-backup:2): pika-backup-WARNING **: 10:21:10.646: src/ui/utils.rs:134:0: 
Background portal response: 
Zbus(MethodError(OwnedErrorName(ErrorName(Str(Owned("org.freedesktop.DBus.Error.UnknownMethod",
 Some("No such interface “org.freedesktop.portal.Background” on object at path 
/org/freedesktop/portal/desktop"), Msg { type: Error, sender: 
UniqueName(Str(Borrowed(":1.74"))), reply-serial: 5, body: Signature("s") }))

  (pika-backup:2): pika-backup-WARNING **: 10:21:10.646: src/ui/utils.rs:377:0: 
Displaying error:
Request to run in background failed
The system does not support running Pika Backup in the background. 
Scheduled backup functionality and continuing backups in the background will 
not be available. This is either a malfunction, misconfi
  …
  issue in your distribution issue tracker.

  ZBus Error: org.freedesktop.DBus.Error.UnknownMethod: No such interface 
“org.freedesktop.portal.Background” on object at path 
/org/freedesktop/portal/desktop
  ```

  Also reported to xdg-desktop-portal github.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/2018440/+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 2042077] Re: Dark mode only works for some GTK windows

2023-10-31 Thread Nathan Teodosio
ADW_COLOR_SCHEME_FORCE_DARK=. fixes it but only in a Gnome environment.

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

Title:
  Dark mode only works for some GTK windows

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Works for nautilus, gnome-{power-statistics,disks}.

  Doesn't work for gnome-{control-center,text-
  editor,calculator,calendar}, which remain on light mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  Date: Tue Oct 31 10:52:00 2023
  DisplayManager:
   
  InstallationDate: Installed on 2022-05-16 (533 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-01-17 (287 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042077/+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 2042077] [NEW] Dark mode only works for some GTK windows

2023-10-31 Thread Nathan Teodosio
Public bug reported:

Works for nautilus, gnome-{power-statistics,disks}.

Doesn't work for gnome-{control-center,text-editor,calculator,calendar},
which remain on light mode.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
Date: Tue Oct 31 10:52:00 2023
DisplayManager:
 
InstallationDate: Installed on 2022-05-16 (533 days ago)
InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
RelatedPackageVersions: mutter-common 45.0-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-01-17 (287 days ago)

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


** Tags: amd64 apport-bug mantic

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

Title:
  Dark mode only works for some GTK windows

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Works for nautilus, gnome-{power-statistics,disks}.

  Doesn't work for gnome-{control-center,text-
  editor,calculator,calendar}, which remain on light mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  Date: Tue Oct 31 10:52:00 2023
  DisplayManager:
   
  InstallationDate: Installed on 2022-05-16 (533 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-01-17 (287 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042077/+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 1986845] Re: "send to" with thunderbird snap

2023-10-31 Thread frenchy82
I can confirm that "drop support for "Send file" via E-mail from file
managers" would be a very very sad news for users

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

Title:
  "send to" with thunderbird snap

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  
  On Ubuntu 22.04 

  If thunderbird snap is the default emailer:

  Right click on a file on the desktop, "send to" opens thunderbird for
  a new mail but without the attachment

  Doing the same from files opens the mail to be sent with the
  attachment (the file on the desktop)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1986845/+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 2031413] Re: Inherited NFSv4 ACLs are overwritten when moving a file

2023-10-31 Thread Bug Watch Updater
** Changed in: glib
   Status: Unknown => New

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

Title:
  Inherited NFSv4 ACLs are overwritten when moving a file

Status in GLib:
  New
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Ubuntu version: 22.04
  libglib2.0 version: libglib2.0-0_2.72.4-0ubuntu2.2

  We are mounting an NFS share from an NFS server (FreeBSD 13). Authorization to
  directories in that share is enforced through NFSv4 ACLs on the server. When
  copying or moving a file to the share, it will inherit ACLs from the 
destination
  directory.

  In most of the cases this works fine. However, when we move a file that has 
ACLs
  to a directory in the share using Nautilus or "gio move", the ACL inheritance
  goes wrong. The destination file will end up with the original ACLs (the ACLs 
it
  had in the source location) instead of the ACLs that are inherited by the
  destination directory.

  This behaviour changed when we upgraded from Ubuntu 20.04 to Ubuntu 22.04. In
  Ubuntu 20.04 the ACL inheritance worked as expected.

  I assume what happens is the following:
  1. A server-side move is performed
  2. The destination file is assigned ACLs (they are inherited from the 
destination directory)
  3. glib overwrites the ACLs of the destination file with the original ACLs

  To workaround the issue we patched glib and removed a call to
  g_file_set_attributes_from_info, see the attached patch. This brings the
  expected behaviour but may have unintended side effects.

  Steps to reproduce:
  1. on the server (FreeBSD): prepare two directories A and B and assign the 
following NFSv4 ACLs:

  # file: A
  # owner: root
  # group: wheel
  user:alice:rwx--daARWc--s:fd-:allow
  owner@:rwxp-daARWc--s:fd-:allow
  group@:--a-R-c--s:fd-:allow
   everyone@:--a-R-c--s:fd-:allow

  # file: B
  # owner: root
  # group: wheel
  user:alice:rwx--daARWc--s:fd-:allow
user:bob:rwx--daARWc--s:fd-:allow
  owner@:rwxp-daARWc--s:fd-:allow
  group@:--a-R-c--s:fd-:allow
   everyone@:--a-R-c--s:fd-:allow

  Note the inheritance flags (fd), which indicate that files in the
  directories will inherit the ACLs.

  2. on the client (Ubuntu): mount the NFS share to /mnt using credentials of 
user "alice"
  3. on the client: echo "hello world" > /mnt/A/test.txt
  4. on the server: list the ACLs of A/test.txt:

  # file: A/test.txt
  # owner: alice
  # group: wheel
  user:alice:rw---daARWc--s:--I:allow
  owner@:rw-p-daARWc--s:--I:allow
  group@:--a-R-c--s:--I:allow
   everyone@:--a-R-c--s:--I:allow

  5. on the client: gio move /mnt/A/test.txt /mnt/B/test.txt
  6. on the server: list the ACLs of B/test.txt

  # file: B/test.txt
  # owner: alice
  # group: wheel
  user:alice:rw---daARWc--s:--I:allow
  owner@:rw-p-daARWc--s:--I:allow
  group@:--a-R-c--s:--I:allow
   everyone@:--a-R-c--s:--I:allow

  We expected an ACE for user bob, but it is missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/2031413/+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 2042077] Screen shot

2023-10-31 Thread Nathan Teodosio
** Attachment added: "Screenshot from 2023-10-31
 10-47-43.png"
   
https://bugs.launchpad.net/bugs/2042077/+attachment/5714608/+files/Screenshot%20from%202023-10-31%0A%2010-47-43.png

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

Title:
  Dark mode only works for some GTK windows

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Works for nautilus, gnome-{power-statistics,disks}.

  Doesn't work for gnome-{control-center,text-
  editor,calculator,calendar}, which remain on light mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  Date: Tue Oct 31 10:52:00 2023
  DisplayManager:
   
  InstallationDate: Installed on 2022-05-16 (533 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-01-17 (287 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042077/+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 2039543] Re: Miss placed Hexchat icon when switching workspaces

2023-10-31 Thread Islam
** Also affects: gnome-shell-extension-appindicator
   Importance: Undecided
   Status: New

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

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

Title:
  Miss placed Hexchat icon when switching workspaces

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

Bug description:
  While switching workspaces, Hexchat icon in the app indicator appears
  bigger than the normal and in a wrong position then disappears.

  Please check the attached screen cast for details.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell-extension-appindicator 57-1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 11:17:05 2023
  InstallationDate: Installed on 2023-10-12 (5 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2039543/+subscriptions


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


Re: [Desktop-packages] [Bug 1990005] Re: Visible columns option missing function

2023-10-31 Thread Eugenio
but in version 22.04.03 LTS it doesn't seem right to me. But is it so
difficult to restore a very useful function?, I don't understand, but
thanks I will continue to use 20.04 LTS


cordiali saluti


THS INFORMATICA
Eugenio D. Giannotti
(+39)  *339 888 16 82*


Il giorno lun 30 ott 2023 alle ore 13:30 Sebastien Bacher <
1990...@bugs.launchpad.net> ha scritto:

> The issue should be fixed in the current version
>
> ** Also affects: nautilus via
>https://gitlab.gnome.org/GNOME/nautilus/-/issues/2496
>Importance: Unknown
>Status: Unknown
>
> ** Changed in: nautilus (Ubuntu)
>Status: Confirmed => Fix Released
>
> ** Changed in: nautilus (Ubuntu)
>  Assignee: Eugenio (thsgiannotti) => (unassigned)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1990005
>
> Title:
>   Visible columns option missing function
>
> Status in Nautilus:
>   Unknown
> Status in nautilus package in Ubuntu:
>   Fix Released
>
> Bug description:
>   In Ubuntu 20.04 nautilus setting Preferences > List Columns was
> affecting display on ALL the folders and was possible to remove the column
> 'Star'
>   while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible
> Columns' affect only the current folder and can't remove the 'Star' column.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.10
>   Package: nautilus 1:43~rc-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
>   Uname: Linux 5.19.0-15-generic x86_64
>   ApportVersion: 2.23.0-0ubuntu2
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Sep 16 20:00:16 2022
>   GsettingsChanges:
>b'org.gnome.nautilus.preferences' b'default-folder-viewer'
> b"'list-view'"
>b'org.gnome.nautilus.window-state' b'initial-size' b'(1064, 734)'
>   InstallationDate: Installed on 2022-09-08 (8 days ago)
>   InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908)
>   SourcePackage: nautilus
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   usr_lib_nautilus:
>file-roller   43~alpha-1
>nautilus-extension-gnome-terminal 3.45.90-1ubuntu1
>python3-nautilus  4.0~alpha-2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nautilus/+bug/1990005/+subscriptions
>
>

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

Title:
  Visible columns option missing function

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

Bug description:
  In Ubuntu 20.04 nautilus setting Preferences > List Columns was affecting 
display on ALL the folders and was possible to remove the column 'Star'
  while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible Columns' 
affect only the current folder and can't remove the 'Star' column.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 16 20:00:16 2022
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1064, 734)'
  InstallationDate: Installed on 2022-09-08 (8 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43~alpha-1
   nautilus-extension-gnome-terminal 3.45.90-1ubuntu1
   python3-nautilus  4.0~alpha-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1990005/+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 1698593] Re: [Blade, Realtek ALC298, Black Mic, Left] No sound at all

2023-10-31 Thread Goddard
2023 still having this issue here

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

Title:
  [Blade, Realtek ALC298, Black Mic, Left] No sound at all

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  I'm trying to get the mic from the combo jack on my Razer Blade
  working. Headphones are functioning perfectly, but the mic seems to be
  picking up on random data, unrelated to sound output or my
  surroundings. I know the jack is working as I dual-boot Windows, and
  it works great there.

  I've added the `options snd-hda-intel model=laptop-dmic` line as
  recommended in some other threads, and tried setting pin 0x18 to mic
  using hdajackretask, but it hasn't fixed it or made any difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   octy   1971 F...m pulseaudio
   /dev/snd/pcmC0D0p:   octy   1971 F...m pulseaudio
   /dev/snd/controlC0:  octy   1971 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Sat Jun 17 15:21:41 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-06 (72 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   octy   1971 F...m pulseaudio
   /dev/snd/pcmC0D0p:   octy   1971 F...m pulseaudio
   /dev/snd/controlC0:  octy   1971 F pulseaudio
  Symptom_Jack: Black Mic, Left
  Symptom_Type: No sound at all
  Title: [Blade, Realtek ALC298, Black Mic, Left] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (63 days ago)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-06-17T15:06:35.753276

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1698593/+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 2007160] Re: Image properties does nothing in lunar

2023-10-31 Thread Sebastien Bacher
** Changed in: nautilus (Ubuntu)
   Status: Incomplete => 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/2007160

Title:
  Image properties does nothing in lunar

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  When testing the current lunar (23.04) pre-installed desktop image for
  the Raspberry Pi, I attempted to retrieve the properties of a captured
  JPEG from nautilus:

  * Right click on a JPEG image
  * Select "Properties" item at the bottom
  * Click on the "Image Properties" link at the bottom of the dialog that opens

  However, nothing happens when clicking on the link. I presume this is
  meant to go to a page listing the details that nautilus used to
  display (resolution, etc). I tested with a couple of different JPEGs
  that display their properties correctly under jammy and kinetic. I'm
  happy to provide test images if required, but I don't think it's
  specific to the JPEGs I'm using.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2007160/+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 2041857] Re: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10

2023-10-31 Thread Paul White
** Package changed: ubuntu => firefox (Ubuntu)

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

Title:
  package firefox (not installed) failed to install/upgrade: new firefox
  package pre-installation script subprocess returned error exit status
  10

Status in firefox package in Ubuntu:
  New

Bug description:
  I used QuickCreate in Windows 11 Hyper-V to create a basic 22.04 system 
(22.04.3 LTS).
  - No special options selected.
  - Install worked as expected.
  - The error in summary occurred during the large software update 
automatically triggered right after first login.

  However, the system (including Firefox) is still up and apparently
  running fine. Will try to manually update Firefox.

  NB: there was a major update to the Windows 11 host yesterday.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct 30 10:42:57 2023
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 10
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  Snap: firefox 100.0-2 ()
  Snap.Changes: no changes found
  Title: package firefox (not installed) failed to install/upgrade: new firefox 
package pre-installation script subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2041857/+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 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception

2023-10-31 Thread zhilong hwang
the screen turn into full white or full black or full strips randomly

** Attachment added: "1698726477_aX6I7W6U.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042054/+attachment/5714568/+files/1698726477_aX6I7W6U.jpg

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

Title:
  22.04.3, zen 4 7840, screen turn white exception

Status in xorg package in Ubuntu:
  New

Bug description:
  My screen suddenly turned completely white, then only the bottom half
  was white, but I can still operate the application window. When moving
  the application window, the bottom half of the screen turns the Ubuntu
  theme color.

  Only lock and unlock the screen or turn off the screen can fix the
  situation.

  There are some photo about the exception attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3
  Uname: Linux 6.5.0-1006-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 12:26:24 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3818]
  InstallationDate: Installed on 2023-10-30 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: LENOVO 83AM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem 
root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2023
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MKCN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76479 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: XiaoXinPro 14 APH8
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8:
  dmi.product.family: XiaoXinPro 14 APH8
  dmi.product.name: 83AM
  dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8
  dmi.product.version: XiaoXinPro 14 APH8
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.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-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042054/+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 2034986] Re: some text became unreadable during a distribution upgrade

2023-10-31 Thread Nick Rosbrook
Because upgrades are not enabled yet for mantic -> noble, we still
cannot explicitly verify the XDG_SESSION_TYPE fix for mantic. However,
(a) since this exact patch was verified for lunar -> mantic, (b) this
patch relates to upgrading *from* mantic rather than *to* mantic, and
(c) we do not want to further delay upgrades to mantic, I believe it is
reasonable to release ubuntu-release-upgrader to mantic-updates without
explicit verification of the XDG_SESSION_TYPE fix.

Hence, I am marking this bug as verified, and am requesting that the SRU
team accepts this rationale.

** Tags removed: verification-needed-mantic
** Tags added: verification-done-mantic

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

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 2041825] Re: Saving a wireguard VPN connection fails

2023-10-31 Thread Sebastien Bacher
Thanks for providing the details

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => New

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => High

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

Title:
  Saving a wireguard VPN connection fails

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

Bug description:
  Adding a new Wireguard VPN connection fails as it isn't shown on the
  GUI under "VPN" (like openvpn connection is).

  this is on 23.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2041825/+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 1990005] Re: Visible columns option missing function

2023-10-31 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/1990005

Title:
  Visible columns option missing function

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

Bug description:
  In Ubuntu 20.04 nautilus setting Preferences > List Columns was affecting 
display on ALL the folders and was possible to remove the column 'Star'
  while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible Columns' 
affect only the current folder and can't remove the 'Star' column.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 16 20:00:16 2022
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1064, 734)'
  InstallationDate: Installed on 2022-09-08 (8 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43~alpha-1
   nautilus-extension-gnome-terminal 3.45.90-1ubuntu1
   python3-nautilus  4.0~alpha-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1990005/+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 2036444] Re: s390x tests regression

2023-10-31 Thread Launchpad Bug Tracker
This bug was fixed in the package libsoup3 - 3.4.4-1

---
libsoup3 (3.4.4-1) unstable; urgency=medium

  * New upstream release
- Fix regression seen in Ubuntu's s390s autopkgtest (LP: #2036444)

 -- Jeremy Bícha   Thu, 26 Oct 2023 20:24:22 -0400

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

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

Title:
  s390x tests regression

Status in libsoup3 package in Ubuntu:
  Fix Released

Bug description:
  https://autopkgtest.ubuntu.com/packages/libs/libsoup3/mantic/s390x

  Reported upstream now as
  https://gitlab.gnome.org/GNOME/libsoup/-/issues/365

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup3/+bug/2036444/+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 2042054] [NEW] 22.04.3, zen 4 7840, screen turn white exception

2023-10-31 Thread zhilong hwang
Public bug reported:

My screen suddenly turned completely white, then only the bottom half
was white, but I can still operate the application window. When moving
the application window, the bottom half of the screen turns the Ubuntu
theme color.

Only lock and unlock the screen or turn off the screen can fix the
situation.

There are some photo about the exception attached.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3
Uname: Linux 6.5.0-1006-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 31 12:26:24 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo Device [17aa:3818]
InstallationDate: Installed on 2023-10-30 (1 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: LENOVO 83AM
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem 
root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/08/2023
dmi.bios.release: 1.27
dmi.bios.vendor: LENOVO
dmi.bios.version: MKCN27WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76479 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: XiaoXinPro 14 APH8
dmi.ec.firmware.release: 1.27
dmi.modalias: 
dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8:
dmi.product.family: XiaoXinPro 14 APH8
dmi.product.name: 83AM
dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8
dmi.product.version: XiaoXinPro 14 APH8
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.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-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

** Attachment added: "1698726947_bPTLiRIb.jpg"
   
https://bugs.launchpad.net/bugs/2042054/+attachment/5714550/+files/1698726947_bPTLiRIb.jpg

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

Title:
  22.04.3, zen 4 7840, screen turn white exception

Status in xorg package in Ubuntu:
  New

Bug description:
  My screen suddenly turned completely white, then only the bottom half
  was white, but I can still operate the application window. When moving
  the application window, the bottom half of the screen turns the Ubuntu
  theme color.

  Only lock and unlock the screen or turn off the screen can fix the
  situation.

  There are some photo about the exception attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3
  Uname: Linux 6.5.0-1006-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 12:26:24 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3818]
  InstallationDate: Installed on 2023-10-30 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: LENOVO 83AM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem 
root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2023
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MKCN27WW
  dmi.board.asset.tag: NO Asset Tag
  

[Desktop-packages] [Bug 2042072] [NEW] Frozen during Screenrecording

2023-10-31 Thread Dhishan Kudwalli
Public bug reported:

When I try screenrecording using Ctrl + Alt + Shift + R the system gets
frozen and unresponsive to any inputs. I'm  having to restart the PC
using power button.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-screenshot 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126
Uname: Linux 5.15.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 31 13:28:55 2023
InstallationDate: Installed on 2023-10-10 (20 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
SourcePackage: gnome-screenshot
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Frozen during Screenrecording

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  When I try screenrecording using Ctrl + Alt + Shift + R the system
  gets frozen and unresponsive to any inputs. I'm  having to restart the
  PC using power button.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 13:28:55 2023
  InstallationDate: Installed on 2023-10-10 (20 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/2042072/+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 2042042] [NEW] Browser does not remember workspace after leaving full screen video

2023-10-31 Thread Daniel LaSalle
Public bug reported:

Using 2x screens in portrait mode, if I display my browser on the right-
side panel of workspace 1, watch a video and full screen it, after I
 off the video the browser will now be displayed on the left-side
panel of workspace 1.

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
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Mon Oct 30 23:06:47 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
 virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
InstallationDate: Installed on 2023-04-14 (199 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu--mate-root ro ipv6.disable=1 pcie_aspm=off 
ipv6.disable=1 pcie_aspm=off
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (17 days ago)
dmi.bios.date: 03/13/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6063
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.cron.daily.apport: [deleted]
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.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

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


** Tags: amd64 apport-bug mantic ubuntu

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

Title:
  Browser does not remember workspace after leaving full screen video

Status in xorg package in Ubuntu:
  New

Bug description:
  Using 2x screens in portrait mode, if I display my browser on the
  right-side panel of workspace 1, watch a video and full screen it,
  after I  off the video the browser will now be displayed on the
  left-side panel of workspace 1.

  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
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Mon Oct 30 23:06:47 2023
  DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / 
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
  InstallationDate: Installed on 2023-04-14 (199 days ago)
  InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  MachineType: {report['dmi.sys.vendor']} 

[Desktop-packages] [Bug 2023183] Re: network-manager autokpgtest failure (nm.py)

2023-10-31 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 1.44.2-1ubuntu2

---
network-manager (1.44.2-1ubuntu2) noble; urgency=medium

  [ Lukas Märdian ]
  * network-manager.postinst: Skip unknown connection profiles (LP: #2039503)
  * d/network-manager.postinst: Drop reboot notification (LP: #2040292)

  [ Danilo Egea Gondolfo ]
  * debian/tests/nm_netplan.py
Start Network Manager via systemd. The .service unit file sets
ProtectSystem to true and we want to run the Netplan tests with this
restriction enabled.
  * d/p/netplan/0003-Allow-the-NetworkManager-daemon-to-write-to-lib-netp.patch
Allow-list /usr/lib/netplan so libnetplan can open files from that
directory with writing permission. See LP: #2040153
  * debian/tests/control
Add all the dependencies required by the nm_netplan.py tests.
  * debian/tests/network_test_base.py.
Increase the waiting time between creating a veth pair and reading their
MAC addresses. On arm64, the system is taking longer to change the MAC
after creation, leading to failures due to differences in the expected
and current MAC addresses. See LP: #2023183

 -- Lukas Märdian   Thu, 26 Oct 2023 11:48:18 +0200

** Changed in: network-manager (Ubuntu Noble)
   Status: In Progress => Fix Released

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

Title:
  network-manager autokpgtest failure (nm.py)

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Lunar:
  Confirmed
Status in network-manager source package in Mantic:
  Confirmed
Status in network-manager source package in Noble:
  Fix Released

Bug description:
  This fails only on arm64.

  https://autopkgtest.ubuntu.com/results/autopkgtest-
  lunar/lunar/arm64/n/network-manager/20230522_141200_71ac4@/log.gz

  To be determined if there is a bug in the package or linux kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2023183/+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 1966433] Re: Pipewire services start up on remote (ssh) logins

2023-10-31 Thread Bug Watch Updater
** Changed in: pipewire (Debian)
   Status: New => Won't Fix

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

Title:
  Pipewire services start up on remote (ssh) logins

Status in pipewire package in Ubuntu:
  Triaged
Status in pipewire package in Debian:
  Won't Fix

Bug description:
  This concern pipewire 0.3.48-1ubuntu1 in Ubuntu jammy.

  I log into an installed system via ssh, and I see

  skunk@darkstar:~$ ps auxww | grep skunk
  root   13771  0.5  0.1  19772 12224 ?Ss   07:35   0:00 sshd: 
skunk [priv]
  skunk  13774  5.4  0.1  17160  9940 ?Ss   07:35   0:00 
/lib/systemd/systemd --user
  skunk  13775  0.0  0.0  25600  5292 ?S07:35   0:00 (sd-pam)
  skunk  13782  0.4  0.0  34460  6360 ?Ssl  07:35   0:00 
/usr/bin/pipewire
  skunk  13783  0.4  0.0  18632  6856 ?Ssl  07:35   0:00 
/usr/bin/pipewire-media-session
  skunk  13801  0.0  0.0   8412  4340 ?Ss   07:35   0:00 
/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile 
--systemd-activation --syslog-only
  skunk  13831  0.0  0.0  19932  8052 ?S07:35   0:00 sshd: 
skunk@pts/0
  skunk  13832  0.0  0.0   5256  4124 pts/0Ss   07:35   0:00 -bash
  skunk  13854  0.0  0.0   7692  3328 pts/0R+   07:35   0:00 ps auxww
  skunk  13855  0.0  0.0   4024  2144 pts/0S+   07:35   0:00 grep 
--color=auto skunk

  Pipewire is a multimedia service. It should not be running in a
  remote, non-graphical login.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1966433/+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 2040292] Re: network-manager SRU flags system for restart required but also restarted the service

2023-10-31 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 1.44.2-1ubuntu2

---
network-manager (1.44.2-1ubuntu2) noble; urgency=medium

  [ Lukas Märdian ]
  * network-manager.postinst: Skip unknown connection profiles (LP: #2039503)
  * d/network-manager.postinst: Drop reboot notification (LP: #2040292)

  [ Danilo Egea Gondolfo ]
  * debian/tests/nm_netplan.py
Start Network Manager via systemd. The .service unit file sets
ProtectSystem to true and we want to run the Netplan tests with this
restriction enabled.
  * d/p/netplan/0003-Allow-the-NetworkManager-daemon-to-write-to-lib-netp.patch
Allow-list /usr/lib/netplan so libnetplan can open files from that
directory with writing permission. See LP: #2040153
  * debian/tests/control
Add all the dependencies required by the nm_netplan.py tests.
  * debian/tests/network_test_base.py.
Increase the waiting time between creating a veth pair and reading their
MAC addresses. On arm64, the system is taking longer to change the MAC
after creation, leading to failures due to differences in the expected
and current MAC addresses. See LP: #2023183

 -- Lukas Märdian   Thu, 26 Oct 2023 11:48:18 +0200

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  network-manager SRU flags system for restart required but also
  restarted the service

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Mantic:
  New

Bug description:
  [ Impact ]

   * During an upgrade (or installation) of the network-manager package, its 
debian/network-manager.postinst maintainer script restarts 
NetworkManager.service and also requests users to reboot their system.
   * It requests a reboot, by calling into 
/usr/share/update-notifier/notify-reboot-required and listing "network-manager" 
in /var/run/reboot-required.pkgs
   * Restarting the systemd service AND asking for a reboot isn't needed. Just 
the service restart is enough and we shouldn't ask for a reboot as that is bad 
UX

  [ Test Plan ]

   * Reboot your system (or clear /var/run/reboot-required.pkgs)
 echo "" | sudo tee /var/run/reboot-required.pkgs
   * Install network-manager from mantic-proposed
 apt install [--reinstall] -t mantic-proposed network-manager
   * Observe that the NetworkManager.service was restarted by this operation: 
"active (running) [...] 2 min ago"
 systemctl status Networkmanager.service
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
preset: enabled)
   Active: active (running) since Wed 2023-10-25 15:21:27 CEST; 2min ago
 Docs: man:NetworkManager(8)
 Main PID: 3880250 (NetworkManager)
Tasks: 4 (limit: 28344)
   Memory: 6.1M
  CPU: 425ms
   CGroup: /system.slice/NetworkManager.service
   └─3880250 /usr/sbin/NetworkManager --no-daemon
   * Observe that network-manager was NOT written to 
/var/run/reboot-required.pkgs
 cat /var/run/reboot-required.pkgs
   * Observe that no GUI popped up asking you for a reboot because of 
NetworkManager

  [ Where problems could occur ]

   * This change is touching a maintainer script (.postinst)
   * Failures or syntax errors could leave the network-manager package 
unconfigured
   * It could break installation of the network-manager package

  [ Other Info ]
   
   * This SRU should probably just be staged, using `block-proposed-mantic` and 
bundled with the next upload.

  === original description ===

  After applying the network-manager SRU in mantic, I get a notification
  that a system restart is required to fully apply updates.

  This immediately raised a question, because I KNOW my network
  connection was restarted when the SRU was installed (I have a VPN that
  did not auto-reconnect).

  And I checked the state of the process - it was definitely restarted
  and is running from the binary currently on disk.

  The network-manager postinst has the following code:

  # request a reboot (NM tears down interfaces on restart
  # which is not the way we want to go)
  [ -x /usr/share/update-notifier/notify-reboot-required ] && \
  /usr/share/update-notifier/notify-reboot-required

  But the service restart is also happening. debian/rules currently has:

  override_dh_installsystemd:
  dh_installsystemd -pnetwork-manager --no-start 
NetworkManager-dispatcher.service NetworkManager-wait-online.service 
nm-priv-helper.service
  dh_installsystemd -pnetwork-manager --no-also NetworkManager.service

  No other systemd overrides. Nothing inhibits the restart of the
  service.

  It needs to be one or the other.  And if we're doing SRUs of network-
  manager, then this is bad UX for 

[Desktop-packages] [Bug 2040153] Re: Network Manager will not remove Netplan YAMLs when connections are deleted

2023-10-31 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 1.44.2-1ubuntu2

---
network-manager (1.44.2-1ubuntu2) noble; urgency=medium

  [ Lukas Märdian ]
  * network-manager.postinst: Skip unknown connection profiles (LP: #2039503)
  * d/network-manager.postinst: Drop reboot notification (LP: #2040292)

  [ Danilo Egea Gondolfo ]
  * debian/tests/nm_netplan.py
Start Network Manager via systemd. The .service unit file sets
ProtectSystem to true and we want to run the Netplan tests with this
restriction enabled.
  * d/p/netplan/0003-Allow-the-NetworkManager-daemon-to-write-to-lib-netp.patch
Allow-list /usr/lib/netplan so libnetplan can open files from that
directory with writing permission. See LP: #2040153
  * debian/tests/control
Add all the dependencies required by the nm_netplan.py tests.
  * debian/tests/network_test_base.py.
Increase the waiting time between creating a veth pair and reading their
MAC addresses. On arm64, the system is taking longer to change the MAC
after creation, leading to failures due to differences in the expected
and current MAC addresses. See LP: #2023183

 -- Lukas Märdian   Thu, 26 Oct 2023 11:48:18 +0200

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

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

Title:
  Network Manager will not remove Netplan YAMLs when connections are
  deleted

Status in netplan.io package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in netplan.io source package in Mantic:
  Invalid
Status in network-manager source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  Desktop users, or any users with YAML files in /usr/lib/netplan, can't delete
  Network Manager connections persistently. That means that, when the 
connection is
  deliberately deleted by the user, it will re-appear when the system is 
rebooted or
  netplan apply is executed.

  This is happening because the systemd service unit is setting the property 
"ProtectSystem"
  to true. Because of that, /usr is being presented to the Network Manager 
daemon as read-only.
  When connections are deleted, libnetplan will try to open its YAML files with 
writing permissions
  and will fail for files from /usr/lib/netplan. Even if the user hasn't added 
any files there manually,
  the file /usr/lib/netplan/00-network-manager-all.yaml will be installed by 
the package ubuntu-settings.

  This issue is fixed by allow-listing /usr/lib/netplan with 
ReadWritePaths=/usr/lib/netplan in systemd
  so the Network Manager's daemon will be able to write to that directory.

  This upload also improves the autopkgtests related to Netplan. Network 
Manager will be
  started by systemd, which ensures we are testing in the same environment 
conditions
  used by a desktop installation. It also adds a few more instances of 
connections deletions so
  we can test a bit more that YAML files are being removed. It also adds all 
the dependencies
  required by the test script (which sadly was causing the nm_netplan.py tests 
to be skipped).

  [ Test Plan ]

  Launch a new Mantic VM:

  $ lxc launch ubuntu:mantic --vm

  Install network-manager and ubuntu-settings:

  # apt install network-manager ubuntu-settings

  Run Netplan

  # netplan apply

  Create a dummy connection via nmcli:

  # nmcli con add type dummy connection.interface-name dummy0

  Check a new YAML will be created in /etc/netplan

  Delete the connection with nmcli

  # nmcli con del dummy-dummy0

  Check the YAML WAS NOT removed from /etc/netplan

  You will see the error below in the NetworkManager's journal

  netplan_delete_connection: Cannot write output state: Read-only file
  system

  Add the PPA containing the fix and run the same test described above

  # add-apt-repository ppa:danilogondolfo/network-manager
  # apt update
  # apt upgrade

  Check that the YAML will be created when the connection is added and
  deleted and the connection is removed.

  [ Where problems could occur ]

  As the only change is a relaxation of the restrictions applied by systemd on 
the environment where Network Manager
  runs, we are not expecting any regression.

  As for the changes in the autopkgtest related to Netplan, they are
  passing on all architectures.

  Autopkgtests

  amd64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/amd64/n/network-manager/20231023_175203_b2798@/log.gz
  ppc64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/ppc64el/n/network-manager/20231023_182332_f0497@/log.gz
  s390x - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/s390x/n/network-manager/20231023_190810_ced8d@/log.gz
  arm64 - 

[Desktop-packages] [Bug 2041857] [NEW] package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10

2023-10-31 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I used QuickCreate in Windows 11 Hyper-V to create a basic 22.04 system 
(22.04.3 LTS).
- No special options selected.
- Install worked as expected.
- The error in summary occurred during the large software update automatically 
triggered right after first login.

However, the system (including Firefox) is still up and apparently
running fine. Will try to manually update Firefox.

NB: there was a major update to the Windows 11 host yesterday.

ProblemType: Package
DistroRelease: Ubuntu 22.04
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Oct 30 10:42:57 2023
ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 10
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.10
Snap: firefox 100.0-2 ()
Snap.Changes: no changes found
Title: package firefox (not installed) failed to install/upgrade: new firefox 
package pre-installation script subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy need-duplicate-check
-- 
package firefox (not installed) failed to install/upgrade: new firefox package 
pre-installation script subprocess returned error exit status 10
https://bugs.launchpad.net/bugs/2041857
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to firefox in Ubuntu.

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