[Desktop-packages] [Bug 1972048] Re: gjs open a window and did't close using the UI

2022-07-08 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  gjs open a window and did't close using the UI

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  gjs open a window and did't close using the UI

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  7 08:30:34 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-18 (50 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1972048/+subscriptions


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


[Desktop-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container

2022-07-08 Thread Mario Limonciello
One possible solution is to split the fwupd package along it's possible plugins 
into multiple packages.
However I tend to agree that it has no use in a cloud or container seed.

I also agree libmm-glib0 shouldn't recommend modem manager.

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

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

Title:
  server image pulls in ModemManager via fwupd, consumes 25MiB RAM in
  every container

Status in fwupd package in Ubuntu:
  Invalid
Status in modemmanager package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Looking at memory utilization in a pristine Ubuntu lxd container (top
  -o RES), I see that ModemManager is running, which I was surprised to
  see is present at all in the stock image.

  Tracking this I find that fwupd depends on libmm-glib0, which in turn
  Recommends: modemmanager.

  Libraries in general should not recommend daemons, so it's possible
  this should be fixed by libmm-glib0 dropping this Recommends.  It
  certainly doesn't seem to be a deliberate decision by the Server Team
  to have modemmanager installed and running by default on all systems.

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


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


[Desktop-packages] [Bug 1980908] Re: duplicity does NOT close properly

2022-07-08 Thread Teh Kok How
Not an "active" process! Backup completed, open up DejaDup GUI Restore
tab to view the content and saw this error!

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

Title:
  duplicity does NOT close properly

Status in Déjà Dup:
  Incomplete
Status in Duplicity:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  Duplicity process stays running after closing deja-dup backups app
  from Ubuntu desktop. Openning up deja-dup again, go to Restore tab,
  error message shows "Another duplicity instance is already running
  with this archive directory". `ps -ef | grep duplicity` shows the
  process still running.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1980908/+subscriptions


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


[Desktop-packages] [Bug 1980239] Re: Update gstreamer to 1.20.3

2022-07-08 Thread Steve Langasek
> For the first time, I made failures in the build tests for most of gstreamer
> fail the build for amd64 & arm64. I did this to try to better comply
> with the SRU guidelines. 

I appreciate this; it's not required by any means but it is a welcome
improvement.

> There is longstanding precedent for gstreamer microreleases to be
> accepted as SRUs and I don't think those have claimed they were being
> done as a GNOME dependency.

This, however, is not persuasive to me.  I don't consider "precedent" to
be a reason not to follow the SRU procedure.  If the other SRU team
members who accepted those SRUs want to explain why they think an
exception should be made here, that's fine, and then we can document it
for the future.  Without having talked to them first, however, my
/suspicion/ is that they were regarding this as covered by the GNOME
exception because of the difficulty we've had pinning down what is or
isn't meant to be covered by it.

> I think this gstreamer-editing-services-1.0 update is worth a
> microrelease SRU. I would need to beg upstream for a test case
> since they didn't provide enough details in their commit messages
> & merge proposals.

That seems reasonable - please do get a test case for it.

> I am ok with gst-python1.0 being rejected since the change is
unimportant.

Ok, I'll go ahead and do that.

> Gstreamer has a solid record of stability

I find I have to balance this against the fact that they have explicitly
partitioned the codec drivers upstream into different levels of support,
and the ones we're talking about here are not part of the GNOME core.

> Is that acceptable or should we do another upload cherrypicking
> the one fix we really care about?

Given that there are no test cases and the possible effects of the
changes are not obvious, please cherry-pick the one fix in order to get
this through into .1.

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

Title:
  Update gstreamer to 1.20.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Jammy:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Jammy:
  Fix Committed
Status in gst-plugins-good1.0 source package in Jammy:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Jammy:
  In Progress
Status in gst-python1.0 source package in Jammy:
  Incomplete
Status in gst-rtsp-server1.0 source package in Jammy:
  In Progress
Status in gstreamer-editing-services1.0 source package in Jammy:
  Incomplete
Status in gstreamer-vaapi source package in Jammy:
  In Progress
Status in gstreamer1.0 source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  Since Ubuntu 22.04 LTS's release with gstreamer 1.20.1, there have been two 
bugfix stable releases. 

  https://gstreamer.freedesktop.org/releases/1.20/#1.20.2
  https://gstreamer.freedesktop.org/releases/1.20/#1.20.3

  Test Case 1
  ---
  We now run upstream's test suite for most gstreamer components at build time 
and fail the build for errors on our key desktop architectures, amd64 & arm64.

  Ensure the builds succeeed.

  Test Case 2
  ---
  Play a variety of videos in Totem. Play a variety of audio tracks in 
Rhythmbox. Try to stream audio and/or video. Try to install a missing codec.

  In all cases, make sure that everything which worked before still
  works.

  What Could Go Wrong
  ---
  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1980239/+subscriptions


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


[Desktop-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container

2022-07-08 Thread Steve Langasek
I've also just discovered that in addition to the second-largest running
process (ModemManager), fwupd is responsible for the third-largest
running process (udisksd).  Perhaps it would be expedient to revisit the
inclusion of fwupd in the seed used for cloud and container images?

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

Title:
  server image pulls in ModemManager via fwupd, consumes 25MiB RAM in
  every container

Status in fwupd package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Looking at memory utilization in a pristine Ubuntu lxd container (top
  -o RES), I see that ModemManager is running, which I was surprised to
  see is present at all in the stock image.

  Tracking this I find that fwupd depends on libmm-glib0, which in turn
  Recommends: modemmanager.

  Libraries in general should not recommend daemons, so it's possible
  this should be fixed by libmm-glib0 dropping this Recommends.  It
  certainly doesn't seem to be a deliberate decision by the Server Team
  to have modemmanager installed and running by default on all systems.

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


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


[Desktop-packages] [Bug 1981109] [NEW] server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container

2022-07-08 Thread Steve Langasek
Public bug reported:

Looking at memory utilization in a pristine Ubuntu lxd container (top -o
RES), I see that ModemManager is running, which I was surprised to see
is present at all in the stock image.

Tracking this I find that fwupd depends on libmm-glib0, which in turn
Recommends: modemmanager.

Libraries in general should not recommend daemons, so it's possible this
should be fixed by libmm-glib0 dropping this Recommends.  It certainly
doesn't seem to be a deliberate decision by the Server Team to have
modemmanager installed and running by default on all systems.

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

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

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


** Tags: rls-kk-incoming

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

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

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Ubuntu Server (ubuntu-server)

** Tags added: rls-kk-incoming

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

Title:
  server image pulls in ModemManager via fwupd, consumes 25MiB RAM in
  every container

Status in fwupd package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Looking at memory utilization in a pristine Ubuntu lxd container (top
  -o RES), I see that ModemManager is running, which I was surprised to
  see is present at all in the stock image.

  Tracking this I find that fwupd depends on libmm-glib0, which in turn
  Recommends: modemmanager.

  Libraries in general should not recommend daemons, so it's possible
  this should be fixed by libmm-glib0 dropping this Recommends.  It
  certainly doesn't seem to be a deliberate decision by the Server Team
  to have modemmanager installed and running by default on all systems.

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


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


[Desktop-packages] [Bug 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled

2022-07-08 Thread Treviño
Mh, I don't see real error related to this, can you maybe attach the
full log?

Ideal would be:
 - Enable auto-hide
 - Replicate the issue
 - Get the log and attach it here

Thanks

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

Title:
  gnome-shell search can't launch apps if dock auto-hide is enabled

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

Bug description:
  The problem happens, when I enable the dock to hide automatically.
  With this enabled, it is not possible to run the programs through the
  search. But when disabled, it is possible to search and run the
  programs. Here's the video of the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 17 18:21:45 2022
  DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed
   v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388]
  InstallationDate: Installed on 2021-04-15 (428 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago)
  dmi.bios.date: 03/04/2017
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1201
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M LX/BR
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled

2022-07-08 Thread paradoxheart
Jul 08 22:43:39 myne gnome-shell[1495]: Running GNOME Shell (using mutter 42.2) 
as a Wayland display server
Jul 08 22:43:39 myne gnome-shell[1495]: Device '/dev/dri/card0' prefers shadow 
buffer
Jul 08 22:43:39 myne gnome-shell[1495]: Added device '/dev/dri/card0' (i915) 
using atomic mode setting.
Jul 08 22:43:39 myne gnome-shell[1495]: Created gbm renderer for 
'/dev/dri/card0'
Jul 08 22:43:39 myne gnome-shell[1495]: Boot VGA GPU /dev/dri/card0 selected as 
primary
Jul 08 22:43:40 myne gnome-shell[1495]: Using public X11 display :1024, (using 
:1025 for managed services)
Jul 08 22:43:40 myne gnome-shell[1495]: Using Wayland display name 'wayland-0'
Jul 08 22:43:40 myne gnome-shell[1495]: Unset XDG_SESSION_ID, 
getCurrentSessionProxy() called outside a user session. Asking logind directly.
Jul 08 22:43:40 myne gnome-shell[1495]: Will monitor session c1
Jul 08 22:43:40 myne gnome-shell[1495]: Extension 
ubuntu-appindicat...@ubuntu.com already installed in 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be 
loaded
Jul 08 22:43:40 myne gnome-shell[1495]: Extension ubuntu-d...@ubuntu.com 
already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. 
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be loaded
Jul 08 22:43:40 myne gnome-shell[1495]: Extension d...@rastersoft.com already 
installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. 
/usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded
Jul 08 22:43:40 myne org.gnome.Shell.desktop[1495]: Window manager warning: 
Failed to parse saved session file: Failed to open file 
“/var/lib/gdm3/.config/mutter/sessions/10aa4c840d4a3e81c71657316619476367001477.ms”:
 No such file or directory
Jul 08 22:43:40 myne gnome-shell[1495]: JS ERROR: TypeError: this._managerProxy 
is undefined

_onGeoclueVanished@resource:///org/gnome/shell/ui/status/location.js:169:9
Jul 08 22:43:40 myne gnome-shell[1495]: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Jul 08 22:43:40 myne gnome-shell[1495]: ATK Bridge is disabled but a11y has 
already been enabled.
Jul 08 22:43:41 myne gnome-shell[1495]: Registering session with GDM
Jul 08 22:43:54 myne gnome-shell[2200]: Running GNOME Shell (using mutter 42.2) 
as a Wayland display server
Jul 08 22:43:54 myne gnome-shell[2200]: Device '/dev/dri/card0' prefers shadow 
buffer
Jul 08 22:43:54 myne gnome-shell[2200]: Added device '/dev/dri/card0' (i915) 
using atomic mode setting.
Jul 08 22:43:54 myne gnome-shell[2200]: Created gbm renderer for 
'/dev/dri/card0'
Jul 08 22:43:54 myne gnome-shell[2200]: Boot VGA GPU /dev/dri/card0 selected as 
primary
Jul 08 22:43:54 myne gnome-shell[2200]: Using public X11 display :0, (using :1 
for managed services)
Jul 08 22:43:54 myne gnome-shell[2200]: Using Wayland display name 'wayland-0'
Jul 08 22:43:54 myne gnome-shell[2200]: Unset XDG_SESSION_ID, 
getCurrentSessionProxy() called outside a user session. Asking logind directly.
Jul 08 22:43:54 myne gnome-shell[2200]: Will monitor session 2
Jul 08 22:43:54 myne gnome-shell[2200]: Telepathy is not available, chat 
integration will be disabled.
Jul 08 22:43:54 myne gnome-shell[2200]: Failed to import DBusMenu, quicklists 
are not avaialble: Error: Requiring Dbusmenu, version none: Typelib file for 
namespace 'Dbusmenu' (any version) not found
Jul 08 22:43:55 myne gnome-shell[2200]: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Jul 08 22:43:55 myne gnome-shell[2200]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
Jul 08 22:43:55 myne gnome-shell[2200]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
Jul 08 22:43:55 myne gnome-shell[2200]: Window manager warning: Overwriting 
existing binding of keysym 39 with keysym 39 (keycode 12).
Jul 08 22:43:55 myne gnome-shell[2200]: Window manager warning: Overwriting 
existing binding of keysym 38 with keysym 38 (keycode 11).
Jul 08 22:43:55 myne gnome-shell[2200]: Window manager warning: Overwriting 
existing binding of keysym 33 with keysym 33 (keycode c).
Jul 08 22:43:55 myne gnome-shell[2200]: Window manager warning: Overwriting 
existing binding of keysym 32 with keysym 32 (keycode b).
Jul 08 22:43:55 myne gnome-shell[2200]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
Jul 08 22:43:55 myne gnome-shell[2200]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
Jul 08 22:43:55 myne gnome-shell[2200]: Window manager warning: Overwriting 
existing binding of keysym 31 with keysym 31 (keycode a).
Jul 08 22:43:56 myne gnome-shell[2200]: ATK Bridge is disabled but a11y has 
already been enabled.
Jul 08 

[Desktop-packages] [Bug 1970473] Re: [radeon] Xorg crashed with SIGSEGV when using the RADEON driver

2022-07-08 Thread Launchpad Bug Tracker
This bug was fixed in the package xserver-xorg-video-ati - 1:19.1.0-3

---
xserver-xorg-video-ati (1:19.1.0-3) unstable; urgency=medium

  * fix-rotation.diff: Fix crash on rotation. (Closes: #1009325)
(LP: #1970473)

 -- Timo Aaltonen   Fri, 08 Jul 2022 12:52:34 +0300

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [radeon] Xorg crashed with SIGSEGV when using the RADEON driver

Status in xserver-xorg-video-ati package in Ubuntu:
  Fix Released

Bug description:
  When using Settings/Display/Orientation/Portret right and Apply then X
  crashes and login screen is displayed. Tested with 3 different AMD
  systems (older). Bug is not present with Intel graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:30:33 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1043:03da]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Hewlett-Packard HP Compaq 6005 Pro MT PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ro_RO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2010
  dmi.bios.release: 1.11
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G6 v01.11
  dmi.board.asset.tag: CZC1332VBJ
  dmi.board.name: 3047h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC1332VBJ
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:br1.11:svnHewlett-Packard:pnHPCompaq6005ProMTPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct6:cvr:skuAT493AV:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq 6005 Pro MT PC
  dmi.product.sku: AT493AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/xserver-xorg-video-ati/+bug/1970473/+subscriptions


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


[Desktop-packages] [Bug 1980934] Re: Backup fail with unknown error

2022-07-08 Thread Michael Terry
Those messages from the log look innocent enough to me. So the backups
themselves work correctly, but when we get to the verification step at
the end, you see an unknown error? No further output in that dialog?

The verification step tries to restore a canary file we insert in the
backup, just to ensure that files can be restored from the new backup.
So something is going wrong with that sample restore...


** Changed in: deja-dup (Ubuntu)
   Status: New => Incomplete

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

Title:
  Backup fail with unknown error

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  I removed the cache and start a backup in console like

  DEJA_DUP_DEBUG=1 deja-dup

  and got during verification the Unknown Error with following final
  outputs

  DUPLICITY: DEBUG 1
  DUPLICITY: . Found manifest volume 845

  DUPLICITY: INFO 1
  DUPLICITY: . Found 845 volumes in manifest

  DUPLICITY: DEBUG 1
  DUPLICITY: . Releasing lockfile 
b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile'

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-7zeqbwou-tempdir/mkstemp-oc2otu7o-1

  DUPLICITY: DEBUG 1
  DUPLICITY: . Releasing lockfile 
b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile'

  DUPLICITY: DEBUG 1
  DUPLICITY: . Releasing lockfile 
b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile'

  I than checked the cache which still contains all files including the
  lockfile

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: deja-dup 40.7-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  7 10:55:01 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  InstallationDate: Installed on 2019-12-07 (942 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to focal on 2020-10-04 (640 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1980934/+subscriptions


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


[Desktop-packages] [Bug 1980908] Re: duplicity does NOT close properly

2022-07-08 Thread Michael Terry
Hi, Kenneth! This would almost certainly just be Deja Dup's fault, I
can't imagine duplicity would be an issue here.

@khteh - it should be safe to kill an active duplicity process and
restart your backup, to recover from this happening as a workaround. But
obviously, there's still the bug that it did happen in the first place.

How did you close Deja Dup? Normally, there's the progress dialog with
cancel or resume later buttons, both of which should stop the duplicity
process. If Deja Dup was shut down unexpectedly, I could maybe see this
happening.

** Changed in: deja-dup
   Status: New => Incomplete

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

Title:
  duplicity does NOT close properly

Status in Déjà Dup:
  Incomplete
Status in Duplicity:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  Duplicity process stays running after closing deja-dup backups app
  from Ubuntu desktop. Openning up deja-dup again, go to Restore tab,
  error message shows "Another duplicity instance is already running
  with this archive directory". `ps -ef | grep duplicity` shows the
  process still running.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1980908/+subscriptions


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


[Desktop-packages] [Bug 1958813] Re: [snap] I have on clean install some weird folder /home/user/Downloads/firefox.tmp/

2022-07-08 Thread Little Girl
I have no idea why this is listed as "Fix Released" since it's currently
still an issue in a fully-updated copy of Kubuntu 22.04 LTS. I agree
that this temporary directory should not be being placed into the
Downloads directory. It should either be being placed into the directory
Snap uses for everything else or into a hidden directory directly in the
Home directory so it can follow the conventions used by other default
software.

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

Title:
  [snap] I have on clean install some weird folder
  /home/user/Downloads/firefox.tmp/

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  I have on clean install some weird folder /home/user/Downloads/firefox.tmp/
  Downloads/
  └── firefox.tmp
  ├── security_state
  ├── Temp-efca5f30-b773-40f3-afd2-fb29f7ca2d30
  │   └── mesa_shader_cache
  │   ├── 5a
  │   │   └── a12b397653d94da952e9174b48042792d0b5b5
  │   ├── 86
  │   │   └── 658cd26a8a5c083a0d01153d2d26eb349759ce
  │   ├── c2
  │   │   └── 6957f33af79c866d74f0dd37b47ef18e57d431
  │   └── index
  └── tmpaddon

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.3
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Mon Jan 24 03:49:13 2022
  InstallationDate: Installed on 2022-01-21 (2 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220121)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04

2022-07-08 Thread Sebastien Bacher
oh great, let's close the bug then, thanks!

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

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

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

Title:
  wifi connection on hotspot with wpa enterprise on 22.04

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid
Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  With 20.04 I used a wifi connection with a hotspot Telenet with following 
parametres:
  security : WPA2 entreprise
  authentification : tunneled TLS
  no AC certificat drequired
  inner authentication : MSCHAPV2(non EAP)
  user name: my id
  password : my pswd

  with 22.04 it doesn’t work anymore nor with the internal broadcom wifi
  nor with dongles (nor my Dlink 140 nor TP-link WN7200)

  This problem is only present with hotspot requesting an identification
  (user+pswd) awith hotspots without identification everything is OK

  in appendice some infos
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michelvlt   1725 F pulseaudio
   /dev/snd/pcmC0D0p:   michelvlt   1725 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source /etc/network/interfaces.d/*
  InstallationDate: Installed on 2022-04-21 (7 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IpRoute:
   default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 
   10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 
   169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 
   192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 
600
  MachineType: Apple Inc. MacBookPro8,1
  NonfreeKernelModules: wl
  Package: wpa
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 87.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245B3640C91C81
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245B3640C91C81
  dmi.modalias: 
dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro8,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+subscriptions


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


[Desktop-packages] [Bug 1980908] Re: duplicity does NOT close properly

2022-07-08 Thread Kenneth Loafman
Also, how did you exit deja-dup? Clean exit or task killed?

Is this repeatable?  I don't have a Linux GUI to test on, just terminal.

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

Title:
  duplicity does NOT close properly

Status in Déjà Dup:
  New
Status in Duplicity:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  Duplicity process stays running after closing deja-dup backups app
  from Ubuntu desktop. Openning up deja-dup again, go to Restore tab,
  error message shows "Another duplicity instance is already running
  with this archive directory". `ps -ef | grep duplicity` shows the
  process still running.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1980908/+subscriptions


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


[Desktop-packages] [Bug 1981025] Re: Firefox SNAP update removes icon from desktop

2022-07-08 Thread Olivier Tilloy
As pointed out on the Lubuntu discourse, the icon on your desktop was
very probably a manual copy of the desktop file that is generated by
snapd. You'll have better luck by making it a symlink to that desktop
file, instead of a copy.

** 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/1981025

Title:
  Firefox SNAP update removes icon from desktop

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Firefox SNAP updated from 102.0 to 102.0.1 today, resulting in the
  desktop icon disappearing, because the firefox_firefox.desktop file
  "icon=" line then points to a now non-existent directory.

  https://discourse.lubuntu.me/t/firefox-snap-updated-firefox-desktop-
  icon-disappeared-after-update/3445

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


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


[Desktop-packages] [Bug 1748895] Re: LO unable to find a working email configuration

2022-07-08 Thread cement_head
I can spawn a composer window (Thunderbird) from LO, but no document
gets attached.  Using the Flatpak install of LO.  Any suggestions?

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

Title:
  LO unable to find a working email configuration

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

Bug description:
  Installed from PPA: ppa:libreoffice/ppa

  $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  $ apt-cache policy libreoffice
  libreoffice:
Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
Version table:
   *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
   1:5.1.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  WHAT YOU EXPECT TO HAPPEN:

Should spawn an new Evolution eMAIL with attached ODF document

  WHAT HAPPENED INSTEAD:

Error Dialogue: LibreOffice is unable to find a working email
  configuration.  Please save your document locally and attached from
  within your eMAIL client.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+subscriptions


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


[Desktop-packages] [Bug 1981025] Re: Firefox SNAP update removes icon from desktop

2022-07-08 Thread Edward
Command doesn't work.

:~$ apport-collect 1981025
The authorization page:
 
(https://launchpad.net/+authorize-token?oauth_token=Kh3CwRWMrWJkRKVgw3MJ_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
/usr/bin/xdg-open: 882: firefox: not found
/usr/bin/xdg-open: 882: firefox: not found
xdg-open: no method available for opening 
'https://launchpad.net/+authorize-token?oauth_token=Kh3CwRWMrWJkRKVgw3MJ_permission=DESKTOP_INTEGRATION'

Then when CTRL-C is pressed to end this:

^CTraceback (most recent call last):
  File "/usr/bin/apport-cli", line 387, in 
if not app.run_argv():
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 719, in run_argv
return self.run_update_report()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 566, in 
run_update_report
if not self.crashdb.can_update(self.options.update_report):
  File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 
529, in can_update
bug = self.launchpad.bugs[id]
  File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 
155, in launchpad
self.__launchpad = Launchpad.login_with('apport-collect',
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 700, in 
login_with
return cls._authorize_token_and_login(
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 451, in 
_authorize_token_and_login
credentials = authorization_engine(credentials, credential_store)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 627, 
in __call__
self.make_end_user_authorize_token(credentials, request_token_string)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 718, 
in make_end_user_authorize_token
self.wait_for_end_user_authorization(credentials)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 813, 
in wait_for_end_user_authorization
if self.check_end_user_authorization(credentials):
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 693, 
in check_end_user_authorization
credentials.exchange_request_token_for_access_token(self.web_root)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 240, 
in exchange_request_token_for_access_token
response, content = _http_post(url, headers, params)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 106, 
in _http_post
response, content = httplib2.Http(
  File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1725, in 
request
(response, content) = self._request(
  File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1441, in 
_request
(response, content) = self._conn_request(conn, request_uri, method, body, 
headers)
  File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1393, in 
_conn_request
response = conn.getresponse()
  File "/usr/lib/python3.10/http/client.py", line 1374, in getresponse
response.begin()
  File "/usr/lib/python3.10/http/client.py", line 318, in begin
version, status, reason = self._read_status()
  File "/usr/lib/python3.10/http/client.py", line 279, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
  File "/usr/lib/python3.10/socket.py", line 705, in readinto
return self._sock.recv_into(b)
  File "/usr/lib/python3.10/ssl.py", line 1273, in recv_into
return self.read(nbytes, buffer)
  File "/usr/lib/python3.10/ssl.py", line 1129, in read
return self._sslobj.read(len, buffer)
KeyboardInterrupt

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

Title:
  Firefox SNAP update removes icon from desktop

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox SNAP updated from 102.0 to 102.0.1 today, resulting in the
  desktop icon disappearing, because the firefox_firefox.desktop file
  "icon=" line then points to a now non-existent directory.

  https://discourse.lubuntu.me/t/firefox-snap-updated-firefox-desktop-
  icon-disappeared-after-update/3445

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


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


[Desktop-packages] [Bug 1981025] Re: Firefox SNAP update removes icon from desktop

2022-07-08 Thread Edward
Attempted again, same thing:

:~$ apport-collect 1981025
The authorization page:
 
(https://launchpad.net/+authorize-token?oauth_token=HQrBgSXhd3p8m5mt8jP3_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
/usr/bin/xdg-open: 882: firefox: not found
/usr/bin/xdg-open: 882: firefox: not found
xdg-open: no method available for opening 
'https://launchpad.net/+authorize-token?oauth_token=HQrBgSXhd3p8m5mt8jP3_permission=DESKTOP_INTEGRATION'

^CTraceback (most recent call last):
  File "/usr/bin/apport-cli", line 387, in 
if not app.run_argv():
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 719, in run_argv
return self.run_update_report()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 566, in 
run_update_report
if not self.crashdb.can_update(self.options.update_report):
  File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 
529, in can_update
bug = self.launchpad.bugs[id]
  File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 
155, in launchpad
self.__launchpad = Launchpad.login_with('apport-collect',
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 700, in 
login_with
return cls._authorize_token_and_login(
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 451, in 
_authorize_token_and_login
credentials = authorization_engine(credentials, credential_store)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 627, 
in __call__
self.make_end_user_authorize_token(credentials, request_token_string)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 718, 
in make_end_user_authorize_token
self.wait_for_end_user_authorization(credentials)
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 811, 
in wait_for_end_user_authorization
time.sleep(access_token_poll_time)
KeyboardInterrupt

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

Title:
  Firefox SNAP update removes icon from desktop

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox SNAP updated from 102.0 to 102.0.1 today, resulting in the
  desktop icon disappearing, because the firefox_firefox.desktop file
  "icon=" line then points to a now non-existent directory.

  https://discourse.lubuntu.me/t/firefox-snap-updated-firefox-desktop-
  icon-disappeared-after-update/3445

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


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


[Desktop-packages] [Bug 1748895] Re: LO unable to find a working email configuration

2022-07-08 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Incomplete => New

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

Title:
  LO unable to find a working email configuration

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

Bug description:
  Installed from PPA: ppa:libreoffice/ppa

  $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  $ apt-cache policy libreoffice
  libreoffice:
Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
Version table:
   *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
   1:5.1.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  WHAT YOU EXPECT TO HAPPEN:

Should spawn an new Evolution eMAIL with attached ODF document

  WHAT HAPPENED INSTEAD:

Error Dialogue: LibreOffice is unable to find a working email
  configuration.  Please save your document locally and attached from
  within your eMAIL client.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+subscriptions


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


[Desktop-packages] [Bug 1803604] Re: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work

2022-07-08 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Incomplete => New

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

Title:
  [upstream] "Send -> Document as e-mail" in Writer / Calc does not work

Status in LibreOffice:
  New
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  LO: Version: 6.1.3.2
  Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1

  In writer I have an open document. If I then want to send it:

  "File - send - document as e-mail"

  **Nothing happens**

  Same with send e-mail as open-document and word document. Only send
  with pdf opens at least the pdf dialogue. But then nothing happens.

  Path to thunderbird: /usr/bin/thunderbird
  Thunderbird opens if I use this path so the path seems correct. No error 
message received.

  Expect: Mail is opened and document attached. (which worked before)

  Update: Just checked in Ubuntu 18.04 and LO 6.06.2
  There it works as expected. Will check my other system again. Maybe it just 
does not work on my other system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+subscriptions


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


[Desktop-packages] [Bug 1803604]

2022-07-08 Thread Qa-admin-q
[Automated Action] NeedInfo-To-Unconfirmed

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

Title:
  [upstream] "Send -> Document as e-mail" in Writer / Calc does not work

Status in LibreOffice:
  New
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  LO: Version: 6.1.3.2
  Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1

  In writer I have an open document. If I then want to send it:

  "File - send - document as e-mail"

  **Nothing happens**

  Same with send e-mail as open-document and word document. Only send
  with pdf opens at least the pdf dialogue. But then nothing happens.

  Path to thunderbird: /usr/bin/thunderbird
  Thunderbird opens if I use this path so the path seems correct. No error 
message received.

  Expect: Mail is opened and document attached. (which worked before)

  Update: Just checked in Ubuntu 18.04 and LO 6.06.2
  There it works as expected. Will check my other system again. Maybe it just 
does not work on my other system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+subscriptions


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


[Desktop-packages] [Bug 1748895]

2022-07-08 Thread Z-bernard-moreton
I get over the problem by inserting a line for claws-mail in apparmor
profile for senddoc, and specifying claws-mail (with full path) in
Options-Tools-...Email.

A better option would be to rewrite the xdg-email code in senddoc along
the lines of the block for claws|sylpheed (though in LO, the 'To' field
is presumably not required ...).  This would make the default generally
useful for all email clients, where currently it simply doesn't attach,
which is the whole point of senddoc ...


I'll continue to hope that Ubuntu 22.04 xdg-utils will fix the attachment 
problem, since it affects scanning to email as well as LO;  but there'' be many 
LO users who remain on current (non-functioning) xdg-email maitto: style.  They 
should be helped, even if the rest of us do find salvation ...

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

Title:
  LO unable to find a working email configuration

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

Bug description:
  Installed from PPA: ppa:libreoffice/ppa

  $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  $ apt-cache policy libreoffice
  libreoffice:
Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
Version table:
   *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
   1:5.1.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  WHAT YOU EXPECT TO HAPPEN:

Should spawn an new Evolution eMAIL with attached ODF document

  WHAT HAPPENED INSTEAD:

Error Dialogue: LibreOffice is unable to find a working email
  configuration.  Please save your document locally and attached from
  within your eMAIL client.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+subscriptions


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


[Desktop-packages] [Bug 1748895]

2022-07-08 Thread Qa-admin-q
[Automated Action] NeedInfo-To-Unconfirmed

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

Title:
  LO unable to find a working email configuration

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

Bug description:
  Installed from PPA: ppa:libreoffice/ppa

  $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  $ apt-cache policy libreoffice
  libreoffice:
Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
Version table:
   *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
   1:5.1.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  WHAT YOU EXPECT TO HAPPEN:

Should spawn an new Evolution eMAIL with attached ODF document

  WHAT HAPPENED INSTEAD:

Error Dialogue: LibreOffice is unable to find a working email
  configuration.  Please save your document locally and attached from
  within your eMAIL client.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+subscriptions


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


[Desktop-packages] [Bug 1803604]

2022-07-08 Thread Z-bernard-moreton
I get over the problem by inserting a line for claws-mail in apparmor
profile for senddoc, and specifying claws-mail (with full path) in
Options-Tools-...Email.

A better option would be to rewrite the xdg-email code in senddoc along
the lines of the block for claws|sylpheed (though in LO, the 'To' field
is presumably not required ...).  This would make the default generally
useful for all email clients, where currently it simply doesn't attach,
which is the whole point of senddoc ...


I'll continue to hope that Ubuntu 22.04 xdg-utils will fix the attachment 
problem, since it affects scanning to email as well as LO;  but there'' be many 
LO users who remain on current (non-functioning) xdg-email maitto: style.  They 
should be helped, even if the rest of us do find salvation ...

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

Title:
  [upstream] "Send -> Document as e-mail" in Writer / Calc does not work

Status in LibreOffice:
  New
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  LO: Version: 6.1.3.2
  Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1

  In writer I have an open document. If I then want to send it:

  "File - send - document as e-mail"

  **Nothing happens**

  Same with send e-mail as open-document and word document. Only send
  with pdf opens at least the pdf dialogue. But then nothing happens.

  Path to thunderbird: /usr/bin/thunderbird
  Thunderbird opens if I use this path so the path seems correct. No error 
message received.

  Expect: Mail is opened and document attached. (which worked before)

  Update: Just checked in Ubuntu 18.04 and LO 6.06.2
  There it works as expected. Will check my other system again. Maybe it just 
does not work on my other system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+subscriptions


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


[Desktop-packages] [Bug 1967111] Re: xfce4-mime-helper --launch WebBrowser does not work with firefox snap

2022-07-08 Thread Bug Watch Updater
** Changed in: xfce4-settings
   Status: New => Fix Released

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

Title:
  xfce4-mime-helper --launch WebBrowser does not work with firefox snap

Status in Xfce4 Settings:
  Fix Released
Status in firefox package in Ubuntu:
  Invalid
Status in xfce4-settings package in Ubuntu:
  Fix Released
Status in firefox source package in Jammy:
  Invalid
Status in xfce4-settings source package in Jammy:
  Fix Released

Bug description:
  With Firefox set as the default browser, `exo-open --launch
  WebBrowser` only outputs the current env vars (seen below).

  Passing in an additional parameter (`exo-open --launch WebBrowser
  google.com`) works as expected.

  SHELL=/bin/bash
  
SESSION_MANAGER=local/xubuntu:@/tmp/.ICE-unix/4173,unix/xubuntu:/tmp/.ICE-unix/4173
  WINDOWID=73400323
  QT_ACCESSIBILITY=1
  COLORTERM=truecolor
  XDG_CONFIG_DIRS=/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
  XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
  XDG_MENU_PREFIX=xfce-
  CLUTTER_BACKEND=x11
  SSH_AUTH_SOCK=/run/user/999/keyring/ssh
  DESKTOP_SESSION=xubuntu
  XDG_SEAT=seat0
  PWD=/home/xubuntu
  LOGNAME=xubuntu
  XDG_SESSION_DESKTOP=xubuntu
  QT_QPA_PLATFORMTHEME=gtk2
  XDG_SESSION_TYPE=x11
  PANEL_GDK_CORE_DEVICE_EVENTS=0
  GPG_AGENT_INFO=/run/user/999/gnupg/S.gpg-agent:0:1
  XAUTHORITY=/home/xubuntu/.Xauthority
  XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/xubuntu
  HOME=/home/xubuntu
  LANG=en_US.UTF-8
  
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
  XDG_CURRENT_DESKTOP=XFCE
  VTE_VERSION=6790
  XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
  LESSCLOSE=/usr/bin/lesspipe %s %s
  XDG_SESSION_CLASS=user
  TERM=xterm-256color
  GTK_OVERLAY_SCROLLING=0
  LESSOPEN=| /usr/bin/lesspipe %s
  USER=xubuntu
  DISPLAY=:0.0
  SHLVL=1
  XDG_VTNR=7
  XDG_SESSION_ID=c2
  XDG_RUNTIME_DIR=/run/user/999
  
XDG_DATA_DIRS=/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share
  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
  GDMSESSION=xubuntu
  DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/999/bus
  _=/usr/bin/exo-open

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-settings/+bug/1967111/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-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-08 Thread Nathan Teodosio
Hey Li, yes, the latest build is only for logging, which can be enabled
by passing --enable-logging=stderr.

Please bear in mind that that build area is mostly a testing ground; not
all new builds therein will be relevant, neither will they always be in
a clean, refined state. Of course, feel free to test whichever you like,
but rest assured that relevant ones will be uploaded to the
candidate/hwacc channel as in the bug description.

-- 
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 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

2022-07-08 Thread Frank Heimes
** Information type changed from Private to Public

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

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  New
Status in nettle package in Ubuntu:
  New

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

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


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


[Desktop-packages] [Bug 1970473] Re: [radeon] Xorg crashed with SIGSEGV when using the RADEON driver

2022-07-08 Thread Simon Iremonger
I can confirm the same crash happening with 22.04 Xorg and radeon card:-

VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar
[Radeon HD 5000/6000/7350/8350 Series]

... when trying to rotate... which always used to work before e.g. in
20.04LTS.

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

Title:
  [radeon] Xorg crashed with SIGSEGV when using the RADEON driver

Status in xserver-xorg-video-ati package in Ubuntu:
  Confirmed

Bug description:
  When using Settings/Display/Orientation/Portret right and Apply then X
  crashes and login screen is displayed. Tested with 3 different AMD
  systems (older). Bug is not present with Intel graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:30:33 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1043:03da]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Hewlett-Packard HP Compaq 6005 Pro MT PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ro_RO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2010
  dmi.bios.release: 1.11
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G6 v01.11
  dmi.board.asset.tag: CZC1332VBJ
  dmi.board.name: 3047h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC1332VBJ
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:br1.11:svnHewlett-Packard:pnHPCompaq6005ProMTPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct6:cvr:skuAT493AV:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq 6005 Pro MT PC
  dmi.product.sku: AT493AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/xserver-xorg-video-ati/+bug/1970473/+subscriptions


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


[Desktop-packages] [Bug 1881941] Re: Ubuntu dock behaves crazy when hidden at the bottom of the screen

2022-07-08 Thread simon coleman
I see this issue fairly frequently with the dock at the RHS of the
display, I do not think it is related to the location.

Having just moved all the other windows on this display away from the
dock location it has opened & remained open without the mouse cursor
over it.

Setting a window to fullscreen again caused the dock to hide & un-
maximising the window did not re-open the dock (ie, it remains hidden).

At this point it can be unhidden normally (without flickering) by moving
the mouse to the screen edge, and dock autohides once the mouse is off
it again.

I conclude there is a problem with the mouseover/show/hide state logic,
since in the example I just gave, the dock opened without the mouseover
as soon as there was screen area for it to avoid overlaying another
window.

Looks like it thought it had a mouseover it was trying to comply with. 
I wonder if the mouseover logic is 
dock_should_be_open = NOT dock_should_be_open

and somehow it ends up inconsistent with the actual open state of the
dock, so tries to simultaneously open & close when the mouse gets to the
edge of the display (and why it popped open without a mouse for me).

hth

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

Title:
  Ubuntu dock behaves crazy when hidden at the bottom of the screen

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

Bug description:
  I had put the dock on the bottom of the screen and also set to hide 
automatically. 
  The dock works fine as expected but there are sometimes (actually like 90% of 
the time) that it behaves weird when I try to access it with the mouse pointer, 
the dock starts to bounce quickly without stopping and then it's kind of hard 
to press the icons on it (when I'm lucky I can click the icon), other times I 
had to move away the pointer from the bottom and then move it back to access 
the dock. 
  I made a video of it although it's very short but you can see for a brief of 
time how the dock starts to bounce.
  I haven't installed new packages or applications that change the behaviour of 
the dock in any way.

  
  tavoge@e6430s:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  
  tavoge@e6430s:~$ apt-cache policy xorg
  xorg:
Instalados: 1:7.7+19ubuntu14
Candidato:  1:7.7+19ubuntu14
Tabla de versión:
   *** 1:7.7+19ubuntu14 500
  500 http://mx.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  3 11:40:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:057d]
  InstallationDate: Installed on 2020-05-29 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Latitude E6430s
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 0XHTPW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/30/2018:svnDellInc.:pnLatitudeE6430s:pvr01:rvnDellInc.:rn0XHTPW:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430s
  dmi.product.sku: Latitude E6430s
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/gnome-shell-extension-ubuntu-dock/+bug/1881941/+subscriptions


-- 

[Desktop-packages] [Bug 1936302] Re: To support elanmoc driver

2022-07-08 Thread Andy Chi
** Changed in: libfprint (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  To support elanmoc driver

Status in OEM Priority Project:
  Fix Released
Status in libfprint package in Ubuntu:
  Fix Released
Status in libfprint source package in Focal:
  Fix Released
Status in libfprint source package in Impish:
  Fix Released

Bug description:
  The upstream already accept the Elan fingerprint support.
  https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/278

  This ID is included in upstream.

  [Impact]

   * Devices have elanmoc [04f3:0c7e] fingerprint component will get
 supported.

  [Test Plan]

   * Find a machine with this fingerprint device

   * Launch `settings` and enable `Fingerprint Login`

   * Enroll finger and then logout

   * Login system with enrolled finger

  [Where problems could occur]

   * The only impact will be [04f3:0c7e] will be supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1936302/+subscriptions


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


[Desktop-packages] [Bug 1973629] Re: Wifi hotspot not configured correctly on restart

2022-07-08 Thread constantin budin
** Attachment added: "Screenshot from 2022-07-08 09-16-59.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+attachment/5602037/+files/Screenshot%20from%202022-07-08%2009-16-59.png

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

Title:
  Wifi hotspot not configured correctly on restart

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have configured the hotspot to automatically start at startup. The
  hotspot correctly starts on startup, but it appears to be configured
  incorrectly. No device connected to it can reach the internet. When
  opening the settings, Wifi is indicated to be disabled, even though
  the hotspot is running (see screenshot).

  The expectation is that the hotspot is fully functional on startup
  meaning every device connected to it can reach the internet.

  Currently the issue can be fixed by activating Wifi and then starting
  a hotspot, even though the hotspot is already running. The hotspot
  started at startup does not have to be shut down before starting a
  hotspot in the settings.

  All this leads me to believe that somewhere the configuration of Wifi
  goes wrong on startup.

  Running Ubuntu 22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dconf-service 0.40.0-3
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 19:59:02 2022
  InstallationDate: Installed on 2021-12-08 (159 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: dconf
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-12-08 (173 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 10.0.0.138 dev enp2s0 proto dhcp metric 100
   10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600
   169.254.0.0/16 dev enp2s0 scope link metric 1000
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.36.4-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled
  no_proxy: localhost,127.0.0.0/8,::1

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


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


[Desktop-packages] [Bug 1973629] Re: Wifi hotspot not configured correctly on restart

2022-07-08 Thread constantin budin
By setting the priority quite high (see attachment)

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

Title:
  Wifi hotspot not configured correctly on restart

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have configured the hotspot to automatically start at startup. The
  hotspot correctly starts on startup, but it appears to be configured
  incorrectly. No device connected to it can reach the internet. When
  opening the settings, Wifi is indicated to be disabled, even though
  the hotspot is running (see screenshot).

  The expectation is that the hotspot is fully functional on startup
  meaning every device connected to it can reach the internet.

  Currently the issue can be fixed by activating Wifi and then starting
  a hotspot, even though the hotspot is already running. The hotspot
  started at startup does not have to be shut down before starting a
  hotspot in the settings.

  All this leads me to believe that somewhere the configuration of Wifi
  goes wrong on startup.

  Running Ubuntu 22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dconf-service 0.40.0-3
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 19:59:02 2022
  InstallationDate: Installed on 2021-12-08 (159 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: dconf
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-12-08 (173 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 10.0.0.138 dev enp2s0 proto dhcp metric 100
   10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600
   169.254.0.0/16 dev enp2s0 scope link metric 1000
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.36.4-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled
  no_proxy: localhost,127.0.0.0/8,::1

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


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


[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions

2022-07-08 Thread jeremyszu
In Focal Stock Ubuntu, I confirmed if user installs "cryptsetup-
initramfs" on I+A platform with choosing display mode to "External
Only", the issue presents.

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

Title:
  Displaylink is extremely slow in Xorg sessions

Status in Nouveau Xorg driver:
  New
Status in OEM Priority Project:
  New
Status in xf86-video-amd:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  In Progress
Status in xorg-server source package in Focal:
  Fix Released
Status in xorg-server source package in Hirsute:
  Won't Fix
Status in xorg-server source package in Impish:
  Fix Released
Status in xorg-server source package in Jammy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Jammy:
  New
Status in xserver-xorg-video-nouveau source package in Jammy:
  New

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

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


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