[Desktop-packages] [Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen

[Daniel van Vugt]

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

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

Title:
  Vertical dual monitor setup with main monitor on bottom causes
  overview to only use one eigth of screen

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

Bug description:
  Very recently I have started experiencing a constant bug of the app
  overview / search functions of gnome shell being entirely unusable
  because shell operates at such a tiny scale that barely anything is
  shown on screen.

  I managed to narrow the problem down to having something to do with
  dual monitors, and then played around a bit with the settings. My
  results are that no matter what other configuration I set my two
  monitors in, gnome-shell operates perfectly. That is, if my secondary
  monitor is on the left, right or below my primary one, all is well.

  If, however, the secondary monitor is set to be on top of the primary
  one (As it physically is in my current setup), then the overview and
  app search functionality starts using some very weird kind of vertical
  scaling and becomes unusable. The window previews are so small that
  the (most of the time invisible) X button is bigger than the window
  itself, thus only making me able to close the windows instead of
  switching to them or moving them. Application search only shows half
  of the first row, the other half fading away.

  I am running Ubuntu 20.04 Focal Fossa (development branch) and version
  3.36.0-2ubuntu1 of gnome-shell.

  Here are screenshots of my problem:
  The overview screen barely showing my open windows
  https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png
  The search function only showing the top half of first row of icons
  https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png
  When you mouse-over the windows many times over and over you might get the X 
button to show
  https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-02-25 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
  Package: gnome-shell 3.36.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen

[Chris Guiver]

I also filed as https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2529

Sorry Jarno, your filing wasn't present when I looked, though i got
called away.. so it was awhile between start & finish of filing.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2529
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2529

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

Title:
  Vertical dual monitor setup with main monitor on bottom causes
  overview to only use one eigth of screen

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

Bug description:
  Very recently I have started experiencing a constant bug of the app
  overview / search functions of gnome shell being entirely unusable
  because shell operates at such a tiny scale that barely anything is
  shown on screen.

  I managed to narrow the problem down to having something to do with
  dual monitors, and then played around a bit with the settings. My
  results are that no matter what other configuration I set my two
  monitors in, gnome-shell operates perfectly. That is, if my secondary
  monitor is on the left, right or below my primary one, all is well.

  If, however, the secondary monitor is set to be on top of the primary
  one (As it physically is in my current setup), then the overview and
  app search functionality starts using some very weird kind of vertical
  scaling and becomes unusable. The window previews are so small that
  the (most of the time invisible) X button is bigger than the window
  itself, thus only making me able to close the windows instead of
  switching to them or moving them. Application search only shows half
  of the first row, the other half fading away.

  I am running Ubuntu 20.04 Focal Fossa (development branch) and version
  3.36.0-2ubuntu1 of gnome-shell.

  Here are screenshots of my problem:
  The overview screen barely showing my open windows
  https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png
  The search function only showing the top half of first row of icons
  https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png
  When you mouse-over the windows many times over and over you might get the X 
button to show
  https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-02-25 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
  Package: gnome-shell 3.36.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1869444] Re: Task Manager tab: File systems completely wrong

[Didier Roche]

Retargetting to correct project with tag

** Package changed: zsys (Ubuntu) => gnome-disk-utility (Ubuntu)

** Tags added: zfs

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

Title:
  Task Manager tab: File systems completely wrong

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  See the screenshot in the annex with system monitor and disk utility display:
  With respect to the display of the file systems tab in Ubuntu 20.04 booted 
from zfs, we could say: "All similarity to reality is purely coincidental" :)

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

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

[Desktop-packages] [Bug 1868896] Re: Minimized windows reappear when closing the overview

[Rocko]

How quickly is Ubuntu likely to be refreshed with the fix? I don't mind
minimized windows pseudo-reappearing after the overview screen closes,
but they also do the same on every right mouse click in many apps, and
then it's a right pain when you keep clicking on them and wonder why
they aren't responding!

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

Title:
  Minimized windows reappear when closing the overview

Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  I just ran all of the updates for 20.04 on two machines, and both
  machines experience the same issue.

  Items do not appear to stay "minimized". For instance, you can
  minimize Thunderbird, and it appears to re-maximize itself. However,
  you cannot click on anything in the maximized window, but you can re-
  minimize it (that button does work), then click the dock to bring it
  back out and it functions properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 24 18:11:35 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
     Subsystem: Dell Iris Plus Graphics G7 [1028:096d]
  InstallationDate: Installed on 2020-03-11 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200311)
  MachineType: Dell Inc. XPS 13 9300
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vp1gr9@/vmlinuz-5.4.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_vp1gr9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.6
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.6:bd01/17/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1869662] [NEW] ubuntu 20.04 daily (iso) live - right-click show.applications & selecting settings shows error

[Chris Guiver]

Public bug reported:

Ubuntu 20.04 LTS live QA-test

On right clicking "Show Applications", you are presented with a "Dash to
Dock Settings" option, on selecting that I get an error message

Execution of "gnome-shell-extension-prefs" failed: Command not found.

The error message is not expected, on an available option.  Maybe it's
not included, but the error message isn't very useful for users as given
as it disappears rather quickly.


I suspect this issue will be a duplicate, alas I couldn't find it and didn't 
get a response on IRC.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CasperVersion: 1.441
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 30 07:24:05 2020
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-03-30 07-26-58.png"
   
https://bugs.launchpad.net/bugs/1869662/+attachment/5343236/+files/Screenshot%20from%202020-03-30%2007-26-58.png

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

Title:
  ubuntu 20.04 daily (iso) live - right-click show.applications &
  selecting settings shows error

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

Bug description:
  Ubuntu 20.04 LTS live QA-test

  On right clicking "Show Applications", you are presented with a "Dash
  to Dock Settings" option, on selecting that I get an error message

  Execution of "gnome-shell-extension-prefs" failed: Command not found.

  The error message is not expected, on an available option.  Maybe it's
  not included, but the error message isn't very useful for users as
  given as it disappears rather quickly.

  
  I suspect this issue will be a duplicate, alas I couldn't find it and didn't 
get a response on IRC.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.441
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 07:24:05 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868896] Re: Minimized windows reappear when closing the overview

[Daniel van Vugt]

Dropping the patch would also fix this bug.

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

Title:
  Minimized windows reappear when closing the overview

Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  I just ran all of the updates for 20.04 on two machines, and both
  machines experience the same issue.

  Items do not appear to stay "minimized". For instance, you can
  minimize Thunderbird, and it appears to re-maximize itself. However,
  you cannot click on anything in the maximized window, but you can re-
  minimize it (that button does work), then click the dock to bring it
  back out and it functions properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 24 18:11:35 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
     Subsystem: Dell Iris Plus Graphics G7 [1028:096d]
  InstallationDate: Installed on 2020-03-11 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200311)
  MachineType: Dell Inc. XPS 13 9300
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vp1gr9@/vmlinuz-5.4.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_vp1gr9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.6
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.6:bd01/17/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1869652] Re: 1:6.4.2-0ubuntu2 breaks ISO builds where libreoffice is seeded

[Rico Tzschichholz]

This should ease the problem
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=e2634c801a29b31bff3f6f77b0fc781450b4

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

Title:
  1:6.4.2-0ubuntu2 breaks ISO builds where libreoffice is seeded

Status in libreoffice package in Ubuntu:
  New

Bug description:
  1:6.4.2-0ubuntu2 breaks Focal ISO builds where libreoffice is seeded

  e.g.

  
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/focal/ubuntu-mate/+build/209527
  
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/focal/kubuntu/+build/209553
  
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/focal/xubuntu/+build/209524

  The following packages have unmet dependencies:
   libreoffice-core : Conflicts: libreoffice-core-nogui but 1:6.4.2-0ubuntu2 is 
to be installed
   libreoffice-core-nogui : Conflicts: libreoffice-core but 1:6.4.2-0ubuntu2 is 
to be installed
    Breaks: libreoffice-calc but 1:6.4.2-0ubuntu2 is to 
be installed
    Breaks: libreoffice-gtk3 but 1:6.4.2-0ubuntu2 is to 
be installed
  E: Unable to correct problems, you have held broken packages.

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

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

[Desktop-packages] [Bug 1868896] Re: Minimized windows reappear when closing the overview

[Daniel van Vugt]

I think we're most likely to drop the patch since even after fixing this
bug it seems to expose new issues in mutter which we don't have time to
fix right now...

3v1n0? seb128?

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

Title:
  Minimized windows reappear when closing the overview

Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  I just ran all of the updates for 20.04 on two machines, and both
  machines experience the same issue.

  Items do not appear to stay "minimized". For instance, you can
  minimize Thunderbird, and it appears to re-maximize itself. However,
  you cannot click on anything in the maximized window, but you can re-
  minimize it (that button does work), then click the dock to bring it
  back out and it functions properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 24 18:11:35 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
     Subsystem: Dell Iris Plus Graphics G7 [1028:096d]
  InstallationDate: Installed on 2020-03-11 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200311)
  MachineType: Dell Inc. XPS 13 9300
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vp1gr9@/vmlinuz-5.4.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_vp1gr9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.6
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.6:bd01/17/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1869662] Re: ubuntu 20.04 daily (iso) live - right-click show.applications & selecting settings shows error

[Launchpad Bug Tracker]

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

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

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

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

Title:
  ubuntu 20.04 daily (iso) live - right-click show.applications &
  selecting settings shows error

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

Bug description:
  Ubuntu 20.04 LTS live QA-test

  On right clicking "Show Applications", you are presented with a "Dash
  to Dock Settings" option, on selecting that I get an error message

  Execution of "gnome-shell-extension-prefs" failed: Command not found.

  The error message is not expected, on an available option.  Maybe it's
  not included, but the error message isn't very useful for users as
  given as it disappears rather quickly.

  
  I suspect this issue will be a duplicate, alas I couldn't find it and didn't 
get a response on IRC.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.441
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 07:24:05 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => New

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

Status in Linux:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1868543] Re: New upstream version 68.6.0 available, fixes security vulnerabilities

[xiconfjs]

Hi Olivier, hi Sebastien,

do you know what the release status of this fix is?


Thanks
Friedrich

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

Title:
  New upstream version 68.6.0 available, fixes security vulnerabilities

Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  There is a new upstream version 68.6.0 available which fixes several medium 
and high risk security vulnerabilities.
  Please release a new Ubuntu package ASAP - see the Debian project, which has 
already done so.

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

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

[Desktop-packages] [Bug 1869662] Re: ubuntu 20.04 daily (iso) live - right-click show.applications & selecting settings shows error

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1869635
   the menu "Dash to Dock Settings" is visible

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

Title:
  ubuntu 20.04 daily (iso) live - right-click show.applications &
  selecting settings shows error

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

Bug description:
  Ubuntu 20.04 LTS live QA-test

  On right clicking "Show Applications", you are presented with a "Dash
  to Dock Settings" option, on selecting that I get an error message

  Execution of "gnome-shell-extension-prefs" failed: Command not found.

  The error message is not expected, on an available option.  Maybe it's
  not included, but the error message isn't very useful for users as
  given as it disappears rather quickly.

  
  I suspect this issue will be a duplicate, alas I couldn't find it and didn't 
get a response on IRC.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.441
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 07:24:05 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1865222] Re: windows disappearing unless in Activities view

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  windows disappearing unless in Activities view

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

Bug description:
  It's happened to me twice after a recent update that I couldn't reach
  a window, even though it was visible in the Activities view and listed
  on the launcher.

  The windows seemed to take focus, but couldn't be seen. Alt+Tab
  switching didn't help either.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 22:00:29 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-10 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/zsh
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1866134] Re: Yaru icons are not shown in Gnome-Software

[Bug Watch Updater]

** Changed in: gnome-software
   Status: Unknown => New

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

Title:
  Yaru icons are not shown in Gnome-Software

Status in GNOME Software:
  New
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  When an icon theme different from Adwaita is selected, the icons from
  that theme are not shown in Gnome-Software.

  This is confusing for user because they now see two different icons
  for the same application (see the screenshot upstream).

  It would be great if Gnome-Software would look for the icon in the
  selected icon theme.

  
  

  Reported upstream here: https://gitlab.gnome.org/GNOME/gnome-
  software/issues/929

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

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

[Desktop-packages] [Bug 1866146] Re: GNOME Shell 3.35.91 extension's preferences doesn't load

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  GNOME Shell 3.35.91 extension's preferences doesn't load

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Using Ubuntu Focal Fossa development with gnome-shell 3.35.91 and
  preferences for extensions doesn't load.  Tried opening using the
  browser, gnome-tweaks, or the new extensions app.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 12:36:15 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-03 (518 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2019-12-10 (85 days ago)

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

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

[Desktop-packages] [Bug 1866044] Re: gnome-shell crashed with signal 5 in clutter_box_layout_allocate() ("ClutterBoxLayout child Gjs_ui_shellEntry_CapsLockWarning natural height: 0.000000 < minimum 24

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with signal 5 in clutter_box_layout_allocate()
  ("ClutterBoxLayout child Gjs_ui_shellEntry_CapsLockWarning natural
  height: 0.00 < minimum 24.00 for width ...") when enable-
  animations=false

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Starting this morning after updating my focal system, some GPG/SSH key
  prompts will cause the entire shell to instantly crash. I also had a
  similar shell crash happen when trying to unlock my laptop after
  having it locked for a little while (but not suspended).

  This unfortunately isn't easy reproduced on demand, but I've had 5
  gnome-shell crashes over the past 4 hours when I have had none of the
  3 months prior, so something feels quite wrong and makes getting any
  work done quite difficult.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  4 08:45:46 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  LocalLibraries: 
/home/stgraber/data/code/go/deps/sqlite/.libs/libsqlite3.so.0.8.6
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
   () at /usr/lib/gnome-shell/libst-1.0.so
   () at /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
   () at /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
   clutter_actor_allocate () at 
/usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to focal on 2018-12-17 (443 days ago)
  UserGroups: adm dialout kvm libvirt lp lpadmin lxd plugdev sbuild scanner 
sudo video
  separator:

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

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

[Desktop-packages] [Bug 1866259] Re: Text clipped on password overlay dialogues

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Text clipped on password overlay dialogues

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released
Status in yaru-theme source package in Focal:
  Fix Released

Bug description:
  On focal with yaru-gtk-theme 20.04.2, the text in the password overlay
  dialogue boxes is clipped. Possibly the font is too big, or the
  dialogue box not wide enough?

  Attached is a screenshot of attempting to mount an encrypted disk image in
  gnome-disks, and I can also reproduce this issue trying to unlock a SSH key.

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

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

[Desktop-packages] [Bug 1866094] Re: Stray B being printed after switching workspaces with wayland

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Stray B being printed after switching workspaces with wayland

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

Bug description:
  The problem is that a stray "B" character is being printed to the
  terminal screen after switching work spaces with the Ctrl+Alt+{Up/Down
  arrows}.

  On the first workspace, I have a few applications running (Firefox is focused)
  On the second workspace I have gnome terminal 3.35.91 running in full screen 
(F11, so no window boarder) running.

  I Ctrl+Alt+Up Arrow to switch to the first workspace and do some
  things in FF and then Ctrl+Alt+Down Arrow to switch back to the second
  workspace and now see a "B" on the command line.

  This happens over and over.. I see the capital B on the commandline
  when I switch to this workspace where the terminal is fullscreened.

  Some things to note about when this happens:
  * This only happens with wayland
  * It happens fairly often but not 100% of the time
  * The key character created is always a "B"
  * I've only seen this key character be created on gnome-terminal
  * There are no journalctl logs generated when this occurs
  * I have to release the Ctrl+Alt+Up and then do Ctrl+Alt+Down to see the B. 
(If I keep Ctrl+Alt pressed and then do Up and Down, the B is not generated)
  * It seems more likely to happen if the first workspace is switched to, spend 
some time there just clicking things or typing or whatever, and then go back to 
the second workspace
  * It only happens if gnome-terminal is full screen'd with F11

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  4 17:24:36 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-13 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-02-28 (4 days ago)

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

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

[Desktop-packages] [Bug 1866419] Re: gnome-shell displays date incorrectly for nl_NL locale

[Bug Watch Updater]

** Changed in: gnome-desktop
   Status: Unknown => Fix Released

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

Title:
  gnome-shell displays date incorrectly for nl_NL locale

Status in gnome-desktop:
  Fix Released
Status in gnome-desktop3 package in Ubuntu:
  Fix Committed
Status in gnome-desktop3 source package in Eoan:
  Fix Committed
Status in gnome-desktop3 source package in Focal:
  Fix Committed

Bug description:
  I am running the regular edition of Ubuntu. I have my system set to
  the nl_NL locale. The clock display on the top bar of gnome-shell is
  displayed as "vr mrt 6 23:45:01". While the individual parts are
  translated correctly, the order is not. It should be "vr 6 mrt
  23:45:01".

  Steps to reproduce:
  - Install in Dutch
  - Observe that the clock in the top bar shows the month name before the day.

  Other notes:
  - Bug is present in at least 18.04, 19.04, 19.10 and the upcoming 20.04
  - Adding/removing parts to the date (like weekday, seconds, etc.) using 
gnome-tweaks does not make any difference: all combinations have this wrong 
date order.

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

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

[Desktop-packages] [Bug 1865221] Re: Workspace switcher scaling up and down depending on the number of active workspaces

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Workspace switcher scaling up and down depending on the number of
  active workspaces

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

Bug description:
  Between 2 and 4 active workspaces, the switcher is scaled down and up,
  playing tricks with my eyes ;P

  See the attached screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 21:54:18 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-10 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/zsh
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868520] Re: Clients fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784) [DRM_FORMAT_XRGB2101010]

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => New

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

Title:
  Clients fail to run with zwp_linux_dmabuf error (failed to import
  supplied dmabufs: Unsupported buffer format 808669784)
  [DRM_FORMAT_XRGB2101010]

Status in Mesa:
  New
Status in MPV:
  Unknown
Status in Mutter:
  Fix Released
Status in mesa package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  When attempting to run es2gears_wayland against GNOME Shell, it fails
  with:

  EGL_VERSION = 1.5
  vertex shader info: 
  fragment shader info: 
  info: 
  [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported 
buffer format 808669784

  The full wayland protocol trace is:

  [3104432.914]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3104432.972]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3104433.139] wl_display@1.delete_id(3)
  [3104433.175] wl_registry@2.global(1, "wl_drm", 2)
  [3104433.207] wl_registry@2.global(2, "wl_compositor", 4)
  [3104433.240]  -> wl_regis...@2.bind(2, "wl_compositor", 1, new id 
[unknown]@4)
  [3104433.285] wl_registry@2.global(3, "wl_shm", 1)
  [3104433.316] wl_registry@2.global(4, "wl_output", 2)
  [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
  [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3)
  [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1)
  [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2)
  [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1)
  [3104433.513] wl_registry@2.global(11, "wl_shell", 1)
  [3104433.542]  -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5)
  [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3)
  [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1)
  [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1)
  [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1)
  [3104433.699] wl_registry@2.global(16, "wl_seat", 5)
  [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
  [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1)
  [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1)
  [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104433.875] wl_registry@2.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
  [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1)
  [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1)
  [3104433.991] wl_callb...@3.done(3421)
  [3104436.266]  -> wl_display@1.get_registry(new id wl_registry@3)
  [3104436.279]  -> wl_disp...@1.sync(new id wl_callback@6)
  [3104436.647] wl_display@1.delete_id(6)
  [3104436.672] wl_registry@3.global(1, "wl_drm", 2)
  [3104436.726]  -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7)
  [3104436.744] wl_registry@3.global(2, "wl_compositor", 4)
  [3104436.780] wl_registry@3.global(3, "wl_shm", 1)
  [3104436.790] wl_registry@3.global(4, "wl_output", 2)
  [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3)
  [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3)
  [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1)
  [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2)
  [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1)
  [3104436.925] wl_registry@3.global(11, "wl_shell", 1)
  [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3)
  [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1)
  [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1)
  [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1)
  [3104436.990] wl_registry@3.global(16, "wl_seat", 5)
  [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1)
  [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1)
  [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1)
  [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104437.066]  -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id 
[unknown]@8)
  [3104437.083] wl_registry@3.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104437.096] wl_registry@3.global(23, "zwp_text_input_manager_v3", 1)
  [3104437.111] wl_registry@3.global(24, "gtk_text_input_manager", 1)
  [3104437.125] wl_registry@3.global(26, "wl_eglstream_controller", 1)
  [3104437.140] wl_callb...@6.done(3421)
  [3104437.146]  -> wl_disp...@1.sync(new id wl_callback@6)
  [3104437.333] wl_dis

[Desktop-packages] [Bug 1867548] Re: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Unknown => New

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

Title:
  Right Alt key is suddenly switched off after invoking Settings -
  Keyboard Shortcuts in Focal

Status in gnome-control-center:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-control-center source package in Focal:
  Confirmed

Bug description:
  As soon as the Keyboard Shortcuts tab window is invoked in the
  Settings Application, Right Alt key is switched off system-wide. This
  happens suddenly even without any action from the user - just simple
  invoking of the window is enough to break the settings.

  This obviously happens because of the new setting in the Keyboard
  Shortcuts appeared in focal: Alternate Characters Key. It sets Right
  Alt by default immediately as this window is opened. This setting
  doesn't have the Not Set option, so it is even not easy to switch back
  to the normal behavior. This setting can be unset only through the
  GNOME Tweaks application: Keyboard & Mouse - Additional Layout Options
  - Key to choose the 3rd level - uncheck the box Right Alt. But this is
  not a good workaround since the Alt key setting will be destroyed
  again as soon as Keyboard Shortcuts are visited in Settings next time.

  The reasonable workaround seems to be introduction an option Not Set
  in the setting Alternate Characters Key and making it default. This
  will fix this bug and will introduce a sane default value because not
  every keyboard layout has a third-option for the keys.

  This is quite significant UX flaw since nothing should be changed
  without explicit user action.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 15 22:33:08 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-04-25 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1865169] Re: volume and light not working in Gnome Shell 3.35

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  volume and light not working in Gnome Shell 3.35

Status in GNOME Shell:
  New
Status in gjs package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to GNOME shell 3.35, the speaker icon in top bar is
  missing and both volume and light sliders are set to 0. Changing
  volume and light from keyboard works, but has no effect in gnome shell
  dropdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-16.19-generic 5.4.22
  Uname: Linux 5.4.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 18:57:54 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-01 (118 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1866851] Re: lock screen scaled down backgound image in top left corner

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  lock screen scaled down backgound image in top left corner

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  The new lock screen in gnome 3.36 looks strange, as if the blurred
  background image is being scaled down to the top left corner of the
  screen.  background image being used is 1920x1440 pixel jpeg, display
  size is 3840x2160, with fractional scaling enabled and set to 175% on
  wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu19
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 10 07:38:52 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-17 (206 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-03-06 (3 days ago)

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

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

[Desktop-packages] [Bug 1865536] Re: OBS consumes all memory, fixed in upstream Mesa

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => Fix Released

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

Title:
  OBS consumes all memory, fixed in upstream Mesa

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  There is an issue where due to a Mesa bug OBS consumes all memory
  eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426.
  Unfortunately, this issue is in all recent Ubuntu versions.

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

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

[Desktop-packages] [Bug 1866275] Re: Password overlay dialogue breaks during screen lock while overlay present

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Password overlay dialogue breaks during screen lock while overlay
  present

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Focal:
  In Progress

Bug description:
  If you have a password overlay dialogue box present on your screen,
  for example, trying to mount an encrypted disk image from gnome-disks,
  or trying to unlock an ssh key, if the lock screen appears while the
  dialogue is in place, after unlocking the screen, you can still enter
  your password into the dialogue and the action still happens (mounting
  the disk image, unlocking the ssh key), but the dialogue box gets
  stuck and does not disappear.

  Steps for reproducing:

  1) In gnome-disks, make a small 10mb disk image, select ext4 and luks. Set a 
trivial password.
  2) Attempt to mount the encrypted disk image
  3) When the password unlock dialogue appears, lock your screen (super + L)
  4) Wake the screen up, unlock computer
  
  5) Enter password into existing dialogue
  6) The dialogue now cannot be dismissed.

  Logs:

  Mar 06 12:46:36 ubuntu0 udisksd[749]: Set up loop device /dev/loop5 (backed 
by /home/ubuntu/Documents/diskimage.img)
  Mar 06 12:46:37 ubuntu0 systemd[1]: fprintd.service: Succeeded.
  Mar 06 12:46:40 ubuntu0 dbus-daemon[703]: [system] Activating via systemd: 
service name='net.reactivated.Fprint' unit='fprintd.service' requested by 
':1.307' (uid=1000 pid=1506 comm=">
  Mar 06 12:46:40 ubuntu0 systemd[1]: Starting Fingerprint Authentication 
Daemon...
  Mar 06 12:46:40 ubuntu0 dbus-daemon[703]: [system] Successfully activated 
service 'net.reactivated.Fprint'
  Mar 06 12:46:40 ubuntu0 systemd[1]: Started Fingerprint Authentication Daemon.
  Mar 06 12:46:40 ubuntu0 gdm-password][1921]: pam_unix(gdm-password:auth): 
Couldn't open /etc/securetty: No such file or directory
  Mar 06 12:46:43 ubuntu0 gnome-shell[1506]: JS WARNING: 
[resource:///org/gnome/shell/gdm/authPrompt.js 316]: reference to undefined 
property "_defaultButtonWellActor"
  Mar 06 12:46:43 ubuntu0 gdm-password][1921]: pam_unix(gdm-password:auth): 
Couldn't open /etc/securetty: No such file or directory
  Mar 06 12:46:43 ubuntu0 gdm-password][1921]: gkr-pam: unlocked login keyring
  Mar 06 12:46:43 ubuntu0 NetworkManager[706]:   [1583452003.9911] 
agent-manager: 
agent[69f92bd444c1b400,:1.307/org.gnome.Shell.NetworkAgent/1000]: agent 
registered
  Mar 06 12:46:43 ubuntu0 dbus-daemon[1259]: [session uid=1000 pid=1259] 
Activating service name='org.freedesktop.FileManager1' requested by ':1.50' 
(uid=1000 pid=1506 comm="/usr/bin/gn>
  Mar 06 12:46:44 ubuntu0 dbus-daemon[1259]: [session uid=1000 pid=1259] 
Activating service name='org.gnome.Nautilus' requested by ':1.50' (uid=1000 
pid=1506 comm="/usr/bin/gnome-shell >
  Mar 06 12:46:44 ubuntu0 gnome-shell[1506]: Unable to mount volume 10.0 MB 
Encrypted: Gio.IOErrorEnum: An operation is already pending
  Mar 06 12:46:51 ubuntu0 udisksd[749]: Unlocked device /dev/loop5 as /dev/dm-3
  Mar 06 12:46:51 ubuntu0 kernel: EXT4-fs (dm-3): mounted filesystem without 
journal. Opts: (null)
  Mar 06 12:53:50 ubuntu0 gnome-shell[1506]: JS WARNING: 
[resource:///org/gnome/shell/ui/unlockDialog.js 762]: reference to undefined 
property "_authPrompt"
  Mar 06 12:53:50 ubuntu0 gnome-shell[1506]: JS ERROR: TypeError: 
this._authPrompt is undefined
     
_escape@resource:///org/gnome/shell/ui/unlockDialog.js:762:13

  Version info:
  - Ubuntu 20.04
  - gnome-shell 3.35.91-1ubuntu2

  Attached is a screencast demonstrating each of the steps for
  reproducing.

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

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

[Desktop-packages] [Bug 1865191] Re: Control center needs a keyboard shortcut for screen brightness

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Unknown => New

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

Title:
  Control center needs a keyboard shortcut for screen brightness

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

Bug description:
  The control center has no pre-made shortcut for screen brightnesss.
  There should at least be an option for screen brightness up and down,
  as there is for sound volume up and down, even if no keys are set by
  default.  As it is, one has to make a complex work-around involving a
  shell script and fiddling with /etc/sudoers.  Please add pre-made
  shortcuts for brightness up and brightness down under the section for
  Keyboard Shortcuts.

  Show Applications -> Settings -> Keyboard Shortcuts -> ???

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.35.91-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 19:26:25 2020
  InstallationDate: Installed on 2020-02-27 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1864274] Re: [iris regression] gfx corruption

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => New

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

Title:
  [iris regression] gfx corruption

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Focal:
  Confirmed

Bug description:
  Hello, after upgrading firefox (and many other packages) on focal
  today, I've got some video artifacts in firefox.

  When typing in text boxes and text fields, the new character is drawn
  very slowly, pixel-by-pixel, and isn't complete until the cursor has
  moved on. When larger portions of the screen are updated, it looks a
  lot like the entire window is being run through a video codec or you
  can see parts of the video memory from other processes. (But it looks
  more deliberate and predictable than either of these descriptions.)

  So far Firefox is the only application I've found that is affected.
  urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.

  I did get cairo package update today, but the changelog is just:

  pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
   -- Matthias Klose   Sat, 08 Feb 2020 11:15:23 +

  And an xorg update:

  xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
   -- Matthias Klose   Sat, 08 Feb 2020 11:21:28 +

  
  So I don't believe these are involved.

  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
  (rev 07)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 73.0.1+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sarnold3296 F pulseaudio
   /dev/snd/controlC0:  sarnold3296 F pulseaudio
  BuildID: 20200217142647
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  Channel: Unavailable
  Date: Sat Feb 22 05:41:10 2020
  ForcedLayersAccel: False
  IncompatibleExtensions:
   Pentadactyl - pentadac...@dactyl.googlecode.com
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  IpRoute:
   default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100 
   10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1 
   192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric 
100 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:737
  PrefSources: prefs.js
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1860764] Re: Line out audio device is missing after resume-from-suspend

[Kai-Heng Feng]

Can you please identify from what kernel version did the regression
start?

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

Title:
  Line out audio device is missing after resume-from-suspend

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this problem happened after i updated system
  when i power on after sleeping i have problem with sounds. it doesn't work.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2511 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (362 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1897 F pulseaudio
   /dev/snd/controlC2:  rob1897 F pulseaudio
   /dev/snd/controlC1:  rob1897 F pulseaudio
   /dev/snd/pcmC1D0p:   rob1897 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (428 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=574eb112-448b-4cfc-bed7-2c5a1ba42abf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (145 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when network-manager is not working [Assertion failure "G_IS_OBJECT (object)" in cc_object_storage_add_object]

[Bug Watch Updater]

** Changed in: network-manager
   Status: New => Fix Released

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

Title:
  gnome-control-center SIGABRT when network-manager is not working
  [Assertion failure "G_IS_OBJECT (object)" in
  cc_object_storage_add_object]

Status in gnome-control-center:
  New
Status in NetworkManager:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center. This problem was most recently seen with package version 
1:3.30.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b90090b3330514b0e5d6f1ed58c2260a77b8e5e8 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  ---

  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143

  ---

  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.

  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.

  [Potential Regression]
  I think it's not a potential regression.

  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

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

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

[Desktop-packages] [Bug 1807276] Re: Cannot open Onscreen Keyboard in Xorg

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Cannot open Onscreen Keyboard in Xorg

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

Bug description:
  Ubuntu 18.10 / GNOME Shell 3.30.1
  ALSO
  Ubuntu 18.04 LTS / GNOME Shell 3.28.1

  Steps to reproduce on our end:

  - Login (Xorg as default)
  - Attempt to swipe up with finger from below screen
  RESULT: It draws a thin vertical (desktop) selection box, but no OSK
  - Logout
  - Log back in, after first hitting 'gear' button to select 'Ubuntu on Wayland'
  - ps -e | grep Xwayland #shows 'Xwayland' process is running
  - Repeat swipe up with finger from below screen
  RESULT: OSK shows up as expected

  This has been verified both in 1920x1080 as well as 3840x2160
  resolutions (also with various scaling options selected)

  Issue is also logged upstream: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/839

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

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

[Desktop-packages] [Bug 1845623] Re: on screen keyboard leaves dark marks on screen after being hidden

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: New => Fix Released

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

Title:
  on screen keyboard leaves dark marks on screen after being hidden

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  Steps to reproduce:
  1. Make the on-screen keyboard appear by tapping on a text field on doing a 
swipe up on the screen with your finger (see video).
  2. Tap the arrow down key to hide the OSK

  Expected result: the OSK disappears

  Actual result: The OSK leaves dark traces on the sides of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 17:51:29 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1788429] Re: gnome-shell crashed with SIGSEGV in g_file_get_parent → _st_theme_resolve_url → _st_theme_node_ensure_background → st_theme_node_paint_equal → st_widget_recompute_

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in g_file_get_parent →
  _st_theme_resolve_url → _st_theme_node_ensure_background →
  st_theme_node_paint_equal → st_widget_recompute_style → ...
  clutter_actor_show → ScreenShield::activate() → ScreenShield::lock()

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.2-0ubuntu0.18.04.1, the problem page at 
https://errors.ubuntu.com/problem/a7a947c33583b6cc42b9caca5a5622d5efcc3501 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1722256] Re: Wifi connection status icon shows a "?" question mark when connected

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Wifi connection status icon shows a "?" question mark when connected

Status in GNOME Shell:
  New
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  https://bugzilla.gnome.org/show_bug.cgi?id=750260

  Wifi connection status icon on the top bar shows a "?" even when connected to 
a wifi network.
  ---
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-28 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Package: gnome-shell 3.26.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1790814] Re: Duplicate entries caused by debs and snaps offering the same application

[Bug Watch Updater]

** Changed in: gnome-software
   Status: Unknown => Fix Released

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

Title:
  Duplicate entries caused by debs and snaps offering the same
  application

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  As a user,
  when I search for a software package,
  I want to see either one, canonical option,
  or I want to see clear visual cues why a software piece is listed multiple 
times,
  So that I either don't have to choose,
  Or that I have enough visual information to make a choice.

  As can be seen in the screenshot, when searching for Gimp, I get two, 
slightly different options.
  As a software engineer, I know the different sources: snaps and debs. And I 
know the reason for having 
  two options. However, this is confusing, even when the cause is known.

  We need either:

  * An opinionated choice to be made: the "software" package should prefer one 
over the other. And list only that one. Commandline tools (apt, deb) still 
offer the choice to install the other option.
  * A visual cue why there are two. Information lacking is: the source: "Ubuntu 
Repository (deb)" or "Snap Store". Additional information is the version: often 
one or the other is newer, or preferred. Note that after clicking the through 
to the details, this information is made avaialble, albeit small and tucked 
away at the bottom. It also does not explain much there, either.

  Additionally, for sysadmins, an option to disable one or the other
  entirely would be useful. This may be in place in some way already,
  but I cannot find this in the configuration of the gnome-software.

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

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

[Desktop-packages] [Bug 864369] Re: Hibernate option missing from gnome-shell session menu

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Hibernate option missing from gnome-shell session menu

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in Baltix:
  New

Bug description:
  I upgraded to Oneiric recently and installed gnome-shell because unity
  still has some pretty serious functionality problems, but discovered
  that the gnome-shell session menu doesn't have a Hibernate option,
  just Suspend.

  I never use suspend, but use hibernate at least twice a day, so this
  regression in functionality is a pain.

  The alternative-status-menu shell extension
  (http://live.gnome.org/GnomeShell/Extensions) for gnome-shell adds the
  Hibernate option back, but it apparently isn't packaged for Ubuntu
  yet.

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

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

[Desktop-packages] [Bug 1844575] Re: Pixelated fonts sometimes

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: New => Fix Released

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

Title:
  Pixelated fonts sometimes

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Running under wayland, with fractional scaling enabled and set to 175%
  on laptop screen, 100% on external screen, sometimes windows like
  nautilus or the file chooser get pixelated fonts (see screenshot).
  Seen this mostly on the 100% external screen, and it goes away if
  maximizing the window or moving the window back and forth between
  screens a few times.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 18 12:59:50 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-17 (32 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-18 (0 days ago)

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

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

[Desktop-packages] [Bug 1868399] Re: Ghost copies of foreground dialogues when using GNOME Magnifier

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => New

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

Title:
  Ghost copies of foreground dialogues when using GNOME Magnifier

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Affected version

  Tested with Ubuntu 20.04 current daily build using Xorg. Mutter
  version 3.36.

  Bug summary

  When using the GNOME magnifier feature ghost copies of dialogues such
  as the Alt+F2 window or the password prompt appear if the magnified
  view moves away from the dialogue.

  Steps to reproduce

  1. Enable GNOME magnifier by pressing Supper + Alt + 8.
  2. Press Alt+F2 to open the command dialogue.
  3. Use the mouse to pan around the screen.

  
  What happened

  A slightly fadded copy of the dialogue will move around the screen,
  keeping its relative position.

  What did you expect to happen

  This should not happen. The dialogue should be displayed once and
  should move appropriately when the magnifier view pans away from it.

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.35.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 21 19:43:49 2020
  InstallationDate: Installed on 2020-03-20 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200320)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1849573] Re: No way to specify tls-version-min or tls-version-max, please include the config options in the GUI config panel.

[Bug Watch Updater]

** Changed in: network-manager-openvpn
   Status: New => Fix Released

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

Title:
  No way to specify tls-version-min or tls-version-max, please include
  the config options in the GUI config panel.

Status in NetworkManager-OpenVPN:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Fix Released

Bug description:
  The OpenVPN plugin for Network Manager does not have any mechanisms to
  interpret tls-version-{min,max} directives for OpenVPN.

  In Debian upstream, especially in Buster and Unstable, they disable
  TLS 1.0, 1.1, and 1.2 by default and use only TLS 1.3 by default.
  Therefore, with OpenVPN servers that only use TLS 1.2 or older, it is
  impossible to establish a tunnel to those locations *unless* you
  specify tls-version-{min,max} in the configurations.

  This can be done in OVPN files for OpenVPN directly, but there is
  currently no mechanism to do this in the GUI.

  This is tracked in Debian https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=933177 as the original cause for TLS 1.3
  support, but if Ubuntu ever defaults OpenSSL to not have TLS 1.0-1.2
  support enabled by default, we will be out of luck.

  Upstream, GNOME has not yet merged a merge request which would add
  this option to the GUI: https://gitlab.gnome.org/GNOME/NetworkManager-
  openvpn/merge_requests/15

  Testing in Debian, the patch works against NetworkManager OpenVPN
  there.  I am currently testing these in Focal, Eoan, and Bionic to see
  if this is something we can possibly include at a future date to fix
  this issue long-term.

  In the interim, this tracks the request to get these features in.

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

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

[Desktop-packages] [Bug 1867080] Re: [radeon] No mouse cursor drawn in Wayland session

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  [radeon] No mouse cursor drawn in Wayland session

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  When I upgraded my desktop yesterday, I could no longer see the mouse
  cursor on the screen.  It still responded to mouse clicks (e.g.
  context menu on right click, pushing the mouse to the top left and
  left clicking went to spread mode, etc).

  This only seems to affect the Wayland session: when I switched back to
  X11 the mouse cursor was visible again.  I also noticed that the mouse
  cursor is absent on the GDM login screen, which I understand is also a
  Wayland based gnome-shell session.

  I tried reproducing the bug on my laptop, but the mouse cursor shows
  just fine there.  The main differences between the systems are the GPU
  (radeon vs. intel) and number of monitors (dual screen vs. single).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 12 10:28:55 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2013-10-29 (2325 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-02-02 (38 days ago)

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

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

[Desktop-packages] [Bug 1864326] Re: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with SIGABRT, assertion failed:
  src/core/window.c:4853:set_workspace_state: 'window->unmanaging ||
  workspace != NULL' should be TRUE

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8

  Gnome Shell crashes and restarts when I try to open a dialog window.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu17
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 22 21:15:33 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-02-04 (18 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: Upgraded to focal on 2020-02-22 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: New => Fix Released

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

Title:
  gnome-shell crashed with SIGABRT:
  mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion
  failed: (workspace == NULL)

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

Bug description:
  https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b

  gnome-shell crashes with this bug every time that:

  * I am editing a file in geany
  * I open the Find window (CTRL-F) and it opens on another monitor
  * I type in some un-findable text in the find window and press ENTER (or 
click the Next button)

  The system beeps to indicate that the text isn't found, but then
  crashes.

  Note especially that the find window must be on the other monitor - if
  it's on the same monitor as geany, gnome-shell doesn't crash.

  (Note: I originally thought that if I moved the find window to the
  other window and then searched, gnome-shell crashed, but I think what
  happens is a) I open the window, b) I move it, search for something,
  and it works, c) I close it and re-open it - it then opens on the
  other monitor and searching will crash gnome-shell.)

  gnome-shell restarts, but the crash causes data loss, as most of the
  running applications don't reappear when it restarts.

  In case it's relevant, I have a laptop screen set at 2048x1152 and an
  external monitor configured to be above it at 2560x1440.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  Uname: Linux 5.4.0-050400rc4-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 22 10:37:36 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1570619894
  InstallationDate: Installed on 2019-07-01 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/rocko
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  separator:

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

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

[Desktop-packages] [Bug 1856160] Re: Bar between bread crumbs and search icon.

[Bug Watch Updater]

** Changed in: nautilus
   Status: New => Fix Released

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

Title:
  Bar between bread crumbs and search icon.

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

Bug description:
  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu1
  3) There should be no bar between bread crumbs and the search icon. If I 
remember correctly.
  4) There is a bar between bread crumbs and search icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 12 03:00:41 2019
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'244'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1216, 604)'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2019-10-28 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1868293] Re: gnome-shell crashed in meta_workspace_index: Workspace does not exist to index!

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  gnome-shell crashed in meta_workspace_index: Workspace does not exist
  to index!

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

Bug description:
  https://errors.ubuntu.com/problem/5340b1db97f4c8202e6c7a695097f4f6c22a0695

  ---

  gnome-shell crashed when I tried to move fireforx from one workspace
  to another.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 18:49:14 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-03-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_bug () at /lib/x86_64-linux-gnu/libmutter-6.so.0
   meta_workspace_index () at /lib/x86_64-linux-gnu/libmutter-6.so.0
   () at /lib/x86_64-linux-gnu/libffi.so.7
   () at /lib/x86_64-linux-gnu/libffi.so.7
   () at /lib/libgjs.so.0
  Title: gnome-shell crashed with SIGABRT in meta_bug()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1813893] Re: OpenVPN LZ4 compression not working in Networkmanager

[Bug Watch Updater]

** Changed in: network-manager-openvpn
   Status: New => Fix Released

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

Title:
  OpenVPN LZ4 compression not working in Networkmanager

Status in NetworkManager-OpenVPN:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Triaged

Bug description:
  Hi there,

  when importing an ovpn profile (from a PFsense in this case) where 
compression is set to LZ4 it won't work.
  Network manager won't save the config properly, as it does not seem to 
support lz4?

  When I manually use

  sudo openvpn --config myconfig.ovpn

  it works just fine.

  OpenVPN 2.4.6 x86_64-pc-linux-gnu

  is being used right now.

  Best regards
  David

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

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

[Desktop-packages] [Bug 1826439] Re: tracker-extract causes system lock-up due to 100% CPU and memory usage

[Bug Watch Updater]

** Changed in: tracker
   Status: New => Fix Released

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

Title:
  tracker-extract causes system lock-up due to 100% CPU and memory usage

Status in Tracker:
  Fix Released
Status in tracker-miners package in Ubuntu:
  Triaged

Bug description:
  Immediately after upgrading from 18.10 to 19.04, my computer froze
  about 30-40 secs after I logged in.

  I finally tracked this down to the tracker-extract process. This
  process starts within about half a minute after logging in. When it
  starts, it's a matter of seconds until it consumes 100% CPU and all
  available system memory (I have 16 GB on an Intel 8700k @ 4.8 GHz and
  SSD/M.2)

  This only happens with my regular user. It does not occur with a newly
  created user (I guess due to the large amount of files within my home
  directory).

  It happens every time I log in.

  I'm filing this bug against the Ubuntu package because this phenomenon
  causes the entire system to freeze up completely. The wheels seem to
  fall off the wagon in such a way the system can't recover. The only
  alternative at this point is a hard reset or SysRQ REISUB. It is not
  possible to switch to a TTY (ctrl-alt-fX), and it's not possible to
  ssh in from another machine. SysRQ-k does not work. I've tried logging
  in to a TTY before logging in to the GUI, and then switching to the
  TTY quickly after logging in to the GUI. Surely enough - a few seconds
  later the TTY locks up as well.

  I can reproduce the problem easily, but I'm not sure how to go about
  debugging it - would be happy to assist. I can't let the process run
  for more than a few seconds at a time so bear that in mind. I tried
  grabbing the process in gdb, but the package seem to be stripped of
  debug symbols. I did a strace -p for a few seconds and the process
  _appears_ to be symlinking files in my homedirectory to a subdirectory
  within /tmp (?!?) - I can get more details here if it helps.

  A bonus question from me is how it's possible that a process run by a
  user can take down the entire system in this manner.

  tracker-extract and tracker-miner-fs: 2.1.6-1
  tracker: 2.1.8-2
  kernel: 5.0.0-13-generic (I've also tried 5.0.9)

  I've attached a photo(!) of top illustrating what's going on (at this
  point the machine has already frozen up. There appears to still be
  some memory available, but this is just because top never got around
  to report the true numbers before the machine died.)

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

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

[Desktop-packages] [Bug 1868207] Re: Fractional scaling window sizes incorrect after resume from suspend

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => New

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

Title:
  Fractional scaling window sizes incorrect after resume from suspend

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  LP bug as requested at
  https://gitlab.gnome.org/GNOME/mutter/issues/1122

  From the summary there:

  With fractional scaling enabled, after resume from suspend, maximised
  & half tiled windows have been resized/scaled so they are too large
  for the screen, and as a result no longer fit on the screen.  Not sure
  if it also happens to windows that aren't in either of these states, I
  rarely have any. Further, most but not all windows are scaled like
  this. Epiphany and Terminal definitely are, maybe XWindows clients
  like Emacs aren't?

  Under 3.34, shell/mutter seemed to notice this and would visibly snap
  the window sizes back to what they should be. Under 3.36, that no
  longer seems to happen - the windows stay too big and I need to
  manually fix them.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.35.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 20 16:54:48 2020
  InstallationDate: Installed on 2018-08-13 (584 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-03-07 (12 days ago)

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

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

[Desktop-packages] [Bug 1868520] Re: Clients fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784) [DRM_FORMAT_XRGB2101010]

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  Clients fail to run with zwp_linux_dmabuf error (failed to import
  supplied dmabufs: Unsupported buffer format 808669784)
  [DRM_FORMAT_XRGB2101010]

Status in Mesa:
  New
Status in MPV:
  Unknown
Status in Mutter:
  Fix Released
Status in mesa package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  When attempting to run es2gears_wayland against GNOME Shell, it fails
  with:

  EGL_VERSION = 1.5
  vertex shader info: 
  fragment shader info: 
  info: 
  [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported 
buffer format 808669784

  The full wayland protocol trace is:

  [3104432.914]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3104432.972]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3104433.139] wl_display@1.delete_id(3)
  [3104433.175] wl_registry@2.global(1, "wl_drm", 2)
  [3104433.207] wl_registry@2.global(2, "wl_compositor", 4)
  [3104433.240]  -> wl_regis...@2.bind(2, "wl_compositor", 1, new id 
[unknown]@4)
  [3104433.285] wl_registry@2.global(3, "wl_shm", 1)
  [3104433.316] wl_registry@2.global(4, "wl_output", 2)
  [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
  [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3)
  [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1)
  [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2)
  [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1)
  [3104433.513] wl_registry@2.global(11, "wl_shell", 1)
  [3104433.542]  -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5)
  [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3)
  [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1)
  [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1)
  [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1)
  [3104433.699] wl_registry@2.global(16, "wl_seat", 5)
  [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
  [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1)
  [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1)
  [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104433.875] wl_registry@2.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
  [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1)
  [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1)
  [3104433.991] wl_callb...@3.done(3421)
  [3104436.266]  -> wl_display@1.get_registry(new id wl_registry@3)
  [3104436.279]  -> wl_disp...@1.sync(new id wl_callback@6)
  [3104436.647] wl_display@1.delete_id(6)
  [3104436.672] wl_registry@3.global(1, "wl_drm", 2)
  [3104436.726]  -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7)
  [3104436.744] wl_registry@3.global(2, "wl_compositor", 4)
  [3104436.780] wl_registry@3.global(3, "wl_shm", 1)
  [3104436.790] wl_registry@3.global(4, "wl_output", 2)
  [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3)
  [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3)
  [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1)
  [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2)
  [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1)
  [3104436.925] wl_registry@3.global(11, "wl_shell", 1)
  [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3)
  [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1)
  [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1)
  [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1)
  [3104436.990] wl_registry@3.global(16, "wl_seat", 5)
  [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1)
  [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1)
  [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1)
  [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104437.066]  -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id 
[unknown]@8)
  [3104437.083] wl_registry@3.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104437.096] wl_registry@3.global(23, "zwp_text_input_manager_v3", 1)
  [3104437.111] wl_registry@3.global(24, "gtk_text_input_manager", 1)
  [3104437.125] wl_registry@3.global(26, "wl_eglstream_controller", 1)
  [3104437.140] wl_callb...@6.done(3421)
  [3104437.146]  -> wl_disp...@1.sync(new id wl_callback@6)
  [3104437.

[Desktop-packages] [Bug 1869635] Re: the menu "Dash to Dock Settings" is visible

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1869635

** Tags added: iso-testing

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

Title:
  the menu "Dash to Dock Settings" is visible

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

Bug description:
  When the user performs a right-button mouse click on the "Show
  Applications" button of the Ubuntu Dock then a "Dash to Dock Settings"
  menu option appears as shown in the attached image.

  Normally, this menu option is only available on the original "Dash to
  Dock" GNOME shell extension used as the basis for the Ubuntu Dock and
  it should not be visible or functional on the Ubuntu Dock itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 02:31:58 2020
  InstallationDate: Installed on 2020-02-12 (46 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to focal on 2020-03-27 (2 days ago)

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

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

[Desktop-packages] [Bug 1862544] Re: Double-clicking a folder sometimes opens another, recently visited folder

[Bug Watch Updater]

** Changed in: nautilus
   Status: Unknown => Fix Released

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

Title:
  Double-clicking a folder sometimes opens another, recently visited
  folder

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

Bug description:
  The following happens for me very frequently. Say I have the following
  folder structure:

  A
  |- B
  |- C
  |- some other files/folders...

  I'm currently browsing the folder B. Then I go up one level, to A, by
  pressing backspace. I then immediately double-click on the icon for
  folder C to enter into it. Very frequently, this instead takes me back
  into folder B.

  What appears to be happening is that when I go up from B to A, if I
  double-click the icon for C while the contents of A are being read
  from disk and the thumbnails are being refreshed, the program
  registers that I have double-clicked something, but after the
  thumbnail refresh has finished, the "selected folder" reverts back to
  B. Hence, the program thinks I double-clicked the icon for B instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
  Uname: Linux 4.15.0-76-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  9 21:42:19 2020
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2020-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1848951] Re: High CPU when just moving the mouse

[Bug Watch Updater]

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  High CPU when just moving the mouse

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had
  Ubuntu 16.04 version but didn't have any such problems with the cpu
  usage.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around for 18.04
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D2V
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1799266] Re: gnome-shell uses high CPU when simply moving windows

[Bug Watch Updater]

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  gnome-shell uses high CPU when simply moving windows

Status in Mutter:
  Fix Released
Status in gjs package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in gjs source package in Bionic:
  Fix Released
Status in gjs source package in Cosmic:
  Fix Released
Status in gjs source package in Disco:
  Fix Released

Bug description:
  After doing a stock install Ubuntu 18.04.1 LTS on an imac 27" 2010 
  8G ram, Intel® Core™ i7 CPU 870 @ 2.93GHz × 8

  Simply moving a window around on the screen increases the cpu usage
  by gnome-shell to 44%. When displaying a movie, totem takes 10%, gnome-shell 
takes 22%.
  etc etc

  System:Host: oldie Kernel: 4.15.0-36-generic x86_64 bits: 64 Desktop: 
Gnome 3.28.3
 Distro: Ubuntu 18.04.1 LTS
  Machine:   Device: desktop System: Apple product: iMac11 3 v: 1.0 serial: N/A
 Mobo: Apple model: Mac-F2238BAE v: iMac11 3 serial: N/A
 UEFI: Apple v: IM112.88Z.0057.B01.1112090906 date: 12/09/11
  CPU:   Quad core Intel Core i7 870 (-MT-MCP-) cache: 8192 KB
 clock speeds: max: 2927 MHz 1: 1271 MHz 2: 1206 MHz 3: 1374 MHz 4: 
1271 MHz 5: 1377 MHz 6: 1266 MHz
 7: 1693 MHz 8: 1279 MHz
  Graphics:  Card: Advanced Micro Devices [AMD/ATI] Broadway PRO [Mobility 
Radeon HD 5850]
 Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 
2560x1440@59.95hz
 OpenGL: renderer: AMD JUNIPER (DRM 2.50.0 / 4.15.0-36-generic, 
LLVM 6.0.0) version: 3.3 Mesa 18.0.5
  Audio: Card-1 Intel 5 Series/3400 Series High Definition Audio driver: 
snd_hda_intel
 Card-2 Advanced Micro Devices [AMD/ATI] Juniper HDMI Audio [Radeon 
HD 5700 Series]
 driver: snd_hda_intel
 Sound: Advanced Linux Sound Architecture v: k4.15.0-36-generic
  Network:   Card-1: Broadcom Limited NetXtreme BCM5764M Gigabit Ethernet PCIe 
driver: tg3
 IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: 
c4:2c:03:30:ce:8e
 Card-2: Qualcomm Atheros AR928X Wireless Network Adapter 
(PCI-Express) driver: ath9k
 IF: wls1 state: down mac: d8:30:62:67:2a:19
  Drives:HDD Total Size: 2500.5GB (38.0% used)
 ID-1: /dev/sda model: WDC_WD1001FALS size: 1000.2GB
 ID-2: USB /dev/sdb model: MK1059GSM size: 1000.2GB
 ID-3: USB /dev/sdd model: Elements_10B8 size: 500.1GB
  Partition: ID-1: / size: 226G used: 125G (58%) fs: ext4 dev: /dev/sda2
 ID-2: /home size: 701G used: 876M (1%) fs: btrfs dev: /dev/sda4
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 56.0C mobo: N/A
 Fan Speeds (in rpm): cpu: 936
  Info:  Processes: 342 Uptime: 3:07 Memory: 2087.3/7967.4MB Client: Shell 
(bash) inxi: 2.3.56

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 19:09:59 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-10-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1860764] Re: Line out audio device is missing after resume-from-suspend

[Daniel van Vugt]

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

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

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

Title:
  Line out audio device is missing after resume-from-suspend

Status in linux package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  this problem happened after i updated system
  when i power on after sleeping i have problem with sounds. it doesn't work.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2511 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (362 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1897 F pulseaudio
   /dev/snd/controlC2:  rob1897 F pulseaudio
   /dev/snd/controlC1:  rob1897 F pulseaudio
   /dev/snd/pcmC1D0p:   rob1897 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (428 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=574eb112-448b-4cfc-bed7-2c5a1ba42abf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (145 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1860764] Re: Line out audio device is missing after resume-from-suspend

[Robert]

So right now it works well. I retested several times. Why ?. I don't
know. You can close the problem

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

Title:
  Line out audio device is missing after resume-from-suspend

Status in linux package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  this problem happened after i updated system
  when i power on after sleeping i have problem with sounds. it doesn't work.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2511 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (362 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1897 F pulseaudio
   /dev/snd/controlC2:  rob1897 F pulseaudio
   /dev/snd/controlC1:  rob1897 F pulseaudio
   /dev/snd/pcmC1D0p:   rob1897 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (428 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=574eb112-448b-4cfc-bed7-2c5a1ba42abf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (145 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1865221] Re: Workspace switcher scaling up and down depending on the number of active workspaces

[Michał Sawicz]

I can confirm this is fixed now.

$ apt policy gnome-shell
gnome-shell:
  Installed: 3.36.0-2ubuntu1
  Candidate: 3.36.0-2ubuntu1
  Version table:
 *** 3.36.0-2ubuntu1 500
500 http://pl.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  Workspace switcher scaling up and down depending on the number of
  active workspaces

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Between 2 and 4 active workspaces, the switcher is scaled down and up,
  playing tricks with my eyes ;P

  See the attached screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 21:54:18 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-10 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/zsh
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[APW]

HP 830 G6
Ubuntu 18.04.4 LTS
5.3.0-42-generic 
Similar to #30.  Curiously, audio and mic worked for a few days when adding 
   options snd-hda-intel dmic_detect=0
then mic disappeared.  Mic reappears but doesn't work after adding
   options snd-hda-intel dmic_detect=0
   options snd-hda-intel index=0 model=laptop-dmic

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions

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

[Desktop-packages] [Bug 1869652] Re: 1:6.4.2-0ubuntu2 breaks ISO builds where libreoffice is seeded

[Rico Tzschichholz]

libreoffice 1:6.4.2-0ubuntu3

https://people.ubuntu.com/~ricotz/sponsoring/

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

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

Title:
  1:6.4.2-0ubuntu2 breaks ISO builds where libreoffice is seeded

Status in libreoffice package in Ubuntu:
  New

Bug description:
  1:6.4.2-0ubuntu2 breaks Focal ISO builds where libreoffice is seeded

  e.g.

  
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/focal/ubuntu-mate/+build/209527
  
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/focal/kubuntu/+build/209553
  
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/focal/xubuntu/+build/209524

  The following packages have unmet dependencies:
   libreoffice-core : Conflicts: libreoffice-core-nogui but 1:6.4.2-0ubuntu2 is 
to be installed
   libreoffice-core-nogui : Conflicts: libreoffice-core but 1:6.4.2-0ubuntu2 is 
to be installed
    Breaks: libreoffice-calc but 1:6.4.2-0ubuntu2 is to 
be installed
    Breaks: libreoffice-gtk3 but 1:6.4.2-0ubuntu2 is to 
be installed
  E: Unable to correct problems, you have held broken packages.

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

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

[Desktop-packages] [Bug 1866999] Re: gnome-calendar does not sync with Google Calendar

[Jeffrey Bouter]

I'm having the same issue, on 20.04, but then with my Nextcloud
calendars. It worked on 3.35.9, but no longer on 3.36

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

Title:
  gnome-calendar does not sync with Google Calendar

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my 
Google Calendar.
  Online accounts is activated and, for example, gnome-contacts does show the 
contacts I have in Google.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-calendar 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 09:47:25 2020
  InstallationDate: Installed on 2018-02-23 (746 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago)

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

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

[Desktop-packages] [Bug 1862053]

[Bergner-gcc]

Simple backports to GCC 8 and 9 exposed some bugs that have already been
fixed on trunk.  The following patch resubmission includes those extra
fixes that need backports too:

https://gcc.gnu.org/ml/gcc-patches/2020-02/msg01253.html

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc-9 package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053]

[Jakub-gcc]

Caused PR93974.

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc-9 package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053] Re: Compiler gets stuck (or extremely slow) on ppc64el

[Bug Watch Updater]

** Changed in: gcc
   Status: In Progress => Confirmed

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc-9 package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053]

[Cvs-commit]

The releases/gcc-8 branch has been updated by Peter Bergner
:

https://gcc.gnu.org/g:53efbfe030a5fda41e5e7856d76ea827dd09f49c

commit r8-10050-g53efbfe030a5fda41e5e7856d76ea827dd09f49c
Author: Peter Bergner 
Date:   Sun Feb 23 22:04:44 2020 -0600

rs6000: Fix infinite loop building ghostscript and icu [PR93658]

Fix rs6000_legitimate_address_p(), which erroneously marks a valid Altivec
address as being invalid, which causes LRA's process_address()  to go into
an infinite loop spilling the same address over and over again.
Include Mike's earlier commits that fix bugs this patch exposes.

Backport from master
2020-02-20  Peter Bergner  

PR target/93658
* config/rs6000/rs6000.c (rs6000_legitimate_address_p): Handle VSX
vector modes.

* gcc.target/powerpc/pr93658.c: New test.
* gcc.target/powerpc/vsx-vector-6-le.c: Update fragile insn count.

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc-9 package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053]

[Bergner-gcc]

Fixed everywhere.

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc-9 package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053]

[Cvs-commit]

The releases/gcc-9 branch has been updated by Peter Bergner
:

https://gcc.gnu.org/g:066184a282b622ac6880150eb4e42fe57881b606

commit r9-8269-g066184a282b622ac6880150eb4e42fe57881b606
Author: Peter Bergner 
Date:   Sun Feb 23 18:22:57 2020 -0600

rs6000: Fix infinite loop building ghostscript and icu [PR93658]

Fix rs6000_legitimate_address_p(), which erroneously marks a valid Altivec
address as being invalid, which causes LRA's process_address()  to go into
an infinite loop spilling the same address over and over again.
Include Mike's earlier commits that fix bugs this patch exposes.

Backport from master
2020-02-20  Peter Bergner  

PR target/93658
* config/rs6000/rs6000.c (rs6000_legitimate_address_p): Handle VSX
vector modes.

* gcc.target/powerpc/pr93658.c: New test.

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc-9 package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053]

[Jakub-gcc]

GCC 9.3.0 has been released, adjusting target milestone.

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc-9 package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053]

[Jakub-gcc]

The fixes have been reverted for 9.3/8.4.

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc-9 package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1866275] Re: Password overlay dialogue breaks during screen lock while overlay present

[Daniel van Vugt]

Not a priority at all. It's really obscure and difficult to encounter:

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2321#note_744172

Also it's not a security issue.

** Changed in: gnome-shell (Ubuntu Focal)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

** Changed in: gnome-shell (Ubuntu Focal)
   Status: In Progress => New

** Tags added: rls-ff-notfixing

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2321
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2321

** Tags removed: champagne

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2446
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2446

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

Title:
  Password overlay dialogue breaks during screen lock while overlay
  present

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell source package in Focal:
  New

Bug description:
  If you have a password overlay dialogue box present on your screen,
  for example, trying to mount an encrypted disk image from gnome-disks,
  or trying to unlock an ssh key, if the lock screen appears while the
  dialogue is in place, after unlocking the screen, you can still enter
  your password into the dialogue and the action still happens (mounting
  the disk image, unlocking the ssh key), but the dialogue box gets
  stuck and does not disappear.

  Steps for reproducing:

  1) In gnome-disks, make a small 10mb disk image, select ext4 and luks. Set a 
trivial password.
  2) Attempt to mount the encrypted disk image
  3) When the password unlock dialogue appears, lock your screen (super + L)
  4) Wake the screen up, unlock computer
  
  5) Enter password into existing dialogue
  6) The dialogue now cannot be dismissed.

  Logs:

  Mar 06 12:46:36 ubuntu0 udisksd[749]: Set up loop device /dev/loop5 (backed 
by /home/ubuntu/Documents/diskimage.img)
  Mar 06 12:46:37 ubuntu0 systemd[1]: fprintd.service: Succeeded.
  Mar 06 12:46:40 ubuntu0 dbus-daemon[703]: [system] Activating via systemd: 
service name='net.reactivated.Fprint' unit='fprintd.service' requested by 
':1.307' (uid=1000 pid=1506 comm=">
  Mar 06 12:46:40 ubuntu0 systemd[1]: Starting Fingerprint Authentication 
Daemon...
  Mar 06 12:46:40 ubuntu0 dbus-daemon[703]: [system] Successfully activated 
service 'net.reactivated.Fprint'
  Mar 06 12:46:40 ubuntu0 systemd[1]: Started Fingerprint Authentication Daemon.
  Mar 06 12:46:40 ubuntu0 gdm-password][1921]: pam_unix(gdm-password:auth): 
Couldn't open /etc/securetty: No such file or directory
  Mar 06 12:46:43 ubuntu0 gnome-shell[1506]: JS WARNING: 
[resource:///org/gnome/shell/gdm/authPrompt.js 316]: reference to undefined 
property "_defaultButtonWellActor"
  Mar 06 12:46:43 ubuntu0 gdm-password][1921]: pam_unix(gdm-password:auth): 
Couldn't open /etc/securetty: No such file or directory
  Mar 06 12:46:43 ubuntu0 gdm-password][1921]: gkr-pam: unlocked login keyring
  Mar 06 12:46:43 ubuntu0 NetworkManager[706]:   [1583452003.9911] 
agent-manager: 
agent[69f92bd444c1b400,:1.307/org.gnome.Shell.NetworkAgent/1000]: agent 
registered
  Mar 06 12:46:43 ubuntu0 dbus-daemon[1259]: [session uid=1000 pid=1259] 
Activating service name='org.freedesktop.FileManager1' requested by ':1.50' 
(uid=1000 pid=1506 comm="/usr/bin/gn>
  Mar 06 12:46:44 ubuntu0 dbus-daemon[1259]: [session uid=1000 pid=1259] 
Activating service name='org.gnome.Nautilus' requested by ':1.50' (uid=1000 
pid=1506 comm="/usr/bin/gnome-shell >
  Mar 06 12:46:44 ubuntu0 gnome-shell[1506]: Unable to mount volume 10.0 MB 
Encrypted: Gio.IOErrorEnum: An operation is already pending
  Mar 06 12:46:51 ubuntu0 udisksd[749]: Unlocked device /dev/loop5 as /dev/dm-3
  Mar 06 12:46:51 ubuntu0 kernel: EXT4-fs (dm-3): mounted filesystem without 
journal. Opts: (null)
  Mar 06 12:53:50 ubuntu0 gnome-shell[1506]: JS WARNING: 
[resource:///org/gnome/shell/ui/unlockDialog.js 762]: reference to undefined 
property "_authPrompt"
  Mar 06 12:53:50 ubuntu0 gnome-shell[1506]: JS ERROR: TypeError: 
this._authPrompt is undefined
     
_escape@resource:///org/gnome/shell/ui/unlockDialog.js:762:13

  Version info:
  - Ubuntu 20.04
  - gnome-shell 3.35.91-1ubuntu2

  Attached is a screencast demonstrating each of the steps for
  reproducing.

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

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

[Desktop-packages] [Bug 1866275] Re: Password overlay dialogue breaks during screen lock while overlay present

[Daniel van Vugt]

... so we can wait for upstream to fix it, along with its sister bug:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2446

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

Title:
  Password overlay dialogue breaks during screen lock while overlay
  present

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell source package in Focal:
  New

Bug description:
  If you have a password overlay dialogue box present on your screen,
  for example, trying to mount an encrypted disk image from gnome-disks,
  or trying to unlock an ssh key, if the lock screen appears while the
  dialogue is in place, after unlocking the screen, you can still enter
  your password into the dialogue and the action still happens (mounting
  the disk image, unlocking the ssh key), but the dialogue box gets
  stuck and does not disappear.

  Steps for reproducing:

  1) In gnome-disks, make a small 10mb disk image, select ext4 and luks. Set a 
trivial password.
  2) Attempt to mount the encrypted disk image
  3) When the password unlock dialogue appears, lock your screen (super + L)
  4) Wake the screen up, unlock computer
  
  5) Enter password into existing dialogue
  6) The dialogue now cannot be dismissed.

  Logs:

  Mar 06 12:46:36 ubuntu0 udisksd[749]: Set up loop device /dev/loop5 (backed 
by /home/ubuntu/Documents/diskimage.img)
  Mar 06 12:46:37 ubuntu0 systemd[1]: fprintd.service: Succeeded.
  Mar 06 12:46:40 ubuntu0 dbus-daemon[703]: [system] Activating via systemd: 
service name='net.reactivated.Fprint' unit='fprintd.service' requested by 
':1.307' (uid=1000 pid=1506 comm=">
  Mar 06 12:46:40 ubuntu0 systemd[1]: Starting Fingerprint Authentication 
Daemon...
  Mar 06 12:46:40 ubuntu0 dbus-daemon[703]: [system] Successfully activated 
service 'net.reactivated.Fprint'
  Mar 06 12:46:40 ubuntu0 systemd[1]: Started Fingerprint Authentication Daemon.
  Mar 06 12:46:40 ubuntu0 gdm-password][1921]: pam_unix(gdm-password:auth): 
Couldn't open /etc/securetty: No such file or directory
  Mar 06 12:46:43 ubuntu0 gnome-shell[1506]: JS WARNING: 
[resource:///org/gnome/shell/gdm/authPrompt.js 316]: reference to undefined 
property "_defaultButtonWellActor"
  Mar 06 12:46:43 ubuntu0 gdm-password][1921]: pam_unix(gdm-password:auth): 
Couldn't open /etc/securetty: No such file or directory
  Mar 06 12:46:43 ubuntu0 gdm-password][1921]: gkr-pam: unlocked login keyring
  Mar 06 12:46:43 ubuntu0 NetworkManager[706]:   [1583452003.9911] 
agent-manager: 
agent[69f92bd444c1b400,:1.307/org.gnome.Shell.NetworkAgent/1000]: agent 
registered
  Mar 06 12:46:43 ubuntu0 dbus-daemon[1259]: [session uid=1000 pid=1259] 
Activating service name='org.freedesktop.FileManager1' requested by ':1.50' 
(uid=1000 pid=1506 comm="/usr/bin/gn>
  Mar 06 12:46:44 ubuntu0 dbus-daemon[1259]: [session uid=1000 pid=1259] 
Activating service name='org.gnome.Nautilus' requested by ':1.50' (uid=1000 
pid=1506 comm="/usr/bin/gnome-shell >
  Mar 06 12:46:44 ubuntu0 gnome-shell[1506]: Unable to mount volume 10.0 MB 
Encrypted: Gio.IOErrorEnum: An operation is already pending
  Mar 06 12:46:51 ubuntu0 udisksd[749]: Unlocked device /dev/loop5 as /dev/dm-3
  Mar 06 12:46:51 ubuntu0 kernel: EXT4-fs (dm-3): mounted filesystem without 
journal. Opts: (null)
  Mar 06 12:53:50 ubuntu0 gnome-shell[1506]: JS WARNING: 
[resource:///org/gnome/shell/ui/unlockDialog.js 762]: reference to undefined 
property "_authPrompt"
  Mar 06 12:53:50 ubuntu0 gnome-shell[1506]: JS ERROR: TypeError: 
this._authPrompt is undefined
     
_escape@resource:///org/gnome/shell/ui/unlockDialog.js:762:13

  Version info:
  - Ubuntu 20.04
  - gnome-shell 3.35.91-1ubuntu2

  Attached is a screencast demonstrating each of the steps for
  reproducing.

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

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

[Desktop-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices

[Martin Büchler]

https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403
may be solved by installing the latest version of

libplist
libimobiledevice
libusbmuxd
usbmuxd

I tested it and write access works again, see comment
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/comments/13

Are there any plans to provide official packages for i.e. 18.04 LTS?

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

Title:
  Need updated libimobiledevice and dependencies to access iOS 13
  devices

Status in libimobiledevice package in Ubuntu:
  Incomplete
Status in libplist package in Ubuntu:
  Confirmed
Status in libusbmuxd package in Ubuntu:
  Confirmed
Status in usbmuxd package in Ubuntu:
  Confirmed

Bug description:
  iOS 13 devices require updated libimobiledevice, libusbmuxd and
  usbmuxd to work correctly. Without the updates, the device appears to
  be accessible but it's impossible to copy files to the devices.

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

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

[Desktop-packages] [Bug 1688592]

[lilydjwg]

I'm glad to here that, but what about support for Firefox on X11? Is it
given up?

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

Title:
  Missing VA-API hardware decoding support drains battery

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

Bug description:
  Current devices ship with graphics devices supporting hardware
  decoding of certain video formats. While doing that, energy can be
  saved, as the main processor can go to sleep, and the graphics devices
  do their jobs more efficiently saving energy.

  Today, the browser is used a lot to watch movies. Unfortunately, the
  Firefox browser does not support VA-API hardware decoding, which is
  the interface to be used for Intel graphics device, which are included
  in current Intel processors.

  The issue in the Mozilla bug tracker [1] is open for over two years.

  Currently, this missing feature is a major show stopper for people
  using Ubuntu GNU/Linux on their laptops, as compared to Microsoft
  Windows one battery charge(?) lasts noticeably less time.

  [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

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

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

[Desktop-packages] [Bug 1838965]

[Michel Dänzer]

Are you enabling the native Wayland backend via the environment variable
`MOZ_ENABLE_WAYLAND=1` (or `GDK_BACKEND=wayland`)?

If not, this is probably an Xwayland issue, possibly fixed in the
upstream xserver 1.20.7 release (or in the upcoming 1.20.8 release).

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

Title:
  Screen tearing in Firefox on Wayland

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

Bug description:
  Details here: https://photos.app.goo.gl/9kA7R6KqNaSsn9CB8

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 68.0.1+build1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190719083815
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  5 13:36:32 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1141
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2019-08-04 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=68.0.1/20190719083815 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1740180]

[Apace-d]

Hi,

I was able to reproduce this issue on Ubuntu 18 with Firefox version
Nightly 76.0a1 (2020-03-17) (64-bit) on game
https://apps.facebook.com/juicejam . Marking that flag as affected.

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

Title:
  Firefox stops loading Farmville 2 and hangs.

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

Bug description:
  STR: Start Firefox (56 or 57), go to Facebook. Start Farmville 2. 
   Farmville 2 hangs while loading. Never plays. 

  The Adobe Flash Player is properly installed. Has also been re-
  installed. Ditto for FireFox.

  Does not matter if using Ubuntu 16.04 or 17.10.

  Farmville 2 via Facebook in Firefox hangs. Also will not work if run
  from the Zynga URL (the makers of Farmville 2. Other Facebook games
  work well. Try "Pearl's Perils."

  Happy to help with testing if you like. This has been tested on both
  desktops and laptops.

  Thanks,

  Ken Wagner

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Dec 26 15:59:05 2017
  InstallationDate: Installed on 2017-03-06 (295 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ken2466 F pulseaudio
   /dev/snd/pcmC0D0p:   ken2466 F...m pulseaudio
   /dev/snd/controlC0:  ken2466 F pulseaudio
   /dev/snd/controlC2:  ken2466 F pulseaudio
  BuildID: 20180614184508
  Channel: beta
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-03-28 (94 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.0.1 dev enp2s0  proto static  metric 100 
   default via 192.168.1.1 dev wlx7cdd908b43ea  proto static  metric 600 
   169.254.0.0/16 dev wlx7cdd908b43ea  scope link  metric 1000 
   192.168.0.0/24 dev enp2s0  proto kernel  scope link  src 192.168.0.10  
metric 100 
   192.168.1.0/24 dev wlx7cdd908b43ea  proto kernel  scope link  src 
192.168.1.2  metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-61ed5f93-fc76-48cc-8c5e-05d080180530
  Package: firefox 61.0~b14+build1-0ubuntu0.16.04.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  PackageArchitecture: amd64
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
   prefs.js
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Profiles: Profile0 (Default) - LastVersion=61.0/20180614184508 (In use)
  RunningIncompatibleAddons: False
  SubmittedCrashIDs:
   bp-61ed5f93-fc76-48cc-8c5e-05d080180530
   bp-481cf9ec-efcd-4900-93aa-4e8940180512
   bp-ad49167e-7776-4ff5-8acc-5adb50180421
   bp-08f026d0-e273-45fb-b355-c70ae0180402
  Tags: xenial third-party-packages beta-channel
  Themes: extensions.sqlite corrupt or missing
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  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.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  --- 
  AddonCom

[Desktop-packages] [Bug 1688592]

[Stransky]

HW decoding support  has landed at Bug 1616185.

*** This bug has been marked as a duplicate of bug 1616185 ***

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

Title:
  Missing VA-API hardware decoding support drains battery

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

Bug description:
  Current devices ship with graphics devices supporting hardware
  decoding of certain video formats. While doing that, energy can be
  saved, as the main processor can go to sleep, and the graphics devices
  do their jobs more efficiently saving energy.

  Today, the browser is used a lot to watch movies. Unfortunately, the
  Firefox browser does not support VA-API hardware decoding, which is
  the interface to be used for Intel graphics device, which are included
  in current Intel processors.

  The issue in the Mozilla bug tracker [1] is open for over two years.

  Currently, this missing feature is a major show stopper for people
  using Ubuntu GNU/Linux on their laptops, as compared to Microsoft
  Windows one battery charge(?) lasts noticeably less time.

  [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

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

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

[Desktop-packages] [Bug 1688592]

[Stransky]

(In reply to lilydjwg from comment #30)
> I'm glad to here that, but what about support for Firefox on X11? Is it given 
> up?

Filed Bug 1619523 for it.

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

Title:
  Missing VA-API hardware decoding support drains battery

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

Bug description:
  Current devices ship with graphics devices supporting hardware
  decoding of certain video formats. While doing that, energy can be
  saved, as the main processor can go to sleep, and the graphics devices
  do their jobs more efficiently saving energy.

  Today, the browser is used a lot to watch movies. Unfortunately, the
  Firefox browser does not support VA-API hardware decoding, which is
  the interface to be used for Intel graphics device, which are included
  in current Intel processors.

  The issue in the Mozilla bug tracker [1] is open for over two years.

  Currently, this missing feature is a major show stopper for people
  using Ubuntu GNU/Linux on their laptops, as compared to Microsoft
  Windows one battery charge(?) lasts noticeably less time.

  [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

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

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

[Desktop-packages] [Bug 1688592]

[Stransky]

(In reply to lilydjwg from comment #30)
> I'm glad to here that, but what about support for Firefox on X11? Is it given 
> up?

Hardware decoding is platform independent so it generally works under X11 as 
it's implemented as Bug 1616185. 
For whole playback chain see Bug 1610199 what's needed to be done fox X11.
I was closing this one as it refers to HW decode only, not the playback.
The overall video playback is tracked at Bug 1210726.

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

Title:
  Missing VA-API hardware decoding support drains battery

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

Bug description:
  Current devices ship with graphics devices supporting hardware
  decoding of certain video formats. While doing that, energy can be
  saved, as the main processor can go to sleep, and the graphics devices
  do their jobs more efficiently saving energy.

  Today, the browser is used a lot to watch movies. Unfortunately, the
  Firefox browser does not support VA-API hardware decoding, which is
  the interface to be used for Intel graphics device, which are included
  in current Intel processors.

  The issue in the Mozilla bug tracker [1] is open for over two years.

  Currently, this missing feature is a major show stopper for people
  using Ubuntu GNU/Linux on their laptops, as compared to Microsoft
  Windows one battery charge(?) lasts noticeably less time.

  [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

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

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

[Desktop-packages] [Bug 1688592]

[Jyavenard-9]

re-opening as a meta bug for VA-API implementation (including X11)

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

Title:
  Missing VA-API hardware decoding support drains battery

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

Bug description:
  Current devices ship with graphics devices supporting hardware
  decoding of certain video formats. While doing that, energy can be
  saved, as the main processor can go to sleep, and the graphics devices
  do their jobs more efficiently saving energy.

  Today, the browser is used a lot to watch movies. Unfortunately, the
  Firefox browser does not support VA-API hardware decoding, which is
  the interface to be used for Intel graphics device, which are included
  in current Intel processors.

  The issue in the Mozilla bug tracker [1] is open for over two years.

  Currently, this missing feature is a major show stopper for people
  using Ubuntu GNU/Linux on their laptops, as compared to Microsoft
  Windows one battery charge(?) lasts noticeably less time.

  [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

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

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

[Desktop-packages] [Bug 711305]

[bam]

(In reply to Brian Vanderburg from comment #8)
> I create custom .desktop files that execute
> "firefox -P  -new-instance %U" 

I don't create custom .desktop file with `-new-instance` for FF but still get 
the "already running error" when trying to open "mailto:"; links while TB is 
open.
How is that?

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

Title:
  Thunderbird is already running, but is not responding. To open a new
  window, you must first close the existing Thunderbird process, or
  restart your system. Error received when clicking a mailto link in
  firefox.

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  This thunderbird error is given when clicking a mailto link. Instead
  of using the thunderbird that's already open it tries to open a new
  instance. Preferred Applications has Thunderbird select, but I have
  also tried Custom command "thunderbird %s". This has been tested on
  10.04 and 10.10. Both result in this error if thunderbird is already
  running.

  Thunderbird is already running, but is not responding. To open a new
  window, you must first close the existing Thunderbird process, or
  restart your system.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic i686
  Architecture: i386
  Date: Tue Feb  1 10:19:09 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANG=en_CA.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

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

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

[Desktop-packages] [Bug 711305]

[bam]

- If I run it with `firefox` command, which is a script, I get the "already 
running error" on `mailto:` links problem
- If I run it with `/usr/lib64/firefox/firefox`, which is a binary - no problem

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

Title:
  Thunderbird is already running, but is not responding. To open a new
  window, you must first close the existing Thunderbird process, or
  restart your system. Error received when clicking a mailto link in
  firefox.

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  This thunderbird error is given when clicking a mailto link. Instead
  of using the thunderbird that's already open it tries to open a new
  instance. Preferred Applications has Thunderbird select, but I have
  also tried Custom command "thunderbird %s". This has been tested on
  10.04 and 10.10. Both result in this error if thunderbird is already
  running.

  Thunderbird is already running, but is not responding. To open a new
  window, you must first close the existing Thunderbird process, or
  restart your system.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic i686
  Architecture: i386
  Date: Tue Feb  1 10:19:09 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANG=en_CA.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

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

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

[Desktop-packages] [Bug 25830]

[Gijskruitbosch+bugs]

Backlog grooming: bugs without an assignee cannot be P1.

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

Title:
  Option to display file in browser, treat as text/plain

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  A suggestion:

  When you click certain files, like .py or .pl files, for example, Firefox 
brings
  up a dialog that offers you the ability to:
  1. Open with a certain application
  2. Save to disk
  What would be nice is a third option:
  3. Treat as text/plain

  The wording could be altered... "Display as text in browser" or
  something.

  Sometimes you just want to quickly visit a file on the web and look for
  something in it, and the fact that you *could* open it in a more customized
  application is true but not really easier for you at that moment. If you just
  want to look a Python script for a version number at the top it is not 
necessary
  to open it in your IDE or save it to disk; you just want to open it in the
  normal viewing window as plain text and quickly find what you need to look at.

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

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

[Desktop-packages] [Bug 1869319] Re: kolla-ansibe debloy vitrage, lack persistor service

[Qitao]

Sorry for this. Accidently selected a wrong project. And fix now.

** Package changed: libssh (Ubuntu) => vitrage

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

Title:
  kolla-ansibe debloy vitrage, lack persistor service

Status in Vitrage:
  In Progress

Bug description:
  https://github.com/openstack/kolla-
  ansible/tree/master/ansible/roles/vitrage/templates ， it only have
  vitrage-ml ,vitrage-graph ,vitrage-api，vitrage-notifier. No vitrage-
  persistor is can not store data in DB.

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

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

[Desktop-packages] [Bug 1864253] Re: Pulseaudio sink/source selection, weird behaviour.

[Bug Watch Updater]

** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  Pulseaudio sink/source selection, weird behaviour.

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a Laptop connected to an USB-C dock. By default the docks analog
  audio output is chosen as the default pulse audio sink. I want that the
  analog output of the Laptop is the default, hence I configured this in
  /etc/pulse/default.py

  This does not work and journalctl informs me that the device chosen by me
  (alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached 
output
  from journalctl.

  I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp
  to prevent pulseaudio getting started in gdm to prevent device capture.

  This does not work, the device does still not exist.
  Restarting pulseaudio sometimes, but not always sets the configured
  default sink. Furthermore plugging in the headphones in the Laptops analog 
input
  switches audio to the dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  findus 3055 F pulseaudio
   /dev/snd/controlC1:  findus 3055 F pulseaudio
   /dev/snd/controlC0:  findus 3055 F pulseaudio
   /dev/snd/pcmC0D0p:   findus 3055 F...m pulseaudio
  CurrentDesktop: i3
  Date: Fri Feb 21 22:19:04 2020
  InstallationDate: Installed on 2019-06-13 (253 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2IET80W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20N3S0UB00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N3S0UB00:pvrThinkPadT490:rvnLENOVO:rn20N3S0UB00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T490
  dmi.product.name: 20N3S0UB00
  dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490
  dmi.product.version: ThinkPad T490
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2020-02-21T20:38:20.081439
  mtime.conffile..etc.pulse.default.pa: 2020-02-21T19:27:57.386938
  mtime.conffile..etc.pulse.system.pa: 2020-02-21T15:23:09.470494

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

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

[Desktop-packages] [Bug 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

[Bug Watch Updater]

** Changed in: pulseaudio
   Status: Unknown => New

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

Title:
  [Dell Inspiron 7370] shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1868353] Re: regression: Bose SL III works in bionic but not in focal

[Bug Watch Updater]

** Changed in: pulseaudio
   Status: Unknown => New

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

Title:
  regression: Bose SL III works in bionic but not in focal

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  blueman-manager successfully pairs and connects to the Bose SL III in
  both bionic and in focal.  in bionic, the Bose SL III then immediately
  shows up in pavucontrol.  in focal, it remains absent.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  Date: Fri Mar 20 19:53:54 2020
  InstallationDate: Installed on 2020-03-15 (5 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ETA2WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C6008SUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E540
  dmi.product.name: 20C6008SUS
  dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1852183]

[Eike Rathke]

*** Bug 131631 has been marked as a duplicate of this bug. ***

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04

Status in LibreOffice:
  Confirmed
Status in Mutter:
  Fix Released
Status in codelite package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Released
Status in codelite source package in Eoan:
  Confirmed
Status in libreoffice source package in Eoan:
  Triaged
Status in mutter source package in Eoan:
  Triaged
Status in codelite source package in Focal:
  Confirmed
Status in libreoffice source package in Focal:
  Triaged
Status in mutter source package in Focal:
  Fix Released

Bug description:
  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  I use LibreOffice Writer a lot, and I now see this problem very often,
  i.e. many times every day.

  There is some discussion of the problem here:

 https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

 https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

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

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

[Desktop-packages] [Bug 1852183]

[timur]

*** Bug 130880 has been marked as a duplicate of this bug. ***

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04

Status in LibreOffice:
  Confirmed
Status in Mutter:
  Fix Released
Status in codelite package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Released
Status in codelite source package in Eoan:
  Confirmed
Status in libreoffice source package in Eoan:
  Triaged
Status in mutter source package in Eoan:
  Triaged
Status in codelite source package in Focal:
  Confirmed
Status in libreoffice source package in Focal:
  Triaged
Status in mutter source package in Focal:
  Fix Released

Bug description:
  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  I use LibreOffice Writer a lot, and I now see this problem very often,
  i.e. many times every day.

  There is some discussion of the problem here:

 https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

 https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

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

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

[Desktop-packages] [Bug 1812754]

[Qa-admin-q]

Dear Kevin,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

Title:
  Libreoffice writer adds blank pages on multiple inputs

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

Bug description:
  When I have multiple .txt files on the command line and start
  libreoffice writer, it adds (many) blank pages to the documents.
  These blanks contain nothing at all and I have not figured out how to
  remove them.  But they are included when I print them.

  I'm attaching a file on which this happens.  It contains an anonymized
  fragment of the original, repeates a number of times.  I suggest you
  create two copies, called perhaps junk1.txt and junk2.txt.

  I use the command "soffice junk*" to load them into the writer, and I
  get the extra blank pages.

  If, however, I just do soffice junk1.txt, I get a document of the
  correct size.

  I can do that of course, but it is still an annoying and inconvenient
  error for my workflow.

  ---

  One hint to debugging: if I do this:

  for i in junk1.txt junk2.txt
  do
soffice $i &
  done

  I see the problem.  If, however, I introduce a delay the problem does
  not appear.  Like so:

  for i in junk1.txt junk2.txt
  do
sleep 2
soffice $i &
  done

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.7-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jan 21 13:58:01 2019
  InstallationDate: Installed on 2018-10-18 (95 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1852183]

[Tom1williams]

I am having the same problem. My work-around was to install XFCE from
the Ubuntu repository. As soon as I logged into an XFCE session instead
of a GNOME session the problem disappeared completely. I think the
people who support mutter have this as a high severity bug.

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04

Status in LibreOffice:
  Confirmed
Status in Mutter:
  Fix Released
Status in codelite package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Released
Status in codelite source package in Eoan:
  Confirmed
Status in libreoffice source package in Eoan:
  Triaged
Status in mutter source package in Eoan:
  Triaged
Status in codelite source package in Focal:
  Confirmed
Status in libreoffice source package in Focal:
  Triaged
Status in mutter source package in Focal:
  Fix Released

Bug description:
  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  I use LibreOffice Writer a lot, and I now see this problem very often,
  i.e. many times every day.

  There is some discussion of the problem here:

 https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

 https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

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

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

[Desktop-packages] [Bug 1828811]

[Libreoffice-commits]

Xisco Fauli committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/1391b1b3eb3d28c7a606a3f0357eef6ca71267e7

tdf#125261: move UItest to CppunitTest

It will be available in 7.0.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  [Upstream] Applying autocorrect to text with URLs causes Writer to
  hang

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

Bug description:
  When attempting to apply autocorrect to text that contains URLs to
  convert to hyperlinks (https://ask.libreoffice.org/en/question/6393
  /how-may-i-do-writer-recognize-hyperlinks-automatically/) causes
  Writer to stop responding requiring a force quit.

  Version 6.2.2.2

  Severity: Normal.

  Reproducible:
  Always

  Steps to reproduce:
  Open a new Writer document.
  Turn URL recognition on - Tools | Auto Correct | Auto correct options | 
Options tab
  Insert text containing URLs (see below)
  Set paragraph style to default
  Apply auto correct - Tools | Auto Correct | Apply

  Actual result:
  Libre Office hangs

  Expected result:
  Auto correct applied, text urls converted to hyperlinks

  Bug is evident in both deb and snap versions of LO, but not in earlier
  5.x or 6.x series.

  Sample test with URLs:
  This webpage is and example of a url that should be able to be converted to a 
hyperlink . As is this page  
and this page .

  These pages should also be able to be converted using the method
  linked to above ,
  .

  A typical use for a page like this would be a bibliography or
  reference list .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 20:38:07 2019
  InstallationDate: Installed on 2019-05-11 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1798400]

[Sergio Callegari]

The premise is that my ignorance on BT is complete. After some
investigation, it is my understanding that RFCOMM channels are to RFCOMM
communication a bit like ports in TCP and UDP, with the main difference
that while there are really a lot of TCP/UDP ports and some of them are
reserved as "well known ports", the number of channels in RFCOMM is
extremely limited, so that there cannot be well known ports.
Furthermore, I understand that no one should "hardwire" RFCOMM channels
and that channels should be released whenever not strictly needed.

If this understanding from myself is correct, there may be issues both in LibO 
and in PA.
>From my understanding:

- LibO and the Impress remote should not hardwire RFCOMM channel 3. I
understand that they should dynamically allocate a channel and make it
discoverable via SDP.

- Impress should not keep binded to an RFCOMM channel all the time.
There should be a visible option to switch on and off the binding
(probably there should be a couple of impress remote related options in
the "Slide Show -> Slide Show Settings" window, including one to fire up
the BT rfcomm binding).

- PA should probably similarly not hardwire channel 3 for its HSP role,
but here the situation seems more complex, because it may be the case
that PA needs to strive for compatibility with devices that do not play
to the rules.

- PA should probably have a DBUS interface to switch on and off the
RFCOMM binding, so that to use an application needing RFCOMM channel 3,
one does not need to take down the whole of PA.

I have opened a bug on PA too. See it at
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/827.  That
report is bad, because when I made it my understanding of BT was even
poorer than it is now.

In any case, it seems to me that the current issue could be fixed
completely on the LibO side, by dynamically allocating the channel and
by letting the app running on the phone discover it via SDP.

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

Title:
  [upstream] Regression: cannot use impress remote over bluetooth with
  ubuntu bionic

Status in LibreOffice:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicab

[Desktop-packages] [Bug 1852183]

[timur]

(In reply to Timur from comment #9)
> This bug is marked All and reproduced also on Windows.

Shall we open a separate bug for Windows?

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04

Status in LibreOffice:
  Confirmed
Status in Mutter:
  Fix Released
Status in codelite package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Released
Status in codelite source package in Eoan:
  Confirmed
Status in libreoffice source package in Eoan:
  Triaged
Status in mutter source package in Eoan:
  Triaged
Status in codelite source package in Focal:
  Confirmed
Status in libreoffice source package in Focal:
  Triaged
Status in mutter source package in Focal:
  Fix Released

Bug description:
  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  I use LibreOffice Writer a lot, and I now see this problem very often,
  i.e. many times every day.

  There is some discussion of the problem here:

 https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

 https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

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

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

[Desktop-packages] [Bug 1736176]

[Saa1-bus]

Hi,
is it possible to make ScrollLock key to be settable as Left/Right/Up/Down keys.

Can anyone explain the problem to do this?

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

Title:
  [upstream] Can't jump between cells when non-english input layout is
  active

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

Bug description:
  Can't jump between LibreOffice Calc cells by arrow keys when non-
  english input layout is active. It's because Ubuntu is using Scroll
  Lock indicator (LED) to show state of layout switch, but in
  LibreOffice Scroll Lock state is used to switch between page's
  scrolling and jumping on cells.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  4 17:25:29 2017
  InstallationDate: Installed on 2017-10-19 (45 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1729433]

[Olivier-crete-x]

I'm still reproducing this on Fedora 31 with the 6.3.4.2-2.fc31 build.

I think the other sub-bug here is that LibreOffice lets me resize the
window to a size smaller than the UI elements.

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

Title:
  LibreOffice doesn't remember window size when running under Wayland

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

Bug description:
  1. Open any LibreOffice document, e.g., a Writer or Calc document.
  2. Make the window a reasonable, non-maximized size.
  3. Maximize the window.
  4. Close LibreOffice.
  5. Open the document again; it will open maximized.
  6. Un-maximize the window.
  7. Observe how the window has a ridiculously small size, not its previously 
unmaximized size.

  LibreOffice or gnome-shell bug? Not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:21:29 2017
  InstallationDate: Installed on 2017-05-19 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago)

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

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

[Desktop-packages] [Bug 1793124]

[kolAflash]

It's still a problem in LibreOffice-6.4.11.

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

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

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

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

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

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

[Desktop-packages] [Bug 1093765]

[Eyalroz]

Created attachment 158272
Manifesting document saved as ODT

The bug still manifests if we save attachment 79954 as an ODT rather
than a DOC file.

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

Title:
  [upstream] switching paragraph style changes character orientation

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

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:4.0.2-0ubuntu1
Candidate: 1:4.0.2-0ubuntu1
Version table:
   *** 1:4.0.2-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in Writer via a terminal:
  cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765/+attachment/3688368/+files/test-bug1093765.doc
 && lowriter --nologo test-bug1093765.doc

  is select all -> change combo box Apply Style from Text Body to
  Heading 1 and the text style changes, preserving the character order.

  4) What happens instead is:
  (Example text=) טקסט לדוגמה

  changes to:
  טקסט לדוגמה (=Example text)

  Microsoft Office Professional Plus 2010 Word Version 14.0.6023.1000 (32-bit) 
changes it to:
  =)טקסט לדוגמהExample text(

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-core 1:3.6.2~rc2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  Uname: Linux 3.5.0-21-generic x86_64
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  Date: Wed Dec 26 11:20:42 2012
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (67 days ago)

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

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

[Desktop-packages] [Bug 1351493]

[Shery38]

Bug of the report is ensured for the fiction for the gaps in the field.
The content of the https://bestwritingsclues.com/reviews/studybay-
review/ is visited for the approach for humans. The chance is vital for
the provision of all humans. The tweet is involved in the terms. fitness
is implied for the joys for the formation for all goals and attainment
for the mid of the tips for all humans.

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

Title:
  soffice.bin crashed with SIGSEGV in ResMgr::GetLong()

Status in LibreOffice:
  Won't Fix
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Print document .odt and crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: libreoffice-core 1:4.2.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Aug  1 17:30:44 2014
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2014-04-27 (96 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer --splash-pipe=5
  SegvAnalysis:
   Segfault happened at: 0x7fce2a274420 <_ZN6ResMgr7GetLongEPv>:movzbl 
(%rdi),%eax
   PC (0x7fce2a274420) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ResMgr::GetLong(void*) () from /usr/lib/libreoffice/program/libmergedlo.so
   ResMgr::ReadLong() () from /usr/lib/libreoffice/program/libmergedlo.so
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
  Title: soffice.bin crashed with SIGSEGV in ResMgr::GetLong()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1093765]

[Eyalroz]

I am:

* ABLE to reproduce with the original attached DOC document.
* UNABLE to reproduce on a plain new document.
* ABLE to reproduce on the ODT version of the original attachment.

LO Version: 6.4.0.3
Build ID: b0a288ab3d2d4774cb44b62f04d5d28733ac6df8
CPU threads: 4; OS: Linux 5.2; UI render: default; VCL: gtk3; 
Locale: he-IL (en_IL); UI-Language: en-US


Now, looking at the saved ODT's XML, we see:






I wonder... perhaps the combination of tags:

fo:text-align="end" style:writing-mode="rl-tb"

is the culprit? That is, perhaps it's treated differently, or scrapped,
when LO switch styles, because it's expecting this information
elsewhere? Just speculating.

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

Title:
  [upstream] switching paragraph style changes character orientation

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

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:4.0.2-0ubuntu1
Candidate: 1:4.0.2-0ubuntu1
Version table:
   *** 1:4.0.2-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in Writer via a terminal:
  cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765/+attachment/3688368/+files/test-bug1093765.doc
 && lowriter --nologo test-bug1093765.doc

  is select all -> change combo box Apply Style from Text Body to
  Heading 1 and the text style changes, preserving the character order.

  4) What happens instead is:
  (Example text=) טקסט לדוגמה

  changes to:
  טקסט לדוגמה (=Example text)

  Microsoft Office Professional Plus 2010 Word Version 14.0.6023.1000 (32-bit) 
changes it to:
  =)טקסט לדוגמהExample text(

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-core 1:3.6.2~rc2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  Uname: Linux 3.5.0-21-generic x86_64
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  Date: Wed Dec 26 11:20:42 2012
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (67 days ago)

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

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

[Desktop-packages] [Bug 725792]

[Eyalroz]

Still seeing this issue manifest with:

Version: 6.4.0.3
Build ID: b0a288ab3d2d4774cb44b62f04d5d28733ac6df8
CPU threads: 4; OS: Linux 5.2; UI render: default; VCL: gtk3; 
Locale: he-IL (en_IL); UI-Language: en-US


However! Different fonts present somewhat different behavior, in the sense that 
not all breaks appear. Specifically, if you change the font in attachment 45268 
(Simchi Chen's attachment from 2011) to David CLM, the break before the number 
12 is gone.

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

Title:
  [Upstream] Using numbers with RTL text breaks underline

Status in LibreOffice:
  Confirmed
Status in OpenOffice:
  New
Status in abiword package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Confirmed
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org
  Binary package hint: libreoffice

  1) 
  Natty:
  lsb_release -rd
  apDescription:Ubuntu Natty (development branch)
  Release:11.04

  Maverick:
  lsb_release -rd
  Description: Ubuntu 10.10
  Release: 10.10

  
  2) 
  Natty:
  apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.3.2-1ubuntu2
Candidate: 1:3.3.2-1ubuntu2
Version table:
   *** 1:3.3.2-1ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100
  /var/lib/dpkg/status

  Maverick:
  apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.2-1ubuntu2~maverick1
    Candidate: 1:3.3.2-1ubuntu2~maverick1
    Version table:
   *** 1:3.3.2-1ubuntu2~maverick1 0
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ maverick/main 
i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one opens via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/725792/+attachment/1981833/+files/underlinebreak.odt
  && loimpress -nologo underlinebreak.odt

  all the characters on one line that are marked underlined have one,
  continuous underline.

  4) What happens instead is that the underline breaks after a number.

  WORKAROUND: Use Abiword.

  Original Reporter Comments:
  -Write some underlined text in an RTL language(tested Hebrew and Arabic)
  -Write a number(still in the same underline)
  Result: the underline breaks.
  This does not happen in English.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: openoffice.org-writer 1:3.2.1-7ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic x86_64
  NonfreeKernelModules: fglrx wl
  Architecture: amd64
  Date: Sun Feb 27 00:18:21 2011
  InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Release amd64 
(20101008.1)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: openoffice.org

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

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

[Desktop-packages] [Bug 1005504]

[Rhkramer-t]

*** Bug 131405 has been marked as a duplicate of this bug. ***

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

Title:
  [Upstream] Writer: Avery 5167 label bottom vertically truncated

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

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.5.3-0ubuntu1
Candidate: 1:3.5.3-0ubuntu1
Version table:
   *** 1:3.5.3-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.5.2-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages

  3) What is expected to happen in Writer is when one clicks File -> New -> 
Labels -> tab Labels -> drop down Brand Avery Letter Size -> drop down Type 
5167 Return Address -> text box Label type:
  test test
  test
  test

  -> click New Document and the content is fully displayed.

  4) What happens instead is the third line down is cut off. For a
  screenshot please see
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1005504/+attachment/3166806/+files/avery2.png
  .

  WORKAROUND: Use return address labels (basic format, works with Avery
  5167, 5267, 6467, 8167, or 8667) downloaded from www.office.com
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1005504/+attachment/3187732/+files/TS102807111.dotx
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Mon May 28 08:08:30 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to precise on 2012-05-10 (17 days ago)

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

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

[Desktop-packages] [Bug 1869568] Re: Unlock takes a long time

[Roger Lipscombe]

I can't do that on my primary PC -- I'm *using* those extensions.

I'll set up my spare PC the same way (with the extensions) and see if I
can repro. Then I'll disable them and see if the problem goes away (or
not).

Gonna take me about a week, though, since this only happens after a
bunch of locking and unlocking.

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

Title:
  Unlock takes a long time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I searched and found related bugs #1774188 and #1847566, but one of
  those is against 19.04, which is end-of-support, and the other was
  abandoned with no feedback from the OP. So, let's try again.

  When unlocking my screen, it takes progressively longer to unlock.
  After a fresh restart, it's pretty quick. After about a day, it takes
  about a second. After a longer period, it takes up to 5 seconds.

  When I press Enter at the lock screen to get to the password entry,
  the "wipe" effect commonly stalls as it gets near the top of the
  screen; not sure if this is related.

  After correctly entering my password, it takes several seconds before
  my desktop is visible. It's _there_, because moving the mouse around
  changes the mouse pointer according to what's under it (e.g. it turns
  into an I-bar on the Firefox search/address box and a finger icon on a
  link). It just takes several seconds to actually draw the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 11:10:07 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-10 (78 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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/1869568/+subscriptions

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

[Desktop-packages] [Bug 1798400] Re: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic

[Bug Watch Updater]

** Bug watch added: PulseAudio #827
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/827

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

Title:
  [upstream] Regression: cannot use impress remote over bluetooth with
  ubuntu bionic

Status in LibreOffice:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:C2:C6:1A:28:71  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:245088 acl:15156 sco:0 events:1266 errors:0
TX bytes:15571 acl:402 sco:1 commands:131 errors:0

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

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