date:20220515

** No longer affects: snapd (Ubuntu)

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

Title:
  No font available after installing in user space

Status in libreoffice package in Ubuntu:
  Fix Committed

Bug description:
  I can't find the installed "Ecofont Vera Sans" under LibreOffice
  (7.3.2.2)  in Ubuntu (20.04.4 LTS).

  ---
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  ---
  LibreOffice (snap snapcraft.io)
  Version: 7.3.2.2 / LibreOffice Community
  Build ID: 454130fadb9a820d3728b86ccb63c8f359d70528
  CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3
  Locale: it-IT (en_US.UTF-8); UI: en-US
  Calc: threaded

  ---
  Ecofont Vera Sans Download page: 
https://www.fonts4free.net/ecofont-vera-sans-font.html

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


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

[Desktop-packages] [Bug 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04

2022-05-15 Thread Chris Guiver

** Summary changed:

- File dialog doesn't return current filter in Ubuntu 20.02
+ File dialog doesn't return current filter in Ubuntu 20.04

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.04

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New
Status in xdg-desktop-portal-gtk source package in Focal:
  New

Bug description:
  The file dialog implementation doesn't return the current filter. It
  is in the spec and it is fixed in newer versions of the portals. But
  the 1.6.0 version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1973564/+subscriptions


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

[Desktop-packages] [Bug 1972059] Re: One screen does not come back from lock

I can't find any reason in those logs for the bug. Maybe try adding this
to /etc/environment:

  MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

and then reboot.

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

Title:
  One screen does not come back from lock

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have 2 screen (Dell).
  Since having upgraded to 22.04, one of them struggles to come back after a 
lock.

  Sometimes takes a few seconds, sometimes it is ok and sometimes it takes 
longer.
  I have found that if I do Ctrl-Alt-F1... the screen comes back.

  I have a DP and HDMI cable and tried to switch them around, it is
  always the same screen: a Dell U2415 UltraSharp 24.

  Never happened with any other version since about 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  7 13:39:19 2022
  DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 
seconds (Configuring libpam-systemd (amd64))
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-02-01 (825 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (7 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  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/mutter/+bug/1972059/+subscriptions


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

[Desktop-packages] [Bug 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.02

2022-05-15 Thread Ted Gould

Attaching a debdiff. For what ever reason this doesn't seem to fix
Inkscape. Though the D-Bus traffic is the same one 20.04 and 22.04 after
this change.

** Patch added: "xdg-desktop-portal-gtk-1.6.0-2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1973564/+attachment/5589943/+files/xdg-desktop-portal-gtk-1.6.0-2.debdiff

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.02

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New
Status in xdg-desktop-portal-gtk source package in Focal:
  New

Bug description:
  The file dialog implementation doesn't return the current filter. It
  is in the spec and it is fixed in newer versions of the portals. But
  the 1.6.0 version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1973564/+subscriptions


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

[Desktop-packages] [Bug 1972080] Re: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)

Maybe one of these will do the trick:

  update-alternatives --config gdm-theme.gresource

  update-alternatives --config x-cursor-theme

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

Title:
  GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white
  square (missing adwaita-icon-theme-full)

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Do not think this is hardware dependent, but I'm using an HPE
  MicroServer Gen10 Plus.

  I installed the server edition of 22.04.  Post-Installation, I added
  some desktop environments.  After logging in, these are working fine.

  However on the gdm login entry and password entry screens I had no
  mouse pointer icon.  A semi-opaque white square tracked the mouse
  movements.  My reading suggested that gdm defaults to using the cursor
  icon theme provided by the adwaita-icon-theme package.  I discovered
  this theme comes in two sizes, a basic, smaller package installed
  automatically and a larger "full" package.

  $ apt list 'adwaita-icon-theme*'
  Listing... Done
  adwaita-icon-theme/jammy,now 41.0-1ubuntu1 all [installed,automatic]
  adwaita-icon-theme-full/jammy,now 41.0-1ubuntu1 all [installed]
  $

  The gdm mouse pointer appears and disappears with installation and
  removal of the package "adwaita-icon-theme-full".  Either gdm's
  dependencies should include the "full" package OR the appropriate
  mouse pointer icons should be moved from the full to the basic
  "adwaita-icon-theme" package.

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


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

[Desktop-packages] [Bug 1965116] Re: Desktop lockup

** Tags added: impish

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

Title:
  Desktop lockup

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  I use Ubuntu 21.10 with Wayland and nvidia drivers. Sometimes, when
  working, the desktop freezes.

  Over ssh, I can see in the system logs many of those messages:

  > gnome-shell[5615]: Key repeat discarded, Wayland compositor doesn't
  seem to be processing events fast enough!

  dmesg doesn't show any problems.

  Xwayland has a very high CPU usage. Killing Xwayland didn't help.

  When I then restart gdm, logging in either works again, or at least
  gdm allows a graceful reboot.

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


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

[Desktop-packages] [Bug 1969598] Re: no auto-focus application after workspace switch

I can't seem to reproduce the problem myself...

Please try disabling the 'Desktop Icons NG' extension in the Extensions
app (may require logging in again) and then tell us if the bug persists.


** Tags added: focus

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

Title:
  no auto-focus application after workspace switch

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1) Setup at least two workspaces.

  2) open at least one GUI application on one of them. Another one is
  focused and no application opened.

  3) switch workspaces from 'empty' to 'with application'

  
  Expected result: last focused GUI application from the new focused workspace 
will be auto-focused again. And all shortcuts right after the switch will be 
applicable to a given application.

  Actual result: application is not focused, all shortcuts are
  applicable to desktop only.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 12:17:48 2022
  DisplayManager: gdm3
  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/1969598/+subscriptions


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

[Desktop-packages] [Bug 1973264] Re: when switching to another workspace, focus is lost

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

** Tags added: focus

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

Title:
  when switching to another workspace, focus is lost

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Good morning,

  Since upgrading to 22.04 there is an annoying bug when switching to
  another workspace. After the switch to one of the other workspaces,
  the desktop has the focus, instead of an application window. Until
  now, the window that most recently had focus on that workspace, would
  get the focus again, which I would consider normal behaviour.

  This bug leads to confusing (sometimes funny) situations, like

  - me switching to another WS
  - press ctrl A to select all text in the window I assume is active
  - nothing seems to happen, but (not visible for me) everything on the desktop 
is selected
  - better not press Del now :)  

  Best,

  Joolz.

  P.S. I hope I filed this in the right section, not sure which
  framework causes this

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


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

[Desktop-packages] [Bug 1969598] Re: no auto-focus application after workspace switch

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

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

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

Title:
  no auto-focus application after workspace switch

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1) Setup at least two workspaces.

  2) open at least one GUI application on one of them. Another one is
  focused and no application opened.

  3) switch workspaces from 'empty' to 'with application'

  
  Expected result: last focused GUI application from the new focused workspace 
will be auto-focused again. And all shortcuts right after the switch will be 
applicable to a given application.

  Actual result: application is not focused, all shortcuts are
  applicable to desktop only.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 12:17:48 2022
  DisplayManager: gdm3
  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/1969598/+subscriptions


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

[Desktop-packages] [Bug 1973264] Re: when switching to another workspace, focus is lost

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

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


** This bug has been marked a duplicate of bug 1969598
   no auto-focus application after workspace switch

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

Title:
  when switching to another workspace, focus is lost

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Good morning,

  Since upgrading to 22.04 there is an annoying bug when switching to
  another workspace. After the switch to one of the other workspaces,
  the desktop has the focus, instead of an application window. Until
  now, the window that most recently had focus on that workspace, would
  get the focus again, which I would consider normal behaviour.

  This bug leads to confusing (sometimes funny) situations, like

  - me switching to another WS
  - press ctrl A to select all text in the window I assume is active
  - nothing seems to happen, but (not visible for me) everything on the desktop 
is selected
  - better not press Del now :)  

  Best,

  Joolz.

  P.S. I hope I filed this in the right section, not sure which
  framework causes this

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


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

[Desktop-packages] [Bug 1956537] Re: Firefox 95.0.2 64-bit Ubuntu gets error from command line launch

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

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

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

Title:
  Firefox 95.0.2 64-bit Ubuntu gets error from command line launch

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Steps to reproduce:

  firefox --private-window https://www.google.com

  Firefox 95.0.2 64-bit
  Ubuntu 21.10 using Unity 7.5

  Actual results:

  ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded 
(failed to map segment from shared object): ignored.
  Gtk-Message: 10:06:43.897: Failed to load module "xapp-gtk3-module"
  Gtk-Message: 10:06:44.073: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:06:44.579: Failed to load module "canberra-gtk-module"

  Expected results:

  These errors shouldn't be generated.

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


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

[Desktop-packages] [Bug 1965087] Re: Pipewire not working on ThinkPad T510

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

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

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

Title:
  Pipewire not working on ThinkPad T510

Status in pipewire package in Ubuntu:
  Expired

Bug description:
  I have 2 user accounts, and one of them is on PulseAudio, which works
  fine.  The primary one, which is on PipeWire, doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pipewire 0.3.48-1ubuntu1
  Uname: Linux 5.16.0-14.2-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 16 02:59:24 2022
  InstallationDate: Installed on 2021-08-07 (221 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to jammy on 2022-02-09 (34 days ago)

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


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

[Desktop-packages] [Bug 1965116] Re: Desktop lockup

[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/1965116

Title:
  Desktop lockup

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  I use Ubuntu 21.10 with Wayland and nvidia drivers. Sometimes, when
  working, the desktop freezes.

  Over ssh, I can see in the system logs many of those messages:

  > gnome-shell[5615]: Key repeat discarded, Wayland compositor doesn't
  seem to be processing events fast enough!

  dmesg doesn't show any problems.

  Xwayland has a very high CPU usage. Killing Xwayland didn't help.

  When I then restart gdm, logging in either works again, or at least
  gdm allows a graceful reboot.

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


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

[Desktop-packages] [Bug 1972080] Re: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)

2022-05-15 Thread Jon LaBadie

Removal of the package 'sabily-gdm-themes' and rebooting had no effect
on my situation.

Daniel, perhaps you have some insight into this.  What information I've found 
in my internet search says that gdm/gdm3 defaults to Adwaita icon theme.  I'm 
looked for "how to configure" type articles
about gdm and none have been applicable or have had not effect.

Do you know how to reconfigure gdm in Ubuntu 22.04?

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

Title:
  GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white
  square (missing adwaita-icon-theme-full)

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Do not think this is hardware dependent, but I'm using an HPE
  MicroServer Gen10 Plus.

  I installed the server edition of 22.04.  Post-Installation, I added
  some desktop environments.  After logging in, these are working fine.

  However on the gdm login entry and password entry screens I had no
  mouse pointer icon.  A semi-opaque white square tracked the mouse
  movements.  My reading suggested that gdm defaults to using the cursor
  icon theme provided by the adwaita-icon-theme package.  I discovered
  this theme comes in two sizes, a basic, smaller package installed
  automatically and a larger "full" package.

  $ apt list 'adwaita-icon-theme*'
  Listing... Done
  adwaita-icon-theme/jammy,now 41.0-1ubuntu1 all [installed,automatic]
  adwaita-icon-theme-full/jammy,now 41.0-1ubuntu1 all [installed]
  $

  The gdm mouse pointer appears and disappears with installation and
  removal of the package "adwaita-icon-theme-full".  Either gdm's
  dependencies should include the "full" package OR the appropriate
  mouse pointer icons should be moved from the full to the basic
  "adwaita-icon-theme" package.

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


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

[Desktop-packages] [Bug 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions

> I'm quite convinced that moving the mouse fast in circles over Firefox
> for example doesn't feel quite right both on Wayland and on Xorg
> on my external monitor.

If you encounter a problem in Xorg sessions then please open a new bug.
This bug is about external monitors in Wayland sessions.

> I just noticed that night light doesn't work on Wayland but I guess that
> is a known issue.

That's bug 1972728.

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

Title:
  [nvidia] Secondary monitor performance is slow on an Nvidia hybrid
  system in Wayland sessions

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  In session with Wayland the Nvidia driver settings do not load. And
  there is a sluggishness when opening apps, show applications menu,
  maximize, changing workspace, resize, changing monitor windows etc.
  When in an Xorg session the Nvidia settings load correctly and the
  performance is satisfactory.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-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  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 21:18:08 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] 
[8086:2086]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] 
[8086:2086]
  InstallationDate: Installed on 2022-04-24 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: Avell High Performance A60 MUV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: QCCFL357.0122.2020.0911.1520
  dmi.board.name: Avell High Performance
  dmi.board.vendor: Avell High Performance
  dmi.chassis.type: 10
  dmi.chassis.vendor: Avell High Performance
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV:
  dmi.product.family: A60 MUV
  dmi.product.name: A60 MUV
  dmi.product.sku: A60 MUV
  dmi.sys.vendor: Avell High Performance
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/mutter/+bug/1970291/+subscriptions


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

[Desktop-packages] [Bug 1973403] Re: gnome-shell is using over 13GB of ram after 5 days

Also while the problem is happening please run:

  ps auxw | grep gnome-shell > psoutput.txt

and attach the resulting text file here.


** Tags added: gnome-shell-leak

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

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

Title:
  gnome-shell is using over 13GB of ram after  5 days

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This is on Ubuntu 22.04
  All updates
  After 5 days gnome-shell is using 13GB or ram.

  System is a Asus PN50
  512 GB m.2 drive
  64 GIG Ram.
  AMD 4800U

  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 14 11:27:20 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-05-07 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RebootRequiredPkgs: Error: path contained symlinks.
  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/1973403/+subscriptions


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

[Desktop-packages] [Bug 1973403] Re: gnome-shell is using over 13GB of ram after 5 days

Thanks for the bug report.

1. Please open the Extensions app (from package gnome-shell-extension-
prefs) and ensure you only have the three Ubuntu extensions loaded.

2. Please run these commands in a Terminal to remove any locally-
installed extensions you might have:

   cd ~/.local/share/gnome-shell/
   rm -rf extensions

3. Log in again and tell us if the problem returns.

4. If the problem does return then it might be related to the flood of
'unable to update icon for multiload' messages in your log. To test that
theory please disable 'Ubuntu AppIndicators' in the Extensions app.

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

Title:
  gnome-shell is using over 13GB of ram after  5 days

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This is on Ubuntu 22.04
  All updates
  After 5 days gnome-shell is using 13GB or ram.

  System is a Asus PN50
  512 GB m.2 drive
  64 GIG Ram.
  AMD 4800U

  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 14 11:27:20 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-05-07 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RebootRequiredPkgs: Error: path contained symlinks.
  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/1973403/+subscriptions


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

[Desktop-packages] [Bug 1950893] Re: Text does not render correctly in SVG file

2022-05-15 Thread PaulSchulz

I can confirm that this bug has been fixed in the latest version of Ubuntu 
22.04.
with: 

Version 101.0.4951.64 (Official Build) snap (64-bit)

snap list | grep chromium
chromium 101.0.4951.641993   latest/stable
canonical**   -

The upstream bug has also been closed.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Fix Released

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

Title:
  Text does not render correctly in SVG file

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  See upstream bug report.
  https://bugs.chromium.org/p/chromium/issues/detail?id=1180484

  It has been fixed in the latest google-chrome-unstable (97.0.4692.8-1)
  deb package from Google.

  Not fixed in 21.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 14 21:59:20 2021
  InstallationDate: Installed on 2018-01-13 (1401 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to impish on 2021-10-15 (30 days ago)

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


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

[Desktop-packages] [Bug 1899252] Re: Alt-Tab raises all windows of an app (when using multiple monitors)

** Tags added: focus

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

Title:
  Alt-Tab raises all windows of an app (when using multiple monitors)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm getting the same behavior as the link below, in Ubuntu 18.04 you
  could do a quick alt+tab to change to the first window of an
  application, but now that I updated it to the latest version (20.04) I
  have the all windows of an app that are displayed with Alt+tab.

  https://bugzilla.gnome.org/show_bug.cgi?id=697480

  This was supposedly fixed by Didier Roche, check out the following
  link https://bugzilla.gnome.org/show_bug.cgi?id=786009.

  The behavior is best described in the videos made by Didier:

  Gnome-session vanilla

  https://youtu.be/D32VEP0sFk4

  Ubuntu-session

  https://youtu.be/k-IBk-Fibj4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 10 13:00:04 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-26 (563 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-02 (7 days ago)

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


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

[Desktop-packages] [Bug 1910112] Re: saturation du journal

Thanks for the bug report. Please tell us if the bug is still occurring.
If so then please run:

  apport-collect 1910112

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

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

Title:
  saturation du journal

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  un fichier exécutable .desktop contenant
  [Desktop Entry]
  Version=1.0
  Type=Application
  Terminal=true
  Name[fr_FR]=journalctl
  Exec=gnome-terminal;journalctl -f
  Name=journalctl

  sature le journal en générant de multiples messages interminables

  uname -a
  Linux jpb-MS-7A70 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Codename: focal

  
  exemple de message
  déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 
gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 
11:18:55 jpb-MS-7A70 gnome-shell[10097]: déc. 21 11:18:55 jpb-MS-7A70

[Desktop-packages] [Bug 1973564] [NEW] File dialog doesn't return current filter in Ubuntu 20.02

2022-05-15 Thread Ted Gould

Public bug reported:

The file dialog implementation doesn't return the current filter. It is
in the spec and it is fixed in newer versions of the portals. But the
1.6.0 version doesn't return it.

This is an issue for Inkscape which uses the filter to select which file
format someone wishes to save as if they override the defaults. This
works well on Ubuntu 22.04.

** Affects: xdg-desktop-portal-gtk (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: xdg-desktop-portal-gtk (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Also affects: xdg-desktop-portal-gtk (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.02

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New
Status in xdg-desktop-portal-gtk source package in Focal:
  New

Bug description:
  The file dialog implementation doesn't return the current filter. It
  is in the spec and it is fixed in newer versions of the portals. But
  the 1.6.0 version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1973564/+subscriptions


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

[Desktop-packages] [Bug 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)

The work is being tracked in
https://gitlab.gnome.org/GNOME/mutter/-/issues/20

** Tags added: jammy

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #20
   https://gitlab.gnome.org/GNOME/mutter/-/issues/20

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

Title:
  the screen keeps locking while I watch video (missing support for
  Wayland's idle_inhibit_unstable_v1)

Status in MPV:
  Fix Released
Status in Mutter:
  New
Status in mpv package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/20

  ---

  Reproducibility:

  100% reproducible

  steps to reproduce:

  1. $ mpv -fv anyvideo_long_enough.anyformat
  2. now please refrain from any mouse/keyboard activity, wait for the 
screensaver to activate
  3. screensaver activates

  problem:

  the screensaver activates

  desired behaviour:

  the screensaver shouldn't activate

  long description:

  Hello,

  the screen keeps locking while I watch video with mpv. Basically the
  screensaver gets activated.

  but according to man mpv:

     --heartbeat-cmd=

    WARNING:
    This  option  is redundant with Lua scripting. Further, it 
shouldn't be needed for disabling screensaver anyway, since mpv will call 
xdg-screensaver
    when using X11 backend. As a consequence this option has been 
deprecated with no direct replacement.

  ...

  That all said as the screen getting locked contradicts the manpage, I
  consider this a bug. Thank you for the fix in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: mpv 0.26.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  1 19:10:42 2018
  InstallationDate: Installed on 2017-12-25 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: mpv
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1948410] Re: [nvidia] Software cursor in Wayland sessions (EGLStreams)

** Description changed:

  Impact
  --
- In the Wayland session with older Nvidia graphics, a software cursor is used 
instead of a hardware cursor. This causes worse performance with unnecessary 
updates of the display.
+ In the Wayland session with older Nvidia graphics (usually nvidia driver 
470), a software cursor is used instead of a hardware cursor. This causes worse 
performance with unnecessary updates of the display.
  
  Test Case
  -
  To see it just add this to /etc/environment:
  
+   MUTTER_DEBUG_FORCE_EGL_STREAM=1
    CLUTTER_PAINT=damage-region
  
  and reboot.
  
  What Could Go Wrong
  ---
  See the master bug for this mutter update LP: #1972726

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

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

Title:
  [nvidia] Software cursor in Wayland sessions (EGLStreams)

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  In the Wayland session with older Nvidia graphics (usually nvidia driver 
470), a software cursor is used instead of a hardware cursor. This causes worse 
performance with unnecessary updates of the display.

  Test Case
  -
  To see it just add this to /etc/environment:

MUTTER_DEBUG_FORCE_EGL_STREAM=1
    CLUTTER_PAINT=damage-region

  and reboot.

  What Could Go Wrong
  ---
  See the master bug for this mutter update LP: #1972726

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


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

[Desktop-packages] [Bug 1969574] Re: [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace

This bug is where all the action was and what we've been linking to for
weeks so this should remain the primary bug.

** This bug is no longer a duplicate of bug 1971693
   Alt+Tab is broken for Java (AWT/Swing) apps in Wayland session

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

Title:
  [Wayland] Can not select JetBrains IntelliJ IDEA windows (including
  Android Studio) with mouse in workspace

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  I have 3 apps open in 1 workspace,
  When i press window key and i want to select app 2 or 3 with mouse, app 1 
shows up!
  I can only go to app 2 with [window + tab] or [alt + tab]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 11:05:02 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-11-25 (145 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-16 (3 days ago)

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


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

[Desktop-packages] [Bug 1970471] Re: Changing applications bug 22.04LTS

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

** This bug is no longer a duplicate of bug 1971693
   Alt+Tab is broken for Java (AWT/Swing) apps in Wayland session
** This bug has been marked a duplicate of bug 1969574
   [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android 
Studio) with mouse in workspace

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

Title:
  Changing applications bug 22.04LTS

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have Firefox and the android studio code opened at the same time.
  If I am using Firefox and want to move into studio code, I press the "super" 
key to show all the apps running and click with my mouse the studio code app. 
Instead of showing ASC it keeps showing me Firefox, but not the other way 
around, when I am in ASC and want to change to Firefox, it does change.
  This only happens when using the "super" key by itself, when using "super + 
tab" or "alt + tab" it does change.

  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
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 21:06:02 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Toshiba Corporation HD Graphics 5500 [1179:000a]
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
   |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 
480M
   |__ Port 8: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
   |__ Port 8: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
  MachineType: TOSHIBA Satellite Pro R50-B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=b739b2dd-b328-4bee-a14e-8e1cc4583783 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2015
  dmi.bios.release: 1.20
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.20
  dmi.board.asset.tag: 00
  dmi.board.name: Satellite Pro R50-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.ec.firmware.release: 1.10
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.20:bd01/30/2015:br1.20:efr1.10:svnTOSHIBA:pnSatelliteProR50-B:pvrPSSG2E-00K004CE:rvnTOSHIBA:rnSatelliteProR50-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:skuPSSG2E:
  dmi.product.family: 00
  dmi.product.name: Satellite Pro R50-B
  dmi.product.sku: PSSG2E
  dmi.product.version: PSSG2E-00K004CE
  dmi.sys.vendor: TOSHIBA
  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/gnome-shell/+bug/1970471/+subscriptions


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

[Desktop-packages] [Bug 1971693] Re: Alt+Tab is broken for Java (AWT/Swing) apps in Wayland session

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

We should keep using bug 1969574 since that's what's been reported on
and linked to for the past few weeks.

** This bug has been marked a duplicate of bug 1969574
   [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android 
Studio) with mouse in workspace

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

Title:
  Alt+Tab is broken for Java (AWT/Swing) apps in Wayland session

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  When switching to a Java UI application using Alt+Tab, very often 
application's window is raised, but it doesn't get keyboard focus - it stays in 
the previous application, and that application continues to process keyboard 
events. When the problem occurs, hovering mouse over Java app's window gets the 
focus transferred to it.
  This problem only happens in Wayland session, not in X.Org session. It can be 
reproduced in Ubuntu 22.04, but not in 20.04.4 version.

  The problem seems to affect all Java versions - reproduced for
  different OpenJDK builds (8, 11, 17, 18). It can also be observed for
  Java version provided by Ubuntu's 'default-jre' package
  (11.0.15+10-Ubuntu-0ubuntu0.22.04.1).

  Test Case
  -
  1. sudo apt install default-jre
  2. Download the minimal test case app from comment #1
  3. From a terminal run the app
  java Downloads/JTextFieldTest.java
  4. Click on the terminal window (instead of the Java app)
  5. Press Alt-Tab to switch focus back to the Java app
  6. Type a few characters.

  The characters should show in the Java app's text field instead of in
  the terminal window.

  What Could Go Wrong
  ---
  See the master bug for this update at LP: #1972726

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


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

[Desktop-packages] [Bug 1973464] Re: Firefox does not supply name when it asks to open default keyring in Lubuntu 20.04

2022-05-15 Thread Chris Guiver

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1973464

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.


(please run it on the impacted box; so details can be correctly populated 
allowing exploration using tools)

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

Title:
  Firefox does not supply name when it asks to open default keyring in
  Lubuntu 20.04

Status in firefox package in Ubuntu:
  New

Bug description:
  When using auto-login in Lubuntu 20.04 LTS, browsing firefox causes
  firefox to send a request to the default keyring to unlock.

  The problem is, it doesn't provide any information about what
  application is making the request. This can be disorienting to the
  user, especially since the security prompt locks out the system until
  you enter the password or press cancel, with no hints about why you're
  getting the message.

  Image: application asking to unlock default keyring.
  https://i.ibb.co/4K36pqT/48cce3e1-abfc-4b12-9561-acb2a78da7bd.jpg

  I have verified that it is firefox, by removing
  ~/.local/share/keyrings directory, and restarting the system. When
  firefox is opened again, you get a new message asking you to create a
  new password for the default keyring.

  Image: Opening firefox prompts the creation of a new password for the default 
keyring.
  https://i.ibb.co/RpSJ8L6/4fda479e-4603-4330-80cf-e2bc20643a61.jpg

  I am not sure what program is handling the default keyring on lubuntu.
  Would it be possible for firefox to supply its name when interacting
  with the default keyring?

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


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

[Desktop-packages] [Bug 1973481] [NEW] eog can't read a perfectly legitimate JPEG image

2022-05-15 Thread JCCyC

Public bug reported:

If you try to open the attached image with eog, it shows an error
"Suspension not allowed here." Also, the file manager can't show a
thumbnail. AND if you set this image as the desktop background you get a
black background.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: eog 42.0-1
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun May 15 19:57:58 2022
InstallationDate: Installed on 2022-04-30 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: eog
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Picture eog gives an error when trying to access"
   
https://bugs.launchpad.net/bugs/1973481/+attachment/5589911/+files/Brambilla%20Montreal%201979.zip

** Description changed:

- If you try to open the attached imege with eog, it shows an error
+ If you try to open the attached image with eog, it shows an error
  "Suspension not allowed here." Also, the file manager can't show a
  thumbnail. AND if you set this image as the desktop background you get a
  black background.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: eog 42.0-1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 19:57:58 2022
  InstallationDate: Installed on 2022-04-30 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  eog can't read a perfectly legitimate JPEG image

Status in eog package in Ubuntu:
  New

Bug description:
  If you try to open the attached image with eog, it shows an error
  "Suspension not allowed here." Also, the file manager can't show a
  thumbnail. AND if you set this image as the desktop background you get
  a black background.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: eog 42.0-1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 19:57:58 2022
  InstallationDate: Installed on 2022-04-30 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1899252] Re: Alt-Tab raises all windows of an app (when using multiple monitors)

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

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

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

Title:
  Alt-Tab raises all windows of an app (when using multiple monitors)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm getting the same behavior as the link below, in Ubuntu 18.04 you
  could do a quick alt+tab to change to the first window of an
  application, but now that I updated it to the latest version (20.04) I
  have the all windows of an app that are displayed with Alt+tab.

  https://bugzilla.gnome.org/show_bug.cgi?id=697480

  This was supposedly fixed by Didier Roche, check out the following
  link https://bugzilla.gnome.org/show_bug.cgi?id=786009.

  The behavior is best described in the videos made by Didier:

  Gnome-session vanilla

  https://youtu.be/D32VEP0sFk4

  Ubuntu-session

  https://youtu.be/k-IBk-Fibj4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 10 13:00:04 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-26 (563 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-02 (7 days ago)

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


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

[Desktop-packages] [Bug 1973288] Re: Since Jammy, Alt+Tab is not working properly

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

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

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

Title:
  Since Jammy, Alt+Tab is not working properly

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Since the upgrade to jammy alt+tab doesn't work any more properly when
  hitting it very fast.

  Doing a slow Alt+Tab works fine, but just quickly hitting the two keys
  will not switch the window any more, instead a notification bubble
  will appear says "Application XYZ is ready".

  It kinda feels like it's a race between the alt+tab and the focus
  stealing prevention. I.e. if one is fast enough, the windows are
  swapped before the focus stealing prevention realizes that the user
  actually wants to change focus and prevents the new window coming to
  the front, just displaying the notification bubble instead.

  FWIW, this is on X11, not sure if wayland would be affected too as
  wayland is not an option for the Dell XPS yet due to HighDPI screen
  scaling not working good enough yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-28.29-generic 5.15.35
  Uname: Linux 5.15.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 13 10:44:32 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-05-13 (364 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (11 days ago)

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


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

[Desktop-packages] [Bug 1973288] Re: Since Jammy, Alt+Tab is not working properly

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

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

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

Title:
  Since Jammy, Alt+Tab is not working properly

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Since the upgrade to jammy alt+tab doesn't work any more properly when
  hitting it very fast.

  Doing a slow Alt+Tab works fine, but just quickly hitting the two keys
  will not switch the window any more, instead a notification bubble
  will appear says "Application XYZ is ready".

  It kinda feels like it's a race between the alt+tab and the focus
  stealing prevention. I.e. if one is fast enough, the windows are
  swapped before the focus stealing prevention realizes that the user
  actually wants to change focus and prevents the new window coming to
  the front, just displaying the notification bubble instead.

  FWIW, this is on X11, not sure if wayland would be affected too as
  wayland is not an option for the Dell XPS yet due to HighDPI screen
  scaling not working good enough yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-28.29-generic 5.15.35
  Uname: Linux 5.15.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 13 10:44:32 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-05-13 (364 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (11 days ago)

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


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

[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04

2022-05-15 Thread Matthew Ruffell

Performing verification for Jammy.

Starting with the broken 3.0.27-2build2 in -release, running

gst-launch-1.0 videotestsrc ! jpegenc ! jpegdec ! clutterautovideosink

shows a grey picture with vertical bars. Opening cheese, we see the same
vertical bars, poor video performance and purple lines.

I enabled -proposed and installed 3.0.27-2ubuntu1, and re-ran

gst-launch-1.0 videotestsrc ! jpegenc ! jpegdec ! clutterautovideosink

and had cheese running. Performance was great, nice and smooth, and
picture is correct.

Tested with my Logitech C720 webcam, and attached is a screenshot of
everything running with 3.0.27-2ubuntu1 from -proposed.

Happy to mark as verified for Jammy.

** Attachment added: "Screenshot of verification for Jammy"

https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+attachment/5589910/+files/Screenshot%20from%202022-05-16%2010-14-41.png

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

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

Title:
cheese display corrupted under Ubuntu 22.04

Status in Cheese:
Unknown
Status in OEM Priority Project:
Confirmed
Status in cheese package in Ubuntu:
Invalid
Status in clutter-gst-3.0 package in Ubuntu:
Fix Released
Status in clutter-gst-3.0 source package in Jammy:
Fix Committed

Bug description:
Impact
==
The cheese app is unusable with color bands showing in the main view.

This bug doesn't affect all webcams. It's unknown what percentage of
webcams are affected.

Test Case

On a system that experiences this bug:
Install the update
Run the cheese app
Verify that the main view shows what your webcam can see normally.
Click the camera button in the bottom toolbar area.
Check if the photo looks normal. You can find it in ~/Pictures/Webcam

What Could Go Wrong
===
Only 4 apps in Ubuntu use clutter-gst: empathy, cheese, lyricue, pinpoint

clutter-gst has been archived by GNOME. (It's recommended for apps to
use GTK4 instead of GTK3 + Clutter). That means it's not possible for
this patch to be accepted upstream. Instead, distros like Arch Linux
are applying this patch.

This patch removes 2 renderers that don't work (RGBx and BGRx) but
still keeps ones that do work: RGBA and BRGA.

Original Bug Report
===
The cheese application produces a corrupted display under Ubuntu 22.04 with a
Logitech C525 webcam. When started from the command line, cheese produces
repeated warnings of the form...

(cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late ():
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
There may be a timestamping problem, or this computer is too slow.

Adding /etc/modprobe.d/uvcvideo.conf

with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue
is not seen in either Ubuntu 21.10 or under Fedora-Workstation-
Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both
Wayland and X11 displays with the Nvidia drivers.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cheese 41.1-1build1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 5 05:15:35 2022
ExecutablePath: /usr/bin/cheese
InstallationDate: Installed on 2022-03-31 (4 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
MachineType: Gigabyte Technology Co., Ltd. X570 UD
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
TERM=xterm-256color
XDG_RUNTIME_DIR=
PATH=(custom, no user)
RelatedPackageVersions:
cheese41.1-1build1
cheese-common 41.1-1build1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F32
dmi.board.asset.tag: Default string
dmi.board.name: X570 UD
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: X570 MB
dmi.product.name: X570 UD
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
---
ProblemType: Bug

[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written

2022-05-15 Thread Bug Watch Updater

** Bug watch added: Mozilla Bugzilla #1768500
   https://bugzilla.mozilla.org/show_bug.cgi?id=1768500

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  Additional information:

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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


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

[Desktop-packages] [Bug 1970989]

2022-05-15 Thread Jérôme Bouat

I'm describing below an other test with the same physical host and virtual 
guest.
I installed the xfce desktop environment (via tasksel) and I uninstalled all 
lxqt packages. I disabled the snap user service start (from the xfce session 
configuration panel).
Then, the cold start of the deb package application is down in less than 2 
seconds (better). Maybe de xfce desktop environment already loaded a few 
libraries (libgtk-3-0, ...).
In addition, I measured the used memory (free -k) by comparing the "used" 
memory field before launch and a few seconds after the window appeared.
With deb package application : 266 MB.
With snap package application : 397 MB (+49%).
It seems the deb package application saves memory because it is sharing the 
libraries with the other applications of the desktop.
Note that I didn't count the used memory by the snap machinery (in case you 
wouldn't install snapd with a deb package application).

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

Title:
  missing a tightly integrated deb package without snap

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Opinion

Bug description:
  I installed the Jammy Jellyfish version. When I launch firefox, the
  delay between my click and the apparition of the window is very long
  compared to the behaviour of the previous versions of Ubuntu. The deb
  package is just pulling the firefox snap. Why did you decide this
  performance regression ?! I don't understand.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  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: XFCE
  Date: Fri Apr 29 21:27:26 2022
  InstallationDate: Installed on 2022-04-24 (5 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1971168]

2022-05-15 Thread Al Savage

Created attachment 9276133
File pickers comparison 1

I've spun up  a fresh 22.04 install in a VM, then run the snap version
of ff 100 (on the right) and ff 100 from linux binaries (on the left).
The file picker is different between the two versions; the binaries
version shows fewer network share aliases, and this binaries version can
successfully read and write to network shares.

The snap version's file picker shows aliases for network shares (and a
printer) and will navigate into those folders and show files, but when a
file is chosen to open, ff does not read the file and does not display
an error.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  Additional information:

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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


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

[Desktop-packages] [Bug 1971168]

2022-05-15 Thread Al Savage

In the fresh VM, I just installed Chrome (google-chrome) from binaries,
and it too uses the troublesome file picker, and has the same issues
("sees" network shares files but does not read them; resizes poorly;
window enlarges by 244px both H & V every time it's invoked).

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  Additional information:

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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


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

[Desktop-packages] [Bug 1971168]

2022-05-15 Thread Al Savage

Created attachment 9276134
File pickers comparison 2

In "File pickers comparison 2", I show that the two file pickers (ff run
from linux binaries vs the snap package) sort files in a different
order, have different options at the bottom, and the bottom window
corners are either square or rounded.

The snap's file picker resizes poorly here, as well.

I ran the ff linux binaries version using the suggestion from
https://bugzilla.mozilla.org/show_bug.cgi?id=1768500#c5

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  Additional information:

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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


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

[Desktop-packages] [Bug 1972131] Re: occasional flashing screen since upgrade to 22.04

2022-05-15 Thread Kent Frazier

Problem seems to manifest itself most often after wake-up from
hibernate.

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

Title:
  occasional flashing screen since upgrade to 22.04

Status in mesa package in Ubuntu:
  New

Bug description:
  Since upgrading to 22.04 I often experienced a flashing screen. I have
  noticed the issue in particular when I have an onboard keyboard
  displayed. Hiding the onboard keyboard and then showing the keyboard
  seems to resolve the flashing problem

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  8 17:20:13 2022
  InstallationDate: Installed on 2020-07-18 (659 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (9 days ago)
  VarLogDistupgradeTermlog:

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


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

[Desktop-packages] [Bug 1973476] [NEW] Startup Applications desktop file untranslated on Ubuntu 22.04

2022-05-15 Thread galen

Public bug reported:

The desktop entry for Startup Applications is untranslated under Ubuntu
22.04 in my native french language.

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

** Attachment added: "Capture-20220515231347-541x350.png"
   
https://bugs.launchpad.net/bugs/1973476/+attachment/5589905/+files/Capture-20220515231347-541x350.png

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

Title:
   Startup Applications desktop file untranslated on Ubuntu 22.04

Status in gnome-session package in Ubuntu:
  New

Bug description:
  The desktop entry for Startup Applications is untranslated under
  Ubuntu 22.04 in my native french language.

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


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

[Desktop-packages] [Bug 1973474] [NEW] Rename "Dock" to "Dash" in Appearance

2022-05-15 Thread Gunnar Hjalmarsson

Public bug reported:

I noticed this commit:

https://github.com/micheleg/dash-to-dock/commit/8ee55c29

If I understand it correctly, it means that we will use the label "Pin
to Dash" instead of "Add to Favorites" as from Ubuntu 22.10. To be
consistent I suggest that we rename the thing in all contexts, and hence
replace "Dock" with "Dash" in all affected strings in the Appearance
section in g-c-c.

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

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

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

** Description changed:

  I noticed this commit:
  
  https://github.com/micheleg/dash-to-dock/commit/8ee55c29
  
  If I understand it correctly, it means that we will use the label "Pin
- to Dash" instead of "Add to Favorites" as from Ubuntu 21.10. To be
+ to Dash" instead of "Add to Favorites" as from Ubuntu 22.10. To be
  consistent I suggest that we rename the thing in all contexts, and hence
  replace "Dock" with "Dash" in all affected strings in the Appearance
  section in g-c-c.

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

Title:
  Rename "Dock" to "Dash" in Appearance

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

Bug description:
  I noticed this commit:

  https://github.com/micheleg/dash-to-dock/commit/8ee55c29

  If I understand it correctly, it means that we will use the label "Pin
  to Dash" instead of "Add to Favorites" as from Ubuntu 22.10. To be
  consistent I suggest that we rename the thing in all contexts, and
  hence replace "Dock" with "Dash" in all affected strings in the
  Appearance section in g-c-c.

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


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

[Desktop-packages] [Bug 1973473] [NEW] Cannot enable LivePatch

2022-05-15 Thread Victor Porton

Public bug reported:

When I click enable live patch, I see: "Could not enable Livepatch. Try
again." Trying again does not help.

See also the screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: software-properties-gtk 0.99.22.1
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun May 15 22:54:53 2022
InstallationDate: Installed on 2022-01-18 (117 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: Upgraded to jammy on 2022-04-29 (16 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment added: "Screenshot from 2022-05-15 22-54-31.png"
   
https://bugs.launchpad.net/bugs/1973473/+attachment/5589896/+files/Screenshot%20from%202022-05-15%2022-54-31.png

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

Title:
  Cannot enable LivePatch

Status in software-properties package in Ubuntu:
  New

Bug description:
  When I click enable live patch, I see: "Could not enable Livepatch.
  Try again." Trying again does not help.

  See also the screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-gtk 0.99.22.1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 22:54:53 2022
  InstallationDate: Installed on 2022-01-18 (117 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (16 days ago)

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


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

[Desktop-packages] [Bug 1972983] Re: File dialog in snap firefox does not have keyboard focus

** Package changed: firefox (Ubuntu) => xdg-desktop-portal-gnome
(Ubuntu)

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

Title:
  File dialog in snap firefox does not have keyboard focus

Status in mutter package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce the issue.

  After first log in into Ubuntu Desktop 22.04

  1. Launch Firefox and open a website (e.g. www.ubuntu.com)
  2. Hit Ctrl+S to open the Save file dialog.
  3. Type "Ubuntu" to replace the default file name ("Enterprise Open Source 
and Linux | Ubuntu.html"). Hit Enter. It works the first time round.
  4. Hit Ctrl+S to open the Save file dialog again.
  5. Type "Ubuntu - 2" to replace the default file name ("Enterprise Open 
Source and Linux | Ubuntu.html"). This time, your typing fails: the file dialog 
is not in focus.

  Expected behavior anytime when opening a File dialog: the file dialog
  should have keyboard focus.

  Observed behavior: the file dialog does not have focus, except the
  very first time in the session.

  Same observations also for File Open dialogs.

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


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

[Desktop-packages] [Bug 1973403] Re: gnome-shell is using over 13GB of ram after 5 days

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

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

Title:
  gnome-shell is using over 13GB of ram after  5 days

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This is on Ubuntu 22.04
  All updates
  After 5 days gnome-shell is using 13GB or ram.

  System is a Asus PN50
  512 GB m.2 drive
  64 GIG Ram.
  AMD 4800U

  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 14 11:27:20 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-05-07 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RebootRequiredPkgs: Error: path contained symlinks.
  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/1973403/+subscriptions


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

[Desktop-packages] [Bug 1973465] Re: I have written a letter with Libre Office but it's impossible to open it

Thank you for filing this bug. Unfortunately, we cannot work on this bug
because your description didn’t include enough information. You may find
it helpful to read “How to report bugs effectively”
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We’d be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the operating system version that
you are using.

Thank you!

** Project changed: pinta => libreoffice (Ubuntu)

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

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

Title:
  I have written a letter with Libre Office but it's impossible to open
  it

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:

  file:///home/defis/Desktop/Capture%20du%202022-05-15%2018-01-21.png

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


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

[Desktop-packages] [Bug 1973465] [NEW] I have written a letter with Libre Office but it's impossible to open it