date:20220830

Please try reinstalling, and let us know how this goes:

sudo apt reinstall firefox

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

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

Title:
  package firefox 104.0+build3-0ubuntu0.20.04.1 failed to
  install/upgrade: end of file on stdin at conffile prompt

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  i don't knoq

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: firefox 104.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.24
  AptOrdering:
   firefox:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akash  1878 F pulseaudio
   /dev/snd/controlC0:  akash  1878 F pulseaudio
  BuildID: 20220818191623
  CasperMD5CheckResult: skip
  Channel: Unavailable
  Date: Mon Aug 29 09:36:54 2022
  ErrorMessage: end of file on stdin at conffile prompt
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-10-11 (321 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  IpRoute:
   default via 192.168.29.1 dev wlp3s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   192.168.29.0/24 dev wlp3s0 proto kernel scope link src 192.168.29.158 metric 
600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, unpackaged
  PythonDetails: /usr/bin/python3.6, Python 3.6.15, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to 
install/upgrade: end of file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2020
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1AET34W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20T6S0UQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.10
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1AET34W(1.10):bd12/19/2020:br1.10:efr1.10:svnLENOVO:pn20T6S0UQ00:pvrThinkPadE14Gen2:rvnLENOVO:rn20T6S0UQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T6_BU_Think_FM_ThinkPadE14Gen2:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20T6S0UQ00
  dmi.product.sku: LENOVO_MT_20T6_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.blacklist.d.firefox:
   /usr/lib/firefox/firefox
   /usr/lib/firefox/plugin-container
  modified.conffile..etc.apport.native-origins.d.firefox:
   LP-PPA-ubuntu-mozilla-daily
   LP-PPA-ubuntu-mozilla-daily-firefox-aurora
   LP-PPA-mozillateam-firefox-next
  modified.conffile..etc.firefox.syspref.js:
   // This file can be used to configure global preferences for Firefox
   // Example: Homepage
   //pref("browser.startup.homepage", "http://www.weebls-stuff.com/wab/;);
  mtime.conffile..etc.apparmor.d.usr.bin.firefox: 2022-05-20T11:44:35
  mtime.conffile..etc.apport.blacklist.d.firefox: 2021-02-05T17:24:22
  mtime.conffile..etc.apport.native-origins.d.firefox: 2021-02-05T17:24:22
  mtime.conffile..etc.firefox.syspref.js: 2020-09-21T22:09:02

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1988016/+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 1988016] Re: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: end of file on stdin at conffile prompt

From DpkgTerminalLog.txt:

Configuration file '/etc/apparmor.d/usr.bin.firefox'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.

When updating firefox, you were prompted to choose an option, and it looks like 
you didn't?
You should probably choose Y (install the package maintainer's version), unless 
you know why you have local modifications to the apparmor profile.

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

Title:
  package firefox 104.0+build3-0ubuntu0.20.04.1 failed to
  install/upgrade: end of file on stdin at conffile prompt

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  i don't knoq

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: firefox 104.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.24
  AptOrdering:
   firefox:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akash  1878 F pulseaudio
   /dev/snd/controlC0:  akash  1878 F pulseaudio
  BuildID: 20220818191623
  CasperMD5CheckResult: skip
  Channel: Unavailable
  Date: Mon Aug 29 09:36:54 2022
  ErrorMessage: end of file on stdin at conffile prompt
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-10-11 (321 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  IpRoute:
   default via 192.168.29.1 dev wlp3s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   192.168.29.0/24 dev wlp3s0 proto kernel scope link src 192.168.29.158 metric 
600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, unpackaged
  PythonDetails: /usr/bin/python3.6, Python 3.6.15, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to 
install/upgrade: end of file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2020
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1AET34W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20T6S0UQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.10
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1AET34W(1.10):bd12/19/2020:br1.10:efr1.10:svnLENOVO:pn20T6S0UQ00:pvrThinkPadE14Gen2:rvnLENOVO:rn20T6S0UQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T6_BU_Think_FM_ThinkPadE14Gen2:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20T6S0UQ00
  dmi.product.sku: LENOVO_MT_20T6_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.blacklist.d.firefox:
   /usr/lib/firefox/firefox
   /usr/lib/firefox/plugin-container
  modified.conffile..etc.apport.native-origins.d.firefox:
   LP-PPA-ubuntu-mozilla-daily
   LP-PPA-ubuntu-mozilla-daily-firefox-aurora
   LP-PPA-mozillateam-firefox-next
  modified.conffile..etc.firefox.syspref.js:
   // This file can be used to configure global preferences for Firefox
   // Example: Homepage
   //pref("browser.startup.homepage", "http://www.weebls-stuff.com/wab/;);
  mtime.conffile..etc.apparmor.d.usr.bin.firefox: 2022-05-20T11:44:35
  mtime.conffile..etc.apport.blacklist.d.firefox: 2021-02-05T17:24:22
  mtime.conffile..etc.apport.native-origins.d.firefox: 2021-02-05T17:24:22
  mtime.conffile..etc.firefox.syspref.js: 2020-09-21T22:09:02

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1988016/+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 1988246] Re: Keep reseting appearance to light mode theme every background-panel load

gnome-control-center (1:43~beta-1ubuntu3)

** Description changed:

  Steps
  
  1. Have dark mode enabled
  2. Open settings at background panel
- 3. Shell theme is reset back to light them
+ 3. Shell theme is reset back to light theme
  
  It keeps resetting theme back to light one every time you open the panel
  which is unwanted.

** Summary changed:

- Keep reseting appearance to light mode theme  every background-panel load
+ Keeps reseting appearance to light mode theme every background-panel load

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

Title:
  Keeps reseting appearance to light mode theme every background-panel
  load

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

Bug description:
  Steps

  1. Have dark mode enabled
  2. Open settings at background panel
  3. Shell theme is reset back to light theme

  It keeps resetting theme back to light one every time you open the
  panel which is unwanted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988246/+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 1988246] [NEW] Keep reseting appearance to light mode theme every background-panel load

Public bug reported:

Steps

1. Have dark mode enabled
2. Open settings at background panel
3. Shell theme is reset back to light theme

It keeps resetting theme back to light one every time you open the panel
which is unwanted.

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


** Tags: kinetic

** Tags added: kinetic

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

Title:
  Keep reseting appearance to light mode theme  every background-panel
  load

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

Bug description:
  Steps

  1. Have dark mode enabled
  2. Open settings at background panel
  3. Shell theme is reset back to light theme

  It keeps resetting theme back to light one every time you open the
  panel which is unwanted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988246/+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 1988245] Re: [Feature] A way to install nvidia driver for development

2022-08-30 Thread jeremyszu

MP is here
https://github.com/tseliot/ubuntu-drivers-common/pull/71

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => jeremyszu (os369510)

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
   Status: New => Confirmed

** Tags added: oem-priority

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

Title:
  [Feature] A way to install nvidia driver for development

Status in OEM Priority Project:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  [Description]
  OEM/ODM/CE/IHV partners need to have a standardize way to install nvidia 
drivers which way needs to make sure the configuration is same as what the end 
user will use.

  As u-d-c has some configuration during the installation, we would like
  to have a way to install nvidia drivers correctly for the business.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1988245/+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 1988245] [NEW] [Feature] A way to install nvidia driver for development

2022-08-30 Thread jeremyszu

Public bug reported:

[Description]
OEM/ODM/CE/IHV partners need to have a standardize way to install nvidia 
drivers which way needs to make sure the configuration is same as what the end 
user will use.

As u-d-c has some configuration during the installation, we would like
to have a way to install nvidia drivers correctly for the business.

** Affects: oem-priority
 Importance: High
 Assignee: jeremyszu (os369510)
 Status: Confirmed

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Assignee: jeremyszu (os369510)
 Status: New


** Tags: jammy oem-priority

** Changed in: ubuntu-drivers-common (Ubuntu)
 Assignee: (unassigned) => jeremyszu (os369510)

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

Title:
  [Feature] A way to install nvidia driver for development

Status in OEM Priority Project:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  [Description]
  OEM/ODM/CE/IHV partners need to have a standardize way to install nvidia 
drivers which way needs to make sure the configuration is same as what the end 
user will use.

  As u-d-c has some configuration during the installation, we would like
  to have a way to install nvidia drivers correctly for the business.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1988245/+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 1987523] Re: Pulsaudio crashes once BT microphone is connected

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

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

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

Title:
  Pulsaudio crashes once BT microphone is connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When I connect my BT headset with microphone and change profile to
  HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog
  reports:

  Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX 
(AVRCP) as /devices/virtual/input/input37
  Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80%
  Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked
  Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data 
descriptor : 0x1 terminating
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of 
process 50808 owned by '1000' RT at priority 5.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source
  Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: 
[51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 3 times!
  Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at 
../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). 
Aborting.
  Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash 
report...
  Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie
  Aug 24 13:44:24 p14s systemd[1]: Started crash report submission.
  Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: 
/var/lock/whoopsie/lock
  Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully.
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk

  I've identified the upstream fix for this:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e

  I've built packages with the fix and can confirm that it does solve
  the problem. Packages are available at:

  https://launchpad.net/~ivoks/+archive/ubuntu/pulse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1987523/+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 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland

2022-08-30 Thread Ubuntu Foundations Team Bug Bot

The attachment "lp1984147.patch" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Monitor switcher popup (Super-P) is not displayed on desktop with
  joined display on Wayland

Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Monitor switcher popup (Super-P) is not displayed on desktop with
  joined display on GNOME 3 in Wayland mode

  [Reproduce Steps]
  1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA 
GPU does not trigger the bug)
  2. Connect the PC with 2 monitors
  3. Use Super-P to switch to joined display (note that using Displays from 
Settings does not trigger the issue)
  4. Use Super-P to switch display mode again

  [Expected Result]
  Display Switcher popup should appear

  [Actual Result]
  Display Switcher does not popup, but tapping Super-P 3 times can still switch 
back to Mirror mode

  [Version]
  gnome-shell42.2-0ubuntu0.2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-10 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: gnome-shell 42.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-43-generic 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/oem-priority/+bug/1984147/+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 1278415] Re: Photo paper is only available in the 10x15cm photo tray

[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Photo paper is only available in the 10x15cm photo tray

Status in HPLIP:
  Incomplete
Status in One Hundred Papercuts:
  Expired
Status in hplip package in Ubuntu:
  Expired

Bug description:
  
  HOW TO REPRODUCE
  

  Try to print using a photo type of paper in the main tray.

  
  **
  EXPECTED BEHAVIOUR
  **

  - To be able to print using photo paper.

  **
  REAL BEHAVIOUR
  **

  - Printing on photo paper is only available in the 10x15cm photo tray.
  - If you try to print in photo paper as it was regular paper, ink blots.

  
  
  RELEVANT DETAILS
  

  - The used printer has been HP Photosmart 6510
  (http://tinyurl.com/n9opn5v)

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: hplip 3.13.9-1ubuntu0.1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CupsErrorLog:
   
  Date: Mon Feb 10 12:59:16 2014
  InstallationDate: Installed on 2013-05-21 (264 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Lpstat: device for Photosmart_6510: 
hp:/usb/Photosmart_6510_series?serial=CN18J3127G05QB
  MachineType: MEDIONPC MS-7358
  MarkForUpload: True
  Papersize: a4
  PpdFiles: Photosmart_6510: HP Photosmart 6510 Series, hpcups 3.13.9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic 
root=UUID=7c16b6a8-52d3-4e20-94c4-933af64fd891 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (115 days ago)
  dmi.bios.date: 02/18/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7358
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/18/2008:svnMEDIONPC:pnMS-7358:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7358:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7358
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1278415/+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 1278415] Re: Photo paper is only available in the 10x15cm photo tray

[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]

** Changed in: hundredpapercuts
   Status: Incomplete => Expired

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

Title:
  Photo paper is only available in the 10x15cm photo tray

Status in HPLIP:
  Incomplete
Status in One Hundred Papercuts:
  Expired
Status in hplip package in Ubuntu:
  Expired

Bug description:
  
  HOW TO REPRODUCE
  

  Try to print using a photo type of paper in the main tray.

  
  **
  EXPECTED BEHAVIOUR
  **

  - To be able to print using photo paper.

  **
  REAL BEHAVIOUR
  **

  - Printing on photo paper is only available in the 10x15cm photo tray.
  - If you try to print in photo paper as it was regular paper, ink blots.

  
  
  RELEVANT DETAILS
  

  - The used printer has been HP Photosmart 6510
  (http://tinyurl.com/n9opn5v)

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: hplip 3.13.9-1ubuntu0.1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CupsErrorLog:
   
  Date: Mon Feb 10 12:59:16 2014
  InstallationDate: Installed on 2013-05-21 (264 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Lpstat: device for Photosmart_6510: 
hp:/usb/Photosmart_6510_series?serial=CN18J3127G05QB
  MachineType: MEDIONPC MS-7358
  MarkForUpload: True
  Papersize: a4
  PpdFiles: Photosmart_6510: HP Photosmart 6510 Series, hpcups 3.13.9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic 
root=UUID=7c16b6a8-52d3-4e20-94c4-933af64fd891 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (115 days ago)
  dmi.bios.date: 02/18/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7358
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/18/2008:svnMEDIONPC:pnMS-7358:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7358:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7358
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1278415/+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 1510932] Re: Keyring window doesn't show which program requests authentication.

[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]

** Changed in: hundredpapercuts
   Status: Incomplete => Expired

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

Title:
  Keyring window doesn't show which program requests authentication.

Status in One Hundred Papercuts:
  Expired
Status in seahorse package in Ubuntu:
  Expired

Bug description:
  When I use my Ubuntu (14.04) computer, the keyring window pops up at
  random moments, for example when I'm watching a YouTube video, it asks
  me to authenticate for something. What 'something' really is, isn't
  specified in the window itself. I don't know wether I should fill in
  my password, since I don't know which program requests a keyring
  unlock.

  I suppose it's a papercut because as a user you show know where to
  authenticate for.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1510932/+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 1510932] Re: Keyring window doesn't show which program requests authentication.

[Expired for seahorse (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Keyring window doesn't show which program requests authentication.

Status in One Hundred Papercuts:
  Expired
Status in seahorse package in Ubuntu:
  Expired

Bug description:
  When I use my Ubuntu (14.04) computer, the keyring window pops up at
  random moments, for example when I'm watching a YouTube video, it asks
  me to authenticate for something. What 'something' really is, isn't
  specified in the window itself. I don't know wether I should fill in
  my password, since I don't know which program requests a keyring
  unlock.

  I suppose it's a papercut because as a user you show know where to
  authenticate for.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1510932/+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 1975746] Re: bookmarks not creating

[Expired for evince (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  bookmarks not creating

Status in evince package in Ubuntu:
  Expired

Bug description:
  Ubuntu 22.04 LTS
  evince 42.1-3
  after updating from ubuntu 20.04 to 22.04, bookmarks in evince stopped 
working (new bookmarks are not created and old bookmarks are not visible).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evince 42.1-3
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 25 23:25:51 2022
  InstallationDate: Installed on 2021-03-24 (427 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to jammy on 2022-05-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1975746/+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 1987038] Proposed package upload rejected

2022-08-30 Thread Chris Halse Rogers

An upload of xserver-xorg-video-amdgpu to jammy-proposed has been
rejected from the upload queue for the following reason: "This looks
like an SRU-acceptable bug, but the uploaded package has weirdly-doubled
patches and FTBFS. Please fix and reupload a package that builds! ☺".

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

Title:
  Fix slow refresh rate when AMD GPU screen in reverse prime mode

Status in HWE Next:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Focal:
  Confirmed
Status in xserver-xorg-video-amdgpu source package in Jammy:
  Confirmed
Status in xserver-xorg-video-amdgpu source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  When AMD GPU is a GPU screen using reverse prime and its the only display, 
the fresh rate is very slow.

  [Fix]
  Enable present extension for GPU screen so it can be a viable CRTC to be 
selected.

  [Test]
  On a I+A laptop and external displays are routed to AMDGPU, disable internal 
display like closing lid can observe the issue.

  With the fix applied, the external display becomes very smooth.

  [Where problems could occur]
  I personally don't see why GPU screen can't use present extension, but this 
is Xorg so there might be some arcane reasons I didn't think of.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1987038/+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 1988234] Re: Shell crash after leting file to be opened with gnome-text-editor

** Description changed:

  Steps
  
  1. Open nautilus
  2. Select text file and from right click context menu select the second 
option Open With...
  3. Choose gnome-text-editor
  4. Shell crashes to GDM
+ 
+ If you perform steps for 1st time after reboot it will work and open the
+ file succesfully, but any subsequent try will lead to the crash.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43~beta.1-2ubuntu3
  Uname: Linux 5.19.5-xanmod1-x64v2 x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 31 03:46:07 2022
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.preferences' b'show-hidden-files' b'true'
   b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1114, 712)'
  InstallationDate: Installed on 2022-05-30 (92 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-08-28 (2 days ago)
  usr_lib_nautilus:
   file-roller   43~alpha-1
   nautilus-extension-gnome-terminal 3.45.90-1ubuntu1

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

Title:
  Shell crash after leting file to be opened with gnome-text-editor

Status in nautilus package in Ubuntu:
  New

Bug description:
  Steps

  1. Open nautilus
  2. Select text file and from right click context menu select the second 
option Open With...
  3. Choose gnome-text-editor
  4. Shell crashes to GDM

  If you perform steps for 1st time after reboot it will work and open
  the file succesfully, but any subsequent try will lead to the crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43~beta.1-2ubuntu3
  Uname: Linux 5.19.5-xanmod1-x64v2 x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 31 03:46:07 2022
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.preferences' b'show-hidden-files' b'true'
   b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1114, 712)'
  InstallationDate: Installed on 2022-05-30 (92 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-08-28 (2 days ago)
  usr_lib_nautilus:
   file-roller   43~alpha-1
   nautilus-extension-gnome-terminal 3.45.90-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1988234/+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 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland

2022-08-30 Thread Yao Wei

The above MR is accepted upstream.

** Patch added: "lp1984147.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1984147/+attachment/5612602/+files/lp1984147.patch

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

Title:
  Monitor switcher popup (Super-P) is not displayed on desktop with
  joined display on Wayland

Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Monitor switcher popup (Super-P) is not displayed on desktop with
  joined display on GNOME 3 in Wayland mode

  [Reproduce Steps]
  1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA 
GPU does not trigger the bug)
  2. Connect the PC with 2 monitors
  3. Use Super-P to switch to joined display (note that using Displays from 
Settings does not trigger the issue)
  4. Use Super-P to switch display mode again

  [Expected Result]
  Display Switcher popup should appear

  [Actual Result]
  Display Switcher does not popup, but tapping Super-P 3 times can still switch 
back to Mirror mode

  [Version]
  gnome-shell42.2-0ubuntu0.2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-10 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: gnome-shell 42.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-43-generic 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/oem-priority/+bug/1984147/+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 1988234] [NEW] Shell crash after leting file to be opened with gnome-text-editor

Public bug reported:

Steps

1. Open nautilus
2. Select text file and from right click context menu select the second option 
Open With...
3. Choose gnome-text-editor
4. Shell crashes to GDM

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: nautilus 1:43~beta.1-2ubuntu3
Uname: Linux 5.19.5-xanmod1-x64v2 x86_64
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 31 03:46:07 2022
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
 b'org.gnome.nautilus.preferences' b'show-hidden-files' b'true'
 b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'"
 b'org.gnome.nautilus.window-state' b'initial-size' b'(1114, 712)'
InstallationDate: Installed on 2022-05-30 (92 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: nautilus
UpgradeStatus: Upgraded to kinetic on 2022-08-28 (2 days ago)
usr_lib_nautilus:
 file-roller   43~alpha-1
 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1

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


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

** Description changed:

  Steps
  
  1. Open nautilus
- 2. Select text file and from right click context menu select Open with
+ 2. Select text file and from right click context menu select Open with...
  3. Choose gnome-text-editor
  4. Shell crashes to GDM
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43~beta.1-2ubuntu3
  Uname: Linux 5.19.5-xanmod1-x64v2 x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 31 03:46:07 2022
  GsettingsChanges:
-  b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
-  b'org.gnome.nautilus.preferences' b'show-hidden-files' b'true'
-  b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'"
-  b'org.gnome.nautilus.window-state' b'initial-size' b'(1114, 712)'
+  b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
+  b'org.gnome.nautilus.preferences' b'show-hidden-files' b'true'
+  b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'"
+  b'org.gnome.nautilus.window-state' b'initial-size' b'(1114, 712)'
  InstallationDate: Installed on 2022-05-30 (92 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-08-28 (2 days ago)
  usr_lib_nautilus:
-  file-roller   43~alpha-1
-  nautilus-extension-gnome-terminal 3.45.90-1ubuntu1
+  file-roller   43~alpha-1
+  nautilus-extension-gnome-terminal 3.45.90-1ubuntu1

** Description changed:

  Steps
  
  1. Open nautilus
- 2. Select text file and from right click context menu select Open with...
+ 2. Select text file and from right click context menu select the second 
option Open With...
  3. Choose gnome-text-editor
  4. Shell crashes to GDM
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43~beta.1-2ubuntu3
  Uname: Linux 5.19.5-xanmod1-x64v2 x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 31 03:46:07 2022
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.preferences' b'show-hidden-files' b'true'
   b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1114, 712)'
  InstallationDate: Installed on 2022-05-30 (92 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-08-28 (2 days ago)
  usr_lib_nautilus:
   file-roller   43~alpha-1
   nautilus-extension-gnome-terminal 3.45.90-1ubuntu1

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

Title:
  Shell crash after leting file to be opened with gnome-text-editor

Status in nautilus package in Ubuntu:
  New

Bug description:
  Steps

  1. Open nautilus
  2. Select text file and from right click context menu select the second 
option Open With...
  3. Choose gnome-text-editor
  4. Shell crashes to GDM

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43~beta.1-2ubuntu3
  Uname: Linux 5.19.5-xanmod1-x64v2 x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 31 03:46:07 2022
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.preferences' b'show-hidden-files' b'true'
   b'org.gnome.nautilus.preferences'

[Desktop-packages] [Bug 1988149] Re: Gnome puts the machine into sleep mode although it is a server with no need or requirement for users to use Gnome

The default value for sleep-inactive-ac-timeout from upstream GNOME is
1200 (20 minutes), but Ubuntu contains an override that sets it to zero
(off) in:

  /usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override

Do you have that file? If not then you are missing:

  sudo apt install ubuntu-settings


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

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

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

Title:
  Gnome puts the machine into sleep mode although it is a server with no
  need or requirement for users to use Gnome

Status in Ubuntu:
  Incomplete

Bug description:
  Installing mythtv (all standard packages and versions which I assume
  are captured by this suite of tools).  Installing either the server
  with desktop or server without desktop (adding mythtv-backend-master)
  and then installing mythtv-backend-master adds Gnome desktop in.

  Configuring the server using ssh (i.e. not the desktop environment on
  the system) the server is put to sleep by Gnome after ~20 minutes.
  This appears to be because there has been no activity on the GDM
  managed GUI desktop session.

  It appears to be resolved by setting the properties below from the
  command line or editing the gdm3 defaults as shown below (hopefully
  belt and braces - no AC timer and don't do anything on the timer
  expiring).

  The machine is an old Intel i3 NUC so perhaps is being detected as a
  latop (which is why I'm repoprting this)  but in any case it's the
  server version of Ubuntu and who wants their server put to sleep if
  no-one's using a GUI for 20 minutes?


  sudo vi /etc/gdm3/greeter.dconf-defaults
  # Automatic suspend
  # =
[org/gnome/settings-daemon/plugins/power]
# - Time inactive in seconds before suspending with AC power
#   1200=20 minutes, 0=never
sleep-inactive-ac-timeout=0
# - What to do after sleep-inactive-ac-timeout
#   'blank', 'suspend', 'shutdown', 'hibernate', 'interactive' or 
'nothing'
sleep-inactive-ac-type='nothing'

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  Date: Tue Aug 30 10:35:51 2022
  InstallationDate: Installed on 2022-08-30 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1988149/+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 1987981] Re: nautilus crashed with SIGSEGV in g_str_hash()

2022-08-30 Thread Seth Arnold

** Information type changed from Private Security to Public

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

Title:
  nautilus crashed with SIGSEGV in g_str_hash()

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  nothing

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43~beta.1-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 16:25:29 2022
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-08-28 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220828)
  ProcCmdline: nautilus
  ProcEnviron:
   LANGUAGE=de_CH:de
   LANG=de_CH.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f9f0cc15434 : movsbl (%rdi),%edx
   PC (0x7f9f0cc15434) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   g_str_hash () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_contains () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgtk-4.so.1
   () at /lib/x86_64-linux-gnu/libgtk-4.so.1
   () at /lib/x86_64-linux-gnu/libgtk-4.so.1
  Title: nautilus crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:
   
  usr_lib_nautilus:
   file-roller   43~alpha-1
   nautilus-extension-gnome-terminal 3.45.90-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1987981/+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 1988016] Re: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: end of file on stdin at conffile prompt

2022-08-30 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package firefox 104.0+build3-0ubuntu0.20.04.1 failed to
  install/upgrade: end of file on stdin at conffile prompt

Status in firefox package in Ubuntu:
  New

Bug description:
  i don't knoq

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: firefox 104.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.24
  AptOrdering:
   firefox:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akash  1878 F pulseaudio
   /dev/snd/controlC0:  akash  1878 F pulseaudio
  BuildID: 20220818191623
  CasperMD5CheckResult: skip
  Channel: Unavailable
  Date: Mon Aug 29 09:36:54 2022
  ErrorMessage: end of file on stdin at conffile prompt
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-10-11 (321 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  IpRoute:
   default via 192.168.29.1 dev wlp3s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   192.168.29.0/24 dev wlp3s0 proto kernel scope link src 192.168.29.158 metric 
600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, unpackaged
  PythonDetails: /usr/bin/python3.6, Python 3.6.15, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to 
install/upgrade: end of file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2020
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1AET34W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20T6S0UQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.10
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1AET34W(1.10):bd12/19/2020:br1.10:efr1.10:svnLENOVO:pn20T6S0UQ00:pvrThinkPadE14Gen2:rvnLENOVO:rn20T6S0UQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T6_BU_Think_FM_ThinkPadE14Gen2:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20T6S0UQ00
  dmi.product.sku: LENOVO_MT_20T6_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.blacklist.d.firefox:
   /usr/lib/firefox/firefox
   /usr/lib/firefox/plugin-container
  modified.conffile..etc.apport.native-origins.d.firefox:
   LP-PPA-ubuntu-mozilla-daily
   LP-PPA-ubuntu-mozilla-daily-firefox-aurora
   LP-PPA-mozillateam-firefox-next
  modified.conffile..etc.firefox.syspref.js:
   // This file can be used to configure global preferences for Firefox
   // Example: Homepage
   //pref("browser.startup.homepage", "http://www.weebls-stuff.com/wab/;);
  mtime.conffile..etc.apparmor.d.usr.bin.firefox: 2022-05-20T11:44:35
  mtime.conffile..etc.apport.blacklist.d.firefox: 2021-02-05T17:24:22
  mtime.conffile..etc.apport.native-origins.d.firefox: 2021-02-05T17:24:22
  mtime.conffile..etc.firefox.syspref.js: 2020-09-21T22:09:02

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1988016/+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 1988016] Re: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: end of file on stdin at conffile prompt

2022-08-30 Thread Seth Arnold

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

** Information type changed from Private Security to Public

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

Title:
  package firefox 104.0+build3-0ubuntu0.20.04.1 failed to
  install/upgrade: end of file on stdin at conffile prompt

Status in firefox package in Ubuntu:
  New

Bug description:
  i don't knoq

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: firefox 104.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.24
  AptOrdering:
   firefox:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akash  1878 F pulseaudio
   /dev/snd/controlC0:  akash  1878 F pulseaudio
  BuildID: 20220818191623
  CasperMD5CheckResult: skip
  Channel: Unavailable
  Date: Mon Aug 29 09:36:54 2022
  ErrorMessage: end of file on stdin at conffile prompt
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-10-11 (321 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  IpRoute:
   default via 192.168.29.1 dev wlp3s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   192.168.29.0/24 dev wlp3s0 proto kernel scope link src 192.168.29.158 metric 
600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, unpackaged
  PythonDetails: /usr/bin/python3.6, Python 3.6.15, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to 
install/upgrade: end of file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2020
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1AET34W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20T6S0UQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.10
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1AET34W(1.10):bd12/19/2020:br1.10:efr1.10:svnLENOVO:pn20T6S0UQ00:pvrThinkPadE14Gen2:rvnLENOVO:rn20T6S0UQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T6_BU_Think_FM_ThinkPadE14Gen2:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20T6S0UQ00
  dmi.product.sku: LENOVO_MT_20T6_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.blacklist.d.firefox:
   /usr/lib/firefox/firefox
   /usr/lib/firefox/plugin-container
  modified.conffile..etc.apport.native-origins.d.firefox:
   LP-PPA-ubuntu-mozilla-daily
   LP-PPA-ubuntu-mozilla-daily-firefox-aurora
   LP-PPA-mozillateam-firefox-next
  modified.conffile..etc.firefox.syspref.js:
   // This file can be used to configure global preferences for Firefox
   // Example: Homepage
   //pref("browser.startup.homepage", "http://www.weebls-stuff.com/wab/;);
  mtime.conffile..etc.apparmor.d.usr.bin.firefox: 2022-05-20T11:44:35
  mtime.conffile..etc.apport.blacklist.d.firefox: 2021-02-05T17:24:22
  mtime.conffile..etc.apport.native-origins.d.firefox: 2021-02-05T17:24:22
  mtime.conffile..etc.firefox.syspref.js: 2020-09-21T22:09:02

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1988016/+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 1987911] Re: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-08-30 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package firefox 104.0+build3-0ubuntu0.20.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  New

Bug description:
  eerror

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 104.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: aufs
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  europassistance   2340 F pulseaudio
   /dev/snd/controlC0:  europassistance   2340 F pulseaudio
  BuildID: 20220818191623
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Fri Aug 26 20:59:33 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-03-09 (170 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IpRoute:
   default via 192.168.1.254 dev wlp1s0 proto dhcp metric 600 
   169.254.0.0/16 dev br-b0b9255f7446 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   172.18.0.0/16 dev br-b0b9255f7446 proto kernel scope link src 172.18.0.1 
linkdown 
   192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.124 metric 
600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-08-26 (0 days ago)
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 7.1
  dmi.bios.vendor: HP
  dmi.bios.version: T82 Ver. 01.07.01
  dmi.board.name: 8895
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 43.25.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 67.37
  dmi.modalias: 
dmi:bvnHP:bvrT82Ver.01.07.01:bd11/12/2021:br7.1:efr67.37:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.25.00:cvnHP:ct10:cvr:sku458Z6EA#ABF:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 845 G8 Notebook PC
  dmi.product.sku: 458Z6EA#ABF
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987911/+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 1987911] Re: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-08-30 Thread Seth Arnold

** Information type changed from Private Security to Public

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

Title:
  package firefox 104.0+build3-0ubuntu0.20.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  New

Bug description:
  eerror

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 104.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: aufs
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  europassistance   2340 F pulseaudio
   /dev/snd/controlC0:  europassistance   2340 F pulseaudio
  BuildID: 20220818191623
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Fri Aug 26 20:59:33 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-03-09 (170 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IpRoute:
   default via 192.168.1.254 dev wlp1s0 proto dhcp metric 600 
   169.254.0.0/16 dev br-b0b9255f7446 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   172.18.0.0/16 dev br-b0b9255f7446 proto kernel scope link src 172.18.0.1 
linkdown 
   192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.124 metric 
600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-08-26 (0 days ago)
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 7.1
  dmi.bios.vendor: HP
  dmi.bios.version: T82 Ver. 01.07.01
  dmi.board.name: 8895
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 43.25.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 67.37
  dmi.modalias: 
dmi:bvnHP:bvrT82Ver.01.07.01:bd11/12/2021:br7.1:efr67.37:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.25.00:cvnHP:ct10:cvr:sku458Z6EA#ABF:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 845 G8 Notebook PC
  dmi.product.sku: 458Z6EA#ABF
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987911/+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 1988143] Update Released

2022-08-30 Thread Łukasz Zemczak

The verification of the Stable Release Update for linux-restricted-
modules-hwe-5.15 has completed successfully and the package is now being
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

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

Title:
  20.04.5 (20220829.1 build) has kernel 5.13 packages

Status in linux-restricted-modules-hwe-5.15 package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  [Impact]

   * Linux-restricted-modules for the 390 drivers were disabled
  temporarily back in January, however they were not re-enabled when
  support for the new kernel was added.

   * Including the 390 release in the ISO causes the 5.13 packages to be
  pulled in.

  [Test Plan]

   * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver
  can be installed with its linux-restricted-modules.

  [Where problems could occur]

   * The addition of modules for an already existing driver series would not
     cause any regressions, since the whole package generation process is 
automated, and this is the only commit that we are going to revert:
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020

  [Other Info]

   * Other kernel releases support the 390 series.
  _

  Examining the .list file for the amd64 image it contains various
  kernel 5.13 .deb packages.

  http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
  amd64.list

  e.g.

  
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
  
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb

  This is a little unexpected given that 5.15 is the default kernel.

  Possibly nvidia-390 doesn't have 5.15 packages?

  This impacts all flavours as well that include nvidia stuff in their
  ISO - so if the solution is to change the meta file for a revised
  regexp for nvidia then all flavours that include nvidia will likewise
  need their meta packages updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/1988143/+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 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages

This bug was fixed in the package linux-restricted-modules-hwe-5.15 -
5.15.0-46.49~20.04.1+1

---
linux-restricted-modules-hwe-5.15 (5.15.0-46.49~20.04.1+1) focal; urgency=medium

  * Miscellaneous Ubuntu changes (LP: #1988143)
- [packaging] revert drop nvidia 390

 -- Alberto Milone   Tue, 30 Aug 2022
11:40:45 +

** Changed in: linux-restricted-modules-hwe-5.15 (Ubuntu)
   Status: New => Fix Released

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

Title:
  20.04.5 (20220829.1 build) has kernel 5.13 packages

Status in linux-restricted-modules-hwe-5.15 package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  [Impact]

   * Linux-restricted-modules for the 390 drivers were disabled
  temporarily back in January, however they were not re-enabled when
  support for the new kernel was added.

   * Including the 390 release in the ISO causes the 5.13 packages to be
  pulled in.

  [Test Plan]

   * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver
  can be installed with its linux-restricted-modules.

  [Where problems could occur]

   * The addition of modules for an already existing driver series would not
     cause any regressions, since the whole package generation process is 
automated, and this is the only commit that we are going to revert:
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020

  [Other Info]

   * Other kernel releases support the 390 series.
  _

  Examining the .list file for the amd64 image it contains various
  kernel 5.13 .deb packages.

  http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
  amd64.list

  e.g.

  
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
  
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb

  This is a little unexpected given that 5.15 is the default kernel.

  Possibly nvidia-390 doesn't have 5.15 packages?

  This impacts all flavours as well that include nvidia stuff in their
  ISO - so if the solution is to change the meta file for a revised
  regexp for nvidia then all flavours that include nvidia will likewise
  need their meta packages updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/1988143/+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 1988230] [NEW] glib 2.73 breaks modemmanager

2022-08-30 Thread Jeremy Bicha

Public bug reported:

I'm filing this bug in case we want to fix it before letting glib 2.73
in to kinetic.

** Affects: glib
 Importance: Unknown
 Status: Unknown

** Affects: glib2.0 (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: modemmanager (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Affects: glib2.0 (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: block-proposed kinetic

** Bug watch added: Debian Bug tracker #1017794
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017794

** Also affects: glib2.0 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017794
   Importance: Unknown
   Status: Unknown

** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2729
   https://gitlab.gnome.org/GNOME/glib/-/issues/2729

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

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

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

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

Title:
  glib 2.73 breaks modemmanager

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Triaged
Status in modemmanager package in Ubuntu:
  Triaged
Status in glib2.0 package in Debian:
  Unknown

Bug description:
  I'm filing this bug in case we want to fix it before letting glib 2.73
  in to kinetic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1988230/+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 1987928] Re: gnome-control-center closes with Gtk Gio Error when trying to access keyboard shortcut details

2022-08-30 Thread Olivier Dierick

Hello,

Here is the output of the suggested commands.

--- dpkg -l gnome-settings-daemon-common ---
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| 
État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom  Version Architecture Description
+++--===--=
ii  gnome-settings-daemon-common 42.1-1ubuntu2.1 all  daemon handling 
the GNOME session settings - common files
--- end dpkg -l gnome-settings-daemon-common ---

--- cat /proc/`pidof gnome-control-center`/maps | grep schemas ---
7f476dfc9000-7f476e02b000 r--p  08:01 32899687   
/usr/share/glib-2.0/schemas/gschemas.compiled
--- end cat /proc/`pidof gnome-control-center`/maps | grep schemas ---

Regards.

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

Title:
  gnome-control-center closes with Gtk Gio Error when trying to access
  keyboard shortcut details

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

Bug description:
  Hello,

  I report this issue on behalf of someone else, I can't use the bug
  reporter on the Ubuntu machine.

  The same issue has been reported by other people on other places:

  Bug report for GNOME:
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1728

  Bug report for Debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008493

  --- lsb_release -rd ---
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  --- end lsb_release -rd ---

  --- apt-cache policy gnome-control-center ---
  gnome-control-center:
Installé : 1:41.7-0ubuntu0.22.04.4
Candidat : 1:41.7-0ubuntu0.22.04.4
   Table de version :
   *** 1:41.7-0ubuntu0.22.04.4 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:41.4-1ubuntu13.2 500
  500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:41.4-1ubuntu12 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  --- end apt-cache policy gnome-control-center ---

  Issue started after update of gnome-control-center on 24 August 2022
  (1:41.7-0ubuntu0.22.04.1 → 1:41.7-0ubuntu0.22.04.4)

  --- Snippet from /var/log/apt/history.log ---
  Start-Date: 2022-08-24  16:56:32
  Commandline: /usr/sbin/synaptic
  Requested-By: michel (1003)
  Upgrade: gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 
1:41.7-0ubun
  tu0.22.04.4), thunderbird:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 
1:91.13.
  0+build1-0ubuntu0.22.04.1), libpam-fprintd:amd64 (1.94.2-1, 
1.94.2-1ubuntu0.22.0
  4.1), isc-dhcp-common:amd64 (4.4.1-2.3ubuntu2.1, 4.4.1-2.3ubuntu2.2), 
thunderbir
  d-locale-en:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 
1:91.13.0+build1-0ubun
  tu0.22.04.1), thunderbird-locale-fr:amd64 
(1:91.12.0+build1-0ubuntu0.22.04.1~mt1
  , 1:91.13.0+build1-0ubuntu0.22.04.1), isc-dhcp-client:amd64 
(4.4.1-2.3ubuntu2.1,
   4.4.1-2.3ubuntu2.2), fprintd:amd64 (1.94.2-1, 1.94.2-1ubuntu0.22.04.1), 
gnome-c
  ontrol-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.4), 
gno
  me-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.4), 
thun
  derbird-locale-en-gb:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 
1:91.13.0+bui
  ld1-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 
(1:91.12.0+build1-0ubuntu0
  .22.04.1~mt1, 1:91.13.0+build1-0ubuntu0.22.04.1), 
thunderbird-gnome-support:amd6
  4 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.0+build1-0ubuntu0.22.04.1)
  End-Date: 2022-08-24  16:57:15
  --- end /var/log/apt/history.log ---

  The user opens gnome-control-center, the main window appears.
  The user selects the keyboard tab and click on the arrow to open the keyboard 
shortcut binding interface.

  The user expects the interface for binding keyboard shortcuts to open.

  Instead, the main gnome-control-center window closes and outputs the
  following error in the terminal:

  --- output of gnome-control-center ---

  (gnome-control-center: 647357): GLib-GIO-ERROR **: 00:31:19.451: Settings 
schema 'org.gnome.settin
  gs-daemon.plugins.media-keys' does not contain a key named 'screenshot'
  Trappe pour point d'arrêt et de trace (core dumped)
  --- end output of gnome-control-center ---

  It was working some time before the update to 1:41.7-0ubuntu0.22.04.4.

  Downgrading the package to 1:41.4-1ubuntu13.2 doesn't fix the issue.

  Regards.

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


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

[Desktop-packages] [Bug 1533631] Re: dhclient killed when DHCPv6 lease is out-of date

2022-08-30 Thread Håkan Kvist

I have filed a separate ticket on this for ubuntu 16.04 and cherry-picked the 
linked fix and tested.
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901

I didn't see this ticket before I filed my ticket.

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

Title:
  dhclient killed when DHCPv6 lease is out-of date

Status in NetworkManager:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Network Manager summarily kills the IPv6 dhclient process when the
  DHCPv6 lease contained in the dhclient6-${UUID}.lease file is out-of
  date, leaving the IPv6 interface without a stateful IPv6 address, or,
  if the "require IPv6 address on this interface" option is enabled,
  causes NM to cycle continuously deactivating and reactivating the
  interface (including the IPv4 addresses).

  This is effectively a Denial Of Service. It can be trivially induced
  if, for example, the dhclient6-$(UUID}.lease file contains a lease
  that was issued before the user went away on vacation or the PC wasn't
  connected to the same network for a few days (depending on the lease
  renew/rebind/expiry times). Calculation on the old lease of

  start + preferred_lifetime < NOW

  triggers dhclient to 'DEPREFER6' the lease (withdraw the address
  record) and ask the DHCPv6 server for a new lease, but Network Manager
  will kill the dhclient because it only sees an 'EXPIRE6' state change.

  In summary, when the DHCPv6 state transitions from "bound" to
  "unknown" then "expire" to "done" Network Manager kills the 'dhclient'
  process before it has chance to request and bind a fresh lease, If
  'dhclient' is run manually with the same command-line options and
  allowed to continue running it correctly gains a new lease.

  Network Manager doesn't know how to handle "DEPREF6", which is sent
  from isc-dhcp dhclient to the helper script (set by "-sf" option).

  So it seems that to correctly solve this issue Network Manager must be
  taught how to handle DEPREF6.

  /var/log/syslog will show a message from dhclient of the form:

  dhclient: PRC: Address 2a02:8011:2007::2 depreferred.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1533631/+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 1969901] Re: network-manager fails to renew ipv6 address

2022-08-30 Thread Håkan Kvist

It seems like https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1533631 is the same bug as this one.

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

Title:
  network-manager fails to renew ipv6 address

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Incomplete

Bug description:
  [Impact]

   * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
  used.

   * Network manager might kill dhclient(6) and fail to start it again
     causing the IPv6 address to be lost on a network that uses mixed
     IPv4/IPV6.
     The network status will still be seen as online in gnome since ipv4
     is still active.
     The user then have to manually remove the dhcpv6 lease files and
     restart ipv6 connection/restart network manager to regain IPv6
     connectivity.

   * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
     is based on 1.10.6):
     
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f

   * Upstream bug:
     https://bugzilla.gnome.org/show_bug.cgi?id=783391

  [Test Plan]

  The test requires three computers
  * one computer runing isc dhcpd server (with network configured static)
  * one computer running patched network manager
  * one computer running vanilla ubuntu

  The idea is to execute on an isolated network and trigger the error by 
changing
  ip range handed out by the dhcp-server to force a nack response back to the
  clients.

  Expected result
  * patched network keeps dhclient6 alive
  * vanilla network manager will fail to keep dhclient6 alive
in network manager logs dhcp6 will expire and not be restarted

  ON THE SERVER
  # Disable app-armor, as it has rules restricting dhcpd
  aa-teardown

  # install isc dhcpserver
  isc-dhcp-server

  # configure network static
  sudo nmcli connection modify "${CONNECTION_NAME}" \
   ipv4.method "manual" \
   ipv4.addresses "192.168.1.1/24" \
   ipv4.gateway "192.168.1.254" \
   ipv4.dns "192.168.1.1" \
   ipv6.method "manual" \
   ipv6.addresses "2001:db8:0:1::1/64" \
   ipv6.gateway "2001:db8:0:1::ffbb" \
   ipv6.dns "2001:db8:0:1::1/64"

  mkdir -p tmp
  touch tmp/dhcpd4_a.leases
  touch tmp/dhcpd4_b.leases
  touch tmp/dhcpd6_a.leases
  touch tmp/dhcpd6_b.leases

  Then it is time to execute dhcpd
  -f - run in foreground
  -d - print errors to stderr instead of syslog

  # Start in separate terminals
  dhcpd -f -d -4 -cf dhcp_v4_a.conf -lf tmp/dhcpd4_a.leases enp0s31f6
  dhcpd -f -d -6 -cf dhcp_v6_a.conf -lf tmp/dhcpd6_a.leases enp0s31f6

  Press ctrl-C to kill servers, then restart with the b configurations

  dhcpd -f -d -4 -cf dhcp_v4_b.conf -lf tmp/dhcpd4_b.leases enp0s31f6
  dhcpd -f -d -6 -cf dhcp_v6_b.conf -lf tmp/dhcpd6_b.leases enp0s31f6

  Then leases to expire (check for clients that kills dhclient)
  Press ctrl-C to kill servers, then restart with the a configurations

  ON THE CLIENTS
  Setup:
  Configure ipv6 network in settings to use dhcp (using the gui)

  Test:
  check that dhcp clients are still running:
  ps aux|grep dhclient

  Expected in output
  one client for dhcpv4
  one client for dhcpv6

  Also check network manager status :
  journalctl -u NetworkManager.service
  journalctl -u NetworkManager.service|grep dhcp6 # to only view dhclient6
  journalctl -u NetworkManager.service|grep dhcp4 # to only view dhclient4

  if dhclient is not running:
  stop network in gui
  remove lease files (/var/lib/NetworkManager/dhclient*.lease). Only remove the 
lease for the client not running.
  start network in gui

  if dhclients are running:
  wait additional ten minutes, repeat from beginning of test

  [Where problems could occur]

   * The change is in the dchp lease expiration handling so verify that
  there is no regression in dhcp renewals on different type of
  configuration include IPv6

  [Other Info]
   * We have tested this patch on a couple of clients where we have seen this
     this problem. If this patch is feasible to include in Ubuntu 18.04 we
     could request more users to test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+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 1969901] Re: network-manager fails to renew ipv6 address

2022-08-30 Thread Håkan Kvist

** Description changed:

  [Impact]
  
   * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
  used.
  
   * Network manager might kill dhclient(6) and fail to start it again
     causing the IPv6 address to be lost on a network that uses mixed
     IPv4/IPV6.
     The network status will still be seen as online in gnome since ipv4
     is still active.
     The user then have to manually remove the dhcpv6 lease files and
     restart ipv6 connection/restart network manager to regain IPv6
     connectivity.
  
   * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
     is based on 1.10.6):
     
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f
  
   * Upstream bug:
     https://bugzilla.gnome.org/show_bug.cgi?id=783391
  
  [Test Plan]
  
-  * The exact conditions for reproducing this bug on mixed IPv4/IPv6
-    networks are not known but includes using both IPv4 and IPv6,
-    both using dhcp.
+ The test requires three computers
+ * one computer runing isc dhcpd server (with network configured static)
+ * one computer running patched network manager
+ * one computer running vanilla ubuntu
+ 
+ The idea is to execute on an isolated network and trigger the error by 
changing
+ ip range handed out by the dhcp-server to force a nack response back to the
+ clients.
+ 
+ Expected result
+ * patched network keeps dhclient6 alive
+ * vanilla network manager will fail to keep dhclient6 alive
+   in network manager logs dhcp6 will expire and not be restarted
+ 
+ ON THE SERVER
+ # Disable app-armor, as it has rules restricting dhcpd
+ aa-teardown
+ 
+ # install isc dhcpserver
+ isc-dhcp-server
+ 
+ # configure network static
+ sudo nmcli connection modify "${CONNECTION_NAME}" \
+  ipv4.method "manual" \
+  ipv4.addresses "192.168.1.1/24" \
+  ipv4.gateway "192.168.1.254" \
+  ipv4.dns "192.168.1.1" \
+  ipv6.method "manual" \
+  ipv6.addresses "2001:db8:0:1::1/64" \
+  ipv6.gateway "2001:db8:0:1::ffbb" \
+  ipv6.dns "2001:db8:0:1::1/64"
+ 
+ mkdir -p tmp
+ touch tmp/dhcpd4_a.leases
+ touch tmp/dhcpd4_b.leases
+ touch tmp/dhcpd6_a.leases
+ touch tmp/dhcpd6_b.leases
+ 
+ Then it is time to execute dhcpd
+ -f - run in foreground
+ -d - print errors to stderr instead of syslog
+ 
+ # Start in separate terminals
+ dhcpd -f -d -4 -cf dhcp_v4_a.conf -lf tmp/dhcpd4_a.leases enp0s31f6
+ dhcpd -f -d -6 -cf dhcp_v6_a.conf -lf tmp/dhcpd6_a.leases enp0s31f6
+ 
+ Press ctrl-C to kill servers, then restart with the b configurations
+ 
+ dhcpd -f -d -4 -cf dhcp_v4_b.conf -lf tmp/dhcpd4_b.leases enp0s31f6
+ dhcpd -f -d -6 -cf dhcp_v6_b.conf -lf tmp/dhcpd6_b.leases enp0s31f6
+ 
+ Then leases to expire (check for clients that kills dhclient)
+ Press ctrl-C to kill servers, then restart with the a configurations
+ 
+ ON THE CLIENTS
+ Setup:
+ Configure ipv6 network in settings to use dhcp (using the gui)
+ 
+ Test:
+ check that dhcp clients are still running:
+ ps aux|grep dhclient
+ 
+ Expected in output
+ one client for dhcpv4
+ one client for dhcpv6
+ 
+ Also check network manager status :
+ journalctl -u NetworkManager.service
+ journalctl -u NetworkManager.service|grep dhcp6 # to only view dhclient6
+ journalctl -u NetworkManager.service|grep dhcp4 # to only view dhclient4
+ 
+ if dhclient is not running:
+ stop network in gui
+ remove lease files (/var/lib/NetworkManager/dhclient*.lease). Only remove the 
lease for the client not running.
+ start network in gui
+ 
+ if dhclients are running:
+ wait additional ten minutes, repeat from beginning of test
  
  [Where problems could occur]
  
   * The change is in the dchp lease expiration handling so verify that
  there is no regression in dhcp renewals on different type of
  configuration include IPv6
  
  [Other Info]
   * We have tested this patch on a couple of clients where we have seen this
     this problem. If this patch is feasible to include in Ubuntu 18.04 we
     could request more users to test.

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

Title:
  network-manager fails to renew ipv6 address

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Incomplete

Bug description:
  [Impact]

   * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
  used.

   * Network manager might kill dhclient(6) and fail to start it again
     causing the IPv6 address to be lost on a network that uses mixed
     IPv4/IPV6.
     The network status will still be seen as online in gnome since ipv4
     is still active.
     The user then have to manually remove the dhcpv6 lease files and
     restart ipv6 connection/restart network manager to regain IPv6
     connectivity.

   * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
     is based on

[Desktop-packages] [Bug 1988071] Re: Update to Unity Control Center to 7.6 version

2022-08-30 Thread Hans Joachim Desserud

** Tags added: upgrade-software-version

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

Title:
  Update to Unity Control Center to 7.6 version

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

Bug description:
  This version of Unity Control Center fixes many bugs, like the broken
  theme selector.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1988071/+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 1988087] Re: GNOME Settings has two Screen Blank controls and only one of them works.

The issue is fixed in git upstream now,
https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/37f5cbe6a
and the change will be in the next update before 22.10

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

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

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

Title:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-control-center package in Fedora:
  Unknown

Bug description:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

  Expected

  Screen Blank controls should preserve the values you set them to.

  Actual

  One of the two Screen blank controls does not preserve the value that
  you set it to.

  Version Info
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ gnome-control-center --version
  gnome-control-center 43.beta

  $ dpkg -l gnome-control-center | tail -n 1 | awk '{print $3}'
  1:43~beta-1ubuntu2

  Reproducing

  1. Run gnome-control-center power
  2. Change "Screen Blank" from the current setting (e.g. 5 minutes) to a 
different value.
  3. Change to another panel (tab) and change back to Power. (e.g. change to 
Audio then back to Power)
  4. Observe that your Screen Blank setting has reverted to the prior value 
(e.g. if you set it to "never" it will return to 5 minutes).
  5. Change to the Privacy panel, then to the Screen panel.
  6. Change the setting for Blank Screen Display to a different value.
  7. Change to another panel and then back to Privacy->Screen.
  8. Your change to the value of Blank Screen Display will have been retained 
(will be the same as you set it a moment ago).
  9. Change to the Power panel and the Screen Blank setting that you selected 
will be displayed there too.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 29 15:14:39 2022
  InstallationDate: Installed on 2022-08-29 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1988087/+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 1987388] Re: Screen Blank reset to 5 minutes

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

** This bug has been marked a duplicate of bug 1988087
   GNOME Settings has two Screen Blank controls and only one of them works.

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

Title:
  Screen Blank reset to 5 minutes

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

Bug description:
  Settings - Power - I set Screen Blank to any value different from 5
  minutes. My value is ignored, Screen Blank is reset to 5 minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 23 12:32:39 2022
  InstallationDate: Installed on 2022-08-11 (11 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220811)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987388/+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 1988087] Re: GNOME Settings has two Screen Blank controls and only one of them works.

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

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

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

Title:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

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

Bug description:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

  Expected

  Screen Blank controls should preserve the values you set them to.

  Actual

  One of the two Screen blank controls does not preserve the value that
  you set it to.

  Version Info
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ gnome-control-center --version
  gnome-control-center 43.beta

  $ dpkg -l gnome-control-center | tail -n 1 | awk '{print $3}'
  1:43~beta-1ubuntu2

  Reproducing

  1. Run gnome-control-center power
  2. Change "Screen Blank" from the current setting (e.g. 5 minutes) to a 
different value.
  3. Change to another panel (tab) and change back to Power. (e.g. change to 
Audio then back to Power)
  4. Observe that your Screen Blank setting has reverted to the prior value 
(e.g. if you set it to "never" it will return to 5 minutes).
  5. Change to the Privacy panel, then to the Screen panel.
  6. Change the setting for Blank Screen Display to a different value.
  7. Change to another panel and then back to Privacy->Screen.
  8. Your change to the value of Blank Screen Display will have been retained 
(will be the same as you set it a moment ago).
  9. Change to the Power panel and the Screen Blank setting that you selected 
will be displayed there too.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 29 15:14:39 2022
  InstallationDate: Installed on 2022-08-29 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1988087/+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 1988087] Re: GNOME Settings has two Screen Blank controls and only one of them works.

** Bug watch added: Red Hat Bugzilla #2122659
   https://bugzilla.redhat.com/show_bug.cgi?id=2122659

** Also affects: gnome-control-center (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=2122659
   Importance: Unknown
   Status: Unknown

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

Title:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

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

Bug description:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

  Expected

  Screen Blank controls should preserve the values you set them to.

  Actual

  One of the two Screen blank controls does not preserve the value that
  you set it to.

  Version Info
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ gnome-control-center --version
  gnome-control-center 43.beta

  $ dpkg -l gnome-control-center | tail -n 1 | awk '{print $3}'
  1:43~beta-1ubuntu2

  Reproducing

  1. Run gnome-control-center power
  2. Change "Screen Blank" from the current setting (e.g. 5 minutes) to a 
different value.
  3. Change to another panel (tab) and change back to Power. (e.g. change to 
Audio then back to Power)
  4. Observe that your Screen Blank setting has reverted to the prior value 
(e.g. if you set it to "never" it will return to 5 minutes).
  5. Change to the Privacy panel, then to the Screen panel.
  6. Change the setting for Blank Screen Display to a different value.
  7. Change to another panel and then back to Privacy->Screen.
  8. Your change to the value of Blank Screen Display will have been retained 
(will be the same as you set it a moment ago).
  9. Change to the Power panel and the Screen Blank setting that you selected 
will be displayed there too.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 29 15:14:39 2022
  InstallationDate: Installed on 2022-08-29 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1988087/+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 1987976] Re: firefox black window

Yes, I can now see the screenshot.

And if you run from a terminal with just "snap run firefox" (i.e.
without any definition of MOZ_ENABLE_WAYLAND), do you get a black
screen?

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

Title:
  firefox black window

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987976/+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 1965094] Re: "Additional Drivers" application crashes on startup

Alberto, could you review that one?

** Changed in: ubuntu-drivers-common (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  "Additional Drivers" application crashes on startup

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  * Click on "Show applications" in the dock
  * Click on "Additional Drivers"

  Expected:
  It is possible to see and install additional drivers
  Actual:
  Application "software-properties-gtk" crashes

  
  Background: I installed 22.04 daily build from scratch on my new Samsung 
laptop just a few days ago and I have almost no custom settings.

  Output from screenfetch:

./+o+-   [...]
y- -yy+  OS: Ubuntu 22.04 jammy
 ://+//-yyo  Kernel: x86_64 Linux 5.15.0-22-generic
 .++ .:/++/-.+sss/`  Uptime: 1d 9h 37m
   .:++o:  //:--:/-  Packages: 1810
  o:+o+:++.`..```.-/oo+/ Shell: bash 5.1.16
 .:+o:+o/.  `+sssoo+/Resolution: 3840x1080
.++/+:+oo+o:` /sssooo.   DE: GNOME 41.4
   /+++//+:`oo+o   /::--:.   WM: Mutter
   \+/+o+++`o++o   ++.   WM Theme: Adwaita
.++.o+++oo+:` /dddhhh.   GTK Theme: Yaru-dark [GTK2/3]
 .+.o+oo:.  `odd+Icon Theme: Yaru
  \+.++o+o``-.:ohdh+ Font: Ubuntu 11
   `:o+++ `oyo++os:  Disk: 21G / 1,2T (2%)
 .o:`.syhhh/.oo++o`  CPU: 11th Gen Intel Core i7-1165G7 @ 
8x 4,7GHz [40.0°C]
 /osyyo++ooo+++/ GPU: Iris Xe Graphics
 ` +oo+++o\: RAM: 2627MiB / 15725MiB
`oo++.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: software-properties-gtk 0.99.19
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 16 08:34:57 2022
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2022-03-14 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  InterpreterPath: /usr/bin/python3.10
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4
  Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 
3.10.1-0ubuntu1
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4']
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with AttributeError in 
packages_for_modalias(): 'Cache' object has no attribute 'packages'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1965094/+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 1968588] Re: Cannot create or add VPN in connection editor

** Tags removed: rls-jj-incoming

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

Title:
  Cannot create or add VPN in connection editor

Status in Network Manager Applet:
  New
Status in network-manager-applet package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed
Status in network-manager-applet source package in Jammy:
  Confirmed
Status in network-manager-vpnc source package in Jammy:
  Confirmed

Bug description:
  In 22.04 I am unable to create a new VPN in network manager and nm-
  connection-editor. After filing in the entire form the save button
  remains disabled!

  watching the terminal provides this error:
  Cannot save connection due to error: Invalid setting General: 
connection.interface-name: '': interface name must not be empty

  Seems like the form validator is not looking at the right field!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager-gnome 1.24.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 11 10:49:34 2022
  ExecutablePath: /usr/bin/nm-connection-editor
  InstallationDate: Installed on 2022-04-09 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE  FILENAME
   
   Wired connection 1  31e61843-ef5f-31e8-96a2-cf86d47e015c  ethernet  
1649688323  Mon 11 Apr 2022 10:45:23 AM EDT  yes  -999  
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s3  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/run/NetworkManager/system-connections/Wired connection 1.nmconnection
  nmcli-dev:
   DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTION  CON-UUID 
 CON-PATH   
   enp0s3  ethernet  connected  full  limited   
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
31e61843-ef5f-31e8-96a2-cf86d47e015c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1968588/+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 1988087] Re: GNOME Settings has two Screen Blank controls and only one of them works.

** Description changed:

  GNOME Settings has two Screen Blank controls and only one of them works.
  
  Expected
  
  Screen Blank controls should preserve the values you set them to.
  
  Actual
  
  One of the two Screen blank controls does not preserve the value that
  you set it to.
  
  Version Info
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic
  
  $ gnome-control-center --version
  gnome-control-center 43.beta
  
  $ dpkg -l gnome-control-center | tail -n 1 | awk '{print $3}'
  1:43~beta-1ubuntu2
  
  Reproducing
  
  1. Run gnome-control-center power
  2. Change "Screen Blank" from the current setting (e.g. 5 minutes) to a 
different value.
- 3. Change to another panel (tab) and change back to Power.
- 4. Observe that you Screen Blank setting has reverted to the prior value 
(e.g. if you set it to "never" it will return to 5 minutes).
+ 3. Change to another panel (tab) and change back to Power. (e.g. change to 
Audio then back to Power)
+ 4. Observe that your Screen Blank setting has reverted to the prior value 
(e.g. if you set it to "never" it will return to 5 minutes).
  5. Change to the Privacy panel, then to the Screen panel.
  6. Change the setting for Blank Screen Display to a different value.
  7. Change to another panel and then back to Privacy->Screen.
  8. Your change to the value of Blank Screen Display will have been retained 
(will be the same as you set it a moment ago).
  9. Change to the Power panel and the Screen Blank setting that you selected 
will be displayed there too.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 29 15:14:39 2022
  InstallationDate: Installed on 2022-08-29 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

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

Bug description:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

  Expected

  Screen Blank controls should preserve the values you set them to.

  Actual

  One of the two Screen blank controls does not preserve the value that
  you set it to.

  Version Info
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ gnome-control-center --version
  gnome-control-center 43.beta

  $ dpkg -l gnome-control-center | tail -n 1 | awk '{print $3}'
  1:43~beta-1ubuntu2

  Reproducing

  1. Run gnome-control-center power
  2. Change "Screen Blank" from the current setting (e.g. 5 minutes) to a 
different value.
  3. Change to another panel (tab) and change back to Power. (e.g. change to 
Audio then back to Power)
  4. Observe that your Screen Blank setting has reverted to the prior value 
(e.g. if you set it to "never" it will return to 5 minutes).
  5. Change to the Privacy panel, then to the Screen panel.
  6. Change the setting for Blank Screen Display to a different value.
  7. Change to another panel and then back to Privacy->Screen.
  8. Your change to the value of Blank Screen Display will have been retained 
(will be the same as you set it a moment ago).
  9. Change to the Power panel and the Screen Blank setting that you selected 
will be displayed there too.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 29 15:14:39 2022
  InstallationDate: Installed on 2022-08-29 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably

[Desktop-packages] [Bug 1699942] Re: network-manager fails to deprecate addresses

The bug is from 2017 without activity until now, from a desktop
perspective it isn't a rls issue, tagging a notfixing

** Tags removed: rls-kk-incoming
** Tags added: rls-kk-notfixing

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

Title:
  network-manager fails to deprecate addresses

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  network manager does not properly deprecate autoconfigured temporary IP 
addresses when ValidLifetime for a prefix is 0 in router advertisements. This 
behaviour is non-compliant with RFC 4861 § 6.3.4, which reads:
  If the prefix is already present in the host's Prefix List as
  the result of a previously received advertisement, reset its
  invalidation timer to the Valid Lifetime value in the Prefix
  Information option.  If the new Lifetime value is zero, time-out
  the prefix immediately.

  The hosts instead continued to use temporary addresses configured
  until they reached their timeout, rather than immediately dropping the
  addresses. It further appears that it is generating new temporary
  addresses when the previous ones expire, but I have not been
  monitoring hosts closely enough to tell for sure---I will update on
  this when I have further information.

  This problem was discovered on Ubuntu Studio 16.04.2; it is not
  present on Ubuntu Server (which uses Debian networking scripts).

  Additional Info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  $ apt-cache policy network-manager
  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.1
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   *** 1.2.6-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+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 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages

2022-08-30 Thread Alberto Milone

** Description changed:

+ [Impact]
+ 
+  * Linux-restricted-modules for the 390 drivers were disabled
+ temporarily back in January, however they were not re-enabled when
+ support for the new kernel was added.
+ 
+  * Including the 390 release in the ISO causes the 5.13 packages to be
+ pulled in.
+ 
+ [Test Plan]
+ 
+  * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver
+ can be installed with its linux-restricted-modules.
+ 
+ [Where problems could occur]
+ 
+  * The addition of modules for an already existing driver series would not
+cause any regressions, since the whole package generation process is 
automated, and this is the only commit that we are going to revert:
+ 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020
+ 
+ [Other Info]
+  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance
+ _
+ 
  Examining the .list file for the amd64 image it contains various kernel
  5.13 .deb packages.
  
  http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
  amd64.list
  
  e.g.
  
  
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
  
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
  This is a little unexpected given that 5.15 is the default kernel.
  
  Possibly nvidia-390 doesn't have 5.15 packages?
  
  This impacts all flavours as well that include nvidia stuff in their ISO
  - so if the solution is to change the meta file for a revised regexp for
  nvidia then all flavours that include nvidia will likewise need their
  meta packages updated.

** Description changed:

  [Impact]
  
-  * Linux-restricted-modules for the 390 drivers were disabled
+  * Linux-restricted-modules for the 390 drivers were disabled
  temporarily back in January, however they were not re-enabled when
  support for the new kernel was added.
  
-  * Including the 390 release in the ISO causes the 5.13 packages to be
+  * Including the 390 release in the ISO causes the 5.13 packages to be
  pulled in.
  
  [Test Plan]
  
-  * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver
+  * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver
  can be installed with its linux-restricted-modules.
  
  [Where problems could occur]
  
-  * The addition of modules for an already existing driver series would not
-cause any regressions, since the whole package generation process is 
automated, and this is the only commit that we are going to revert:
+  * The addition of modules for an already existing driver series would not
+    cause any regressions, since the whole package generation process is 
automated, and this is the only commit that we are going to revert:
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020
  
  [Other Info]
-  
-  * Anything else you think is useful to include
-  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
-  * and address these questions in advance
+ 
+  * Other kernel releases support the 390 series.
  _
  
  Examining the .list file for the amd64 image it contains various kernel
  5.13 .deb packages.
  
  http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
  amd64.list
  
  e.g.
  
  
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
  
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
  This is a little unexpected given that 5.15 is the default kernel.
  
  Possibly nvidia-390 doesn't have 5.15 packages?
  
  This impacts all flavours as well that include nvidia stuff in their ISO
  - so if the solution is to change the meta file for a revised regexp for
  nvidia then all flavours that include nvidia will likewise need their
  meta packages updated.

[Desktop-packages] [Bug 1988062] Re: Tests are failing on builders with proxy set

** Changed in: glib-networking (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Tests are failing on builders with proxy set

Status in glib-networking package in Ubuntu:
  Fix Released

Bug description:
  Reported upstream https://gitlab.gnome.org/GNOME/glib-
  networking/-/issues/195

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1988062/+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 1982959] Re: When I send an email in Thunderbird in the Ubuntu 22.04 Daily Build from 07/27/2022 08:35 , the desktop environment crashes.

Thanks for following up!

** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  When I send an email in Thunderbird in the Ubuntu 22.04 Daily Build
  from  07/27/2022 08:35  , the desktop environment crashes.

Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  Whenever I send an email in Thunderbird in Ubuntu 22.04 Daily Build from  
07/27/2022 08:35, the desktop environment crashes.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1587 F wireplumber
   /dev/snd/seq:max1580 F pipewire
  BuildID: 20220725200630
  CasperMD5CheckResult: pass
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:306
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 22.10
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-07-28 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220727)
  IpRoute:
   default via 192.168.188.1 dev enp0s3 proto dhcp src 192.168.188.50 metric 
100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000 
   192.168.188.0/24 dev enp0s3 proto kernel scope link src 192.168.188.50 
metric 100
  Package: thunderbird 1:102.1.0+build2-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:306
  Profile0PrefSources: prefs.js
  Profile0Prefs:
   extensions.lastAppVersion: "102.1.0" (prefs.js)
   places.database.lastMaintenance: 1659004289 (prefs.js)
   privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js)
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=102.1.0/20220725200630 (In use)
  RunningIncompatibleAddons: False
  Tags:  kinetic wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1982959/+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 1982963] Re: Firefox produces a black window

Good to know, thanks for following up!

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Firefox produces a black window

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  When I start Firefox in Ubuntu 22.10 Daily Build from 07/27/2022
  08:35, it´s window is black.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1982963/+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 1988160] Re: gjs-console crashed with SIGABRT in g_assertion_message_expr()

2022-08-30 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private Security to Public Security

** Tags removed: need-amd64-retrace

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

Title:
  gjs-console crashed with SIGABRT in g_assertion_message_expr()

Status in gjs package in Ubuntu:
  New

Bug description:
  dopo sudo do-release-upgrade, ho avuto questo messaggio: "Ubuntu ha
  riscontrato un errore interno",chi mi può aiutare ?

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gjs 1.73.2-1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 30 13:47:22 2022
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2022-08-29 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcCmdline: /usr/bin/gjs /usr/bin/gnome-characters --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: gjs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
  Title: gjs-console crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1988160/+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 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages

2022-08-30 Thread Łukasz Zemczak

...discussed this with the kernel team and it seems to be a bug in the
5.15 hwe lrm kernel packages. Apparently because of an error, the
nvidia-390 packages have not been prepared for this kernel. And since we
pull in 390 (and should), this causes the build infrastructure to pull
in the old 5.13 kernels along with them.

The kernel team is working on a lrm-only respin.

** Also affects: linux-restricted-modules-hwe-5.15 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Invalid

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

Title:
  20.04.5 (20220829.1 build) has kernel 5.13 packages

Status in linux-restricted-modules-hwe-5.15 package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Examining the .list file for the amd64 image it contains various
  kernel 5.13 .deb packages.

  http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
  amd64.list

  e.g.

  
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
  
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb

  This is a little unexpected given that 5.15 is the default kernel.

  Possibly nvidia-390 doesn't have 5.15 packages?

  This impacts all flavours as well that include nvidia stuff in their
  ISO - so if the solution is to change the meta file for a revised
  regexp for nvidia then all flavours that include nvidia will likewise
  need their meta packages updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/1988143/+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 1988159] [NEW] Nautilus cannot open password-protected .rar File

2022-08-30 Thread Marcel Steiner

Public bug reported:


I use Ubuntu 22.04 and I have installed sudo apt install unrar. But if I
want to open a password protected .rar file in Nautilus with Extract
here... then it should ask me the password, but instead the error There
was an error extracting name.rar and Block checksum error: got Oxe3,
expected 0x71 pops up.

If I open it via a terminal with unrar e name.rar it works perfectly.
If I double click the name.rar then it opens a window and I am asked to 
give the password and I can nicely extract the content

In 20.04 this works fine.

https://askubuntu.com/questions/1425302/nautilus-cannot-open-password-
protected-rar-file

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: file-roller 3.42.0-1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 30 13:51:07 2022
InstallationDate: Installed on 2022-07-07 (54 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: file-roller
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Nautilus cannot open password-protected .rar File

Status in file-roller package in Ubuntu:
  New

Bug description:

  I use Ubuntu 22.04 and I have installed sudo apt install unrar. But if
  I want to open a password protected .rar file in Nautilus with Extract
  here... then it should ask me the password, but instead the error
  There was an error extracting name.rar and Block checksum error: got
  Oxe3, expected 0x71 pops up.

  If I open it via a terminal with unrar e name.rar it works perfectly.
  If I double click the name.rar then it opens a window and I am asked to 
give the password and I can nicely extract the content

  In 20.04 this works fine.

  https://askubuntu.com/questions/1425302/nautilus-cannot-open-password-
  protected-rar-file

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: file-roller 3.42.0-1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 30 13:51:07 2022
  InstallationDate: Installed on 2022-07-07 (54 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: file-roller
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1988159/+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 1988087] Re: GNOME Settings has two Screen Blank controls and only one of them works.

This is no longer true:
no longer affects:  gnome-control-center (Debian) 

Which is to say this does affect Debian (bookworm/sid) "unstable".

** Bug watch added: Debian Bug tracker #1018762
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018762

** Also affects: gnome-control-center via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018762
   Importance: Unknown
   Status: Unknown

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

Title:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

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

Bug description:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

  Expected

  Screen Blank controls should preserve the values you set them to.

  Actual

  One of the two Screen blank controls does not preserve the value that
  you set it to.

  Version Info
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ gnome-control-center --version
  gnome-control-center 43.beta

  $ dpkg -l gnome-control-center | tail -n 1 | awk '{print $3}'
  1:43~beta-1ubuntu2

  Reproducing

  1. Run gnome-control-center power
  2. Change "Screen Blank" from the current setting (e.g. 5 minutes) to a 
different value.
  3. Change to another panel (tab) and change back to Power.
  4. Observe that you Screen Blank setting has reverted to the prior value 
(e.g. if you set it to "never" it will return to 5 minutes).
  5. Change to the Privacy panel, then to the Screen panel.
  6. Change the setting for Blank Screen Display to a different value.
  7. Change to another panel and then back to Privacy->Screen.
  8. Your change to the value of Blank Screen Display will have been retained 
(will be the same as you set it a moment ago).
  9. Change to the Power panel and the Screen Blank setting that you selected 
will be displayed there too.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 29 15:14:39 2022
  InstallationDate: Installed on 2022-08-29 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1988087/+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 1988155] [NEW] conflicts with gnome-text-editor

Public bug reported:

Upgrading to kinetic

Dépaquetage de ghex (43~alpha-1) sur (3.41.1-1) ...
dpkg: erreur de traitement de l'archive 
/tmp/apt-dpkg-install-EiOQj3/0596-ghex_43~alpha-1_amd64.deb (--unpack) :
 tentative de remplacement de « 
/usr/share/icons/hicolor/scalable/actions/document-modified-symbolic.svg », qui 
appar
tient aussi au paquet gnome-text-editor 42.2-1ubuntu1

** Affects: gnome-text-editor (Ubuntu)
 Importance: High
 Status: Invalid

** Changed in: gnome-text-editor (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-text-editor (Ubuntu)
   Status: New => Invalid

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

Title:
  conflicts with gnome-text-editor

Status in gnome-text-editor package in Ubuntu:
  Invalid

Bug description:
  Upgrading to kinetic

  Dépaquetage de ghex (43~alpha-1) sur (3.41.1-1) ...
  dpkg: erreur de traitement de l'archive 
/tmp/apt-dpkg-install-EiOQj3/0596-ghex_43~alpha-1_amd64.deb (--unpack) :
   tentative de remplacement de « 
/usr/share/icons/hicolor/scalable/actions/document-modified-symbolic.svg », qui 
appar
  tient aussi au paquet gnome-text-editor 42.2-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1988155/+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 1988156] [NEW] conflicts with ghex

Public bug reported:

Upgrading to kinetic

Dépaquetage de ghex (43~alpha-1) sur (3.41.1-1) ...
dpkg: erreur de traitement de l'archive 
/tmp/apt-dpkg-install-EiOQj3/0596-ghex_43~alpha-1_amd64.deb (--unpack) :
 tentative de remplacement de « 
/usr/share/icons/hicolor/scalable/actions/document-modified-symbolic.svg », qui 
appar
tient aussi au paquet gnome-text-editor 42.2-1ubuntu1

** Affects: gnome-text-editor (Ubuntu)
 Importance: High
 Assignee: Jeremy Bicha (jbicha)
 Status: Confirmed

** Changed in: gnome-text-editor (Ubuntu)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: gnome-text-editor (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-text-editor (Ubuntu)
   Status: New => Confirmed

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

Title:
  conflicts with ghex

Status in gnome-text-editor package in Ubuntu:
  Confirmed

Bug description:
  Upgrading to kinetic

  Dépaquetage de ghex (43~alpha-1) sur (3.41.1-1) ...
  dpkg: erreur de traitement de l'archive 
/tmp/apt-dpkg-install-EiOQj3/0596-ghex_43~alpha-1_amd64.deb (--unpack) :
   tentative de remplacement de « 
/usr/share/icons/hicolor/scalable/actions/document-modified-symbolic.svg », qui 
appar
  tient aussi au paquet gnome-text-editor 42.2-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1988156/+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 1988151] Re: Printer not working anymore after update

2022-08-30 Thread Chris Guiver

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

You've provided no details of what Ubuntu product you're using, what
release, what package(s) are involved, type of connections, is this a
new install (days?, weeks? months?)? old install (days? weeks? months?
years?) with changes made etc...  You do mention updates, but gave no
specifics. Support would likely help you better, and this question can
be turned into a Support Question too.

I've marked this as 'incomplete', if you believe I'm in error and do
wish to report a bug, status can be returned to "New" after you've left
a comment provide details so package involved in the bug-filing can be
determined, then you'll be requested to provide more details (via
`apport-collect`)

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

Title:
  Printer not working anymore after update

Status in cups package in Ubuntu:
  New

Bug description:
  Multifunction printer (Brother MFC-J6510DW) not working anymore.
  Since one of the last updates the printer is cancelling the print job it 
receives.
  Reinstallation of the driver/printer trying all available connections did not 
bring success.
  (dnssd, IPP, LPD, Socket, etc. using cups, with and without dedicated driver 
.ppd.)

  Printer scan function is working, though.

  Printer works under windows.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1988151/+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 1988151] Re: Printer not working anymore after update

2022-08-30 Thread Paul White

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

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

Title:
  Printer not working anymore after update

Status in cups package in Ubuntu:
  New

Bug description:
  Multifunction printer (Brother MFC-J6510DW) not working anymore.
  Since one of the last updates the printer is cancelling the print job it 
receives.
  Reinstallation of the driver/printer trying all available connections did not 
bring success.
  (dnssd, IPP, LPD, Socket, etc. using cups, with and without dedicated driver 
.ppd.)

  Printer scan function is working, though.

  Printer works under windows.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1988151/+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 1988151] [NEW] Printer not working anymore after update

You have been subscribed to a public bug:

Multifunction printer (Brother MFC-J6510DW) not working anymore.
Since one of the last updates the printer is cancelling the print job it 
receives.
Reinstallation of the driver/printer trying all available connections did not 
bring success.
(dnssd, IPP, LPD, Socket, etc. using cups, with and without dedicated driver 
.ppd.)

Printer scan function is working, though.

Printer works under windows.

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


** Tags: connectivity printer
-- 
Printer not working anymore after update
https://bugs.launchpad.net/bugs/1988151
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to cups 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 1982959] Re: When I send an email in Thunderbird in the Ubuntu 22.04 Daily Build from 07/27/2022 08:35 , the desktop environment crashes.

2022-08-30 Thread Tassilo Mödl

Oh, the error is fixed in the today´s build!

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

Title:
  When I send an email in Thunderbird in the Ubuntu 22.04 Daily Build
  from  07/27/2022 08:35  , the desktop environment crashes.

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  Whenever I send an email in Thunderbird in Ubuntu 22.04 Daily Build from  
07/27/2022 08:35, the desktop environment crashes.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1587 F wireplumber
   /dev/snd/seq:max1580 F pipewire
  BuildID: 20220725200630
  CasperMD5CheckResult: pass
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:306
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 22.10
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-07-28 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220727)
  IpRoute:
   default via 192.168.188.1 dev enp0s3 proto dhcp src 192.168.188.50 metric 
100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000 
   192.168.188.0/24 dev enp0s3 proto kernel scope link src 192.168.188.50 
metric 100
  Package: thunderbird 1:102.1.0+build2-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:306
  Profile0PrefSources: prefs.js
  Profile0Prefs:
   extensions.lastAppVersion: "102.1.0" (prefs.js)
   places.database.lastMaintenance: 1659004289 (prefs.js)
   privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js)
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=102.1.0/20220725200630 (In use)
  RunningIncompatibleAddons: False
  Tags:  kinetic wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1982959/+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 1982963] Re: Firefox produces a black window

2022-08-30 Thread Tassilo Mödl

Oh, the error is fixed in the today´s release!

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

Title:
  Firefox produces a black window

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When I start Firefox in Ubuntu 22.10 Daily Build from 07/27/2022
  08:35, it´s window is black.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1982963/+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 1988149] [NEW] Gnome puts the machine into sleep mode although it is a server with no need or requirement for users to use Gnome

2022-08-30 Thread richard shooter

Public bug reported:

Installing mythtv (all standard packages and versions which I assume are
captured by this suite of tools).  Installing either the server with
desktop or server without desktop (adding mythtv-backend-master) and
then installing mythtv-backend-master adds Gnome desktop in.

Configuring the server using ssh (i.e. not the desktop environment on
the system) the server is put to sleep by Gnome after ~20 minutes.  This
appears to be because there has been no activity on the GDM managed GUI
desktop session.

It appears to be resolved by setting the properties below from the
command line or editing the gdm3 defaults as shown below (hopefully belt
and braces - no AC timer and don't do anything on the timer expiring).

The machine is an old Intel i3 NUC so perhaps is being detected as a
latop (which is why I'm repoprting this)  but in any case it's the
server version of Ubuntu and who wants their server put to sleep if no-
one's using a GUI for 20 minutes?


sudo vi /etc/gdm3/greeter.dconf-defaults
# Automatic suspend
# =
[org/gnome/settings-daemon/plugins/power]
# - Time inactive in seconds before suspending with AC power
#   1200=20 minutes, 0=never
sleep-inactive-ac-timeout=0
# - What to do after sleep-inactive-ac-timeout
#   'blank', 'suspend', 'shutdown', 'hibernate', 'interactive' or 
'nothing'
sleep-inactive-ac-type='nothing'

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
Date: Tue Aug 30 10:35:51 2022
InstallationDate: Installed on 2022-08-30 (0 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
ProcEnviron:
 SHELL=/bin/bash
 LANG=C.UTF-8
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Gnome puts the machine into sleep mode although it is a server with no
  need or requirement for users to use Gnome

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Installing mythtv (all standard packages and versions which I assume
  are captured by this suite of tools).  Installing either the server
  with desktop or server without desktop (adding mythtv-backend-master)
  and then installing mythtv-backend-master adds Gnome desktop in.

  Configuring the server using ssh (i.e. not the desktop environment on
  the system) the server is put to sleep by Gnome after ~20 minutes.
  This appears to be because there has been no activity on the GDM
  managed GUI desktop session.

  It appears to be resolved by setting the properties below from the
  command line or editing the gdm3 defaults as shown below (hopefully
  belt and braces - no AC timer and don't do anything on the timer
  expiring).

  The machine is an old Intel i3 NUC so perhaps is being detected as a
  latop (which is why I'm repoprting this)  but in any case it's the
  server version of Ubuntu and who wants their server put to sleep if
  no-one's using a GUI for 20 minutes?


  sudo vi /etc/gdm3/greeter.dconf-defaults
  # Automatic suspend
  # =
[org/gnome/settings-daemon/plugins/power]
# - Time inactive in seconds before suspending with AC power
#   1200=20 minutes, 0=never
sleep-inactive-ac-timeout=0
# - What to do after sleep-inactive-ac-timeout
#   'blank', 'suspend', 'shutdown', 'hibernate', 'interactive' or 
'nothing'
sleep-inactive-ac-type='nothing'

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  Date: Tue Aug 30 10:35:51 2022
  InstallationDate: Installed on 2022-08-30 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1988149/+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 1987628] Re: Xwayland fails to start on Xilinx: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane

Patch for jammy

** Patch added: "xwayland_22.1.1-1ubuntu0.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1987628/+attachment/5612505/+files/xwayland_22.1.1-1ubuntu0.2.debdiff

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

Title:
  Xwayland fails to start on Xilinx: symbol lookup error:
  /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane

Status in xwayland package in Ubuntu:
  Fix Released
Status in xwayland source package in Jammy:
  In Progress

Bug description:
  [Impact]

  Xwayland fails to start on Xilinx:

  /usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined
  symbol: gbm_bo_get_fd_for_plane

  Without Xwayland you cannot run X11 apps in Wayland sessions (or even
  log into a gnome-shell Wayland session).

  [Test Plan]

  Run: Xwayland -h

  Expected: Command line options to be displayed.

  Observed: symbol lookup error: /usr/bin/Xwayland: undefined symbol:
  gbm_bo_get_fd_for_plane

  [Where problems could occur]

  Since this changes Xwayland initialization for all platforms, risk of
  bugs and regressions reaches all platforms. At best an Xwayland
  failure would prevent X11 apps from working properly, or at worst
  prevent gnome-shell Wayland sessions from starting (this bug).

  [Other Info]

  Fixing this for jammy is a prerequisite to resolve bug 1961563.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1987628/+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 1987945] Re: [snap] chromium does not read root-owned files in $HOME

2022-08-30 Thread Walter

Thanks for the forward!

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

Title:
[snap] chromium does not read root-owned files in $HOME

Status in chromium-browser package in Ubuntu:
Confirmed

Bug description:
Today, I literally spent hours trying to figure out why I cound't
upload a large file.

Of course I thought the problem was the size of the file.

It wasn't. The problem was that Chromium in Snap for some reason is
confined so that it can SEE file-owned-by-root.zip, but NOT READ file-
owned-by-root.zip.

I tried to upload the big file onto a PsiTransfer webpage. And it
simply stalled. The apache2 backend reported 400-errors and I got no
useful info out of that.

Chromium itself reported this in the Networking tab:

PATCH https://PSITRANSFER_HOST/path net::ERR_FAILED

Which is totally useless. In no way could I expect that the ultimate
cause was that the local file was not owned by me.

_If I can see the file, and I have read-permissions on it, I expect
that I can upload the file._

Another example:

$ ls -l ~/Junk/rode_muur*
-rw-rw-r-- 1 walter walter 64773 aug 27 18:08 /home/walter/Junk/rode_muur.jpg
-rw-rw-r-- 1 root root 64773 aug 27 18:08
/home/walter/Junk/rode_muur_root.jpg

Trying to upload rode_muur_root.jpg to e.g.
https://www.filestack.com/fileschool/html/html-file-upload-tutorial-
example/ yields this error-page:

This site can’t be reached
The webpage at
https://www.filestack.com/fileschool/html/html-file-upload-tutorial-example/fileupload.php
might be temporarily down or it may have moved permanently to a new web
address.
ERR_ACCESS_DENIED

That does not tell me that there is a problem with the local file.
That looks like a remote problem, am I right?

What would be the fix?

- Either don't show the file, if you're not letting me access it;
- or let me access the file;
- or, if that isn't possible, give me a reasonable error message. Having to
look in journalctl [1] as root to find out why a client application is
misbehaving is just not acceptable.

[1] # journalctl -t audit -n1 -o cat
AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium"
name="/home/walter/Junk/rode_muur_root.jpg" pid=768825 comm="ThreadPoolForeg"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

(I know that I'll be complaining to deaf ears. You have your reasons
for putting all the browsers in snap. But from a user's perspective,
this whole snap thing has been One Giant Disappointment. I'm actually
considering moving to alternative distros after more than 10 perfectly
satisfactory years on Ubuntu.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987945/+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 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages

2022-08-30 Thread fossfreedom

** Description changed:

  Examining the .list file for the amd64 image it contains various kernel
  5.13 .deb packages.
  
  http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
  amd64.list
  
  e.g.
  
  
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
  
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
  This is a little unexpected given that 5.15 is the default kernel.
  
  Possibly nvidia-390 doesn't have 5.15 packages?
+ 
+ This impacts all flavours as well that include nvidia stuff in their ISO
+ - so if the solution is to change the meta file for a revised regexp for
+ nvidia then all flavours that include nvidia will likewise need their
+ meta packages updated.

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

Title:
  20.04.5 (20220829.1 build) has kernel 5.13 packages

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Examining the .list file for the amd64 image it contains various
  kernel 5.13 .deb packages.

  http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
  amd64.list

  e.g.

  
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
  
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb

  This is a little unexpected given that 5.15 is the default kernel.

  Possibly nvidia-390 doesn't have 5.15 packages?

  This impacts all flavours as well that include nvidia stuff in their
  ISO - so if the solution is to change the meta file for a revised
  regexp for nvidia then all flavours that include nvidia will likewise
  need their meta packages updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1988143/+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 1987628] Re: Xwayland fails to start on Xilinx: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane

** Description changed:

+ [Impact]
+ 
  Xwayland fails to start on Xilinx:
  
  /usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined
  symbol: gbm_bo_get_fd_for_plane
  
  This is particularly important since it prevents gnome-shell from
  starting Wayland sessions.
+ 
+ [Test Plan]
+ 
+ Run: Xwayland -h
+ 
+ Expected: Command line options to be displayed.
+ 
+ Observed: symbol lookup error: /usr/bin/Xwayland: undefined symbol:
+ gbm_bo_get_fd_for_plane
+ 
+ [Where problems could occur]
+ 
+ Since this changes Xwayland initialization for all platforms, risk of
+ bugs and regressions reaches all platforms. Without Xwayland you cannot
+ run X11 apps in Wayland sessions (or even log into a gnome-shell Wayland
+ session).
+ 
+ [Other Info]
+  
+ Fixing this for jammy is a prerequisite to resolve bug 1961563.

** Description changed:

  [Impact]
  
  Xwayland fails to start on Xilinx:
  
  /usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined
  symbol: gbm_bo_get_fd_for_plane
  
- This is particularly important since it prevents gnome-shell from
- starting Wayland sessions.
+ Without Xwayland you cannot run X11 apps in Wayland sessions (or even
+ log into a gnome-shell Wayland session).
  
  [Test Plan]
  
  Run: Xwayland -h
  
  Expected: Command line options to be displayed.
  
  Observed: symbol lookup error: /usr/bin/Xwayland: undefined symbol:
  gbm_bo_get_fd_for_plane
  
  [Where problems could occur]
  
  Since this changes Xwayland initialization for all platforms, risk of
- bugs and regressions reaches all platforms. Without Xwayland you cannot
- run X11 apps in Wayland sessions (or even log into a gnome-shell Wayland
- session).
+ bugs and regressions reaches all platforms.
  
  [Other Info]
-  
+ 
  Fixing this for jammy is a prerequisite to resolve bug 1961563.

** Description changed:

  [Impact]
  
  Xwayland fails to start on Xilinx:
  
  /usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined
  symbol: gbm_bo_get_fd_for_plane
  
  Without Xwayland you cannot run X11 apps in Wayland sessions (or even
  log into a gnome-shell Wayland session).
  
  [Test Plan]
  
  Run: Xwayland -h
  
  Expected: Command line options to be displayed.
  
  Observed: symbol lookup error: /usr/bin/Xwayland: undefined symbol:
  gbm_bo_get_fd_for_plane
  
  [Where problems could occur]
  
  Since this changes Xwayland initialization for all platforms, risk of
- bugs and regressions reaches all platforms.
+ bugs and regressions reaches all platforms. At best an Xwayland failure
+ would prevent X11 apps from working properly, or at worst prevent gnome-
+ shell Wayland sessions from starting (this bug).
  
  [Other Info]
  
  Fixing this for jammy is a prerequisite to resolve bug 1961563.

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

Title:
  Xwayland fails to start on Xilinx: symbol lookup error:
  /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane

Status in xwayland package in Ubuntu:
  Fix Released
Status in xwayland source package in Jammy:
  In Progress

Bug description:
  [Impact]

  Xwayland fails to start on Xilinx:

  /usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined
  symbol: gbm_bo_get_fd_for_plane

  Without Xwayland you cannot run X11 apps in Wayland sessions (or even
  log into a gnome-shell Wayland session).

  [Test Plan]

  Run: Xwayland -h

  Expected: Command line options to be displayed.

  Observed: symbol lookup error: /usr/bin/Xwayland: undefined symbol:
  gbm_bo_get_fd_for_plane

  [Where problems could occur]

  Since this changes Xwayland initialization for all platforms, risk of
  bugs and regressions reaches all platforms. At best an Xwayland
  failure would prevent X11 apps from working properly, or at worst
  prevent gnome-shell Wayland sessions from starting (this bug).

  [Other Info]

  Fixing this for jammy is a prerequisite to resolve bug 1961563.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1987628/+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 1988143] [NEW] 20.04.5 (20220829.1 build) has kernel 5.13 packages

2022-08-30 Thread fossfreedom

Public bug reported:

Examining the .list file for the amd64 image it contains various kernel
5.13 .deb packages.

http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
amd64.list

e.g.

/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb

This is a little unexpected given that 5.15 is the default kernel.

Possibly nvidia-390 doesn't have 5.15 packages?

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal iso-testing

** Tags added: iso-testing

** Description changed:

  Examining the .list file for the amd64 image it contains various kernel
  5.13 .deb packages.
+ 
+ http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
+ amd64.list
+ 
+ e.g.
+ 
+ 
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
+ 
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
+ 
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
+ 
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
+ 
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
  This is a little unexpected given that 5.15 is the default kernel.
  
  Possibly nvidia-390 doesn't have 5.15 packages?

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

Title:
  20.04.5 (20220829.1 build) has kernel 5.13 packages

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Examining the .list file for the amd64 image it contains various
  kernel 5.13 .deb packages.

  http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
  amd64.list

  e.g.

  
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
  
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb

  This is a little unexpected given that 5.15 is the default kernel.

  Possibly nvidia-390 doesn't have 5.15 packages?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1988143/+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 1987628] Re: Xwayland fails to start on Xilinx: symbol lookup error: /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane

xwayland (2:22.1.3-2) unstable; urgency=medium

  [ Daniel van Vugt ]
  * Add xwayland-Detect-gbm_bo_get_fd_for_plane-at-runtime.patch

 -- Timo Aaltonen   Thu, 25 Aug 2022 13:03:43 +0300


** Changed in: xwayland (Ubuntu)
   Status: In Progress => Fix Released

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

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

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

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

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

Title:
  Xwayland fails to start on Xilinx: symbol lookup error:
  /usr/bin/Xwayland: undefined symbol: gbm_bo_get_fd_for_plane

Status in xwayland package in Ubuntu:
  Fix Released
Status in xwayland source package in Jammy:
  In Progress

Bug description:
  Xwayland fails to start on Xilinx:

  /usr/bin/Xwayland: symbol lookup error: /usr/bin/Xwayland: undefined
  symbol: gbm_bo_get_fd_for_plane

  This is particularly important since it prevents gnome-shell from
  starting Wayland sessions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1987628/+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 1987976] Re: firefox black window

If applicable, I let you open a new bug description ;)

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

Title:
  firefox black window

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987976/+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 1987976] Re: firefox black window

I think this time it works because I renamed the file. Any misleading
character in the old name ?

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

Title:
  firefox black window

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987976/+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 1987976] Re: firefox black window

Let me try once again the attachment...

** Attachment added: "Capture.png"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987976/+attachment/5612493/+files/Capture.png

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

Title:
  firefox black window

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987976/+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 1987976] Re: firefox black window

With 
MOZ_ENABLE_WAYLAND=0 snap run firefox
it works too (no black screen), although the output shows messages:

nicolas@nicolas-fixe:~$ MOZ_ENABLE_WAYLAND=0 snap run firefox
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot open directory "/var/lib": permission denied
Gtk-Message: 10:32:53.386: Failed to load module "canberra-gtk-module"
Gtk-Message: 10:32:53.396: Failed to load module "canberra-gtk-module"
ATTENTION: default value of option mesa_glthread overridden by environment.
Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs

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

Title:
  firefox black window

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987976/+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 1987945] Re: [snap] chromium does not read root-owned files in $HOME

> Yes, I will argue with you there.

Don't get me wrong, yours is a totally valid use case. I'm just saying
it's perhaps not that common, and perhaps doesn't justify the use of the
"read: all" attribute on the home interface, which would mean that the
interface wouldn't be auto-connected, which would affect many more
users.

With the current situation, it's a trade-off, and as such it doesn't
address all the use cases perfectly.

Now, I'll inquire with the snap security team whether using that
attribute and requesting auto-connection would be acceptable, and if it
is we'll make the change so that you don't have to tamper with system-
wide apparmor abstractions to get what you need.

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

Title:
[snap] chromium does not read root-owned files in $HOME

Status in chromium-browser package in Ubuntu:
Confirmed

Bug description:
Today, I literally spent hours trying to figure out why I cound't
upload a large file.

Of course I thought the problem was the size of the file.

It wasn't. The problem was that Chromium in Snap for some reason is
confined so that it can SEE file-owned-by-root.zip, but NOT READ file-
owned-by-root.zip.

I tried to upload the big file onto a PsiTransfer webpage. And it
simply stalled. The apache2 backend reported 400-errors and I got no
useful info out of that.

Chromium itself reported this in the Networking tab:

PATCH https://PSITRANSFER_HOST/path net::ERR_FAILED

Which is totally useless. In no way could I expect that the ultimate
cause was that the local file was not owned by me.

_If I can see the file, and I have read-permissions on it, I expect
that I can upload the file._

Another example:

$ ls -l ~/Junk/rode_muur*
-rw-rw-r-- 1 walter walter 64773 aug 27 18:08 /home/walter/Junk/rode_muur.jpg
-rw-rw-r-- 1 root root 64773 aug 27 18:08
/home/walter/Junk/rode_muur_root.jpg

Trying to upload rode_muur_root.jpg to e.g.
https://www.filestack.com/fileschool/html/html-file-upload-tutorial-
example/ yields this error-page:

That does not tell me that there is a problem with the local file.
That looks like a remote problem, am I right?

What would be the fix?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987945/+subscriptions

[Desktop-packages] [Bug 1987945] Re: [snap] chromium does not read root-owned files in $HOME

Let's see what the snapd folks have to say about it:
https://forum.snapcraft.io/t/auto-connecting-the-home-interface-with-
read-all-for-a-browser-snap/31525

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

Title:
[snap] chromium does not read root-owned files in $HOME

Status in chromium-browser package in Ubuntu:
Confirmed

Bug description:
Today, I literally spent hours trying to figure out why I cound't
upload a large file.

Of course I thought the problem was the size of the file.

It wasn't. The problem was that Chromium in Snap for some reason is
confined so that it can SEE file-owned-by-root.zip, but NOT READ file-
owned-by-root.zip.

I tried to upload the big file onto a PsiTransfer webpage. And it
simply stalled. The apache2 backend reported 400-errors and I got no
useful info out of that.

Chromium itself reported this in the Networking tab:

PATCH https://PSITRANSFER_HOST/path net::ERR_FAILED

Which is totally useless. In no way could I expect that the ultimate
cause was that the local file was not owned by me.

_If I can see the file, and I have read-permissions on it, I expect
that I can upload the file._

Another example:

$ ls -l ~/Junk/rode_muur*
-rw-rw-r-- 1 walter walter 64773 aug 27 18:08 /home/walter/Junk/rode_muur.jpg
-rw-rw-r-- 1 root root 64773 aug 27 18:08
/home/walter/Junk/rode_muur_root.jpg

Trying to upload rode_muur_root.jpg to e.g.
https://www.filestack.com/fileschool/html/html-file-upload-tutorial-
example/ yields this error-page:

That does not tell me that there is a problem with the local file.
That looks like a remote problem, am I right?

What would be the fix?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987945/+subscriptions

[Desktop-packages] [Bug 1987945] Re: [snap] chromium does not read root-owned files in $HOME

There are precedents for this use case, apparently:
https://forum.snapcraft.io/t/interface-auto-connect-request-for-the-
universal-update-utility-snap-home-read-all/23125.

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

Title:
[snap] chromium does not read root-owned files in $HOME

Status in chromium-browser package in Ubuntu:
Confirmed

Bug description:
Today, I literally spent hours trying to figure out why I cound't
upload a large file.

Of course I thought the problem was the size of the file.

It wasn't. The problem was that Chromium in Snap for some reason is
confined so that it can SEE file-owned-by-root.zip, but NOT READ file-
owned-by-root.zip.

I tried to upload the big file onto a PsiTransfer webpage. And it
simply stalled. The apache2 backend reported 400-errors and I got no
useful info out of that.

Chromium itself reported this in the Networking tab:

PATCH https://PSITRANSFER_HOST/path net::ERR_FAILED

Which is totally useless. In no way could I expect that the ultimate
cause was that the local file was not owned by me.

_If I can see the file, and I have read-permissions on it, I expect
that I can upload the file._

Another example:

$ ls -l ~/Junk/rode_muur*
-rw-rw-r-- 1 walter walter 64773 aug 27 18:08 /home/walter/Junk/rode_muur.jpg
-rw-rw-r-- 1 root root 64773 aug 27 18:08
/home/walter/Junk/rode_muur_root.jpg

Trying to upload rode_muur_root.jpg to e.g.
https://www.filestack.com/fileschool/html/html-file-upload-tutorial-
example/ yields this error-page:

That does not tell me that there is a problem with the local file.
That looks like a remote problem, am I right?

What would be the fix?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987945/+subscriptions

[Desktop-packages] [Bug 1987945] Re: [snap] chromium does not read root-owned files in $HOME

2022-08-30 Thread Walter

Okay. So to unbreak the confinement in the mean time, one can do this:

(1) Find an include that is not owned by snap (because an update will
likely break things again):

# sed -e '/#include/!d;s/.*#include //' \
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium |
sort -u

I choose abstractions/X.

(2) Edit that file -- /etc/apparmor.d/abstractions/X -- and place this
at the end:

# Give back read permissions to ALL files, not just user-owned-files
# Added here (it's included by /var/lib/snapd/apparmor/profiles/*)
# because snap likely won't give me a proper local hook to fix
# broken rules (LP: #1987945)
@{HOME}/[^.]** r,

(3) systemctl restart snapd.apparmor.service

Now you have succesfully "compromised security" on your system: all
apparmor profiles that include will get read powers in
your homedir. But your most used tool -- the browser -- is usable again.

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

Title:
[snap] chromium does not read root-owned files in $HOME

Status in chromium-browser package in Ubuntu:
Confirmed

Bug description:
Today, I literally spent hours trying to figure out why I cound't
upload a large file.

Of course I thought the problem was the size of the file.

It wasn't. The problem was that Chromium in Snap for some reason is
confined so that it can SEE file-owned-by-root.zip, but NOT READ file-
owned-by-root.zip.

I tried to upload the big file onto a PsiTransfer webpage. And it
simply stalled. The apache2 backend reported 400-errors and I got no
useful info out of that.

Chromium itself reported this in the Networking tab:

PATCH https://PSITRANSFER_HOST/path net::ERR_FAILED

Which is totally useless. In no way could I expect that the ultimate
cause was that the local file was not owned by me.

_If I can see the file, and I have read-permissions on it, I expect
that I can upload the file._

Another example:

$ ls -l ~/Junk/rode_muur*
-rw-rw-r-- 1 walter walter 64773 aug 27 18:08 /home/walter/Junk/rode_muur.jpg
-rw-rw-r-- 1 root root 64773 aug 27 18:08
/home/walter/Junk/rode_muur_root.jpg

Trying to upload rode_muur_root.jpg to e.g.
https://www.filestack.com/fileschool/html/html-file-upload-tutorial-
example/ yields this error-page:

That does not tell me that there is a problem with the local file.
That looks like a remote problem, am I right?

What would be the fix?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987945/+subscriptions

[Desktop-packages] [Bug 1987737] Re: firefox from snap disabled save button in subfolders

2022-08-30 Thread Alejandro R. Mosteo

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

I guess this info is no longer needed, but just in case:

Neither of /usr/libexec/xdg-desktop-portal-gtk -rv or journalctl -f
produce any new output while reproducing the bug.

$ LANG=C dpkg -l xdg-desktop-portal*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version Architecture Description
+++-==-===--
ii  xdg-desktop-portal 1.14.3-0ubuntu2 amd64desktop integration 
portal for Flatpak and Snap
un  xdg-desktop-portal-backend  (no description 
available)
ii  xdg-desktop-portal-gnome   42.0.1-1ubuntu2 amd64GNOME portal 
backend for xdg-desktop-portal
ii  xdg-desktop-portal-gtk 1.14.0-1build1  amd64GTK+/GNOME portal 
backend for xdg-desktop-portal

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

Title:
  firefox from snap disabled save button in subfolders

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 22.04 fully updated
  2) Firefox snap id 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  3) I expect being able to save a file to folders in my home folder or in a 
usb drive
  4) When selecting a plugged-in USB drive or the home folder I can save, once 
I enter a subfolder the "save" button in the save dialog gets greyed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop:
   
  Date: Fri Aug 26 10:11:37 2022
  InstallationDate: Installed on 2021-07-14 (407 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (1 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-07-14T15:11:35.001074

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987737/+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 1987737] Re: firefox from snap disabled save button in subfolders

2022-08-30 Thread Alejandro R. Mosteo

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

> Does it ungrey if you edit the filename? it seems a bit similar to bug
#1971516

Indeed it does. It's a duplicate then, I will mark it as such.

** This bug has been marked a duplicate of bug 1971516
   Entering fileselector subdir disables the save button until filename is 
edited

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

Title:
  firefox from snap disabled save button in subfolders

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 22.04 fully updated
  2) Firefox snap id 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  3) I expect being able to save a file to folders in my home folder or in a 
usb drive
  4) When selecting a plugged-in USB drive or the home folder I can save, once 
I enter a subfolder the "save" button in the save dialog gets greyed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop:
   
  Date: Fri Aug 26 10:11:37 2022
  InstallationDate: Installed on 2021-07-14 (407 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (1 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-07-14T15:11:35.001074

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987737/+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 1983645] Re: Can't find 5G option in Network Mode under Mobile Network

2022-08-30 Thread Dirk Su

Tested on OAS4-DVT1-C4 (202208-30540) which has Fibcom DW5931e
installed. Install gnome-control-center 1:41.7-0ubuntu0.22.04.5 from
jammy-proposed. And update modemmanager to 1.19.1-683270f4  from
https://launchpad.net/~dirksu/+archive/ubuntu/wwan-test. Enabled mobile
network through gnome-control-center, there is 5G option in 'Network
Mode'.

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

** Changed in: oem-priority
   Status: Confirmed => Fix Committed

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

Title:
  Can't find 5G option in Network Mode under Mobile Network

Status in OEM Priority Project:
  Fix Committed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  There is no 5G related option in Network Mode under Mobile Network

  [Test case]
  1. System should have 5G capable hardware (SIM and WWAN module) and 5G 
enabled Modem Manager (>=1.19.1)
  2. Enable mobile network
  3. Check network mode
  4. There should be 5G related option

  [Where problems could occur]
  gnome-control-center interact with Modem Manager to get current network mode 
and set preferred network mode. Modem Manager will filter the unsupported mode. 
The risk will be low.

  [Other info]
  This patch is from upstream gnome-control-center. For more information
  refer to 
https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1388

  The patch also adds some new user visible strings, those will be
  translatable on launchpad and initially displayed in english but we
  can get translations updated then as part of the next language packs
  refresh

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1983645/+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 1987979] Re: [snap] Firefox Narrator stopped working after upgrade from 20.04 to 22.04

It's being worked on

- https://tracker.debian.org/news/1357468/accepted-speech-
dispatcher-0112-1-source-into-unstable/ fixes the service listing no
voice by default

- https://github.com/snapcore/snapd/pull/12081 updates the snap
permission to be able to talk to the service

- we need to fix the service activation not working from the snap (which
can be workarounded by starting speech-dispatcher manually)

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

Title:
  [snap] Firefox Narrator stopped working after upgrade from 20.04 to
  22.04

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  In Progress

Bug description:
  I just noticed that the narrator feature, which reads articles out
  load with TTS in Firefox reading view stopped working after upgrading
  to 22.04. Another user reported the same problem on ask Ubuntu:

  https://askubuntu.com/questions/1418391/no-tts-voices-on-
  firefox-v102-0-after-upgrading-to-ubuntu-22-04-lts

  Also, if you have no clue what this is about:
  https://askubuntu.com/questions/953509/how-can-i-change-the-voice-
  used-by-firefox-reader-view-narrator-in-ubuntu

  ---

  1)

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

  2) Firefox is a snap now, but I guess for the feature to work it needs
  to detect TTS which is packaged as deb.

  $  snap list firefox
  Name Version  Rev   Tracking   Publisher  Notes
  firefox  104.0-3  1749  latest/stable  mozilla✓   -

  $  apt-cache policy espeak speech-dispatcher-espeak-ng firefox
  espeak:
    Installed: 1.48.15+dfsg-3
    Candidate: 1.48.15+dfsg-3
    Version table:
   *** 1.48.15+dfsg-3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status
  speech-dispatcher-espeak-ng:
    Installed: 0.11.1-1ubuntu1
    Candidate: 0.11.1-1ubuntu1
    Version table:
   *** 0.11.1-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.11.1-1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  firefox:
    Installed: (none)
    Candidate: 1:1snap1-0ubuntu2
    Version table:
   1:1snap1-0ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  3) open a website, enter reader mode, click the icon with sound waves
  and hear the text being read with TTS

  4) the icon is missing

  ---

  Edit: I tested Firefox Flatpak and it is also affected, my best guess
  is that Firefox is not at fault.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1987979/+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 1987979] Re: [snap] Firefox Narrator stopped working after upgrade from 20.04 to 22.04

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

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

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

Title:
  [snap] Firefox Narrator stopped working after upgrade from 20.04 to
  22.04

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  In Progress

Bug description:
  I just noticed that the narrator feature, which reads articles out
  load with TTS in Firefox reading view stopped working after upgrading
  to 22.04. Another user reported the same problem on ask Ubuntu:

  https://askubuntu.com/questions/1418391/no-tts-voices-on-
  firefox-v102-0-after-upgrading-to-ubuntu-22-04-lts

  Also, if you have no clue what this is about:
  https://askubuntu.com/questions/953509/how-can-i-change-the-voice-
  used-by-firefox-reader-view-narrator-in-ubuntu

  ---

  1)

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

  2) Firefox is a snap now, but I guess for the feature to work it needs
  to detect TTS which is packaged as deb.

  $  snap list firefox
  Name Version  Rev   Tracking   Publisher  Notes
  firefox  104.0-3  1749  latest/stable  mozilla✓   -

  $  apt-cache policy espeak speech-dispatcher-espeak-ng firefox
  espeak:
    Installed: 1.48.15+dfsg-3
    Candidate: 1.48.15+dfsg-3
    Version table:
   *** 1.48.15+dfsg-3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status
  speech-dispatcher-espeak-ng:
    Installed: 0.11.1-1ubuntu1
    Candidate: 0.11.1-1ubuntu1
    Version table:
   *** 0.11.1-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.11.1-1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  firefox:
    Installed: (none)
    Candidate: 1:1snap1-0ubuntu2
    Version table:
   1:1snap1-0ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  3) open a website, enter reader mode, click the icon with sound waves
  and hear the text being read with TTS

  4) the icon is missing

  ---

  Edit: I tested Firefox Flatpak and it is also affected, my best guess
  is that Firefox is not at fault.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1987979/+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 1987945] Re: [snap] chromium does not read root-owned files in $HOME

2022-08-30 Thread Walter

"Arguably"

Yes, I will argue with you there.

- How about tcpdump writing as the tcpdump user+group in my homedir? I
can read them, delete them, but not send them to someone using the
browser?

- Me getting files as root, because I need special powers (for vpn,
network, usb, ...)? mv(1)/cp(1) will not chown by default.

- Having read-only files in a homedir, administered by root?

If the argument is that no one is ever root to do user-stuff on their
desktop, then you'll likely lose the power-users.

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

Title:
[snap] chromium does not read root-owned files in $HOME

Status in chromium-browser package in Ubuntu:
Confirmed

Bug description:
Today, I literally spent hours trying to figure out why I cound't
upload a large file.

Of course I thought the problem was the size of the file.

It wasn't. The problem was that Chromium in Snap for some reason is
confined so that it can SEE file-owned-by-root.zip, but NOT READ file-
owned-by-root.zip.

I tried to upload the big file onto a PsiTransfer webpage. And it
simply stalled. The apache2 backend reported 400-errors and I got no
useful info out of that.

Chromium itself reported this in the Networking tab:

PATCH https://PSITRANSFER_HOST/path net::ERR_FAILED

Which is totally useless. In no way could I expect that the ultimate
cause was that the local file was not owned by me.

_If I can see the file, and I have read-permissions on it, I expect
that I can upload the file._

Another example:

$ ls -l ~/Junk/rode_muur*
-rw-rw-r-- 1 walter walter 64773 aug 27 18:08 /home/walter/Junk/rode_muur.jpg
-rw-rw-r-- 1 root root 64773 aug 27 18:08
/home/walter/Junk/rode_muur_root.jpg

Trying to upload rode_muur_root.jpg to e.g.
https://www.filestack.com/fileschool/html/html-file-upload-tutorial-
example/ yields this error-page:

That does not tell me that there is a problem with the local file.
That looks like a remote problem, am I right?

What would be the fix?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987945/+subscriptions

[Desktop-packages] [Bug 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)

2022-08-30 Thread vadim

But in wayland everything works fine, wayland have some other overlay
algorithm.

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

Title:
  Can't click context menu items when they cover the dock (in a Xorg
  session)

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

Bug description:
  ubuntu dock in bottom position won't let me click on button (convert
  java file to Kotlin file) in android studio, but in the left position
  everything works correctly. That is, if the menu android studio
  overlaps the ubuntu dock, then the menu buttons will not be pressed.

  https://youtu.be/KsOVG7Uucow

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sun Aug 14 10:52:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed
   openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-07-13 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1986451/+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 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)

2022-08-30 Thread vadim

i don't use auto-hide

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

Title:
  Can't click context menu items when they cover the dock (in a Xorg
  session)

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

Bug description:
  ubuntu dock in bottom position won't let me click on button (convert
  java file to Kotlin file) in android studio, but in the left position
  everything works correctly. That is, if the menu android studio
  overlaps the ubuntu dock, then the menu buttons will not be pressed.

  https://youtu.be/KsOVG7Uucow

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sun Aug 14 10:52:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed
   openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-07-13 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1986451/+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 1973638] Re: gnome-shell 42 leaks tens of megabytes with every screenshot

Nevermind. The gnome-shell fix was reverted upstream because it is
incorrect.

** Tags removed: rls-jj-incoming

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Triaged

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

Title:
  gnome-shell 42 leaks tens of megabytes with every screenshot

Status in GNOME Shell:
  Unknown
Status in gjs package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gjs source package in Jammy:
  Fix Released
Status in gnome-shell source package in Jammy:
  Triaged

Bug description:
  [Impact]

  gnome-shell's memory usage grows by tens of megabytes with every
  screenshot. A few screenshots make it 100MB larger and a few dozen
  screenshots make it 1GB larger.

  [Test Plan for GNOME Shell Fix]

  TODO

  [Test Plan for GJS Fix]

  1. Log into gnome-shell.

  2. Measure its real memory usage:

     grep RSS /proc/`pidof gnome-shell`/status

  3. Take 20 full screen screenshots by pressing PrtScn each time. No
  need to save them anywhere.

  4. Measure the memory usage again.

  Expected: Memory usage grows a little but growth does not exceed a few
  hundred megabytes. It should level off after a while and sometimes
  even shrink due to garbage collection.

  Observed: Memory usage grows without bounds, easily exceeding 1GB
  after about 20 screenshots (depending on screen resolution). It never
  shrinks significantly.

  [Where problems could occur]

  Since the fix affects GJS, problems could occur in any part of gnome-
  shell.

  [Other Info]

  This leak requires multiple fixes to minimize the memory usage. For
  the moment we are only aiming to fix the main GJS portion of the bug
  that allows memory usage to exceed 1GB.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1973638/+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 1988100] Re: totem-video-thumbnailer fails in OpenBLAS blas_thread_init

> OpenBLAS blas_thread_init: pthread_create failed for thread 7 of 16:
Resource temporarily unavailable

16 threads is not much so that alone isn't the issue. However
https://github.com/xianyi/OpenBLAS/issues/1668 mentions that the
offending code might have set the stack ulimit to gigabytes in size,
which would make the system quickly run out of virtual address space
when creating new threads. Although I doubt the offending "LSF" code is
something totem uses, your issue does also look like it has run out of
address space for new thread stacks.


** Bug watch added: github.com/xianyi/OpenBLAS/issues #1668
   https://github.com/xianyi/OpenBLAS/issues/1668

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

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

Title:
  totem-video-thumbnailer fails in OpenBLAS blas_thread_init

Status in openblas package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  totem-video-thumbnailer appears to be crashing and so no video
  thumbnails are generated. This is what happens when I run it manually:

  $ totem-video-thumbnailer -v sample.mp4 sample.png
  TotemVideoThumbnailer-Message: 11:08:44.734: Initialised libraries, about to 
create video widget
  TotemVideoThumbnailer-Message: 11:08:44.739: setting URI 
file:///home/aaron/tmp/sample.mp4
  TotemVideoThumbnailer-Message: 11:08:44.739: Video widget created
  TotemVideoThumbnailer-Message: 11:08:44.739: About to open video file

  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.806:
  failed to create thread: Error creating thread: Resource temporarily
  unavailable

  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.808: failed 
to create thread: Error creating thread: Resource temporarily unavailable
  terminate called after throwing an instance of 'std::bad_alloc'
    what():  std::bad_alloc
  Aborted

  Passing the -l flag causes it to work fine.

  Also, in other tests, which I fail to replicate now, I saw this error:
  OpenBLAS blas_thread_init: RLIMIT_NPROC 125184 current, 125184 max

  As a workaround I have installed ffmpegthumbnailer and $ln -s
  /usr/share/thumbnailers/ffmpegthumbnailer.thumbnailer
  ~/.local/share/thumbnailers/ffmpegthumbnailer.thumbnailer

  This has things working for me, but does not really address the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: totem 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 30 10:53:06 2022
  InstallationDate: Installed on 2021-09-24 (339 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: totem
  UpgradeStatus: Upgraded to jammy on 2022-07-19 (41 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-09-27T12:02:48.414586

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openblas/+bug/1988100/+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 1988100] Re: Video thumbnails fail to generate

** Package changed: totem (Ubuntu) => openblas (Ubuntu)

** Summary changed:

- Video thumbnails fail to generate
+ totem-video-thumbnailer fails in OpenBLAS blas_thread_init

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

Title:
  totem-video-thumbnailer fails in OpenBLAS blas_thread_init

Status in openblas package in Ubuntu:
  New

Bug description:
  totem-video-thumbnailer appears to be crashing and so no video
  thumbnails are generated. This is what happens when I run it manually:

  $ totem-video-thumbnailer -v sample.mp4 sample.png
  TotemVideoThumbnailer-Message: 11:08:44.734: Initialised libraries, about to 
create video widget
  TotemVideoThumbnailer-Message: 11:08:44.739: setting URI 
file:///home/aaron/tmp/sample.mp4
  TotemVideoThumbnailer-Message: 11:08:44.739: Video widget created
  TotemVideoThumbnailer-Message: 11:08:44.739: About to open video file

  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.806:
  failed to create thread: Error creating thread: Resource temporarily
  unavailable

  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.808: failed 
to create thread: Error creating thread: Resource temporarily unavailable
  terminate called after throwing an instance of 'std::bad_alloc'
    what():  std::bad_alloc
  Aborted

  Passing the -l flag causes it to work fine.

  Also, in other tests, which I fail to replicate now, I saw this error:
  OpenBLAS blas_thread_init: RLIMIT_NPROC 125184 current, 125184 max

  As a workaround I have installed ffmpegthumbnailer and $ln -s
  /usr/share/thumbnailers/ffmpegthumbnailer.thumbnailer
  ~/.local/share/thumbnailers/ffmpegthumbnailer.thumbnailer

  This has things working for me, but does not really address the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: totem 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 30 10:53:06 2022
  InstallationDate: Installed on 2021-09-24 (339 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: totem
  UpgradeStatus: Upgraded to jammy on 2022-07-19 (41 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-09-27T12:02:48.414586

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openblas/+bug/1988100/+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 1988100] Re: Video thumbnails fail to generate