[Desktop-packages] [Bug 2062916] Re: evolution has undefined symbol in newest libwebkit2gtk

2024-04-22 Thread Marc Deslauriers
That is pretty odd, I can't reproduce this issue on jammy.

what's the output of "ldd /lib/x86_64-linux-
gnu/libwebkit2gtk-4.0.so.37"?

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

Title:
  evolution  has undefined symbol in newest libwebkit2gtk

Status in evolution package in Ubuntu:
  New
Status in webkit2gtk package in Ubuntu:
  Triaged

Bug description:
  evolution: symbol lookup error: /lib/x86_64-linux-
  gnu/libwebkit2gtk-4.0.so.37: undefined symbol:
  gbm_bo_create_with_modifiers2

  
  The libwebkit2gtk version is
  libwebkit2gtk-4.0-37_2.44.0-0ubuntu0.22.04.1_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/2062916/+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 2051543] Re: When I use a keyboard shortcut to lower a window, the window retains its keyboard focus.

2024-04-12 Thread Marc Deslauriers
** Information type changed from Public Security to Public

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

Title:
  When I use a keyboard shortcut to lower a window, the window retains
  its keyboard focus.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This happens no matter which focusing strategy i choose (click to
  focus or hover to focus). Until a few weeks ago, the new top window
  would receive focus when using hover to focus.

  This can be a security risk in that you often start typing in the
  wrong window.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 13:53:47 2024
  DistUpgraded: 2023-10-24 00:16:21,014 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2021-02-23 (1070 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=4fc71965-9660-4a7c-ada5-7906da430d47 ro quiet splash intel_iommu=off 
vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-10-23 (98 days ago)
  dmi.bios.date: 08/15/2023
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET72W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF004UMD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET72W(1.51):bd08/15/2023:br1.51:efr1.22:svnLENOVO:pn20HF004UMD:pvrThinkPadT470s:rvnLENOVO:rn20HF004UMD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HF_BU_Think_FM_ThinkPadT470s:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HF004UMD
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-02-23 (1072 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: gnome-shell 45.2-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 45.2-0ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-23 (99 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev 
sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051543/+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 2060859] Re: Xorg freeze

2024-04-12 Thread Marc Deslauriers
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.

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

** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2060859

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Whenever I open my laptop and start working, after some time (after
  10-15 minutes) this automatically starts happening for all the
  applications (terminal and all application ). and this happens every
  day And the laptop stops working. Even the laptop doesn't turn off. i
  forcefully close the laptop ( i already make 30gb swap partition) .
  and when i hover on anything , my cursor look like square

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 23:41:40 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev c2) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:3804]
  InstallationDate: Installed on 2024-04-08 (2 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=2a9c63d2-ea20-46aa-b9d5-674c8d948bd2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2021
  dmi.bios.release: 1.28
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BUCN28WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55722WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15API
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnLENOVO:bvrBUCN28WW:bd01/12/2021:br1.28:efr1.28:svnLENOVO:pn81UT:pvrLenovoIdeaPadS145-15API:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15API:skuLENOVO_MT_81UT_BU_idea_FM_IdeaPadS145-15API:
  dmi.product.family: IdeaPad S145-15API
  dmi.product.name: 81UT
  dmi.product.sku: LENOVO_MT_81UT_BU_idea_FM_IdeaPad S145-15API
  dmi.product.version: Lenovo IdeaPad S145-15API
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060859/+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 2060900] Re: gst-plugin-scanner crashed with SIGABRT in __assert_fail_base()

2024-04-12 Thread Marc Deslauriers
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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2060900/+attachment/5763572/+files/CoreDump.gz

** 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 gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2060900

Title:
  gst-plugin-scanner crashed with SIGABRT in __assert_fail_base()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  this give me error from some files

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: libgstreamer1.0-0 1.24.1-1build1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Apr 11 11:07:09 2024
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
  InstallationDate: Installed on 2024-04-04 (7 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/../../lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
 -l /usr/bin/rhythmbox
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SignalName: SIGABRT
  SourcePackage: gstreamer1.0
  StacktraceTop:
   __assert_fail_base (fmt=0x702a92dd01e8 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x702a7b4e1c90 "subsampling == 
SUBSAMPLE_YUV420 || subsampling == SUBSAMPLE_YUV422H || subsampling == 
SUBSAMPLE_YUV422V || subsampling == SUBSAMPLE_RGBX", 
file=file@entry=0x702a7b4e44b6 "i965_drv_video.c", line=line@entry=4653, 
function=function@entry=0x702a7b511600 "i965_check_alloc_surface_bo") at 
./assert/assert.c:94
   __assert_fail (assertion=0x702a7b4e1c90 "subsampling == SUBSAMPLE_YUV420 || 
subsampling == SUBSAMPLE_YUV422H || subsampling == SUBSAMPLE_YUV422V || 
subsampling == SUBSAMPLE_RGBX", file=0x702a7b4e44b6 "i965_drv_video.c", 
line=4653, function=0x702a7b511600 "i965_check_alloc_surface_bo") at 
./assert/assert.c:103
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   vaCreateSurfaces () from /lib/x86_64-linux-gnu/libva.so.2
  Title: gst-plugin-scanner crashed with SIGABRT in __assert_fail_base()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2060900/+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 2051536] Re: security update regression tracking bug

2024-01-29 Thread Marc Deslauriers
** Also affects: xwayland (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xwayland (Ubuntu Focal)
   Status: New => Invalid

** Changed in: xwayland (Ubuntu Mantic)
   Status: New => Fix Released

** Changed in: xwayland (Ubuntu Noble)
   Status: New => Fix Released

** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2051536

Title:
  security update regression tracking bug

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xwayland package in Ubuntu:
  Fix Released
Status in xorg-server source package in Focal:
  In Progress
Status in xwayland source package in Focal:
  Invalid
Status in xorg-server source package in Jammy:
  In Progress
Status in xwayland source package in Jammy:
  In Progress
Status in xorg-server source package in Mantic:
  In Progress
Status in xwayland source package in Mantic:
  Fix Released
Status in xorg-server source package in Noble:
  Fix Released
Status in xwayland source package in Noble:
  Fix Released

Bug description:
  USN-6587-1 fixed security issues in X.Org. A commit was missing which
  may result in a regression (memory leak).

  See:

  https://bugs.debian.org/1061110
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/1623

  
https://gitlab.freedesktop.org/xorg/xserver/-/commit/8b75ec34dfbe435cd3a17e64138e22a37395a6d8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2051536/+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 2051536] [NEW] security update regression tracking bug

2024-01-29 Thread Marc Deslauriers
*** This bug is a security vulnerability ***

Public security bug reported:

USN-6587-1 fixed security issues in X.Org. A commit was missing which
may result in a regression (memory leak).

See:

https://bugs.debian.org/1061110
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1623

https://gitlab.freedesktop.org/xorg/xserver/-/commit/8b75ec34dfbe435cd3a17e64138e22a37395a6d8

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: xorg-server (Ubuntu Focal)
 Importance: Undecided
 Assignee: Marc Deslauriers (mdeslaur)
 Status: In Progress

** Affects: xorg-server (Ubuntu Jammy)
 Importance: Undecided
 Assignee: Marc Deslauriers (mdeslaur)
 Status: In Progress

** Affects: xorg-server (Ubuntu Mantic)
 Importance: Undecided
 Assignee: Marc Deslauriers (mdeslaur)
 Status: In Progress

** Affects: xorg-server (Ubuntu Noble)
 Importance: Undecided
 Status: Fix Released

** Also affects: xorg-server (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: xorg-server (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: xorg-server (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: xorg-server (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu Noble)
   Status: New => Fix Released

** Changed in: xorg-server (Ubuntu Focal)
   Status: New => In Progress

** Changed in: xorg-server (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: xorg-server (Ubuntu Mantic)
   Status: New => In Progress

** Changed in: xorg-server (Ubuntu Focal)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: xorg-server (Ubuntu Jammy)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: xorg-server (Ubuntu Mantic)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

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

Title:
  security update regression tracking bug

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Focal:
  In Progress
Status in xorg-server source package in Jammy:
  In Progress
Status in xorg-server source package in Mantic:
  In Progress
Status in xorg-server source package in Noble:
  Fix Released

Bug description:
  USN-6587-1 fixed security issues in X.Org. A commit was missing which
  may result in a regression (memory leak).

  See:

  https://bugs.debian.org/1061110
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/1623

  
https://gitlab.freedesktop.org/xorg/xserver/-/commit/8b75ec34dfbe435cd3a17e64138e22a37395a6d8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2051536/+subscriptions


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


[Desktop-packages] [Bug 2046633] Re: Don't include 'nmcli -f all con' output in bug report (for privacy)

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

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

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

Status in network-manager package in Ubuntu:
  New

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2046633/+subscriptions


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


[Desktop-packages] [Bug 2047595] Re: sound control panel security

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

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

Title:
  sound control panel security

Status in gnome-shell package in Ubuntu:
  New

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

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


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


[Desktop-packages] [Bug 2047595] Re: sound control panel security

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

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

Title:
  sound control panel security

Status in gnome-shell package in Ubuntu:
  New

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

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


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


[Desktop-packages] [Bug 2046037] Re: CVE-2023-6185 and CVE-2023-6186

2023-12-14 Thread Marc Deslauriers
These have been published now, thanks!

https://ubuntu.com/security/notices/USN-6546-1
https://ubuntu.com/security/notices/USN-6546-2

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

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

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

Title:
  CVE-2023-6185 and CVE-2023-6186

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Focal:
  Fix Released
Status in libreoffice source package in Jammy:
  Fix Released
Status in libreoffice source package in Lunar:
  Fix Released
Status in libreoffice source package in Mantic:
  Fix Released
Status in libreoffice source package in Noble:
  Fix Released

Bug description:
  CVE-2023-6185: "Improper input validation enabling arbitrary Gstreamer 
pipeline injection"
  https://www.libreoffice.org/about-us/security/advisories/cve-2023-6185/

  CVE-2023-6186: "Link targets allow arbitrary script execution"
  https://www.libreoffice.org/about-us/security/advisories/cve-2023-6186/

  
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/log/?h=wip/focal-6.4
  
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/log/?h=wip/jammy-7.3

  
  More information will follow.

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


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


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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2042350/+subscriptions


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


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

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

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

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

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


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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2042350/+subscriptions


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


[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2023-10-20 Thread Marc Peña
> Can you ascertain if your smart card is supported by OpenSC?

Yes, totally. It's a DNIe:
https://github.com/OpenSC/OpenSC/wiki/DNIe-(OpenDNIe)/dca4ae71aac1deb510df0d2b9afebb59afd07feb

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in Mozilla Firefox:
  Confirmed
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1967632/+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 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2023-10-19 Thread Marc Peña
OK, now chromium starts, but when I try to access some website that
requires the certificate on my smartcard, it seems like it's doing
nothing to access the smartcard, so to speak.

Eveything works OK on my non-snaped Firefox.

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in Mozilla Firefox:
  Confirmed
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1967632/+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 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2023-10-18 Thread Marc Peña
Hi! I wanted to try this. This is what I did:

$ sudo snap set system experimental.parallel-instances=true
$ snap refresh --beta snapd
$ sudo snap install --channel stable/pkcs chromium_pkcs
$ sudo snap connect chromium_pkcs:pcscd

But I get an error when trying to execute chromium:

$ chromium_pkcs
/snap/chromium/2648/usr/lib/chromium-browser/chrome: symbol lookup error: 
/snap/chromium/2648/gnome-platform/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0: 
undefined symbol: hb_ot_color_has_paint

Is this compatible with parallel installs or the problem lays somewhere
else?

Thanks!

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in Mozilla Firefox:
  Confirmed
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1967632/+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 2036310] Re: gnome shell crash after sleep mode

2023-10-13 Thread Marc Deslauriers
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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2036310

Title:
  gnome shell crash after sleep mode

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Gnome crashed after sleep mode, the dock disappears and nothing works

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 16 14:46:26 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-09-15 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 42.9-0ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036310/+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 2036321] Re: Periodically flickering of speaker icon

2023-10-13 Thread Marc Deslauriers
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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2036321

Title:
  Periodically flickering of speaker icon

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Flickering of speaker icon continuously so that I am not able to use
  Ubuntu 20.04.6 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.14
  ProcVersionSignature: Ubuntu 5.15.0-85.95~20.04.2-generic 5.15.122
  Uname: Linux 5.15.0-85-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-85-generic.
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: PCH [HDA Intel PCH], device 0: ALC3223 Analog [ALC3223 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vishal 1379 F pulseaudio
   /dev/snd/pcmC1D0p:   vishal 1379 F...m pulseaudio
   /dev/snd/controlC0:  vishal 1379 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'HDMI'/'HDA Intel HDMI at 0xb071 irq 50'
 Mixer name : 'Intel Haswell HDMI'
 Components : 'HDA:80862807,80860101,0010'
 Controls  : 35
 Simple ctrls  : 5
  Card1.Amixer.info:
   Card hw:1 'PCH'/'HDA Intel PCH at 0xb0714000 irq 48'
 Mixer name : 'Realtek ALC3223'
 Components : 'HDA:10ec0283,102805e9,0013'
 Controls  : 25
 Simple ctrls  : 13
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 16 21:05:29 2023
  InstallationDate: Installed on 2022-08-21 (390 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0Y4M2K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/27/2019:efr1.1:svnDellInc.:pnInspiron5537:pvrA12:rvnDellInc.:rn0Y4M2K:rvrA00:cvnDellInc.:ct8:cvrA12:skuInspiron5537:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5537
  dmi.product.sku: Inspiron 5537
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2036321/+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 2036746] Re: CVE-2023-43090: avoid exposing window previews on lock screen via keyboard

2023-09-20 Thread Marc Deslauriers
** Changed in: gnome-shell (Ubuntu Lunar)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

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

Title:
  CVE-2023-43090: avoid exposing window previews on lock screen via
  keyboard

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Lunar:
  Confirmed

Bug description:
  Security Impact
  ---
  Open windows can be viewed from the lock screen without unlocking the screen.

  Test Case
  -
  From upstream

  This is the broken case and should not happen:

  - Lock screen (e.g. Super+L)
  - Press PrtScn to open screenshot tool
  - Press V twice to toggle the screenshot tool from picture mode to video mode 
and then back to picture mode. (First bug: it should not be possible to enter 
video mode when the UI element is insensitive.)
  - Enter the window selection mode by clicking or pressing W
  - Now all of the user's windows may be viewed despite the session being 
locked.

  Initial Testing Done
  
  I built the package locally. I installed the updated packages on Ubuntu 23.04 
and was no longer able to reproduce the failure case.

  Other Info
  --
  I was unable to duplicate the failure with Ubuntu 22.04 LTS.

  GNOME Shell 42 (included in 22.04 LTS) was the first GNOME release
  with an embedded screenshot tool; previously it used gnome-screenshot.
  So older versions are definitely not affected. GNOME Shell 42 reached
  End of Life earlier this year, but it does not appear to be affected
  by this issue.

  This issue has been fixed for Ubuntu 23.10 with GNOME Shell 45.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2036746/+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 1971242] Re: printing PDF appears always grey, no color

2023-09-12 Thread Marc Deslauriers
I have tested the lunar-proposed package (2.4.2-3ubuntu2.3), and after
updating the package, and recreating the printer, it now defaults to
printing in colour when using Okular.

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

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  Fix Released
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Fix Released
Status in okular package in Ubuntu:
  Confirmed
Status in cups source package in Jammy:
  Fix Committed
Status in cups source package in Lunar:
  Fix Committed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

  [ Impact ]

  If the PPD file for a printer has a ColorModel option and the only
  choice in it for printing in color is not named RGB but CMYK instead,
  the printer cannot be made printing in color with intuitive methods,
  usually selcting the color choice in the print dialog (which makes
  ColorModel=CMYK be sent along with the job).

  Only an ugly command-line-based workaround, running the command

  lpadmin -p PRINTER -o print-color-mode-default=color

  makes the printer print in color.

  An example for printers with such PPDs are printers from RICOH and OEM
  (Lanier, InfoTec, Savin, ..), so many high-end color laser printers
  are affected.

  [ Test Plan ]

  Remove the workaround if you had applied it:

  lpadmin -p PRINTER -R print-color-mode-default

  If you have an affected printer, print a PDF file (or use the print
  functionality in an application) with colored content and choose the
  setting for color printing in the print dialog. When printing via
  command line do

  lp -d PRINTER -o ColorModel=CMYK FILE.pdf

  Without the SRU applied you will get a grayscale/monochrome printout,
  with it applied, you will get a colored printout.

  To test without a printer:

  Stop CUPS:

  sudo systemctl stop cups

  Edit /etc/cups/cups-files.conf to have a line

  FileDevice Yes

  and start CUPS again:

  sudo systemctl start cups

  Then create a queue using the attached sample PPD file:

  lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
  PDF_Printer-PDF.ppd

  Print a file to this queue as described above. When the job is done
  ("lpstat" does not show it any more), open /tmp/printout with a text
  editor. Check whether it contains a line

  @PJL SET RENDERMODE=COLOR

  near its beginning, and NOT a line

  @PJL SET RENDERMODE=GRAYSCALE

  [ Where problems could occur ]

  The patches are simple and they are also for some time in newer CUPS
  versions (2.4.2 and newer) which are included in several distributions
  (Ubuntu 22.10, 23.04, and others) and did not cause any complaints
  about color printing. So the regression potential is very low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD

2023-07-25 Thread Marc Deslauriers
Kinetic has now reached end-of-life. There is nothing else to sponsor in
this bug for now.

I am unsubscribing ubuntu-security-sponsors. If a new debdiff is
attached for sponsoring, please re-subscribe the team. Thanks!

** Changed in: nemo (Ubuntu Kinetic)
   Status: In Progress => Won't Fix

** Changed in: caja (Ubuntu Kinetic)
   Status: New => Won't Fix

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

Title:
  CVE-2022-37290: Pasted zip archive/invalid file causes NPD

Status in caja package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Fix Released
Status in nemo package in Ubuntu:
  Fix Committed
Status in caja source package in Focal:
  New
Status in nautilus source package in Focal:
  Fix Released
Status in nemo source package in Focal:
  New
Status in caja source package in Jammy:
  New
Status in nautilus source package in Jammy:
  Fix Released
Status in nemo source package in Jammy:
  New
Status in caja source package in Kinetic:
  Won't Fix
Status in nautilus source package in Kinetic:
  Fix Released
Status in nemo source package in Kinetic:
  Won't Fix
Status in caja source package in Lunar:
  New
Status in nautilus source package in Lunar:
  Fix Released
Status in nemo source package in Lunar:
  Fix Committed

Bug description:
  A bug for the triage/patching of CVE-2022-37290.

  In get_basename() and g_file_get_basename(), when the file name cannot
  be parsed, NULL is returned; Nautilus does not check this and this
  results in a NPD and a crash.

  The issue on GNOME GitLab explains this pretty well:
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376

  And the code in question is also in Nemo and Caja.

  History of the code: The faulty code was introduced in Nautilus 2.20,
  before Nemo and Caja were forked; these file managers have the same
  issue and same code in the function.

  The simplest POC I found was running this via DBus, which I'm not 100%
  sure if I've altered correctly for Nemo and Caja, but regardless for
  Nautilus this results in a crash.

  ```
  Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 
'G_IS_OBJECT (object)' failed
  Nov 27 20:38:32 Joshua-2210Test kernel: [  825.449866] pool-org.gnome.[5439]: 
segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in 
libglib-2.0.so.0.7400.0[7f3058c03000+8f000]
  Nov 27 20:38:32 Joshua-2210Test kernel: [  825.449878] Code: 0f 85 bc fe ff 
ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 
89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 
00 0f b6 42 01 48 8d
  ```

  Attached is the poc.py, made by Wu Chunming.

  ** Nemo **
  Upstream, version 5.6.0:
  (more advanced/verbose) upstream patch: 
https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005
  possible further problems: 
https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 27 20:41:20 2022
  GsettingsChanges:

  InstallationDate: Installed on 2022-09-18 (70 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 2021484] Re: Editing a VPN ask to introduce credentials but if you cancel can be accessed anyway

2023-07-18 Thread Marc Deslauriers
Are you in the admin or the sudo group? What's the output of the
"groups" command?

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

Title:
  Editing a VPN ask to introduce credentials but if you cancel can be
  accessed anyway

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  I'm logged as a normal user without admin privileges. When I try to
  edit a VPN I'm asked to introduce the credentials of the admin,
  nevertheless if I click cancel I can still access to the VPN
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-settings 20.04.6
  ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98
  Uname: Linux 5.15.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 29 11:16:38 2023
  InstallationDate: Installed on 2022-05-04 (389 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2021484/+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 2024182] Re: GHSL-2023-139: use-after-free in user.c

2023-06-28 Thread Marc Deslauriers
** Information type changed from Private Security to Public Security

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

Title:
  GHSL-2023-139: use-after-free in user.c

Status in accountsservice package in Ubuntu:
  In Progress
Status in accountsservice source package in Focal:
  Fix Released
Status in accountsservice source package in Jammy:
  Fix Released
Status in accountsservice source package in Kinetic:
  Fix Released
Status in accountsservice source package in Lunar:
  Fix Released
Status in accountsservice source package in Mantic:
  In Progress

Bug description:
  # GitHub Security Lab (GHSL) Vulnerability Report, accountsservice:
  `GHSL-2023-139`

  The [GitHub Security Lab](https://securitylab.github.com) team has
  identified a potential security vulnerability in
  [accountsservice](https://code.launchpad.net/ubuntu/+source/accountsservice).

  We are committed to working with you to help resolve this issue. In
  this report you will find everything you need to effectively
  coordinate a resolution of this issue with the GHSL team.

  If at any point you have concerns or questions about this process,
  please do not hesitate to reach out to us at `security...@github.com`
  (please include `GHSL-2023-139` as a reference).

  If you are _NOT_ the correct point of contact for this report, please
  let us know!

  ## Summary

  An unprivileged local attacker can trigger a use-after-free
  vulnerability in accountsservice by sending a D-Bus message to the
  accounts-daemon process.

  ## Product

  accountsservice

  ## Tested Version

  
[22.08.8-1ubuntu7](https://launchpad.net/ubuntu/+source/accountsservice/22.08.8-1ubuntu7)

  The bug is easier to observe on Ubuntu 23.04 than on Ubuntu 22.04 LTS,
  but it is present on both.

  ## Details

  ### Use-after-free when `throw_error` is called (`GHSL-2023-139`)

  After receiving a D-Bus [method
  call](https://dbus.freedesktop.org/doc/dbus-
  specification.html#message-protocol-types), a D-Bus server is expected
  to send either a `METHOD_RETURN` or a `ERROR` message back to the
  client, _but not both_. This is done incorrectly in several places in
  accountsservice. For example, in
  
[`user_change_language_authorized_cb`](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010-set-
  language.patch?h=import/22.08.8-1ubuntu7#n427):

  ```c
  static void
  user_change_language_authorized_cb (Daemon*daemon,
  User  *user,
  GDBusMethodInvocation *context,
  gpointer   data)

  {
  const gchar *language = data;

  if (!user_HOME_available (user)) {

  /* SetLanguage was probably called from a login greeter,
 and HOME not mounted and/or not decrypted.
 Hence don't save anything, or else accountsservice
 and ~/.pam_environment would become out of sync. */
  throw_error (context, ERROR_FAILED, "not access to HOME yet 
so language not saved");  <= 1
  goto out;
  }

  

  out:
  accounts_user_complete_set_language (ACCOUNTS_USER (user), context);  
<= 2
  }
  ```

  If `user_HOME_available` returns an error, then `throw_error` is
  called at 1 to send an `ERROR` message, but a regular `METHOD_RETURN`
  is also sent at 2. This is incorrect D-Bus protocol, but the more
  serious problem is that it causes a use-after-free because both
  `throw_error` and `accounts_user_complete_set_language` decrease the
  reference count on `context`. In other words, `context` is freed by
  `throw_error` and a UAF occurs in
  `accounts_user_complete_set_language`.

  An attacker can trigger the bug above by causing `user_HOME_available`
  to fail, which they can do by deleting all the files from their home
  directory. But there are other incorrect uses of `throw_error` in
  `user.c` which are less inconvenient to trigger. For example, this
  command triggers a call to `throw_error` in `user_update_environment`
  due to the invalid characters in the string.

  ```bash
  dbus-send --system --print-reply --dest=org.freedesktop.Accounts 
/org/freedesktop/Accounts/User`id -u` org.freedesktop.Accounts.User.SetLanguage 
string:'**'
  ```

  On Ubuntu 23.04, the above command causes `accounts-daemon` to crash
  with a `SIGSEGV`. But on Ubuntu 22.04 LTS it doesn't cause any visible
  harm. The difference is due to a recent [change in
  
GLib's](https://gitlab.gnome.org/GNOME/glib/-/commit/69e9ba80e2f4d2061a1a68d72bae1c32c1e4f8fa)
  memory allocation: older versions of GLib used the "slice" allocator,
  but newer version uses the system allocator. The system allocator
  trashes the memory when it's freed in a way that causes the 

[Desktop-packages] [Bug 2024642] Re: Upgrading libx11-6_2:1.6.2-1ubuntu2.1+esm3 failed

2023-06-23 Thread Marc Deslauriers
Updates were pushed to fix this issue. Please re-open this bug if this
problem is still occurring.

** Changed in: libx11 (Ubuntu)
   Status: New => Invalid

** Changed in: libx11 (Ubuntu Trusty)
   Status: New => Fix Released

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

Title:
  Upgrading libx11-6_2:1.6.2-1ubuntu2.1+esm3 failed

Status in libx11 package in Ubuntu:
  Invalid
Status in libx11 source package in Trusty:
  Fix Released

Bug description:
  Upgrading esm3 on Trusty is failed.

  Preparing to unpack .../libx11-6_2%3a1.6.2-1ubuntu2.1+esm3_amd64.deb ...
  Unpacking libx11-6:amd64 (2:1.6.2-1ubuntu2.1+esm3) over (2:1.6.2-1ubuntu2.1) 
...
  dpkg: error processing archive 
/var/cache/apt/archives/libx11-6_2%3a1.6.2-1ubuntu2.1+esm3_amd64.deb (--unpack):
   trying to overwrite shared '/usr/share/doc/libx11-6/changelog.Debian.gz', 
which is different from other instances of package libx11-6:amd64
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libx11-6_2%3a1.6.2-1ubuntu2.1+esm3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/2024642/+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 1971242] Re: printing PDF appears always grey, no color

2023-06-22 Thread Marc Deslauriers
Unfortunately the package in -proposed was superseded by a security
update, and will need to be updated again.

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  Fix Released
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Fix Released
Status in okular package in Ubuntu:
  Confirmed
Status in cups source package in Jammy:
  Fix Committed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

  [ Impact ]

  If the PPD file for a printer has a ColorModel option and the only
  choice in it for printing in color is not named RGB but CMYK instead,
  the printer cannot be made printing in color with intuitive methods,
  usually selcting the color choice in the print dialog (which makes
  ColorModel=CMYK be sent along with the job).

  Only an ugly command-line-based workaround, running the command

  lpadmin -p PRINTER -o print-color-mode-default=color

  makes the printer print in color.

  An example for printers with such PPDs are printers from RICOH and OEM
  (Lanier, InfoTec, Savin, ..), so many high-end color laser printers
  are affected.

  [ Test Plan ]

  Remove the workaround if you had applied it:

  lpadmin -p PRINTER -R print-color-mode-default

  If you have an affected printer, print a PDF file (or use the print
  functionality in an application) with colored content and choose the
  setting for color printing in the print dialog. When printing via
  command line do

  lp -d PRINTER -o ColorModel=CMYK FILE.pdf

  Without the SRU applied you will get a grayscale/monochrome printout,
  with it applied, you will get a colored printout.

  To test without a printer:

  Stop CUPS:

  sudo systemctl stop cups

  Edit /etc/cups/cups-files.conf to have a line

  FiileDevice Yes

  and start CUPS again:

  sudo systemctl start cups

  Then create a queue using the attached sample PPD file:

  lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
  PDF_Printer-PDF.ppd

  Print a file to this queue as described above. When the job is done
  ("lpstat" does not show it any more), open /tmp/printout with a text
  editor. Check whether it contains a line

  @PJL SET RENDERMODE=COLOR

  near its beginning, and NOT a line

  @PJL SET RENDERMODE=GRAYSCALE

  [ Where problems could occur ]

  The patches are simple and they are also for some time in newer CUPS
  versions (2.4.2 and newer) which are included in several distributions
  (Ubuntu 22.10, 23.04, and others) and did not cause any complaints
  about color printing. So the regression potential is very low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 2022391] Re: security breach

2023-06-09 Thread Marc Deslauriers
** Package changed: ubuntu => gnome-control-center (Ubuntu)

** Information type changed from Public Security to Public

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

Title:
  security breach

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

Bug description:
  i update to lunar-lobster a few days ago (40 days ).I understand that i as a 
beta version but when i go to the security settings i saw that my firmware 
didnt pass the test so i dont know if is a problem of the version or is my 
laptop's problem 
  My computer hardware :

  System:
Host: carlos-NBD-WXX9 Kernel: 6.2.0-20-generic arch: x86_64 bits: 64
  Desktop: GNOME v: 44.0 Distro: Ubuntu 23.04 (Lunar Lobster)
  Machine:
Type: Laptop System: HUAWEI product: NBD-WXX9 v: M1010
  serial: 
Mobo: HUAWEI model: NBD-WXX9-PCB-B4 v: M1010 serial: 
  UEFI: HUAWEI v: 2.30 date: 07/04/2022
  Battery:
ID-1: BAT1 charge: 17.9 Wh (33.0%) condition: 54.2/54.9 Wh (98.7%)
  volts: 7.5 min: 7.6
  CPU:
Info: quad core 11th Gen Intel Core i5-1135G7 [MT MCP] speed (MHz):
  avg: 1364 min/max: 400/4200
  Graphics:
Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
Device-2: Quanta ov9734_techfront_camera type: USB driver: uvcvideo
Display: wayland server: X.Org v: 1.22.1.8 with: Xwayland v: 22.1.8
  compositor: gnome-shell driver: X: loaded: modesetting unloaded: 
fbdev,vesa
  dri: iris gpu: i915 resolution: 1920x1080~60Hz
API: OpenGL v: 4.6 Mesa 23.0.2 renderer: Mesa Intel Xe Graphics (TGL GT2)
  Network:
Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi
  Drives:
Local Storage: total: 476.94 GiB used: 149.06 GiB (31.3%)
  Info:
Processes: 337 Uptime: 1h 35m Memory: 7.54 GiB used: 4.27 GiB (56.6%)
Shell: Bash inxi: 3.3.25



  Informe de seguridad del dispositivo
  ==

  Detalles del informe
Fecha generada:  2023-06-02 22:48:37
Versión de fwupd1.8.12

  System details
Modelo de hardware:  HUAWEI NBD-WXX9
Procesador   11th Gen Intel(R) Core(TM) 
i5-1135G7 @ 2.40GHz
SO:  Ubuntu 23.04
Nivel de seguridad:  HSI:0! (v1.8.12)

  HSI-1 Pruebas
Intel Management Engine Version:   Falló (No válido)
UEFI Platform Key:   Correcto (Válido)
TPM v2.0:Correcto (Encontrada)
Firmware BIOS Region:Correcto (Bloqueada)
Firmware Write Protection Lock:  Correcto (Activada)
Platform Debugging:  Correcto (No activada)
Intel Management Engine Manufacturing Mode:  Correcto (Bloqueada)
UEFI Secure Boot:Correcto (Activada)
Firmware Write Protection:   Correcto (No activada)
Intel Management Engine Override:Correcto (Bloqueada)
TPM Platform Configuration:  Correcto (Válido)

  HSI-2 Pruebas
Intel BootGuard Fuse:Correcto (Válido)
Intel BootGuard Verified Boot: Falló (No válido)
Intel BootGuard ACM Protected: Falló (No válido)
Intel BootGuard: Correcto (Activada)
TPM Reconstruction:Falló (No encontrada)
IOMMU Protection:  Falló (No encontrada)
Platform Debugging:  Correcto (Bloqueada)

  HSI-3 Pruebas
Suspend To RAM:  Correcto (No activada)
Intel BootGuard Error Policy:  Falló (No válido)
Pre-boot DMA Protection: Correcto (Activada)
Intel CET:   Correcto (Activada)
Suspend To Idle: Correcto (Activada)

  HSI-4 Pruebas
Encrypted RAM: Falló (No admitida)
Intel SMAP:  Correcto (Activada)

  Pruebas de tiempo de ejecución
Firmware Updater Verification:   Correcto (No envenenado)
Linux Kernel Lockdown:   Correcto (Activada)
Linux Swap:Falló (No cifrado)
Linux Kernel Verification:   Correcto (No envenenado)
Intel CET:   Correcto (Admitida)

  Eventos de seguridad del equipo
2023-04-21 20:11:14   Firmware Updater VerificationCorrecto (No activada → 
No envenenado)
2023-01-28 17:13:05   Firmware Updater VerificatiFalló (No envenenado → No 
activada)

  

[Desktop-packages] [Bug 2022002] Re: browsers are not working suddenly...

2023-06-09 Thread Marc Deslauriers
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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2022002

Title:
  browsers are not working suddenly...

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  same as up

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  1 01:06:40 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-05-05 (25 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2022002/+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 2021935] Re: ubuntu desktop (mantic) error on post-install login

2023-06-09 Thread Marc Deslauriers
** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-messages/+bug/2021935/+attachment/5676873/+files/CoreDump.gz

** Information type changed from Public Security to Public

** Tags added: lunar

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

Title:
  ubuntu desktop (mantic) error on post-install login

Status in ayatana-indicator-messages package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop (mantic) install on hp dc7700 as QA-test.

  Install was a re-use of SDA6 which was Ubuntu-MATE 23.04 with music
  added to /home/Music, plus audacious, figlet, fortune, aptitude &
  other apps added earlier today expecting this re-install (no format)
  to auto-reinstall

  The install was PERFECT & as expected, but on first login I got an
  ERROR, PLEASE REPORT which is why this report.

  I've not detected any issues though.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: ayatana-indicator-messages 22.9.0-1
  Uname: Linux 6.2.0-20-generic x86_64
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed May 31 15:43:45 2023
  ExecutablePath: 
/usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service
  ExecutableTimestamp: 1664708325
  ProcCmdline: 
/usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service
  ProcCwd: /home/guiverc
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: ayatana-indicator-messages
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-messages/+bug/2021935/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD

2023-05-31 Thread Marc Deslauriers
Oh, that would be great, I could release them all at once. Thanks!

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

Title:
  CVE-2022-37290: Pasted zip archive/invalid file causes NPD

Status in caja package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Fix Released
Status in nemo package in Ubuntu:
  Fix Committed
Status in caja source package in Focal:
  New
Status in nautilus source package in Focal:
  Fix Released
Status in nemo source package in Focal:
  New
Status in caja source package in Jammy:
  New
Status in nautilus source package in Jammy:
  Fix Released
Status in nemo source package in Jammy:
  New
Status in caja source package in Kinetic:
  New
Status in nautilus source package in Kinetic:
  Fix Released
Status in nemo source package in Kinetic:
  In Progress
Status in caja source package in Lunar:
  New
Status in nautilus source package in Lunar:
  Fix Released
Status in nemo source package in Lunar:
  Fix Committed

Bug description:
  A bug for the triage/patching of CVE-2022-37290.

  In get_basename() and g_file_get_basename(), when the file name cannot
  be parsed, NULL is returned; Nautilus does not check this and this
  results in a NPD and a crash.

  The issue on GNOME GitLab explains this pretty well:
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376

  And the code in question is also in Nemo and Caja.

  History of the code: The faulty code was introduced in Nautilus 2.20,
  before Nemo and Caja were forked; these file managers have the same
  issue and same code in the function.

  The simplest POC I found was running this via DBus, which I'm not 100%
  sure if I've altered correctly for Nemo and Caja, but regardless for
  Nautilus this results in a crash.

  ```
  Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 
'G_IS_OBJECT (object)' failed
  Nov 27 20:38:32 Joshua-2210Test kernel: [  825.449866] pool-org.gnome.[5439]: 
segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in 
libglib-2.0.so.0.7400.0[7f3058c03000+8f000]
  Nov 27 20:38:32 Joshua-2210Test kernel: [  825.449878] Code: 0f 85 bc fe ff 
ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 
89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 
00 0f b6 42 01 48 8d
  ```

  Attached is the poc.py, made by Wu Chunming.

  ** Nemo **
  Upstream, version 5.6.0:
  (more advanced/verbose) upstream patch: 
https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005
  possible further problems: 
https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 27 20:41:20 2022
  GsettingsChanges:

  InstallationDate: Installed on 2022-09-18 (70 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 2017362] Re: package firefox 112.0.1+build1-0ubuntu0.22.04.1~mt1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2023-04-28 Thread Marc Deslauriers
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/2017362

Title:
  package firefox 112.0.1+build1-0ubuntu0.22.04.1~mt1 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:
  

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: firefox 112.0.1+build1-0ubuntu0.22.04.1~mt1
  ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.23.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nphuoctho  89254 F pulseaudio
  BuildID: 20230414125621
  CasperMD5CheckResult: pass
  Channel: Unavailable
  Date: Sun Apr 23 00:41:49 2023
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  InstallationDate: Installed on 2023-04-08 (14 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  IpRoute:
   default via 192.168.100.1 dev wlp0s20f3 proto dhcp src 192.168.100.244 
metric 20600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.100.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.100.244 
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.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 112.0.1+build1-0ubuntu0.22.04.1~mt1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to kinetic on 2023-04-22 (0 days ago)
  dmi.bios.date: 04/27/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ECCN23WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55756 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Flex 5 14IIL05
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrECCN23WW:bd04/27/2020:br1.22:efr1.18:svnLENOVO:pn81X1:pvrIdeaPadFlex514IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514IIL05:skuLENOVO_MT_81X1_BU_idea_FM_IdeaPadFlex514IIL05:
  dmi.product.family: IdeaPad Flex 5 14IIL05
  dmi.product.name: 81X1
  dmi.product.sku: LENOVO_MT_81X1_BU_idea_FM_IdeaPad Flex 5 14IIL05
  dmi.product.version: IdeaPad Flex 5 14IIL05
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2017362/+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 2017426] Re: Can't connect with RDP from/to LTS22.04

2023-04-28 Thread Marc Deslauriers
** Information type changed from Public Security to Public

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

Title:
  Can't connect with RDP from/to LTS22.04

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

Bug description:
  I use on both side the default apps and desktop environment: 
gnome-control-center, remmina & wayland.
  I tried with all three possible server side session locked/unlocked/closed.
  lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  apt-cache policy gnome-remote-desktop
  gnome-remote-desktop:
Installé : 42.7-0ubuntu1
Candidat : 42.7-0ubuntu1
   Table de version :
   *** 42.7-0ubuntu1 500 (phased 0%)
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.0-4ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  I tried also with ssh tunnel disabled (and port 3389 opened for remote 
access) 
  Chain INPUT (policy DROP 4 packets, 240 bytes)
   pkts bytes target prot opt in out source   
destination 
140 15693 ACCEPT tcp  --  *  *   192.168.22.290.0.0.0/0 
   tcp dpt:3389

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2017426/+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 2007743] Re: intramfs Failed: ZSTD-compressed data

2023-03-29 Thread Marc Püschel
@Julian Andres Klode (~juliank) thank you very much for this
information, I appreciate your work very much!

Do I have to do something, or comes this update for 22.04.2 LTS
automatically?

I'm honestly afraid of testing it, I could get more problems as before.
Furthermore, I really don't want to have more bugs, hope for your understanding 
...
I would honestly prefer a bug fix in public status, can't really believe that 
I'm the only one who is affected by this Bug ...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2007743

Title:
  intramfs Failed: ZSTD-compressed data

Status in grub2-unsigned package in Ubuntu:
  Triaged

Bug description:
  The current updates of Ubuntu 22.04.2 LTS results on boot (black
  screen) the message "not enough memory, press any key" and after comes
  any others "error messages" too and then Ubuntu starts!

  Maybe this Bug results from the current AMD Kernel Updates on "modern"
  Prozessors or Update for the Grub or something - i'don't know - there
  are many System-Updates yesterday and all comes over Ubuntu Store as
  package

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

  # dpkg -l | grep init
  ii  busybox-initramfs  1:1.30.1-7ubuntu3  
  amd64Standalone shell setup for initramfs
  ii  gnome-initial-setup42.0.1-1ubuntu2.3  
  amd64Initial GNOME system setup helper
  ii  init   1.62   
  amd64metapackage ensuring an init system is installed
  ii  init-system-helpers1.62   
  all  helper tools for all init systems
  ii  initramfs-tools0.140ubuntu13.1
  all  generic modular initramfs generator (automation)
  ii  initramfs-tools-bin0.140ubuntu13.1
  amd64binaries used by initramfs-tools
  ii  initramfs-tools-core   0.140ubuntu13.1
  all  generic modular initramfs generator (core tools)
  ii  libatopology2:amd641.2.6.1-1ubuntu1   
  amd64shared library for handling ALSA topology definitions
  ii  libklibc:amd64 2.0.10-4   
  amd64minimal libc subset for use with initramfs
  ii  lsb-base   11.1.0ubuntu4  
  all  Linux Standard Base init script functionality
  ii  ncurses-base   6.3-2  
  all  basic terminal type definitions
  ii  sysvinit-utils 3.01-1ubuntu1  
  amd64System-V-like utilities
  ii  xinit  1.4.1-0ubuntu4 
  amd64X server initialisation tool

  # dpkg -l | grep zfs
  -> brings no information here

  # zfs list
  -> zfs is not installed here

  if you need more system-infos to solve this Bug, please let me know!
  The first error means "Not Enough Memory, Please press any key" - you can 
press any key (but you don't need) and it comes the "intramfs Failed: 
ZSTD-compressed data ..." and then the Ubuntu Login screen comes up.

  Please be patient with me, I'm new to Ubuntu and Launchpad and don't
  know much about it yet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743/+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 2007743] Re: intramfs Failed: ZSTD-compressed data

2023-03-29 Thread Marc Püschel
@Julian Andres Klode (~juliank) thank you very much for this
information, I appreciate your work very much!

do i have to do something or comes this update for 22.04.2 LTS
automatically? I have a productive system, here i will not test
anything. Oh, and I'm a pro user, so I have the functionality
"Livepatch"

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2007743

Title:
  intramfs Failed: ZSTD-compressed data

Status in grub2-unsigned package in Ubuntu:
  Triaged

Bug description:
  The current updates of Ubuntu 22.04.2 LTS results on boot (black
  screen) the message "not enough memory, press any key" and after comes
  any others "error messages" too and then Ubuntu starts!

  Maybe this Bug results from the current AMD Kernel Updates on "modern"
  Prozessors or Update for the Grub or something - i'don't know - there
  are many System-Updates yesterday and all comes over Ubuntu Store as
  package

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

  # dpkg -l | grep init
  ii  busybox-initramfs  1:1.30.1-7ubuntu3  
  amd64Standalone shell setup for initramfs
  ii  gnome-initial-setup42.0.1-1ubuntu2.3  
  amd64Initial GNOME system setup helper
  ii  init   1.62   
  amd64metapackage ensuring an init system is installed
  ii  init-system-helpers1.62   
  all  helper tools for all init systems
  ii  initramfs-tools0.140ubuntu13.1
  all  generic modular initramfs generator (automation)
  ii  initramfs-tools-bin0.140ubuntu13.1
  amd64binaries used by initramfs-tools
  ii  initramfs-tools-core   0.140ubuntu13.1
  all  generic modular initramfs generator (core tools)
  ii  libatopology2:amd641.2.6.1-1ubuntu1   
  amd64shared library for handling ALSA topology definitions
  ii  libklibc:amd64 2.0.10-4   
  amd64minimal libc subset for use with initramfs
  ii  lsb-base   11.1.0ubuntu4  
  all  Linux Standard Base init script functionality
  ii  ncurses-base   6.3-2  
  all  basic terminal type definitions
  ii  sysvinit-utils 3.01-1ubuntu1  
  amd64System-V-like utilities
  ii  xinit  1.4.1-0ubuntu4 
  amd64X server initialisation tool

  # dpkg -l | grep zfs
  -> brings no information here

  # zfs list
  -> zfs is not installed here

  if you need more system-infos to solve this Bug, please let me know!
  The first error means "Not Enough Memory, Please press any key" - you can 
press any key (but you don't need) and it comes the "intramfs Failed: 
ZSTD-compressed data ..." and then the Ubuntu Login screen comes up.

  Please be patient with me, I'm new to Ubuntu and Launchpad and don't
  know much about it yet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743/+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 2007743] Re: intramfs Failed: ZSTD-compressed data

2023-03-25 Thread Marc Püschel
now added to this bug:
@Andy Whitcroft (~apw)
@Andy Whitcroft (~apw2)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2007743

Title:
  intramfs Failed: ZSTD-compressed data

Status in grub2-unsigned package in Ubuntu:
  Triaged

Bug description:
  The current updates of Ubuntu 22.04.2 LTS results on boot (black
  screen) the message "not enough memory, press any key" and after comes
  any others "error messages" too and then Ubuntu starts!

  Maybe this Bug results from the current AMD Kernel Updates on "modern"
  Prozessors or Update for the Grub or something - i'don't know - there
  are many System-Updates yesterday and all comes over Ubuntu Store as
  package

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

  # dpkg -l | grep init
  ii  busybox-initramfs  1:1.30.1-7ubuntu3  
  amd64Standalone shell setup for initramfs
  ii  gnome-initial-setup42.0.1-1ubuntu2.3  
  amd64Initial GNOME system setup helper
  ii  init   1.62   
  amd64metapackage ensuring an init system is installed
  ii  init-system-helpers1.62   
  all  helper tools for all init systems
  ii  initramfs-tools0.140ubuntu13.1
  all  generic modular initramfs generator (automation)
  ii  initramfs-tools-bin0.140ubuntu13.1
  amd64binaries used by initramfs-tools
  ii  initramfs-tools-core   0.140ubuntu13.1
  all  generic modular initramfs generator (core tools)
  ii  libatopology2:amd641.2.6.1-1ubuntu1   
  amd64shared library for handling ALSA topology definitions
  ii  libklibc:amd64 2.0.10-4   
  amd64minimal libc subset for use with initramfs
  ii  lsb-base   11.1.0ubuntu4  
  all  Linux Standard Base init script functionality
  ii  ncurses-base   6.3-2  
  all  basic terminal type definitions
  ii  sysvinit-utils 3.01-1ubuntu1  
  amd64System-V-like utilities
  ii  xinit  1.4.1-0ubuntu4 
  amd64X server initialisation tool

  # dpkg -l | grep zfs
  -> brings no information here

  # zfs list
  -> zfs is not installed here

  if you need more system-infos to solve this Bug, please let me know!
  The first error means "Not Enough Memory, Please press any key" - you can 
press any key (but you don't need) and it comes the "intramfs Failed: 
ZSTD-compressed data ..." and then the Ubuntu Login screen comes up.

  Please be patient with me, I'm new to Ubuntu and Launchpad and don't
  know much about it yet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743/+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 2007743] Re: intramfs Failed: ZSTD-compressed data

2023-03-25 Thread Marc Püschel
@Julian Andres Klode (~juliank)

what is the current status of progress here? Does anyone working on
this? Or should I wait for 23.04.X LTS release and cross my fingers?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2007743

Title:
  intramfs Failed: ZSTD-compressed data

Status in grub2-unsigned package in Ubuntu:
  Triaged

Bug description:
  The current updates of Ubuntu 22.04.2 LTS results on boot (black
  screen) the message "not enough memory, press any key" and after comes
  any others "error messages" too and then Ubuntu starts!

  Maybe this Bug results from the current AMD Kernel Updates on "modern"
  Prozessors or Update for the Grub or something - i'don't know - there
  are many System-Updates yesterday and all comes over Ubuntu Store as
  package

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

  # dpkg -l | grep init
  ii  busybox-initramfs  1:1.30.1-7ubuntu3  
  amd64Standalone shell setup for initramfs
  ii  gnome-initial-setup42.0.1-1ubuntu2.3  
  amd64Initial GNOME system setup helper
  ii  init   1.62   
  amd64metapackage ensuring an init system is installed
  ii  init-system-helpers1.62   
  all  helper tools for all init systems
  ii  initramfs-tools0.140ubuntu13.1
  all  generic modular initramfs generator (automation)
  ii  initramfs-tools-bin0.140ubuntu13.1
  amd64binaries used by initramfs-tools
  ii  initramfs-tools-core   0.140ubuntu13.1
  all  generic modular initramfs generator (core tools)
  ii  libatopology2:amd641.2.6.1-1ubuntu1   
  amd64shared library for handling ALSA topology definitions
  ii  libklibc:amd64 2.0.10-4   
  amd64minimal libc subset for use with initramfs
  ii  lsb-base   11.1.0ubuntu4  
  all  Linux Standard Base init script functionality
  ii  ncurses-base   6.3-2  
  all  basic terminal type definitions
  ii  sysvinit-utils 3.01-1ubuntu1  
  amd64System-V-like utilities
  ii  xinit  1.4.1-0ubuntu4 
  amd64X server initialisation tool

  # dpkg -l | grep zfs
  -> brings no information here

  # zfs list
  -> zfs is not installed here

  if you need more system-infos to solve this Bug, please let me know!
  The first error means "Not Enough Memory, Please press any key" - you can 
press any key (but you don't need) and it comes the "intramfs Failed: 
ZSTD-compressed data ..." and then the Ubuntu Login screen comes up.

  Please be patient with me, I'm new to Ubuntu and Launchpad and don't
  know much about it yet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743/+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 2001503] Re: gnome-control-center crashed with SIGSEGV -- pipewire

2023-03-17 Thread Marc Deslauriers
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 gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2001503

Title:
  gnome-control-center crashed with SIGSEGV -- pipewire

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

Bug description:
  Just upgraded from 22.04 to 22.10 and am trying to get pipewire +
  pulseaudio working. It seems like some of the apps (gsd-sound?) aren't
  quite ready for pipewire ... restarting the services (systemctl --user
  restart pipewire pipewire-pulse) causes the sound settings dialog to
  collect a lot of stale entries for output devices. When I select them
  and try to test, the app crashes.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  3 10:03:34 2023
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2022-01-05 (363 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcCmdline: gnome-control-center
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f3523070a2f:mov%esi,(%rdx)
   PC (0x7f3523070a2f) ok
   source "%esi" ok
   destination "(%rdx)" (0x0021) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libpulse.so.0
   pa_context_set_card_profile_by_index () at 
/lib/x86_64-linux-gnu/libpulse.so.0
   gvc_mixer_card_change_profile ()
   gvc_mixer_control_change_profile_on_selected_device ()
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: Upgraded to kinetic on 2022-12-28 (5 days ago)
  UserGroups: adm cdrom dialout dip disk docker libvirt lpadmin lxd plugdev 
sambashare sudo wireshark
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-24T09:03:25.873541
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2001503/+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 2008662] Re: How do I fix error : "Appear a prohibit icon

2023-03-17 Thread Marc Deslauriers
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 gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/2008662

Title:
  How do I fix error : "Appear a prohibit icon

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

Bug description:
  How do I fix error : "Appear a prohibit icon

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-appindicator 42-2~fakesync1
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 27 11:23:28 2023
  InstallationDate: Installed on 2022-09-14 (165 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2008662/+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 2009948] Re: Problem with xorg

2023-03-17 Thread Marc Deslauriers
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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2009948

Title:
  Problem with xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-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  525.85.05  Sat Jan 14 
00:49:50 UTC 2023
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 09:08:31 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:0959]
 Subsystem: Dell GP108M [GeForce MX230] [1028:0959]
  InstallationDate: Installed on 2023-03-10 (0 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: Dell Inc. Vostro 5490
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=b6242c65-c3ec-45af-912f-e70f66a54868 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2022
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.0
  dmi.board.name: 0M9F58
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.0:bd07/08/2022:br1.20:svnDellInc.:pnVostro5490:pvr:rvnDellInc.:rn0M9F58:rvrA04:cvnDellInc.:ct10:cvr:sku0959:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5490
  dmi.product.sku: 0959
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2009948/+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 2011284] Re: A flickering and glitching problem

2023-03-17 Thread Marc Deslauriers
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

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

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

Title:
  A flickering and glitching problem

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Dear Ubuntu Dev,

  
  I've been using my linux UBUNTU 18.04 LTS for the past 6 months and the day 
since I got this computer,It started glitching.Can you please fix that?I have a 
screenshot of the problem and I am unable to play some games due to this 
completely glitching and flickering

  Sincerely,

  Nihar Raju

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 11 10:44:09 2023
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev df) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:879e]
  InstallationDate: Installed on 2021-02-22 (746 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 245 G8 Notebook PC
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=0c18d80a-c684-48f5-881d-dbe1c2478f74 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2021
  dmi.bios.vendor: AMI
  dmi.bios.version: F.62
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 879E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 84.49
  dmi.chassis.asset.tag: 5CG13423RK
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.62:bd04/23/2021:svnHewlett-Packard:pnHP245G8NotebookPC:pvr:rvnHewlett-Packard:rn879E:rvr84.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 245 G8 Notebook PC
  dmi.product.sku: 404V1PC#ACJ
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2011284/+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 2000644] Re: switching workspaces with shortcut sometimes freezes screen

2023-03-13 Thread marc
I also experience this.. 
But mostly i cant exit overview.  so its not frozen, just stuck. i can still 
click things

i think i also crash when i use a workspace sorting extension.  
and i think i crashed when using pixel safer and with xprop installed

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

Title:
  switching workspaces with shortcut sometimes freezes screen

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The bottom panel with dots to show which workspace you are on when
  switching with ctrl+alt+arrow sometimes doesn't disappear and gets
  stuck in a half faded or not faded state.  In that state the mouse
  appear stuck and the screen freezes until the super key is pressed to
  show overview or the workspace is switched again.

  Ubuntu 22.10, gnome-shell 43.1-0ubuntu1, Wayland, Nvidia on-demand,
  Nvidia driver 525.60.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2000644/+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 2007743] Re: intramfs Failed: ZSTD-compressed data

2023-03-13 Thread Marc Püschel
@Julian Andres Klode (~juliank)

what is the current status of progress here? it would be really nice, if
a bugfix will be released soon.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2007743

Title:
  intramfs Failed: ZSTD-compressed data

Status in grub2-unsigned package in Ubuntu:
  Triaged

Bug description:
  The current updates of Ubuntu 22.04.2 LTS results on boot (black
  screen) the message "not enough memory, press any key" and after comes
  any others "error messages" too and then Ubuntu starts!

  Maybe this Bug results from the current AMD Kernel Updates on "modern"
  Prozessors or Update for the Grub or something - i'don't know - there
  are many System-Updates yesterday and all comes over Ubuntu Store as
  package

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

  # dpkg -l | grep init
  ii  busybox-initramfs  1:1.30.1-7ubuntu3  
  amd64Standalone shell setup for initramfs
  ii  gnome-initial-setup42.0.1-1ubuntu2.3  
  amd64Initial GNOME system setup helper
  ii  init   1.62   
  amd64metapackage ensuring an init system is installed
  ii  init-system-helpers1.62   
  all  helper tools for all init systems
  ii  initramfs-tools0.140ubuntu13.1
  all  generic modular initramfs generator (automation)
  ii  initramfs-tools-bin0.140ubuntu13.1
  amd64binaries used by initramfs-tools
  ii  initramfs-tools-core   0.140ubuntu13.1
  all  generic modular initramfs generator (core tools)
  ii  libatopology2:amd641.2.6.1-1ubuntu1   
  amd64shared library for handling ALSA topology definitions
  ii  libklibc:amd64 2.0.10-4   
  amd64minimal libc subset for use with initramfs
  ii  lsb-base   11.1.0ubuntu4  
  all  Linux Standard Base init script functionality
  ii  ncurses-base   6.3-2  
  all  basic terminal type definitions
  ii  sysvinit-utils 3.01-1ubuntu1  
  amd64System-V-like utilities
  ii  xinit  1.4.1-0ubuntu4 
  amd64X server initialisation tool

  # dpkg -l | grep zfs
  -> brings no information here

  # zfs list
  -> zfs is not installed here

  if you need more system-infos to solve this Bug, please let me know!
  The first error means "Not Enough Memory, Please press any key" - you can 
press any key (but you don't need) and it comes the "intramfs Failed: 
ZSTD-compressed data ..." and then the Ubuntu Login screen comes up.

  Please be patient with me, I'm new to Ubuntu and Launchpad and don't
  know much about it yet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743/+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 2007743] Re: intramfs Failed: ZSTD-compressed data

2023-03-02 Thread Marc Püschel
@Julian Andres Klode (juliank)

thanks for getting back. Okay, please keep me up-to-date and do not
forget the bug

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2007743

Title:
  intramfs Failed: ZSTD-compressed data

Status in grub2-unsigned package in Ubuntu:
  Triaged

Bug description:
  The current updates of Ubuntu 22.04.2 LTS results on boot (black
  screen) the message "not enough memory, press any key" and after comes
  any others "error messages" too and then Ubuntu starts!

  Maybe this Bug results from the current AMD Kernel Updates on "modern"
  Prozessors or Update for the Grub or something - i'don't know - there
  are many System-Updates yesterday and all comes over Ubuntu Store as
  package

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

  # dpkg -l | grep init
  ii  busybox-initramfs  1:1.30.1-7ubuntu3  
  amd64Standalone shell setup for initramfs
  ii  gnome-initial-setup42.0.1-1ubuntu2.3  
  amd64Initial GNOME system setup helper
  ii  init   1.62   
  amd64metapackage ensuring an init system is installed
  ii  init-system-helpers1.62   
  all  helper tools for all init systems
  ii  initramfs-tools0.140ubuntu13.1
  all  generic modular initramfs generator (automation)
  ii  initramfs-tools-bin0.140ubuntu13.1
  amd64binaries used by initramfs-tools
  ii  initramfs-tools-core   0.140ubuntu13.1
  all  generic modular initramfs generator (core tools)
  ii  libatopology2:amd641.2.6.1-1ubuntu1   
  amd64shared library for handling ALSA topology definitions
  ii  libklibc:amd64 2.0.10-4   
  amd64minimal libc subset for use with initramfs
  ii  lsb-base   11.1.0ubuntu4  
  all  Linux Standard Base init script functionality
  ii  ncurses-base   6.3-2  
  all  basic terminal type definitions
  ii  sysvinit-utils 3.01-1ubuntu1  
  amd64System-V-like utilities
  ii  xinit  1.4.1-0ubuntu4 
  amd64X server initialisation tool

  # dpkg -l | grep zfs
  -> brings no information here

  # zfs list
  -> zfs is not installed here

  if you need more system-infos to solve this Bug, please let me know!
  The first error means "Not Enough Memory, Please press any key" - you can 
press any key (but you don't need) and it comes the "intramfs Failed: 
ZSTD-compressed data ..." and then the Ubuntu Login screen comes up.

  Please be patient with me, I'm new to Ubuntu and Launchpad and don't
  know much about it yet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743/+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 2008907] Re: Ubuntu 22.04.2 Update GNOME-Software fails

2023-03-01 Thread Marc Püschel
the problem solved itself by unknown reason. Unfortunately i can't close
or delete this bug.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2008907

Title:
  Ubuntu 22.04.2 Update GNOME-Software fails

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results

  Prepared update not found: /var/lib/PackageKit/prepared-update

  If i run

  # sudo apt-get update && sudo apt-get dist-upgrade

  I get this (sorry german only):

  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure

  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?

  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.

  https://abload.de/img/bildschirmfotovom20237pdzo.png

  Or is this a result of this:
  https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743

  And i have little investigated this error, and i found out, that Red Hat had 
in 2021 a similar issue
  https://bugzilla.redhat.com/show_bug.cgi?id=1995817

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2008907/+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 2008907] Re: Ubuntu 22.04.2 Update GNOME-Software fails

2023-03-01 Thread Marc Püschel
sorry, please ignore this BUG here, i don't know why but now i was able
to download the updates and install it successfully.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2008907

Title:
  Ubuntu 22.04.2 Update GNOME-Software fails

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results

  Prepared update not found: /var/lib/PackageKit/prepared-update

  If i run

  # sudo apt-get update && sudo apt-get dist-upgrade

  I get this (sorry german only):

  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure

  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?

  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.

  https://abload.de/img/bildschirmfotovom20237pdzo.png

  Or is this a result of this:
  https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743

  And i have little investigated this error, and i found out, that Red Hat had 
in 2021 a similar issue
  https://bugzilla.redhat.com/show_bug.cgi?id=1995817

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2008907/+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 2007743] Re: intramfs Failed: ZSTD-compressed data

2023-03-01 Thread Marc Püschel
what is the current status of progress here? it would be really nice, if
a bugfix will be released soon.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2007743

Title:
  intramfs Failed: ZSTD-compressed data

Status in grub2-unsigned package in Ubuntu:
  Triaged

Bug description:
  The current updates of Ubuntu 22.04.2 LTS results on boot (black
  screen) the message "not enough memory, press any key" and after comes
  any others "error messages" too and then Ubuntu starts!

  Maybe this Bug results from the current AMD Kernel Updates on "modern"
  Prozessors or Update for the Grub or something - i'don't know - there
  are many System-Updates yesterday and all comes over Ubuntu Store as
  package

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

  # dpkg -l | grep init
  ii  busybox-initramfs  1:1.30.1-7ubuntu3  
  amd64Standalone shell setup for initramfs
  ii  gnome-initial-setup42.0.1-1ubuntu2.3  
  amd64Initial GNOME system setup helper
  ii  init   1.62   
  amd64metapackage ensuring an init system is installed
  ii  init-system-helpers1.62   
  all  helper tools for all init systems
  ii  initramfs-tools0.140ubuntu13.1
  all  generic modular initramfs generator (automation)
  ii  initramfs-tools-bin0.140ubuntu13.1
  amd64binaries used by initramfs-tools
  ii  initramfs-tools-core   0.140ubuntu13.1
  all  generic modular initramfs generator (core tools)
  ii  libatopology2:amd641.2.6.1-1ubuntu1   
  amd64shared library for handling ALSA topology definitions
  ii  libklibc:amd64 2.0.10-4   
  amd64minimal libc subset for use with initramfs
  ii  lsb-base   11.1.0ubuntu4  
  all  Linux Standard Base init script functionality
  ii  ncurses-base   6.3-2  
  all  basic terminal type definitions
  ii  sysvinit-utils 3.01-1ubuntu1  
  amd64System-V-like utilities
  ii  xinit  1.4.1-0ubuntu4 
  amd64X server initialisation tool

  # dpkg -l | grep zfs
  -> brings no information here

  # zfs list
  -> zfs is not installed here

  if you need more system-infos to solve this Bug, please let me know!
  The first error means "Not Enough Memory, Please press any key" - you can 
press any key (but you don't need) and it comes the "intramfs Failed: 
ZSTD-compressed data ..." and then the Ubuntu Login screen comes up.

  Please be patient with me, I'm new to Ubuntu and Launchpad and don't
  know much about it yet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743/+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 2008907] Re: Ubuntu 22.04.2 Update GNOME-Software fails

2023-03-01 Thread Marc Püschel
** Description changed:

  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results
  
  Prepared update not found: /var/lib/PackageKit/prepared-update
  
  If i run
  
  # sudo apt-get update && sudo apt-get dist-upgrade
  
  I get this (sorry german only):
  
  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure
  
  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?
  
  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.
  
  https://abload.de/img/bildschirmfotovom20237pdzo.png
+ 
+ Or is this a result of this:
+ https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743

** Description changed:

  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results
  
  Prepared update not found: /var/lib/PackageKit/prepared-update
  
  If i run
  
  # sudo apt-get update && sudo apt-get dist-upgrade
  
  I get this (sorry german only):
  
  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure
  
  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?
  
  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.
  
  https://abload.de/img/bildschirmfotovom20237pdzo.png
  
  Or is this a result of this:
  https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743
+ 
+ And i have little investigated this error, and i found out, that Red Hat had 
in 2021 a similar issue
+ https://bugzilla.redhat.com/show_bug.cgi?id=1995817

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2008907

Title:
  Ubuntu 22.04.2 Update GNOME-Software fails

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results

  Prepared update not found: /var/lib/PackageKit/prepared-update

  If i run

  # sudo apt-get update && sudo apt-get dist-upgrade

  I get this (sorry german only):

  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    

[Desktop-packages] [Bug 2008907] Re: Ubuntu 22.04.2 Update fails

2023-03-01 Thread Marc Püschel
** Description changed:

  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results
  
  Prepared update not found: /var/lib/PackageKit/prepared-update
  
  If i run
  
  # sudo apt-get update && sudo apt-get dist-upgrade
  
  I get this (sorry german only):
  
  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure
  
  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?
  
  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.
  
  https://abload.de/img/bildschirmfotovom20237pdzo.png
- 
- @Julian Andres Klode (juliank):
- 
- ich habe absichtlich dich hier hinzugefügt, weil ich weiß, dass du
- deutsch sprichst ;-)

** Summary changed:

- Ubuntu 22.04.2 Update fails
+ Ubuntu 22.04.2 Update GNOME-Software fails

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2008907

Title:
  Ubuntu 22.04.2 Update GNOME-Software fails

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results

  Prepared update not found: /var/lib/PackageKit/prepared-update

  If i run

  # sudo apt-get update && sudo apt-get dist-upgrade

  I get this (sorry german only):

  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure

  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?

  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.

  https://abload.de/img/bildschirmfotovom20237pdzo.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2008907/+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 2008907] Re: Ubuntu 22.04.2 Update fails

2023-03-01 Thread Marc Püschel
** Description changed:

  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results
  
  Prepared update not found: /var/lib/PackageKit/prepared-update
  
  If i run
  
  # sudo apt-get update && sudo apt-get dist-upgrade
  
  I get this (sorry german only):
  
  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure
  
  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?
  
  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.
  
+ https://abload.de/img/bildschirmfotovom20237pdzo.png
+ 
  @Julian Andres Klode (juliank):
  
  ich habe absichtlich dich hier hinzugefügt, weil ich weiß, dass du
  deutsch sprichst ;-)

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

Title:
  Ubuntu 22.04.2 Update fails

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results

  Prepared update not found: /var/lib/PackageKit/prepared-update

  If i run

  # sudo apt-get update && sudo apt-get dist-upgrade

  I get this (sorry german only):

  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure

  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?

  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.

  https://abload.de/img/bildschirmfotovom20237pdzo.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2008907/+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 2008907] Re: Ubuntu 22.04.2 Update fails

2023-03-01 Thread Marc Püschel
** Package changed: ubuntu => gnome-software (Ubuntu)

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

Title:
  Ubuntu 22.04.2 Update fails

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results

  Prepared update not found: /var/lib/PackageKit/prepared-update

  If i run

  # sudo apt-get update && sudo apt-get dist-upgrade

  I get this (sorry german only):

  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure

  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?

  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.

  https://abload.de/img/bildschirmfotovom20237pdzo.png

  @Julian Andres Klode (juliank):

  ich habe absichtlich dich hier hinzugefügt, weil ich weiß, dass du
  deutsch sprichst ;-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2008907/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD

2023-02-17 Thread Marc Deslauriers
The update is for kinetic, did you test it on kinetic?

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

Title:
  CVE-2022-37290: Pasted zip archive/invalid file causes NPD

Status in caja package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Fix Released
Status in nemo package in Ubuntu:
  Fix Committed
Status in caja source package in Focal:
  New
Status in nautilus source package in Focal:
  Fix Released
Status in nemo source package in Focal:
  New
Status in caja source package in Jammy:
  New
Status in nautilus source package in Jammy:
  Fix Released
Status in nemo source package in Jammy:
  New
Status in caja source package in Kinetic:
  New
Status in nautilus source package in Kinetic:
  Fix Released
Status in nemo source package in Kinetic:
  In Progress
Status in caja source package in Lunar:
  New
Status in nautilus source package in Lunar:
  Fix Released
Status in nemo source package in Lunar:
  Fix Committed

Bug description:
  A bug for the triage/patching of CVE-2022-37290.

  In get_basename() and g_file_get_basename(), when the file name cannot
  be parsed, NULL is returned; Nautilus does not check this and this
  results in a NPD and a crash.

  The issue on GNOME GitLab explains this pretty well:
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376

  And the code in question is also in Nemo and Caja.

  History of the code: The faulty code was introduced in Nautilus 2.20,
  before Nemo and Caja were forked; these file managers have the same
  issue and same code in the function.

  The simplest POC I found was running this via DBus, which I'm not 100%
  sure if I've altered correctly for Nemo and Caja, but regardless for
  Nautilus this results in a crash.

  ```
  Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 
'G_IS_OBJECT (object)' failed
  Nov 27 20:38:32 Joshua-2210Test kernel: [  825.449866] pool-org.gnome.[5439]: 
segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in 
libglib-2.0.so.0.7400.0[7f3058c03000+8f000]
  Nov 27 20:38:32 Joshua-2210Test kernel: [  825.449878] Code: 0f 85 bc fe ff 
ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 
89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 
00 0f b6 42 01 48 8d
  ```

  Attached is the poc.py, made by Wu Chunming.

  ** Nemo **
  Upstream, version 5.6.0:
  (more advanced/verbose) upstream patch: 
https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005
  possible further problems: 
https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 27 20:41:20 2022
  GsettingsChanges:

  InstallationDate: Installed on 2022-09-18 (70 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD

2023-02-09 Thread Marc Deslauriers
ACK on the debdiff in comment #8. I have slightly adjusted it to add the
bug number to the changelog and to fix the urls in the patch. I have
uploaded it to the security team PPA here:

https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa

Please test it to make sure it works properly, and comment back in this
bug, at which point I will release it as a security update. Thanks!

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

Title:
  CVE-2022-37290: Pasted zip archive/invalid file causes NPD

Status in caja package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Fix Released
Status in nemo package in Ubuntu:
  Fix Committed
Status in caja source package in Focal:
  New
Status in nautilus source package in Focal:
  Fix Released
Status in nemo source package in Focal:
  New
Status in caja source package in Jammy:
  New
Status in nautilus source package in Jammy:
  Fix Released
Status in nemo source package in Jammy:
  New
Status in caja source package in Kinetic:
  New
Status in nautilus source package in Kinetic:
  Fix Released
Status in nemo source package in Kinetic:
  In Progress
Status in caja source package in Lunar:
  New
Status in nautilus source package in Lunar:
  Fix Released
Status in nemo source package in Lunar:
  Fix Committed

Bug description:
  A bug for the triage/patching of CVE-2022-37290.

  In get_basename() and g_file_get_basename(), when the file name cannot
  be parsed, NULL is returned; Nautilus does not check this and this
  results in a NPD and a crash.

  The issue on GNOME GitLab explains this pretty well:
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376

  And the code in question is also in Nemo and Caja.

  History of the code: The faulty code was introduced in Nautilus 2.20,
  before Nemo and Caja were forked; these file managers have the same
  issue and same code in the function.

  The simplest POC I found was running this via DBus, which I'm not 100%
  sure if I've altered correctly for Nemo and Caja, but regardless for
  Nautilus this results in a crash.

  ```
  Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 
'G_IS_OBJECT (object)' failed
  Nov 27 20:38:32 Joshua-2210Test kernel: [  825.449866] pool-org.gnome.[5439]: 
segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in 
libglib-2.0.so.0.7400.0[7f3058c03000+8f000]
  Nov 27 20:38:32 Joshua-2210Test kernel: [  825.449878] Code: 0f 85 bc fe ff 
ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 
89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 
00 0f b6 42 01 48 8d
  ```

  Attached is the poc.py, made by Wu Chunming.

  ** Nemo **
  Upstream, version 5.6.0:
  (more advanced/verbose) upstream patch: 
https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005
  possible further problems: 
https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 27 20:41:20 2022
  GsettingsChanges:

  InstallationDate: Installed on 2022-09-18 (70 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3

2023-02-07 Thread Marc Deslauriers
We are not going to release these yet, we are blocked on comment #8.

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

Title:
  [jammy] Update gjs to 1.74 using mozjs102 102.3

Status in gjs package in Ubuntu:
  Fix Released
Status in mozjs102 package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Fix Committed
Status in mozjs102 source package in Jammy:
  Fix Committed
Status in mozjs102 source package in Kinetic:
  Fix Committed

Bug description:
  Impact
  --
  GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). 
Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 
ESR series for security updates for the next year.

  This requires updating gjs from 1.72 to 1.74 from GNOME 43, as
  packaged in Ubuntu 22.10.

  This will be done as a Security Update.

  Updating mozjs in stable Ubuntu releases was recommended when Ubuntu
  first switched back to GNOME, but this is the first time it's been
  done.

  Security Impact
  ---
  I looked through
  https://github.com/mozilla/gecko-dev/commits/esr102/js
  and searched for referenced bug numbers in
  https://www.mozilla.org/en-US/security/advisories/
  for Firefox ESR releases since Ubuntu's 91.10

  and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE
  issued) mentioned at

  https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/

  Uploaded Packages
  -
  We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being 
careful to publish it in main, not universe.
  And we'll update gjs.
  No other packages need to be updated for this change.
  mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are 
generally not possible), but nothing else in Ubuntu uses it.

  Test Case
  -
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

  Security Sponsoring
  ---
  sudo apt install git-buildpackage
  gbp clone https://salsa.debian.org/gnome-team/gjs
  cd gjs
  git checkout ubuntu/jammy
  gbp buildpackage --git-builder="debuild -S -nc"

  mkdir ../tarballs; cd ../tarballs
  pull-lp-source mozjs102 kinetic
  cd ..
  gbp clone https://salsa.debian.org/gnome-team/mozjs
  cd mozjs
  git checkout ubuntu/102/jammy
  gbp buildpackage --git-builder="debuild --no-lintian -S -nc" 
--git-tarball-dir=../tarballs
  # That avoids needing to recreate the original tarball from pristine-tar 
which takes a while. Also, running lintian takes a while.

  Initial Testing Done
  
  I built the packages in my PPA.
  I installed the packages on Ubuntu 22.04 LTS and successfully completed the 
Test Case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+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 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3

2023-02-06 Thread Marc Deslauriers
The image builds are pulling in -proposed?

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

Title:
  [jammy] Update gjs to 1.74 using mozjs102 102.3

Status in gjs package in Ubuntu:
  Fix Released
Status in mozjs102 package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Fix Committed
Status in mozjs102 source package in Jammy:
  Fix Committed
Status in mozjs102 source package in Kinetic:
  Fix Committed

Bug description:
  Impact
  --
  GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). 
Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 
ESR series for security updates for the next year.

  This requires updating gjs from 1.72 to 1.74 from GNOME 43, as
  packaged in Ubuntu 22.10.

  This will be done as a Security Update.

  Updating mozjs in stable Ubuntu releases was recommended when Ubuntu
  first switched back to GNOME, but this is the first time it's been
  done.

  Security Impact
  ---
  I looked through
  https://github.com/mozilla/gecko-dev/commits/esr102/js
  and searched for referenced bug numbers in
  https://www.mozilla.org/en-US/security/advisories/
  for Firefox ESR releases since Ubuntu's 91.10

  and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE
  issued) mentioned at

  https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/

  Uploaded Packages
  -
  We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being 
careful to publish it in main, not universe.
  And we'll update gjs.
  No other packages need to be updated for this change.
  mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are 
generally not possible), but nothing else in Ubuntu uses it.

  Test Case
  -
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

  Security Sponsoring
  ---
  sudo apt install git-buildpackage
  gbp clone https://salsa.debian.org/gnome-team/gjs
  cd gjs
  git checkout ubuntu/jammy
  gbp buildpackage --git-builder="debuild -S -nc"

  mkdir ../tarballs; cd ../tarballs
  pull-lp-source mozjs102 kinetic
  cd ..
  gbp clone https://salsa.debian.org/gnome-team/mozjs
  cd mozjs
  git checkout ubuntu/102/jammy
  gbp buildpackage --git-builder="debuild --no-lintian -S -nc" 
--git-tarball-dir=../tarballs
  # That avoids needing to recreate the original tarball from pristine-tar 
which takes a while. Also, running lintian takes a while.

  Initial Testing Done
  
  I built the packages in my PPA.
  I installed the packages on Ubuntu 22.04 LTS and successfully completed the 
Test Case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

2023-01-07 Thread Marc Peña
Hi again @nteodosio and happy new year!

Any progress to report in the last 2 months?

Thanks!

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  1. Install the Chromium snap,

     sudo snap install --channel stable/hwacc chromium

  2. Start Chromium,

     snap run chromium

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples.

  4. Enter about:media-internals in the address bar, click the
  corresponding box (if the video is playing, it will have the "(kPlay)"
  identifier) and note what the page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
  - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
  - Distro version (`grep VERSION= /etc/os_release`);
  - GPU (`lscpu`);
  - CPU generation (`lscpu`).

  Currently it seems to work for all reporters on Xorg.

  The version in stable/hwacc is fixed.

  Versions in other channels (edge/hwacc, beta/hwacc, candidate/hwacc)
  follow the Chromium release cycle (dev, beta and stable channels as in
  https://omahaproxy.appspot.com/all.json?os=linux).

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3

2022-12-15 Thread Marc Deslauriers
mozjs102 and gjs packages have been uploaded for jammy, and mozjs102 for
kinetic, into the security team PPA here:

https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages

Once they are finished building, they can be pocket-copied by an archive
admin into the -proposed pocket for more testing.

Thanks!

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

Title:
  [jammy] Update gjs to 1.74 using mozjs102 102.3

Status in gjs package in Ubuntu:
  Confirmed
Status in mozjs102 package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). 
Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 
ESR series for security updates for the next year.

  This requires updating gjs from 1.72 to 1.74 from GNOME 43, as
  packaged in Ubuntu 22.10.

  This will be done as a Security Update.

  Updating mozjs in stable Ubuntu releases was recommended when Ubuntu
  first switched back to GNOME, but this is the first time it's been
  done.

  Security Impact
  ---
  I looked through
  https://github.com/mozilla/gecko-dev/commits/esr102/js
  and searched for referenced bug numbers in
  https://www.mozilla.org/en-US/security/advisories/
  for Firefox ESR releases since Ubuntu's 91.10

  and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE
  issued) mentioned at

  https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/

  Uploaded Packages
  -
  We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being 
careful to publish it in main, not universe.
  And we'll update gjs.
  No other packages need to be updated for this change.
  mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are 
generally not possible), but nothing else in Ubuntu uses it.

  Test Case
  -
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

  Security Sponsoring
  ---
  sudo apt install git-buildpackage
  gbp clone https://salsa.debian.org/gnome-team/gjs
  cd gjs
  git checkout ubuntu/jammy
  gbp buildpackage --git-builder="debuild -S -nc"

  mkdir ../tarballs; cd ../tarballs
  pull-lp-source mozjs102 kinetic
  cd ..
  gbp clone https://salsa.debian.org/gnome-team/mozjs
  cd mozjs
  git checkout ubuntu/102/jammy
  gbp buildpackage --git-builder="debuild --no-lintian -S -nc" 
--git-tarball-dir=../tarballs
  # That avoids needing to recreate the original tarball from pristine-tar 
which takes a while. Also, running lintian takes a while.

  Initial Testing Done
  
  I built the packages in my PPA.
  I installed the packages on Ubuntu 22.04 LTS and successfully completed the 
Test Case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+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 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3

2022-12-12 Thread Marc Deslauriers
Looks like a few more CVEs have been published between 102.3 in karmic
and 102.5 in lunar:

102.4 CVE-2022-42928 bug 1791520
102.5 CVE-2022-45406 bug 1791975
102.5 CVE-2022-45409 bug 1796901

Perhaps we should move to 102.5?

I have to admit, bumping to a new major release of mozjs sounds risky.
What are the plans to test all the arbitrary gnome-shell plugins that
could be installed in user environments? How well does gnome-shell
handle a plugin that could crash on startup if there is an
incompatibility with a newer mozjs version?

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-42928

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-45406

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-45409

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

Title:
  [jammy] Update gjs to 1.74 using mozjs102 102.3

Status in gjs package in Ubuntu:
  Confirmed
Status in mozjs102 package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). 
Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 
ESR series for security updates for the next year.

  This requires updating gjs from 1.72 to 1.74 from GNOME 43, as
  packaged in Ubuntu 22.10.

  This will be done as a Security Update.

  Updating mozjs in stable Ubuntu releases was recommended when Ubuntu
  first switched back to GNOME, but this is the first time it's been
  done.

  Security Impact
  ---
  I looked through
  https://github.com/mozilla/gecko-dev/commits/esr102/js
  and searched for referenced bug numbers in
  https://www.mozilla.org/en-US/security/advisories/
  for Firefox ESR releases since Ubuntu's 91.10

  and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE
  issued) mentioned at

  https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/

  Uploaded Packages
  -
  We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being 
careful to publish it in main, not universe.
  And we'll update gjs.
  No other packages need to be updated for this change.
  mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are 
generally not possible), but nothing else in Ubuntu uses it.

  Test Case
  -
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

  Security Sponsoring
  ---
  sudo apt install git-buildpackage
  gbp clone https://salsa.debian.org/gnome-team/gjs
  cd gjs
  git checkout ubuntu/jammy
  gbp buildpackage --git-builder="debuild -S -nc"

  mkdir ../tarballs; cd ../tarballs
  pull-lp-source mozjs102 kinetic
  cd ..
  gbp clone https://salsa.debian.org/gnome-team/mozjs
  cd mozjs
  git checkout ubuntu/102/jammy
  gbp buildpackage --git-builder="debuild --no-lintian -S -nc" 
--git-tarball-dir=../tarballs
  # That avoids needing to recreate the original tarball from pristine-tar 
which takes a while. Also, running lintian takes a while.

  Initial Testing Done
  
  I built the packages in my PPA.
  I installed the packages on Ubuntu 22.04 LTS and successfully completed the 
Test Case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

2022-11-10 Thread Marc Peña
Hi! From: https://code.launchpad.net/~nteodosio/chromium-
browser/+git/chromium-browser/+merge/428038/comments/1137194

Is there any ETA for finishing the legal review of the inclusion of the
non-free driver?

Thanks!

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  1. Install the Chromium snap,

     sudo snap install --channel beta/hwacc chromium

  2. Start Chromium,

     snap run chromium

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples.

  4. Enter about:media-internals in the address bar, click the
  corresponding box (if the video is playing, it will have the "(kPlay)"
  identifier) and note what the page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
  - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
  - Distro version (`grep VERSION= /etc/os_release`);
  - GPU (`lscpu`);
  - CPU generation (`lscpu`).

  Currently it seems to work for all reporters on Xorg, but not for all
  reporters on Wayland.

  Just to situate ourselves, beta/hwacc is [1] and I plan to merge it in
  the main snap via [2]. Comments before #176 refer to [3] and _should_
  be roughly equivalent to [1], but I wouldn't be surprised if it turned
  out not to be.

  [1]: 
https://launchpad.net/~nteodosio/+snap/chromium-browser-dev/+build/1875127
  [2]: 
https://code.launchpad.net/~nteodosio/chromium-browser/+git/chromium-browser/+merge/428038
  [3]: 
https://launchpad.net/~nteodosio/+snap/chromium-browser-hwacc/+build/1838168

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1995300] Re: package libice-dev:amd64 2:1.0.10-1build2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

2022-11-04 Thread Marc Deslauriers
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

** Changed in: libice (Ubuntu)
   Status: New => Invalid

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

Title:
  package libice-dev:amd64 2:1.0.10-1build2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in libice package in Ubuntu:
  Invalid

Bug description:
  sorry for my bad english.. i hope you will get what im saying..  i
  tried check my java version and i checked in terminal.. and i get try
  sudo apt install javac some files are missing... after then i
  downloaded 400++ files in terminal.. it automatically downloaded
  archive files then.. in this process... my system get stuck.. lag..
  and then automatically closed my firefox and then... that installing
  terminal .. then i reopened the terminal and.. then.. i tried that
  command again. then the system tell me to try debug package and then i
  tried.. after that.. i get this bug..Once again sorry for my. bad
  english Im from a poor family and im living in India thats the reason
  for it.. I hope you will understand what im trying to say...  and i
  think im using in low pc.. produced by indian government for 2020 12th
  higher secondary school... so that will be the reason for this
  computer.. problem...

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libice-dev:amd64 2:1.0.10-1build2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Mon Oct 31 22:18:38 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DpkgTerminalLog:
   dpkg: error processing package libice-dev:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev ea) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:39f6]
  InstallationDate: Installed on 2022-09-22 (39 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 81FS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=9353f229-cae8-42c4-a405-1dbfcbe64318 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.6
  SourcePackage: libice
  Title: package libice-dev:amd64 2:1.0.10-1build2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2019
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UCN21WW(V1.10.ELCOT.1)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K88286 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo E41-25
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr7UCN21WW(V1.10.ELCOT.1):bd01/23/2019:br1.21:efr1.21:svnLENOVO:pn81FS:pvrLenovoE41-25:rvnLENOVO:rnLNVNB161216:rvrSDK0K88286WIN:cvnLENOVO:ct10:cvrLenovoE41-25:skuLENOVO_MT_81FS_BU_idea_FM_E41-25:
  dmi.product.family: E41-25
  dmi.product.name: 81FS
  dmi.product.sku: LENOVO_MT_81FS_BU_idea_FM_E41-25
  dmi.product.version: Lenovo E41-25
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 

[Desktop-packages] [Bug 1992279] Re: package libreoffice-ogltrans 1:7.3.6-0ubuntu0.22.04.1 failed to install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor

2022-10-27 Thread Marc Deslauriers
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 libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1992279

Title:
  package libreoffice-ogltrans 1:7.3.6-0ubuntu0.22.04.1 failed to
  install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor

Status in libreoffice package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-ogltrans 1:7.3.6-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Oct  8 19:19:11 2022
  ErrorMessage: bağımlılık sorunları - yapılandırılmadan bırakılıyor
  InstallationDate: Installed on 2022-10-08 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: libreoffice
  Title: package libreoffice-ogltrans 1:7.3.6-0ubuntu0.22.04.1 failed to 
install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1992279/+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 1994067] Re: "Windows 11 Pro" and "Ubuntu 22.04.1 LTS" are installed and up to date on the laptop. There is no hardware problem with the laptop. No sound from operating system

2022-10-27 Thread Marc Deslauriers
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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1994067

Title:
  "Windows 11 Pro" and "Ubuntu 22.04.1 LTS" are installed and up to date
  on the laptop. There is no hardware problem with the laptop. No sound
  from operating system "Ubuntu 22.04.1 LTS". But the sound comes from
  the operating system "Windows 11 Pro" without any problems.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  "Windows 11 Pro" and "Ubuntu 22.04.1 LTS" are installed and up to date
  on the laptop. There is no hardware problem with the laptop. No sound
  from operating system "Ubuntu 22.04.1 LTS". But the sound comes from
  the operating system "Windows 11 Pro" without any problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  muhammed   1749 F pulseaudio
   /dev/snd/controlC1:  muhammed   1749 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 24 22:46:37 2022
  InstallationDate: Installed on 2022-10-19 (5 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/28/2021
  dmi.bios.release: 87.176
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: TN1V7.10_Monster
  dmi.board.asset.tag: Board Asset Tag
  dmi.board.name: Huma H5 V3.2
  dmi.board.vendor: Monster
  dmi.board.version: V20
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Monster
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 6.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrTN1V7.10_Monster:bd12/28/2021:br87.176:efr6.6:svnMONSTER:pnHumaH5V3.2:pvrV10:rvnMonster:rnHumaH5V3.2:rvrV20:cvnMonster:ct10:cvrChassisVersion:skuH5V32TN1156MSCD:
  dmi.product.family: HUMA
  dmi.product.name: Huma H5 V3.2
  dmi.product.sku: H5V32TN1156MSCD
  dmi.product.version: V10
  dmi.sys.vendor: MONSTER
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2022-10-24T22:36:17.567999

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1994067/+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 1972654] Re: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable

2022-10-13 Thread Marc Deslauriers
ACK from the security team to sync from unstable.

Please make sure the policy overrides in policykit-desktop-privileges
still work or are converted to their equivalent JS before doing so.

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

Title:
  [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian
  unstable

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable
  for Ubuntu 23.04

  Changelog entries since current kinetic version 0.105-33:
  
https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog

  In particular, see the 0.120-4 changelog entry.

  I am filing a bug for Security Team review.
  Previously, Debian and Ubuntu developers agreed to keep using
  the last version of policykit before it switched to using JavaScript rules.

  But that was years ago. I believe Debian & Ubuntu are the only distros
  to have opted out of the new policykit. It is harder to maintain
  the old style rules when upstream rules use the new format. And it is
  a challenge to backport security and other bugfixes from the new
  series, without making mistakes or missing important details.

  There was a proposal to use duktape instead of mozjs for the JavaScript
  interpreter but I don't think that's been merged yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1983778] Re: Major security issue in Ubuntu Desktop default config - Removable Media

2022-09-23 Thread Marc Deslauriers
I personally don't think the reasons you've listed above are good enough
to change the default setting, but please file a bug with the upstream
project and you can convince them to change them:

https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues

Once you've filed a bug with the GNOME project, please paste the bug
number here.

Thanks!

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

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

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

Title:
  Major security issue in Ubuntu Desktop default config - Removable
  Media

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

Bug description:
  There is a MAJOR SECURITY VULNERABILITY in Ubuntu Desktop since
  release 18.04 !

  Recently I used Ubuntu 22.04 LTS and noticed that the issue still
  exist!

  
  I don’t know the reason for it, but default values for “Removable Media” are 
VERY Risky!
  It will automatically run the software which is attached to the removable 
media.
  Why? Why has Ubuntu still didn’t disable that option?

  
  The following is the default configuration (the “bad” configuration):
  https://imgur.com/XXXQlV2

  The following is the configuration which Ubuntu should be having (it is the 
fix to the problem):
  https://imgur.com/a/0JeM6ve

  Please change the default configurations for Ubuntu!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983778/+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 1988378] Re: Firefox allows a user to alter/delete a third party website cookie

2022-09-16 Thread Marc Deslauriers
Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it
would make more sense to raise your question in the support tracker.
Please visit https://answers.launchpad.net/ubuntu/+addquestion

** Information type changed from Private Security to Public

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

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

Title:
  Firefox allows a user to alter/delete a third party website cookie

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  I was in conflict with a certain technological company. I usually
  browsed their website, downloaded a few PDF files, and contacted with
  them via a Yahoo mail account using the Firefox browser. Some of the
  emails from the company had graphic signatures. At a certain date
  where my contract with the company ended, and I choosed not to renew
  the contract, I wasn't able to access my Yahoo mail account using the
  bookmark, and I had to enter my Yahoo mail password. If the user
  doesn't remember a website's password, this can be unpleasant. I have
  a Yahoo mail account for years, and this never happened to me. It
  looks like the vulnerability is that a developer from company X can
  write code on a website, a PDF file, or linked to an email, that will
  alter/delete a cookie that belongs to website Y.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1988378/+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 1989729] Re: Problem with graphics card

2022-09-16 Thread Marc Deslauriers
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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1989729

Title:
  Problem with graphics card

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,Names Hamdaan. I have installed Ubuntu on my PC about 4-5 days ago.
  At first I didn't seem to notice, But as I used my PC I've been
  noticing that it seems that my PC's graphics card is not working as
  efficient as before. But when I read the driver name I got to know
  that it has not downloaded the correct Driver software , and I don't
  know how to fix that?. Thanks in advance for answering.

  IN CASE YOU NEED IT:
   PC MODEL: Acer Aspire E1-572
   MEMORY  : 4.0 GiB
  PROCESSER: Intel® Core™ i5-4200U CPU @ 1.60GHz × 4
   OS TYPE : 64x

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 15 17:46:25 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Haswell-ULT Integrated Graphics 
Controller [1025:0775]
  InstallationDate: Installed on 2022-09-13 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Aspire E1-572
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=fcb232d7-2139-4cee-b321-7332acc47658 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2014
  dmi.bios.release: 2.17
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.17
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HW
  dmi.board.vendor: Acer
  dmi.board.version: V2.17
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 2.17
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.17:bd09/02/2014:br2.17:efr2.17:svnAcer:pnAspireE1-572:pvrV2.17:rvnAcer:rnEA50_HW:rvrV2.17:cvnAcer:ct10:cvrChassisVersion:skuAspireE1-572_0775_V2.17:
  dmi.product.family: SharkBay System
  dmi.product.name: Aspire E1-572
  dmi.product.sku: Aspire E1-572_0775_V2.17
  dmi.product.version: V2.17
  dmi.sys.vendor: Acer
  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.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/xorg/+bug/1989729/+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 1989953] Re: to update media key session

2022-09-16 Thread Marc Deslauriers
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 chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1989953

Title:
  to update media key session

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  the chromium needs to update the media key session cause it rejected
  the Binge website by playing the movie

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989953/+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 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental

2022-09-12 Thread Marc Deslauriers
I also don't think this is a blocker anymore, as long as polkitd-pkla is
a strong dependency in Ubuntu, so we don't inadvertently stop shipping
it. It would be nice to get a similar list of packages in Ubuntu, as I
suspect we have many more than Debian. We may also need to update the
policykit-desktop-privileges package to ensure it still applies
appropriate policy.

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

Title:
  [security review] Sync policykit-1 0.120-6 (main) from Debian
  experimental

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Please sync policykit-1 0.120-6 (main) from Debian experimental

  Changelog entries since current kinetic version 0.105-33:
  https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6

  In particular, see the 0.120-4 changelog entry.

  I am filing a bug for Security Team review.
  Previously, Debian and Ubuntu developers agreed to keep using
  the last version of policykit before it switched to using JavaScript rules.

  But that was years ago. I believe Debian & Ubuntu are the only distros
  to have opted out of the new policykit. It is harder to maintain
  the old style rules when upstream rules use the new format. And it is
  a challenge to backport security and other bugfixes from the new
  series, without making mistakes or missing important details.

  There was a proposal to use duktape instead of mozjs for the JavaScript
  interpreter but I don't think that's been merged yet.

  It appears the Debian maintainer is considering switching Debian to the
  updated version in time for the next Debian Stable release (so uploading
  to unstable later this year).

  My requested deadline is August 25, Ubuntu 22.10 Feature Freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1930140] Re: GUI "Extract Here" bug - loop until disk is full

2022-08-24 Thread Marc Deslauriers
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 Public Security to Public

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

Title:
  GUI "Extract Here"  bug - loop until disk is full

Status in file-roller package in Ubuntu:
  New

Bug description:
  What happened
  -
  When .rar file is extracted using GUI by right clicking the file and 
selecting "Extract Here", the process continued until the disk is full.

  What I expected
  ---
  Extracting the .rar file without consuming my whole disk. Actual file size 
after extraction is 22-23MB. 

  
  How it got resolved
  ---
  So I installed unrar package using "sudo apt-get install unrar" and the 
problem got resolved. Seems like a bug since the unrar package was not there by 
default and without unrar the process consumes the whole disk.

  OS details are as follows
  
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1930140/+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 1914279] Re: linux from security may force reboots without complete dkms modules

2022-08-24 Thread Marc Deslauriers
** Changed in: openafs (Ubuntu)
   Status: New => Confirmed

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

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Fix Released
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  Confirmed
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently

2022-08-22 Thread Marc Deslauriers
Another issue to consider here is that there is no secure way to display
the information in the first place. If some of those settings are
disabled, malware can simply modify the app to display a green checkbox
next to Level 3, leading to a false sense of security.

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

Title:
  43: New Device Security feature is confusing and unhelpful currently

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

Bug description:
  GNOME 43 added a new Device Security feature in the Settings app.

  You can access it in gnome-control-center 1:43~beta-1ubuntu1
  1. Open the Settings app
  2. Click Privacy then Device Security

  The Security Events aren't clickable.

  A default Ubuntu install only gets us "Security Level 1". The highest
  level is "Security Level 3".

  There isn't anything an Ubuntu user can do to get to a higher security
  level from the Device Security screen.

  If a user attempts to get their system to a higher security level, I
  think they could break their system since this isn't something we
  currently support.

  Therefore, I think we ought to hide/disable the screen for Ubuntu
  22.10. We can work towards better integrating this screen for Ubuntu
  in future releases.

  I'm attaching several screenshots although it's worth trying out the
  feature for yourself too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+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 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently

2022-08-20 Thread Marc Deslauriers
I don't understand not only why those advanced features would be exposed
in a GUI, but why ordinary users would care at all about most of those
settings.

If we're going to expose "security information" to users, we should
probably start by showing basic stuff, like if they are properly getting
security updates, if remote login via ssh is turned on with passwords
instead of certificates, whether they are using disk encryption or not,
etc.

If regular users can't easily fix the issues listed in there, from the
GUI itself, I don't think it's appropriate to display that in the
settings app.

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

Title:
  43: New Device Security feature is confusing and unhelpful currently

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

Bug description:
  GNOME 43 added a new Device Security feature in the Settings app.

  You can access it in gnome-control-center 43~beta-1ubuntu1 by
  1. Open the Settings app
  2. Click Privacy then Device Security

  The Security Events aren't clickable.

  A default Ubuntu install only gets us "Security Level 1". The highest
  level is "Security Level 3".

  There isn't anything an Ubuntu user can do to get to a higher security
  level from the Device Security screen.

  If a user attempts to get their system to a higher security level, I
  think they could break their system since this isn't something we
  currently support.

  Therefore, I think we ought to hide/disable the screen for Ubuntu
  22.10. We can work towards better integrating this screen for Ubuntu
  in future releases.

  I'm attaching several screenshots although it's worth trying out the
  feature for yourself too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

2022-08-09 Thread Marc Deslauriers
** Changed in: gdk-pixbuf (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in gdk-pixbuf source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.

   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer
  limit.

   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.

   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.

   * Any app using gdk-pixbuf is affected, mainly file managers and
  image viewers.

  [Test Plan]

   * Take the POC's - they can be found in the issue in the GNOME repo

   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
   - PCManFM, LXDE's file manager which straight up crashes
   - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app 
still usable, no memory issues)
   - Eye of GNOME (eog) triggers the segfault in syslog
   - Eye of MATE (eom) segfaults

   * If you or the system couldn't tell something is wrong, cat
  /var/log/syslog and enjoy the segfaults or out of memory warnings or
  even kernel spam.

  [Where problems could occur]

   * The patch itself is simple, but since gdk-pixbuf is often used with
  GTK apps a mistake here could be problematic.

   * It is possible, and has happened in the past (which has been
  patched) that other bad GIFs can cause other crashes.

   * That patch is essentially overflow checks -  changes with GLib
  (GNOME's, not to be confused with glibc) and the functions used in not
  only the patch but all of gdk-pixbuf can cause problems

   * Other failures to properly handle GIFs and broken or intentionally
  tampered GIFs can continue and always will open the door for security
  holes for other bugs

  * Again, overall a simple patch but as long as the GIFs remain handled
  properly, and no changes to the GLib functions are made and to other
  apps that use gdk-pixbuf (and assuming are not affected by the change
  and still work), the patch does not have much regression potential.

  [Other Info]

   * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
   * Files attached are examples or crashes
   * Again, all apps using gdk-pixbuf are affected
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190
   * 
https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

2022-08-05 Thread Marc Deslauriers
ACK on the debdiff in comment #5, I am currently building it (with a
slight change to add the bug number to the changelog) and will release
it as a security update next week. Thanks!

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress
Status in gdk-pixbuf source package in Focal:
  New

Bug description:
  [Impact]

   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.

   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer
  limit.

   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.

   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.

   * Any app using gdk-pixbuf is affected, mainly file managers and
  image viewers.

  [Test Plan]

   * Take the POC's - they can be found in the issue in the GNOME repo

   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
   - PCManFM, LXDE's file manager which straight up crashes
   - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app 
still usable, no memory issues)
   - Eye of GNOME (eog) triggers the segfault in syslog
   - Eye of MATE (eom) segfaults

   * If you or the system couldn't tell something is wrong, cat
  /var/log/syslog and enjoy the segfaults or out of memory warnings or
  even kernel spam.

  [Where problems could occur]

   * The patch itself is simple, but since gdk-pixbuf is often used with
  GTK apps a mistake here could be problematic.

   * It is possible, and has happened in the past (which has been
  patched) that other bad GIFs can cause other crashes.

   * That patch is essentially overflow checks -  changes with GLib
  (GNOME's, not to be confused with glibc) and the functions used in not
  only the patch but all of gdk-pixbuf can cause problems

   * Other failures to properly handle GIFs and broken or intentionally
  tampered GIFs can continue and always will open the door for security
  holes for other bugs

  * Again, overall a simple patch but as long as the GIFs remain handled
  properly, and no changes to the GLib functions are made and to other
  apps that use gdk-pixbuf (and assuming are not affected by the change
  and still work), the patch does not have much regression potential.

  [Other Info]

   * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
   * Files attached are examples or crashes
   * Again, all apps using gdk-pixbuf are affected
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190
   * 
https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

2022-07-29 Thread Marc Peña
@seb128 & @nteodosio: is there any more tests to do?
Is there any ETA for this to be released to the latest/* channels?

Thanks!

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  1. Install the snap with

     sudo snap install --channel candidate/hwacc chromium

  2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
  --enable-features=VaapiVideoDecoder

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples

  4. Enter about:media-internals in the address bar and note what the
  page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if 
possible;
  - Distro version (if in doubt, `grep VERSION= /etc/os_release`);
  - GPU (if in doubt, attach the output of `lscpu`);
  - CPU generation (if in doubt, attach the output of `lscpu`).

  About the last point, it may be that unfortunately only those with
  newer generations of Intel CPUs will have luck with this, but it's
  still an uncertainty. So reports are highly welcome.

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

2022-07-09 Thread Marc Peña
I've tested this again with the updated instructions:
$ sudo snap refresh --channel candidate/hwacc chromium
$ snap run chromium --disable-features=UseChromeOSDirectVideoDecoder 
--enable-features=VaapiVideoDecoder

And it also worked OK.

The only thing is that I'm seeing the following warnings and error in
the console:

Warning: /usr/lib/x86_64-linux-gnu/libvulkan_intel.so: cannot open shared 
object file: No such file or directory
Warning: loader_icd_scan: Failed loading library associated with ICD JSON 
/usr/lib/x86_64-linux-gnu/libvulkan_intel.so.Ignoring this JSON
Warning: /usr/lib/x86_64-linux-gnu/libvulkan_lvp.so: cannot open shared object 
file: No such file or directory
Warning: loader_icd_scan: Failed loading library associated with ICD JSON 
/usr/lib/x86_64-linux-gnu/libvulkan_lvp.so.Ignoring this JSON
Warning: /usr/lib/x86_64-linux-gnu/libvulkan_radeon.so: cannot open shared 
object file: No such file or directory
Warning: loader_icd_scan: Failed loading library associated with ICD JSON 
/usr/lib/x86_64-linux-gnu/libvulkan_radeon.so.Ignoring this JSON
Warning: vkCreateInstance: Found no drivers!
Error: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
at CheckVkSuccessImpl 
(../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)
at CreateVkInstance 
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:387)
at Initialize 
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:263)
at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:193)
at operator() 
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:462)

Here is the required info:
- Video used: big-buck-bunny-1080p-30sec.mp4
- kVideoDecoderName: "VDAVideoDecoder"
- Distro: Ubuntu 20.04
- GPU: HD Graphics 620
- CPU: Intel Core i7-7500U

Thanks!

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  1. Install the snap with

     sudo snap install --channel candidate/hwacc chromium

  2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
  --enable-features=VaapiVideoDecoder

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples

  4. Enter about:media-internals in the address bar and note what the
  page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if 
possible;
  - Distro version (if in doubt, `grep VERSION= /etc/os_release`);
  - GPU (if in doubt, attach the output of `lscpu`);
  - CPU generation (if in doubt, attach the output of `lscpu`).

  About the last point, it may be that unfortunately only those with
  newer generations of Intel CPUs will have luck with this, but it's
  still an uncertainty. So reports are highly welcome.

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1977968] [NEW] Security update tracking bug

2022-06-08 Thread Marc Deslauriers
*** This bug is a security vulnerability ***

Public security bug reported:

This bug is to track the security update that will contain these
possibly security-relevant commits:

https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=e2b0f0d8d63e1223bb714a9efb37e2257818268b

https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=7a80d2096f1b7125085e21448112aa02f49f5e9a

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

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

Title:
  Security update tracking bug

Status in bluez package in Ubuntu:
  New

Bug description:
  This bug is to track the security update that will contain these
  possibly security-relevant commits:

  
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=e2b0f0d8d63e1223bb714a9efb37e2257818268b

  
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=7a80d2096f1b7125085e21448112aa02f49f5e9a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1977968/+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 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental

2022-06-06 Thread Marc Deslauriers
My understanding is the Debian experimental version doesn't support both
at the same time, it's one or the other depending on which binary
package you install. We definitely don't want that.

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

Title:
  [security review] Sync policykit-1 0.120-6 (main) from Debian
  experimental

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Please sync policykit-1 0.120-6 (main) from Debian experimental

  Changelog entries since current kinetic version 0.105-33:
  https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6

  In particular, see the 0.120-4 changelog entry.

  I am filing a bug for Security Team review.
  Previously, Debian and Ubuntu developers agreed to keep using
  the last version of policykit before it switched to using JavaScript rules.

  But that was years ago. I believe Debian & Ubuntu are the only distros
  to have opted out of the new policykit. It is harder to maintain
  the old style rules when upstream rules use the new format. And it is
  a challenge to backport security and other bugfixes from the new
  series, without making mistakes or missing important details.

  There was a proposal to use duktape instead of mozjs for the JavaScript
  interpreter but I don't think that's been merged yet.

  It appears the Debian maintainer is considering switching Debian to the
  updated version in time for the next Debian Stable release (so uploading
  to unstable later this year).

  My requested deadline is August 25, Ubuntu 22.10 Feature Freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1975602] Re: 2.36.2 security update tracking bug

2022-05-24 Thread Marc Deslauriers
** Changed in: webkit2gtk (Ubuntu)
   Status: New => Fix Released

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

Title:
  2.36.2 security update tracking bug

Status in webkit2gtk package in Ubuntu:
  Fix Released

Bug description:
  Bug to track the 2.36.2 security update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1975602/+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 1975602] [NEW] 2.36.2 security update tracking bug

2022-05-24 Thread Marc Deslauriers
*** This bug is a security vulnerability ***

Public security bug reported:

Bug to track the 2.36.2 security update.

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

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

Title:
  2.36.2 security update tracking bug

Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  Bug to track the 2.36.2 security update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1975602/+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 1974250] Re: ~/.pam_environment gets created as owned by root

2022-05-24 Thread Marc Deslauriers
** Information type changed from Private Security to Public Security

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

** Also affects: accountsservice (Ubuntu Kinetic)
   Importance: High
   Status: Fix Released

** Changed in: accountsservice (Ubuntu Jammy)
   Status: New => Fix Released

** Changed in: accountsservice (Ubuntu Kinetic)
   Status: Fix Released => Confirmed

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

Title:
  ~/.pam_environment gets created as owned by root

Status in accountsservice package in Ubuntu:
  Confirmed
Status in accountsservice source package in Jammy:
  Fix Released
Status in accountsservice source package in Kinetic:
  Confirmed

Bug description:
  Something has happened lately with accountsservice, which makes it act
  as root instead of the current user when creating ~/.pam_environment.
  The very old bug #904395 comes to mind, and this smells a security
  issue.

  The function which is supposed to prevent this behavior is here:

  https://salsa.debian.org/freedesktop-
  team/accountsservice/-/blob/ubuntu/debian/patches/0010-set-
  language.patch#L75

  Haven't investigated further yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1974250/+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 1971415] Re: Remote desktop is automatically enabled after login

2022-05-18 Thread Marc Deslauriers
This patch is still broken. The same thing happens with VNC:

1- Turn on remote desktop, turn on VNC.
2- Only turn off remote desktop while leaving VNC checked
3- Reboot
4- The VNC port is listening to connections even though remote desktop says off 
in the control center.

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

Title:
  Remote desktop is automatically enabled after login

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Jammy:
  Confirmed

Bug description:
  Details:
  Turning off RDP Remote Desktop Sharing with gnome-control-center would only 
turn off RDP sharing for the current session. Upon logging back in, RDP Sharing 
would be enabled again without any additional user interaction or notification.

  Other Info:
  As mentioned in the comments at 
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1825
  this issue could have been avoided if Ubuntu's gnome-remote-desktop didn't 
keep the systemd user service always running. I do intend to fix that issue 
also but it is a more complicated fix. I think it will require a maintainer 
script to remove the automatic conffiles added by dh. I will do the 
gnome-remote-desktop bugfix as a normal non-security SRU.

  Original Bug Report:
  If I disable sharing/remote desktop in GNOME Control Center, then log out and 
back in, it is automatically enabled again. I report this as a security 
vulnerability because remote desktop is enabled without the user's knowledge.

  Software versions:
  - Ubuntu 22.04
  - gnome-remote-desktop 42.0-4ubuntu1
  - gnome-control-center 1:41.4-1ubuntu13

  Steps to reproduce:
  1. Start with Remote Desktop enabled. "systemctl --user status 
gnome-remote-desktop.service" reports "active (running)".
  2. Disable Remote Desktop in Control Center. systemctl reports "inactive 
(dead)".
  3. Log out and back in.
  4. Open Control Center. Remote Desktop is enabled again. systemctl reports 
"active (running)".

  Expected behavior:
  Remote Desktop should stay disabled upon the new login.

  Actual behavior:
  Remote Desktop was automatically enabled again.

  Previous discussion: https://gitlab.gnome.org/GNOME/gnome-control-
  center/-/issues/1775#note_1443319

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1971415/+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 1967626] Re: 22.04 beta Network Manager still sets wrong IPv6 routing

2022-05-11 Thread Marc Deslauriers
** Bug watch added: 
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #840
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/840

** Also affects: network-manager via
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/840
   Importance: Unknown
   Status: Unknown

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

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

Title:
  22.04 beta Network Manager still sets wrong IPv6 routing

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  that's a bug I've already reported earlier both to ubuntu and network-
  manager upstream, and nobody seems to care about.

  I'm using an AVM FritzBox, a router family very common in Germany and
  Europe for DSL and DOCSIS, but saw reports of people confirming the
  problem with other routers.

  The router sends ICMPv6 router advertisements, which contain for both
  the configured site-local address and the provider-assigned world-
  routable address range both a

  * prefix information 
  * router advertisement on itself

  All other OS and machines I have, including

  * Debian
  * Ubuntu Server
  * Ubuntu Core
  * Raspberry Pi OS
  * Other Linuxes
  * MacOS
  *...

  correctly set a link route on the network device for both the official
  and the site local address.

  Only Ubuntu Desktop machines with that damned Network Manager set a
  route to the router instead of a link route.

  The consequence is, that IPv6 still works, but significantly to slow,
  since packages are not switched on the network switch, but routed on
  the router, which dramatically decreases speed.

  
  I've reported this upstream to Network Manager, see the discussion on 

  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/840

  but they do not even seem to understand the issue (Network Manager
  written by people not really understanding routing...)

  Their point of view is that the router will fix things by sending
  redirects. However, ICMPv6 redirects are considered a security problem
  and usually recommended to be turned off.

  The answer from NetworkManager developers is to fix the router, not
  the Network Manager to stop sending router advertisings, but can't
  explain why all other OS and other Linux distributions, including
  Ubuntu server and Ubuntu core do it correctly, and just NM doing it
  wrong.

  So Ubuntu/NetworkManagers unability to fix or even notice this
  essential problem forces people to either accept terribly slow IPv6
  traffic in local networks, or to leave the machine open for ICMPv6
  redirects, which, in general, is a security flaw and vulnerable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1967626/+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 1969593] Re: rules to prevent non-root users from rebooting not taken into account

2022-05-11 Thread Marc Deslauriers
Great, thanks!

** Changed in: policykit-1 (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  rules to prevent non-root users from rebooting not taken into account

Status in policykit-1 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  On fresh Ubuntu Jammy installation, I add a 
"/etc/polkit-1/localauthority/90-mandatory.d/restriction.pkla" file with the 
following contents :
  [Disable power-off]
  Identity=unix-user:*
  Action=org.freedesktop.login1.power-off
  ResultActive=no
  ResultInactive=no
  ResultAny=no

  [Disable power-off when others are logged in]
  Identity=unix-user:*
  Action=org.freedesktop.login1.power-off-multiple-sessions
  ResultActive=no
  ResultInactive=no
  ResultAny=no

  [Disable_reboot]
  Identity=unix-user:*
  Action=org.freedesktop.login1.reboot
  ResultActive=no
  ResultInactive=no
  ResultAny=no

  [Disable_reboot_when_others_are_logged_in]
  Identity=unix-user:*
  Action=org.freedesktop.login1.reboot-multiple-sessions
  ResultActive=no
  ResultInactive=no
  ResultAny=no


  
  It must prevent non-root users from shutdowning and rebooting the system. But 
it only prevent shutdowning. Rebooting is still possible for a non-root user.

  We can see it using pkcheck command (as a non-root user) :
  $ pkcheck --action-id org.freedesktop.login1.power-off --process $PPID ; echo 
$?
  Not authorized.
  1
  $ pkcheck --action-id org.freedesktop.login1.reboot --process $PPID ; echo $?
  0

  
  As this problem can lead to unexpected reboot on multi-users systems (a 
disponibilty concern), I checked the "This bug is a security vulnerability" box.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: policykit-1 0.105-33
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 10:53:27 2022
  InstallationDate: Installed on 2022-04-20 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1969593/+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 1969593] Re: rules to prevent non-root users from rebooting not taken into account

2022-05-10 Thread Marc Deslauriers
I'm setting the status of this bug as "incomplete". Please let us know
if that solved the problem for you or not. Thanks!

** Changed in: policykit-1 (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  rules to prevent non-root users from rebooting not taken into account

Status in policykit-1 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  On fresh Ubuntu Jammy installation, I add a 
"/etc/polkit-1/localauthority/90-mandatory.d/restriction.pkla" file with the 
following contents :
  [Disable power-off]
  Identity=unix-user:*
  Action=org.freedesktop.login1.power-off
  ResultActive=no
  ResultInactive=no
  ResultAny=no

  [Disable power-off when others are logged in]
  Identity=unix-user:*
  Action=org.freedesktop.login1.power-off-multiple-sessions
  ResultActive=no
  ResultInactive=no
  ResultAny=no

  [Disable_reboot]
  Identity=unix-user:*
  Action=org.freedesktop.login1.reboot
  ResultActive=no
  ResultInactive=no
  ResultAny=no

  [Disable_reboot_when_others_are_logged_in]
  Identity=unix-user:*
  Action=org.freedesktop.login1.reboot-multiple-sessions
  ResultActive=no
  ResultInactive=no
  ResultAny=no


  
  It must prevent non-root users from shutdowning and rebooting the system. But 
it only prevent shutdowning. Rebooting is still possible for a non-root user.

  We can see it using pkcheck command (as a non-root user) :
  $ pkcheck --action-id org.freedesktop.login1.power-off --process $PPID ; echo 
$?
  Not authorized.
  1
  $ pkcheck --action-id org.freedesktop.login1.reboot --process $PPID ; echo $?
  0

  
  As this problem can lead to unexpected reboot on multi-users systems (a 
disponibilty concern), I checked the "This bug is a security vulnerability" box.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: policykit-1 0.105-33
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 10:53:27 2022
  InstallationDate: Installed on 2022-04-20 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1969593/+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 1969593] Re: rules to prevent non-root users from rebooting not taken into account

2022-05-10 Thread Marc Deslauriers
Systemd has a bunch of "imply" rules on other actionstry adding the
following:

[Disable more reboot actions]
Identity=unix-user:*
Action=org.freedesktop.login1.reboot-ignore-inhibit;org.freedesktop.login1.set-reboot-*
ResultActive=no
ResultInactive=no
ResultAny=no

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

Title:
  rules to prevent non-root users from rebooting not taken into account

Status in policykit-1 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  On fresh Ubuntu Jammy installation, I add a 
"/etc/polkit-1/localauthority/90-mandatory.d/restriction.pkla" file with the 
following contents :
  [Disable power-off]
  Identity=unix-user:*
  Action=org.freedesktop.login1.power-off
  ResultActive=no
  ResultInactive=no
  ResultAny=no

  [Disable power-off when others are logged in]
  Identity=unix-user:*
  Action=org.freedesktop.login1.power-off-multiple-sessions
  ResultActive=no
  ResultInactive=no
  ResultAny=no

  [Disable_reboot]
  Identity=unix-user:*
  Action=org.freedesktop.login1.reboot
  ResultActive=no
  ResultInactive=no
  ResultAny=no

  [Disable_reboot_when_others_are_logged_in]
  Identity=unix-user:*
  Action=org.freedesktop.login1.reboot-multiple-sessions
  ResultActive=no
  ResultInactive=no
  ResultAny=no


  
  It must prevent non-root users from shutdowning and rebooting the system. But 
it only prevent shutdowning. Rebooting is still possible for a non-root user.

  We can see it using pkcheck command (as a non-root user) :
  $ pkcheck --action-id org.freedesktop.login1.power-off --process $PPID ; echo 
$?
  Not authorized.
  1
  $ pkcheck --action-id org.freedesktop.login1.reboot --process $PPID ; echo $?
  0

  
  As this problem can lead to unexpected reboot on multi-users systems (a 
disponibilty concern), I checked the "This bug is a security vulnerability" box.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: policykit-1 0.105-33
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 10:53:27 2022
  InstallationDate: Installed on 2022-04-20 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1969593/+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 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental

2022-05-09 Thread Marc Deslauriers
We do not want policykit to use the unmaintainable mozjs backend. That
would be a hard NACK from the Security Team.

The duktape backend has been merged upstream. So in order to sync this
to Ubuntu, the following must be done:

1- Get Debian to switch to the duktape backend
2- Get Debian to transition all packages in the archive from PKLA policy files 
to JS policy files
3- Transition Ubuntu packages not in Debian from PKLA policy files to JS policy 
files
4- Investigate Snap policykit support, and if required, transition Snaps from 
PKLA policy files to JS policy files.

Once the transition has been done for all software, policykit can be
switched to the duktape policykit backend by syncing the package from
Debian. Hopefully at that point it will be in Unstable, and not in
experimental.

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

Title:
  [security review] Sync policykit-1 0.120-6 (main) from Debian
  experimental

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Please sync policykit-1 0.120-6 (main) from Debian experimental

  Changelog entries since current kinetic version 0.105-33:
  https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6

  In particular, see the 0.120-4 changelog entry.

  I am filing a bug for Security Team review.
  Previously, Debian and Ubuntu developers agreed to keep using
  the last version of policykit before it switched to using JavaScript rules.

  But that was years ago. I believe Debian & Ubuntu are the only distros
  to have opted out of the new policykit. It is harder to maintain
  the old style rules when upstream rules use the new format. And it is
  a challenge to backport security and other bugfixes from the new
  series, without making mistakes or missing important details.

  There was a proposal to use duktape instead of mozjs for the JavaScript
  interpreter but I don't think that's been merged yet.

  It appears the Debian maintainer is considering switching Debian to the
  updated version in time for the next Debian Stable release (so uploading
  to unstable later this year).

  My requested deadline is August 25, Ubuntu 22.10 Feature Freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf

2022-05-01 Thread Marc H.
I have the same issue on Windows 11, Chrome/Edge freezing for about 3-4
seconds when you save any file to disk. This started a few days ago.

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

Title:
  Brave & Chrome browsers freezes on download and print to pdf

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Whenever any file is downloaded, the browser will freeze.

  Similarly, the browser will freeze when a page is printed to pdf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1971058] [NEW] package yaru-theme-gnome-shell 21.10.2 failed to install/upgrade: new yaru-theme-gnome-shell package pre-installation script subprocess returned error exit statu

2022-04-30 Thread Marc Cabana
Public bug reported:

Can't install do-release-upgrade

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: yaru-theme-gnome-shell 21.10.2
ProcVersionSignature: Ubuntu 5.13.0-40.45-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu71.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sat Apr 30 18:40:19 2022
Dependencies:
 
ErrorMessage: new yaru-theme-gnome-shell package pre-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2021-03-27 (399 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123)
PackageArchitecture: all
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.20.9ubuntu2
 apt  2.3.9
SourcePackage: yaru-theme
Title: package yaru-theme-gnome-shell 21.10.2 failed to install/upgrade: new 
yaru-theme-gnome-shell package pre-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to impish on 2022-04-30 (0 days ago)

** Affects: yaru-theme (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package yaru-theme-gnome-shell 21.10.2 failed to install/upgrade: new
  yaru-theme-gnome-shell package pre-installation script subprocess
  returned error exit status 1

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  Can't install do-release-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: yaru-theme-gnome-shell 21.10.2
  ProcVersionSignature: Ubuntu 5.13.0-40.45-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Apr 30 18:40:19 2022
  Dependencies:
   
  ErrorMessage: new yaru-theme-gnome-shell package pre-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-03-27 (399 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.9
  SourcePackage: yaru-theme
  Title: package yaru-theme-gnome-shell 21.10.2 failed to install/upgrade: new 
yaru-theme-gnome-shell package pre-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to impish on 2022-04-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1971058/+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 1971001] Re: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal, Impish and Jammy

2022-04-30 Thread Marc Deslauriers
** Changed in: tiff (Ubuntu)
   Status: New => Confirmed

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

Title:
  Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal, Impish and
  Jammy

Status in tiff package in Ubuntu:
  Confirmed

Bug description:
  The versions in Trusty, Xenial, Bionic, Focal and Impish may be
  vulnerable to all CVEs below.

  The version in Jammy is vulnerable to CVE-2022-0865.

  Debian released an advisory on March 24.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1971001/+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 1970783] Re: Multiple vulnerabilities in Bionic

2022-04-29 Thread Marc Deslauriers
We are no longer able to update webkit2gtk in bionic as it has new
toolchain requirements that can't be met. See:

https://wiki.ubuntu.com/SecurityTeam/FAQ#WebKitGTK

** Changed in: webkit2gtk (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  Multiple vulnerabilities in Bionic

Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  The version in Bionic has multiple vulnerabilities.

  Please backport version 2.36.0 or at least the security fixes in that
  version.

  Upstream and Debian have released advisories on April 8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1970783/+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 1969932] Re: Security issue in Ghostscript 9.26 due to missing patch

2022-04-25 Thread Marc Deslauriers
Thanks for filing the upstream bug, I am making this bug public since
the commits are public and the issue is fixed in later releases. Thanks!

** Information type changed from Private Security to Public Security

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

Title:
  Security issue in Ghostscript 9.26 due to missing patch

Status in ghostscript package in Ubuntu:
  New

Bug description:
  I'm a German security researcher and submitted a report via HackerOne
  to Yahoo, they encouraged me to notify you directly regarding this
  issue. As it turned out, older Ubuntu LTS versions are affected:

  - ghostscript_9.26~dfsg+0-0ubuntu0.18.04.15 (Bionic Beaver)
  - ghostscript_9.26~dfsg+0-0ubuntu0.16.04.14 (Xenial Xerus)
  - ghostscript_9.26~dfsg+0-0ubuntu0.14.04.8 (Trusty Tahr)

  The issue is caused by a missing patch from 2019 [1], a variant of
  CVE-2019-6116, which can lead to a -dSAFER bypass (i.e., a malicious
  PostScript/EPS file can potentially execute arbitrary shell commands).
  Jammy Jellyfish, Impish Indri, and Focal Fossa are *not* affected.

  *Countermeasures:* Make sure to apply this patch [1] to the older LTS
  versions (14/16/18).

  [1] https://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=430e2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1969932/+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 1970121] Re: sharing enabled by default on 22.04

2022-04-24 Thread Marc Deslauriers
*** This bug is a duplicate of bug 1969619 ***
https://bugs.launchpad.net/bugs/1969619

** This bug has been marked a duplicate of bug 1969619
   RDP Sharing appears on by default in jammy

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

Title:
  sharing enabled by default on 22.04

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

Bug description:
  After install and first boot, sharing is enabled by default in Ubuntu
  22.04. It should be disabled initially. I used the minimal install
  function and it seems to be related to gnome-remote-desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970121/+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 1964724] Re: the laptop is slowing down I suspect the graphics

2022-03-30 Thread Marc Deslauriers
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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1964724

Title:
  the laptop is slowing down I suspect the graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  I am sure that the video driver does not work because it is very
  stupid

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-36.41~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 14 01:26:27 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:081b]
  InstallationDate: Installed on 2022-03-11 (2 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Acer Aspire V5-132P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-36-generic 
root=UUID=3ed9b8cd-2125-43f4-af3a-b14a5314ae6e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 07/19/2013
  dmi.bios.release: 2.4
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.04
  dmi.board.name: Angel_CY
  dmi.board.vendor: Acer
  dmi.board.version: V2.04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.04
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.04:bd07/19/2013:br2.4:efr1.5:svnAcer:pnAspireV5-132P:pvrV2.04:rvnAcer:rnAngel_CY:rvrV2.04:cvnAcer:ct9:cvrV2.04:skuAspireV5-132P_081B_2.04:
  dmi.product.family: Aspire V5-132P
  dmi.product.name: Aspire V5-132P
  dmi.product.sku: Aspire V5-132P_081B_2.04
  dmi.product.version: V2.04
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110+git2203100500.7c28f5~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.1~git2203130600.177805~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1964724/+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 1964795] Re: gnome-keyring-daemon crashed with signal 7

2022-03-30 Thread Marc Deslauriers
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 gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1964795

Title:
  gnome-keyring-daemon crashed with signal 7

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  gnome-keyring:
Installed: 40.0-3ubuntu1
Candidate: 40.0-3ubuntu1
Version table:
   *** 40.0-3ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
  100 /var/lib/dpkg/status

  Background process crashes unexpectedly a few moments after login.

  I'm running the dev release of Jammy on a Raspberry Pi 400 with all
  updates applied.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-keyring 40.0-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19
  Uname: Linux 5.15.0-1003-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Mon Mar 14 15:26:41 2022
  Disassembly: => 0x:   Cannot access memory at address 0x
  ExecutablePath: /usr/bin/gnome-keyring-daemon
  ImageMediaBuild: 20201022
  ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  Signal: 7
  SourcePackage: gnome-keyring
  StacktraceTop:
   ()
   ()
   () at /lib/aarch64-linux-gnu/libgio-2.0.so.0
   g_signal_emit_valist () at /lib/aarch64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () at /lib/aarch64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-keyring-daemon crashed with signal 7
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (6 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1964795/+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 1965114] Re: computer errs

2022-03-30 Thread Marc Deslauriers
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

** Changed in: xorg (Ubuntu)
   Status: New => Invalid

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

Title:
  computer errs

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  OS  performs  errors

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174
  Uname: Linux 5.4.0-105-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Mar 16 15:41:52 2022
  DistUpgraded: 2022-02-14 15:26:03,689 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad X240 [17aa:2214]
  InstallationDate: Installed on 2021-01-14 (425 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20AMCTO1WW
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-105-generic 
root=UUID=fb3eedbf-03ca-48cd-b4f6-ab7e0a3a9af6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2022-02-14 (30 days ago)
  dmi.bios.date: 08/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET76WW (2.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AMCTO1WW
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:svnLENOVO:pn20AMCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20AMCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X240
  dmi.product.name: 20AMCTO1WW
  dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
  dmi.product.version: ThinkPad X240
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Thu Sep 30 14:17:53 2021
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1965114/+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 1965686] Re: After the laptop comes out of sleep mode, the desktop environment for some reason breaks and appears crashes window

2022-03-30 Thread Marc Deslauriers
** 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1965686

Title:
  After the laptop comes out of sleep mode, the desktop environment for
  some reason breaks and appears crashes window

Status in gnome-shell package in Ubuntu:
  New

Bug description:

  I've been running Ubuntu 20.04 for about a month now. Lock screen is
  crashing the UI in 20.04.

  I don't know how to stop crashing my screen so I forcefully press
  power off button and turn on again my computer every time I use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 20 22:26:56 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-18 (61 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965686/+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 1965869] Re: Screen only partially locked. Password promt was visible, but switching to window and typing eg in terminal was possible

2022-03-30 Thread Marc Deslauriers
** Package changed: ubuntu => gnome-shell (Ubuntu)

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

Title:
  Screen only partially locked. Password promt was visible, but
  switching to window and typing eg in terminal was possible

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Today I returned to my PC, which was on over night.

  The screen was only partially locked. The password prompt was full
  screen except the start menu on the left was visible. I was able to
  click on the Icons of running applications and was able to type in an
  open terminal which responded correctly and executed the commands (I
  tried "reset").

  I have no Idea what can cause this issue and would appreciate help on
  how to gather information that can help the Ubuntu team find the cause
  of the issue.

  I saved copies of dmesg, syslog and kern.log.
  I have not tried reproducing the bug.
  I do not know if I actively locked the screen or if I just walked off 
yesterday.

  Best Regards,
  Chris

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 22 08:16:18 2022
  InstallationDate: Installed on 2021-12-13 (98 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965869/+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 1966572] Re: Chromium Zero Day

2022-03-30 Thread Marc Deslauriers
This is published now:

https://ubuntu.com/security/notices/USN-5350-1

** Changed in: chromium-browser (Ubuntu)
   Status: New => Fix Released

** Information type changed from Private Security to Public Security

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

Title:
  Chromium Zero Day

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Please see: https://chromereleases.googleblog.com/2022/03/stable-
  channel-update-for-desktop_25.html

  Apparently this also affects the Chromium package and is being
  actively exploited in the wild:

  > [$TBD][1309225] High CVE-2022-1096: Type Confusion in V8. Reported
  by anonymous on 2022-03-23

  Please update from Version 97.0.4692.20 (last updated 2021-11-26) to
  latest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1966572/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

2022-03-10 Thread Marc Peña
Hi again! @Olivier, maybe I'm a bit lost, but don't we need "use_vaapi =
true" in the GN arguments?
https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/gpu/vaapi.md#vaapi-
on-linux

I don't see it set here: https://git.launchpad.net/~chromium-
team/chromium-browser/+git/snap-from-source/tree/build/args.gn?h=stable

Or maybe is it set by default since 2020?
https://chromium.googlesource.com/chromium/src.git/+/d658439002fc9bc6b4deeec71738600402ea9742

Sorry for the noise if that's the case!

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency

2022-03-09 Thread Marc Deslauriers
Thanks!

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

Title:
  focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically
  installed due to new dependency

Status in webkit2gtk package in Ubuntu:
  Fix Released

Bug description:
  Version: 2.34.6-0ubuntu0.20.04.1

  This security update for focal does not seem to be automatically
  upgradeable by unattended-upgrades:

  2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but 
fails to be marked for upgrade (E:Unable to correct problems, you have held 
broken packages.)
  2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but 
fails to be marked for upgrade (E:Unable to correct problems, you have held 
broken packages.)
  2022-03-05 14:32:38,031 INFO No packages found that can be upgraded 
unattended and no pending auto-removals
  2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back 
because a related package is kept back or due to local apt_preferences(5).
  2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back 
because a related package is kept back or due to local apt_preferences(5).

  apt-mark showhold lists no held packages, and there are no
  apt_preferences set. The actual cause seems to be an extra dependency
  on libopengl0 which has been added with the upgrade. Is this
  intentional?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
  Uname: Linux 5.4.0-100-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Mar  5 14:39:24 2022
  InstallationDate: Installed on 2018-06-15 (1358 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: webkit2gtk
  UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1963751/+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 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency

2022-03-08 Thread Marc Deslauriers
** Package changed: unattended-upgrades (Ubuntu) => webkit2gtk (Ubuntu)

** Changed in: webkit2gtk (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically
  installed due to new dependency

Status in webkit2gtk package in Ubuntu:
  Fix Released

Bug description:
  Version: 2.34.6-0ubuntu0.20.04.1

  This security update for focal does not seem to be automatically
  upgradeable by unattended-upgrades:

  2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but 
fails to be marked for upgrade (E:Unable to correct problems, you have held 
broken packages.)
  2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but 
fails to be marked for upgrade (E:Unable to correct problems, you have held 
broken packages.)
  2022-03-05 14:32:38,031 INFO No packages found that can be upgraded 
unattended and no pending auto-removals
  2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back 
because a related package is kept back or due to local apt_preferences(5).
  2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back 
because a related package is kept back or due to local apt_preferences(5).

  apt-mark showhold lists no held packages, and there are no
  apt_preferences set. The actual cause seems to be an extra dependency
  on libopengl0 which has been added with the upgrade. Is this
  intentional?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
  Uname: Linux 5.4.0-100-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Mar  5 14:39:24 2022
  InstallationDate: Installed on 2018-06-15 (1358 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: webkit2gtk
  UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1963751/+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 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency

2022-03-07 Thread Marc Deslauriers
The new dependency on libopengl0 is expected. The new version of
WebKitGTK fixed opengl detection and the new dependency is now required.

I am going to re-assign this bug to unattended-upgrades. If it's not
willing to install new dependencies, it definitely should get fixed as
some security updates will always get held back.

** Package changed: webkit2gtk (Ubuntu) => unattended-upgrades (Ubuntu)

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

Title:
  focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically
  installed due to new dependency

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Version: 2.34.6-0ubuntu0.20.04.1

  This security update for focal does not seem to be automatically
  upgradeable by unattended-upgrades:

  2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but 
fails to be marked for upgrade (E:Unable to correct problems, you have held 
broken packages.)
  2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but 
fails to be marked for upgrade (E:Unable to correct problems, you have held 
broken packages.)
  2022-03-05 14:32:38,031 INFO No packages found that can be upgraded 
unattended and no pending auto-removals
  2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back 
because a related package is kept back or due to local apt_preferences(5).
  2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back 
because a related package is kept back or due to local apt_preferences(5).

  apt-mark showhold lists no held packages, and there are no
  apt_preferences set. The actual cause seems to be an extra dependency
  on libopengl0 which has been added with the upgrade. Is this
  intentional?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
  Uname: Linux 5.4.0-100-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Mar  5 14:39:24 2022
  InstallationDate: Installed on 2018-06-15 (1358 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: webkit2gtk
  UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago)

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


  1   2   3   4   5   6   7   8   9   10   >