date:20200329

Yes, the bug is still there :(

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

Title:
  Panel menu icons are briefly way too big (when opened the first time)

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

Bug description:
  On every fresh boot, the first time when you click the drop down menu for 
SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY 
THE FIRST TIME WHEN YOU RESTART the machine!!
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell app-picker-view uint32 1
   org.gnome.shell favorite-apps ['chromium-browser.desktop', 
'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']
   org.gnome.desktop.interface enable-animations false
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-31 (46 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-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/1724098/+subscriptions

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

[Desktop-packages] [Bug 1724098]

2020-03-29 Thread Strangiato Xanadu

(In reply to Daniel van Vugt from comment #12)
> Bug fixed by the new menu design in 3.35/3.36.

I can't confirm.
Still happening on Arch Linux after upgrade to Gnome 3.36.
It's less noticeable at least.

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

Title:
  Panel menu icons are briefly way too big (when opened the first time)

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

Bug description:
  On every fresh boot, the first time when you click the drop down menu for 
SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY 
THE FIRST TIME WHEN YOU RESTART the machine!!
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell app-picker-view uint32 1
   org.gnome.shell favorite-apps ['chromium-browser.desktop', 
'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']
   org.gnome.desktop.interface enable-animations false
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-31 (46 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-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/1724098/+subscriptions

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

[Desktop-packages] [Bug 1869650] [NEW] changing screen position, dash is gone, background is black.. and flashing white on any attempt to operate anything

Public bug reported:

Ubuntu 20.04 LTS daily QA-test (live) on hp dc7700 (c2d-e6320, 5gb,
nvidia quadro nvs 290)

Background:

Another exploration of http://launchpad.net/bugs/1869571, primarily as I
want screen dump to file bug upstream as requested; this box shares
screens of hp 8200 that had it before, so I'd expect can easily re-
create it..

(this box has menu on display I prefer, so maybe has cables reversed to
hp 8200 used earlier)

What I did:

Opened `displays` to adjust to match setup (vertical alignment of screens); and 
on hitting "apply" the system has gone strange
 - black background (both displays)
 - lots of (white) flashing on mouse movements if near panel/dash
 - dash is gone, like it has background color but icons gone, now only ~half 
height of monitor (it was screen height before apply with icons)

Menu items could no longer be operated as not viewable (let alone white
flashes being very annoying)

I pressed printscreen to get screencapture once `ubuntu-bug` was
started; and the dash was re-drawn!!? (it was not there after screen
position was changed & until printscreen was hit)...

Printscreen also stopped all white-flashes, and the system is now
operational again?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.0-2ubuntu1
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 05:21:52 2020
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 'au'), 
('xkb', 'cm'), ('xkb', 'gb')]"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  changing screen position, dash is gone, background is black.. and
  flashing white on any attempt to operate anything

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 LTS daily QA-test (live) on hp dc7700 (c2d-e6320, 5gb,
  nvidia quadro nvs 290)

  Background:

  Another exploration of http://launchpad.net/bugs/1869571, primarily as
  I want screen dump to file bug upstream as requested; this box shares
  screens of hp 8200 that had it before, so I'd expect can easily re-
  create it..

  (this box has menu on display I prefer, so maybe has cables reversed
  to hp 8200 used earlier)

  What I did:

  Opened `displays` to adjust to match setup (vertical alignment of screens); 
and on hitting "apply" the system has gone strange
   - black background (both displays)
   - lots of (white) flashing on mouse movements if near panel/dash
   - dash is gone, like it has background color but icons gone, now only ~half 
height of monitor (it was screen height before apply with icons)

  Menu items could no longer be operated as not viewable (let alone
  white flashes being very annoying)

  I pressed printscreen to get screencapture once `ubuntu-bug` was
  started; and the dash was re-drawn!!? (it was not there after screen
  position was changed & until printscreen was hit)...

  Printscreen also stopped all white-flashes, and the system is now
  operational again?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  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 05:21:52 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  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/g

[Desktop-packages] [Bug 1868116] Re: QEMU monitor no longer works

2020-03-29 Thread Christian Ehrhardt 

Thanks Ken!
I verified it and the new version indeed fixes the issue in focal.

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

Title:
  QEMU monitor no longer works

Status in QEMU:
  New
Status in qemu package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in qemu package in Debian:
  Unknown

Bug description:
  Repro:
  VTE
  $ meson _build && ninja -C _build && ninja -C _build install

  qemu:
  $ ../configure --python=/usr/bin/python3 --disable-werror --disable-user 
--disable-linux-user --disable-docs --disable-guest-agent --disable-sdl 
--enable-gtk --disable-vnc --disable-xen --disable-brlapi --disable-fdt 
--disable-hax --disable-vde --disable-netmap --disable-rbd --disable-libiscsi 
--disable-libnfs --disable-smartcard --disable-libusb --disable-usb-redir 
--disable-seccomp --disable-glusterfs --disable-tpm --disable-numa 
--disable-opengl --disable-virglrenderer --disable-xfsctl --disable-vxhs 
--disable-slirp --disable-blobs --target-list=x86_64-softmmu --disable-rdma 
--disable-pvrdma --disable-attr --disable-vhost-net --disable-vhost-vsock 
--disable-vhost-scsi --disable-vhost-crypto --disable-vhost-user 
--disable-spice --disable-qom-cast-debug --disable-vxhs --disable-bochs 
--disable-cloop --disable-dmg --disable-qcow1 --disable-vdi --disable-vvfat 
--disable-qed --disable-parallels --disable-sheepdog --disable-avx2 
--disable-nettle --disable-gnutls --disable-capstone --disable-tools 
--disable-libpmem --disable-iconv --disable-cap-ng
  $ make

  Test:
  $ LD_LIBRARY_PATH=/usr/local/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH 
./build/x86_64-softmmu/qemu-system-x86_64 -enable-kvm --drive 
media=cdrom,file=http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso
  - switch to monitor with CTRL+ALT+2
  - try to enter something

  Affects head of both usptream git repos.

  
  --- original bug ---

  It was observed that the QEMU console (normally accessible using
  Ctrl+Alt+2) accepts no input, so it can't be used. This is being
  problematic because there are cases where it's required to send
  commands to the guest, or key combinations that the host would grab
  (as Ctrl-Alt-F1 or Alt-F4).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: qemu 1:4.2-3ubuntu2
  Uname: Linux 5.6.0-rc6+ x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 12:16:31 2020
  Dependencies:

  InstallationDate: Installed on 2017-06-13 (1009 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID PIDPPID %CPU COMMAND
   qemu-system-x86 Sl+   1000  1000   34275   25235 29.2 qemu-system-x86_64 -m 
4G -cpu Skylake-Client -device virtio-vga,virgl=true,xres=1280,yres=720 -accel 
kvm -device nec-usb-xhci -serial vc -serial stdio -hda 
/home/usuario/Sistemas/androidx86.img -display gtk,gl=on -device usb-audio
   kvm-nx-lpage-re S0 0   34284   2  0.0 [kvm-nx-lpage-re]
   kvm-pit/34275   S0 0   34286   2  0.0 [kvm-pit/34275]
  MachineType: LENOVO 80UG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-rc6+ 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 
i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 
zswap.enabled=1 zswap.zpool=z3fold 
resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M 
usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y 
scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 
nbd.max_part=63
  SourcePackage: qemu
  UpgradeStatus: Upgraded to focal on 2019-12-22 (87 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240

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

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

[Desktop-packages] [Bug 1867133] Re: Ubuntu logo vanishes and fades back in (with a slightly different size) on gdm start

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

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

Title:
  Ubuntu logo vanishes and fades back in (with a slightly different
  size) on gdm start

Status in gnome-shell package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Won't Fix

Bug description:
  spinner theme flickers Ubuntu logo on gdm transition

  At the end of boot, spinner disappears and Ubuntu logo remains 100%
  opacity white on screen.

  Then GDM starts, and performs a fade-in animation of background
  gradient, and fade-ins Ubuntu logo.

  This results in visual flicker, where Ubuntu logo temporarily
  dissappears and instantly fades back in.

  This should be more smooth. For example, gdm could paint ubuntu logo
  at 100% opacity white without animation, whilst everything else fades-
  in. Or we could fade out ubuntu-logo in the spinner plymouth theme,
  such that on boot it is a tasteful pulsating logo that fades out, and
  back in.

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

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

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

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/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 1869635] Re: the menu "Dash to Dock Settings" is visible

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

-- 
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 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen

Please report the problem to the upstream developers at:

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues

and then tell us the new bug ID.

-- 
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 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/ubuntu/+source/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 1869568] Re: Unlock takes a long time

Since we find so many bugs are caused by extensions we first need you to
uninstall all of these:

'audio-output-switcher@anduchs',
'alternate-...@gnome-shell-extensions.gcampax.github.com',
'multi-monitors-add-on@spin83',
'dash-to-pa...@jderose9.github.com'

Be sure to uninstall them and don't just disable them because a disabled
extension can still interfere with the shell.


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/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 1869485] Re: mobile internet G4 not possible

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

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

Title:
  mobile internet G4 not possible

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  no connecting to the mobile internet G4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Mar 28 13:37:17 2020
  DistUpgraded: 2018-08-18 11:06:47,630 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1043:14e2]
 Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1043:14e2]
  InstallationDate: Installed on 2014-08-29 (2037 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: ASUSTeK Computer Inc. X51L
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=4d7525b3-75a6-483e-8dad-b34a49f9c185 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-18 (588 days ago)
  dmi.bios.date: 02/27/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X51L
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr205:bd02/27/2008:svnASUSTeKComputerInc.:pnX51L:pvr1.0:rvnASUSTeKComputerInc.:rnX51L:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: X51L
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Sat Aug 18 07:19:25 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5460 
   vendor CMO
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Desktop-packages] [Bug 1869549] Re: Whenever a sound needs to be played the screen blanks out

Please:

1. Run:

   dmesg > before.txt

2. Reproduce the bug.

3. Run:

   dmesg > after.txt

4. Attach both 'before.txt' and 'after.txt' here.

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Whenever a sound needs to be played the screen blanks out

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever a sound needs to be played the screen blanks out for a
  second, then the screen comes back on, and the sound plays.

  Examples of sounds are when I press Tab on the terminal, and there are
  no possible completions, or when I press the down button on the
  terminal, and there are no further lines below, then it blanks out,
  comes back, and then plays the "ding" tone telling me there are no
  further completions or lines.

  However, after one blank-out, if I keep pressing the down button, the
  sounds play normally without blanking out for a short time. After that
  period, it repeats again on doing something that would cause the sound
  to be played again.

  I'm on a relatively new HP Pavilion CS3006TX, running 20.04 Focal
  Fossa (Development branch)

  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: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 09:05:04 2020
  DistUpgraded: 2020-03-28 14:50:01,253 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-42-generic, x86_64: installed
   nvidia, 435.21, 5.4.0-18-generic, x86_64: installed
   virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed
   virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:86e2]
 Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:86e2]
  InstallationDate: Installed on 2019-11-30 (119 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:03bc Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Laptop 15-cs3xxx
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=5ee3ea75-c293-4350-b4ea-e81ef28c7f78 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-03-28 (0 days ago)
  dmi.bios.date: 08/23/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.03
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 86E2
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.03:bd08/23/2019:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cs3xxx
  dmi.product.sku: 8LX85PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati:

[Desktop-packages] [Bug 1868780] Re: [virtio] Xubuntu 20.04 - Blank screen after login

I can't see anything graphics-related happening or going wrong.

This sounds like a lightdm problem. Maybe this is it:

Mar 28 10:16:56 testvm lightdm[934]: pam_succeed_if(lightdm:auth):
requirement "user ingroup nopasswdlogin" not met by user "test"


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

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

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

Title:
  [virtio] Xubuntu 20.04 - Blank screen after login

Status in lightdm package in Ubuntu:
  New

Bug description:
  Both on Xubuntu 20.04 23rd March and 24th March daily build.
  Using Martin Wimpress QuickEMU setup.
  Installation part of xubuntu is working fine.
  But after install and reboot, you get the login box. I type in the password 
for the user and then just get a black screen and mouse cursor, no other error 
boxes or gui.
  Have tested my QuickEMU setup on ubuntu-mate and do not see this issue, only 
on Xubuntu daily builds do I see this issue.

  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
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Mar 24 16:40:12 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  InstallationDate: Installed on 2020-03-24 (0 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=4b1c21e9-1325-435b-9ade-04263b901e6d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU
  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 N/A
  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/lightdm/+bug/1868780/+subscriptions

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

[Desktop-packages] [Bug 1869470] Re: Can't minimize Thunderbird Lightning reminder window

** Package changed: mutter (Ubuntu) => thunderbird (Ubuntu)

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

Title:
  Can't minimize Thunderbird Lightning reminder window

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Ever since Ubuntu moved back to Gnome from Unity, it's impossible to
  minimize the Thunderbird Lightning reminder window. It's really
  annoying, the window is always on top of Thunderbird and has to be
  constantly moved around to use the program.

  Closing the window makes no sense as a) it tends to start syncing the
  events with reminders, which can show conflict prompts requiring even
  more work from the user and b) the window comes back very quickly. So,
  minimize makes the most sense.

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

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

[Desktop-packages] [Bug 1830079] Re: PAM errors logged when pam_kwallet is not installed

** Tags added: xenial

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

Title:
  PAM errors logged when pam_kwallet is not installed

Status in lightdm package in Ubuntu:
  New

Bug description:
  ii  lightdm1.18.3-0ubuntu amd64  Display Manager
  VERSION="16.04.6 LTS (Xenial Xerus)"

  Running with XFCE installed, I see the following in /var/log/auth.log:

  May 21 15:52:09 lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  May 21 15:52:09 lightdm: PAM adding faulty module: pam_kwallet.so
  May 21 15:52:09 lightdm: PAM unable to dlopen(pam_kwallet5.so): 
/lib/security/pam_kwallet5.so: cannot open shared object file: No such file or 
directory
  May 21 15:52:09 lightdm: PAM adding faulty module: pam_kwallet5.so

  These can be avoided by prefixing the optional components in
  /etc/pam.d/lightdm (and lightdm-greeter) by a "-" as follows:

  #%PAM-1.0
  authrequisite   pam_nologin.so
  authsufficient  pam_succeed_if.so user ingroup nopasswdlogin
  @include common-auth
  -authoptionalpam_gnome_keyring.so
  @include common-account
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
  #session requiredpam_loginuid.so
  session requiredpam_limits.so
  @include common-session
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
  -session optionalpam_gnome_keyring.so auto_start
  -session optionalpam_kwallet.so auto_start
  -session optionalpam_kwallet5.so auto_start
  session requiredpam_env.so readenv=1
  session requiredpam_env.so readenv=1 user_readenv=1 
envfile=/etc/default/locale
  @include common-password

  From man pam.conf:

  If the type value from the list above is prepended with a - character
  the PAM library will not log to the system log if it is not possible
  to load the module because it is missing in the system. This can be
  useful especially for modules which are not always installed on the
  system and are not required for correct authentication and
  authorization of the login session.

  Also, isn't it required to have:

  -auth   optional  pam_kwallet.so

  for pam_kallet to work, as it needs access to the password?

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

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

[Desktop-packages] [Bug 1868296] Re: Placing window buttons on the left breaks title bar rendering

** Summary changed:

- gnome-tweaks UI breaks on lower resolution
+ Placing window buttons on the left breaks title bar rendering

** No longer affects: gnome-tweaks (Ubuntu)

** Summary changed:

- Placing window buttons on the left breaks title bar rendering
+ Placing window buttons on the left breaks gnome-tweaks title bar rendering

** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Low

** Also affects: gnome-tweaks (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-tweaks (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Placing window buttons on the left breaks gnome-tweaks title bar
  rendering

Status in gnome-tweaks package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  On 1366 * 768 resolution of my laptop (Dell E7259) gnome-tweaks UI
  breaks and some parts of it go missing.

  After maximizing the window, it works as normal again.

  Ubuntu versions I tried and had this problem:
  1. Ubuntu 19.10
  2. Ubuntu 20.20 daily iso

  Ubuntu versions I tried and do not have this problem:
  1. ubuntu 18.04

  Update: this problem only happens when window buttons are placed at
  left side of it.

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

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

[Desktop-packages] [Bug 1868614] Re: Login starts at native resolution before visibly switching to the configured resolution

Yes, to progress the issue please report it to the upstream developers
at:

  https://gitlab.gnome.org/GNOME/gnome-shell/issues

and then tell us the new bug ID.

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

Title:
  Login starts at native resolution before visibly switching to the
  configured resolution

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

Bug description:
  This happens on Ubuntu 19.10 and still happening on Ubuntu 20.04

  Let me give a little background

  My laptop (Razer Stealth) has a built in display with default 3840 by 2160.
  I currently have it set up to 1920 by 1080, as it drains the battery faster 
using the higher resolution.

  At login, the resolution show at 1920 by 1080, but after entering the
  password, the screen changes the resolution back to the default (3840
  by 2160), but once the desktop of the user loads it changes back to
  1920 by 1080.

  The change of resolution can be noticeable because the size of the mouse 
pointer becomes much smaller when logging in.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2020-03-17 08:21:46,611 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed
   virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. Skylake GT2 [HD Graphics 520] [1a58:674d]
  InstallationDate: Installed on 2019-09-28 (178 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  MachineType: Razer Blade Stealth
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=3eed045c-673f-4583-9b55-d04adb18adc3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Tags:  wayland-session focal ubuntu reproducible
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-03-17 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: ABCDEF
  dmi.board.name: SKYBAY
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: ABCDEF
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/30/2015:svnRazer:pnBladeStealth:pvr1.04:rvnINTELCorporation:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.name: Blade Stealth
  dmi.product.sku: RZ09-01682E24
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer
  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 N/A
  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/1868614/+subscriptions

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

[Desktop-packages] [Bug 1867757] Re: Please pull Mutter cursor fixes for DisplayLink devices

It means a fix has been committed to SCM (somewhere) for inclusion in
the next update or release.

Including upstream commits is a new policy we just started to make bug
tracking for packaging easier. There is no Ubuntu repo containing this
fix right now so I totally agree and understand the new policy can be
confusing.

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

Title:
  Please pull Mutter cursor fixes for DisplayLink devices

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  For GNOME/Wayland to use hardware cursors on DisplayLink devices
  (proprietary userspace driver for USB 3 devices), the following Mutter
  fixes should be included:

  Mutter 3.34 branch (tentatively 3.34.5):
  - https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1116 Initialize 
cursor support on GPU hotplug (backport to 3.34)

  Mutter 3.36 (currently master) branch (tentatively 3.36.1):
  - https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1079 Handle lack of 
explicit cursor planes better
  - https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1097 Initialize 
cursor support on GPU hotplug

  Without "Initialize cursor support on GPU hotplug" performance on
  hotplugged DisplayLink devices that create a new DRM device node
  suffers, because Mutter uses a software cursor which implies that
  DisplayLink needs to update the whole screen on every cursor motion.

  Without "Handle lack of explicit cursor planes better" there will not
  be a cursor at all on DisplayLink devices in Mutter 3.36.

  I would assume that the 3.34 branch is relevant to Ubuntu 19.10 and
  the 3.36 branch is relevant to Ubuntu 20.04.

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

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

[Desktop-packages] [Bug 1869344] Re: gnome-shell right mouse click brings minimized windows to foreground

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

Sounds closely related to bug 1868896. But see also bug 1868911 (comment
#2).

** This bug has been marked a duplicate of bug 1868896
   Minimized windows reappear when closing the overview

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

Title:
  gnome-shell right mouse click  brings minimized windows to foreground

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In today's update of Ubuntu 20.04, if I do this:

  * Run Firefox non-maximized
  * Run another app (eg nautilus or gnome-terminal)
  * Minimize the other app
  * Right-click on the firefox window

  then the other app suddenly re-appears. You can only interact with its
  titlebar, though - you can't type into gnome-terminal or choose a file
  in nautilus. Using the titlebar, you can move it around and if you
  click on the maximize icon or double-click to maximize it, it explodes
  out into nothingness (effectively, it re-minimizes). You can't
  minimize it, though, using the minimize button.

  This happens both in Wayland and in X11 and it happens with all
  extensions disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  Uname: Linux 5.6.0-050600rc7-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 17:50:39 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (270 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2019-12-08 (110 days ago)

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

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

[Desktop-packages] [Bug 1584716] Re: Text corruption in various Gnome apps since Xenial upgrade

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

apport-collect 1584716

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

** Tags added: xenial

** Package changed: gnome-desktop (Ubuntu) => xorg (Ubuntu)

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

** Bug watch removed: freedesktop.org Bugzilla #88584
   https://bugs.freedesktop.org/show_bug.cgi?id=88584

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

Title:
  Text corruption in various Gnome apps since Xenial upgrade

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Since the Ubuntu Xenial upgrade, I've had various instances of text
  corruption. I use a gnome-shell session. I (think) see this only if
  the laptop has suspended and restored.

  I'm using the intel graphics driver from ppa:oibaf/graphics-drivers
  (in a failed attempt to try and upgrade myself out of the issue), but
  it was happening before changing to a custom PPA.

  This affects such a wide array of parts of the desktop that I suspect
  it's likely to be a basic X11 driver or GTK-level bug.

  Screenshots attached.

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

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

[Desktop-packages] [Bug 1574800] Re: Cannot switch between windows by clicking or click OS-related UI

It's probably not realistic to expect any gnome-shell fixes in 16.04.
Please upgrade to 18.04 or later.

** Package changed: gnome-desktop (Ubuntu) => gnome-desktop3 (Ubuntu)

** Package changed: gnome-desktop3 (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Cannot switch between windows by clicking or click OS-related UI

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  I cannot switch between windows by clicking (must use alt+tab); I also
  cannot click the user profile on login (must use "Enter" on
  highlighted user account). Just updated to Ubuntu 160.4

  The problem exists no matter which windows I try to click between
  (Chrome, Firefox, Terminal, Settings, etc...). Major productivity
  bug...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Apr 25 14:23:28 2016
  InstallationDate: Installed on 2015-10-05 (202 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  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/1574800/+subscriptions

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

[Desktop-packages] [Bug 1687245] Re: Improper lock screen scaling on 4k monitor

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Package changed: gnome-desktop (Ubuntu) => gnome-desktop3 (Ubuntu)

** Changed in: gnome-desktop3 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Improper lock screen scaling on 4k monitor

Status in Ubuntu GNOME:
  New
Status in gnome-desktop3 package in Ubuntu:
  Won't Fix

Bug description:
  I'm using Ubuntu Gnome 17.04, fully up to date. On the lock screen,
  the features are much smaller than the normal ones on a 4k monitor,
  even with no scaling enabled. I'll give you any other information
  you'd like upon request, I just don't know what else you'd need to
  replicate this. Please tell me if I should submit this to gnome
  instead.

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

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

[Desktop-packages] [Bug 1644268] Re: GnomeDesktop-WARNING **: Failed to load XKB rules file

** Package changed: gnome-desktop (Ubuntu) => gnome-desktop3 (Ubuntu)

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

Title:
  GnomeDesktop-WARNING **: Failed to load XKB rules file

Status in Canonical System Image:
  In Progress
Status in gnome-desktop:
  Expired
Status in gnome-desktop3 package in Ubuntu:
  Triaged

Bug description:
  Reproduce:
  open System Settings -> Languages -> External Keyboard

  What happens:
  No available layouts are shown, an error appears in the log:

  (process:11469): GnomeDesktop-WARNING **: Failed to load XKB rules
  file /usr/share/X11/xkb/rules/evdev.xml: Failed to open file
  '/usr/share/X11/xkb/rules/evdev.xml': No such file or directory

  What should happen:
  ltinkl | it should be using XKB_CONFIG_ROOT
  ltinkl | which we override inside our snappy env

  See also: http://paste.ubuntu.com/23482865/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644268/+subscriptions

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

[Desktop-packages] [Bug 1702258] Re: aplications don't use tray icons on ubuntu-session

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Package changed: gnome-desktop (Ubuntu) => gnome-desktop3 (Ubuntu)

** Changed in: gnome-desktop3 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  aplications don't use tray icons on ubuntu-session

Status in gnome-desktop3 package in Ubuntu:
  Won't Fix

Bug description:
  After switching from gnome-session to ubuntu-session on 17.10 clipit, 
remmina, seafile and others apps don't show up in tray icons in gnome-shell. 
  Switching back to gnome-session in lightdm everything works perfectly.
  Only pidgin shows up in gnome-session and ubuntu-session.

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

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

[Desktop-packages] [Bug 1793918] Re: Add/reintroduce setting to enable suspend on lid-close with external monitors attached

** Tags added: bionic

** Package changed: gnome-desktop (Ubuntu) => gnome-desktop3 (Ubuntu)

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

Title:
  Add/reintroduce setting to enable suspend on lid-close with external
  monitors attached

Status in gnome-desktop3 package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-tweaks package in Ubuntu:
  Confirmed

Bug description:
  With Ubuntu 18.04 my laptop does not suspend when lid is closed while
  external monitors are attached. This might be a good behavior for many
  users but I want to have my laptop suspend again when I close it.

  Some time ago there was an option in gsettings scheme org.gnome
  .settings-daemon.plugins.power named lid-close-suspend-with-external-
  monitor (introduced in
  https://bugzilla.gnome.org/show_bug.cgi?id=657201). This settings
  seems to have no effect anymore and seems to be removed in the current
  scheme (repatched in ubuntu's version only).

  This is realy anoying because at the moment the laptop does not
  suspend at all with lid-close action because the nvidia driver
  discover the internal built-in display under DP-4. That makes gnome
  think that there is an external monitor connected. Is this a bug in
  nvidia driver or a problem of gnome-desktop's gnome-rr which thinks
  that only monitors with "LVDS|Lvds|LCD|eDP|DSI" in it's name could be
  an internal display? However this might be another bug. I want to
  suspend with realy external monitors attached anyhow because I always
  use my laptop as second/third monitor.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

** Changed in: gnome-desktop (Ubuntu)
   Status: In Progress => Fix Committed

** Tags added: fixed-in-3.36.1 fixed-upstream

** No longer affects: gnome-shell (Ubuntu)

** Also affects: gnome-desktop (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: gnome-desktop (Ubuntu Focal)
   Importance: Low
 Assignee: Michael Steenbeek (gymnasiast)
   Status: Fix Committed

** Changed in: gnome-desktop (Ubuntu Eoan)
   Status: New => Fix Committed

** Changed in: gnome-desktop (Ubuntu Eoan)
   Importance: Undecided => Low

** Changed in: gnome-desktop (Ubuntu Eoan)
 Assignee: (unassigned) => Michael Steenbeek (gymnasiast)

** Tags added: fixed-in-3.34.5

** Also affects: gnome-desktop3 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-desktop3 (Ubuntu Eoan)
   Status: New => Fix Committed

** Changed in: gnome-desktop3 (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: gnome-desktop3 (Ubuntu Eoan)
   Importance: Undecided => Low

** Changed in: gnome-desktop3 (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: gnome-desktop3 (Ubuntu Eoan)
 Assignee: (unassigned) => Michael Steenbeek (gymnasiast)

** Changed in: gnome-desktop3 (Ubuntu Focal)
 Assignee: (unassigned) => Michael Steenbeek (gymnasiast)

** No longer affects: gnome-desktop (Ubuntu)

** No longer affects: gnome-desktop (Ubuntu Eoan)

** No longer affects: gnome-desktop (Ubuntu Focal)

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

Title:
  gnome-shell displays date incorrectly for nl_NL locale

Status in gnome-desktop:
  Unknown
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 1726192] Re: 17.10 Login To Wayland Fails Unless User Logs Into Unity First

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Package changed: gnome-desktop (Ubuntu) => gnome-desktop3 (Ubuntu)

** Changed in: gnome-desktop3 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  17.10 Login To Wayland Fails Unless User Logs Into Unity First

Status in gnome-desktop3 package in Ubuntu:
  Won't Fix

Bug description:
  After upgrading from 17.04 to 17.10, it's not possible to log into the
  default 'Ubuntu' session unless I log into Unity first. If I log into
  Unity, immediately log out, then log into Ubuntu, it logs in without
  issue.

  If I don't log into Unity first, the login attempt to Ubuntu briefly
  shows a black screen, then returns immediately to the login prompt.

  From suspend or hibernate, I can continue using the Wayland session
  without issue through poweroff. If I reboot or shutdown, the first
  login needs to be Unity, then I can log out and back to the Ubuntu
  session normally.

  Attached is some output from syslog showing gnome-session related
  errors. I'm not sure if they show the specific error, but they do
  appear at the time a first Ubuntu login is attempted.

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

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

[Desktop-packages] [Bug 1843201] Re: Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome

A few issues here:

  * Ubuntu 19.04 is no longer supported

  * "Unity in Wayland" does not exist

  * gnome-desktop is not a package that has been used since 14.04

** Package changed: gnome-desktop (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Unity in Wayland prompts for keyboard focus on each run of ssh-
  askpass-gnome

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in ssh-askpass-fullscreen package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Invalid

Bug description:
  When using a Wayland-based Unity session on Ubuntu 19.04:

  1. Have ssh-askpass-gnome as your askpass program.
  2. ssh-add -c 
  3. `ssh` to a host

  Each time, before the ssh-askpass prompt is shown, Unity shows this
  dialog:

  +-+
  | |
  | ssh-askpass wants to inhibit shortcuts  |
  | |
  | You can restore Shortcuts by pressing   |
  | Super+Escape.   |
  | |
  |_|
  |   Deny | Allow  |
  +-+

  This is mildly distracting, and it means that you need to hit ,
  answer, , instead of just answer .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ssh-askpass-gnome 1:7.9p1-10
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  8 15:04:25 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1
  InstallationDate: Installed on 2019-08-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago)

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

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

[Desktop-packages] [Bug 1726192] Re: 17.10 Login To Wayland Fails Unless User Logs Into Unity First

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

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

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

Title:
  17.10 Login To Wayland Fails Unless User Logs Into Unity First

Status in gnome-desktop3 package in Ubuntu:
  Won't Fix

Bug description:
  After upgrading from 17.04 to 17.10, it's not possible to log into the
  default 'Ubuntu' session unless I log into Unity first. If I log into
  Unity, immediately log out, then log into Ubuntu, it logs in without
  issue.

  If I don't log into Unity first, the login attempt to Ubuntu briefly
  shows a black screen, then returns immediately to the login prompt.

  From suspend or hibernate, I can continue using the Wayland session
  without issue through poweroff. If I reboot or shutdown, the first
  login needs to be Unity, then I can log out and back to the Ubuntu
  session normally.

  Attached is some output from syslog showing gnome-session related
  errors. I'm not sure if they show the specific error, but they do
  appear at the time a first Ubuntu login is attempted.

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

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

[Desktop-packages] [Bug 1848335] Re: xdg-open (and others) don't handle spaces in directory names properly

This bug was fixed in the package xdg-utils - 1.1.3-2ubuntu1

---
xdg-utils (1.1.3-2ubuntu1) focal; urgency=medium

  * Sync with Debian. Remaining change:
- Add debian/xdg-utils.links:
  + Symlink /usr/bin/xdg-open to /usr/bin/browse (LP: #1624022)

xdg-utils (1.1.3-2) unstable; urgency=medium

  [ Debian Janitor ]
  * Bump debhelper from old 10 to 12.
  * Set debhelper-compat version in Build-Depends.
  * Add upstream metadata info.

  [ Nicholas Guriev ]
  * Shift debian/NEWS content to the left.
  * Set Rules-Requires-Root: no in debian/control.
  * Obey the nocheck build option.
  * Bump Standards-Version to 4.5.0.
  * Add machine readable debian/copyright file.
  * Now uscan(1) watches FreeDesktop GitLab.
  * Add trailing new line into auto-generated patch header.
  * Drop redundant invocation dh_installchangelogs in debian/rules.
  * Install release notes as NEWS file in according P. 12.7 of the Debian
policy.
  * xdg-mime: Create config directory if it does not exist yet.
Closes: #652038.

  [ Rex Dieter ]
  * xdg-open: Do better pcmanfm check, fix AND operator. Closes: #908760,
Upstream: BR106636, BR106161.

  [ Alberto Salvia Novella ]
  * xdg-email: Support for Deepin.

  [ Mario van der Linde ]
  * Enable Cinnamon screensaver for XDG aware desktop environments (e.g. LXQt).

  [ Iain Lane ]
  * xdg-screensaver: Sanitise window name before sending it over the bus.
Closes: #910070, LP: #1743216, Upstream: BR108121.

  [ Andrea Tarocchi ]
  * xdg-open: correct handling directories with spaces in the name.
LP: #1848335, Upstream: #166.

 -- Jeremy Bicha   Sun, 29 Mar 2020 19:38:09 -0400

** Changed in: xdg-utils (Ubuntu)
   Status: New => Fix Released

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

Title:
  xdg-open (and others) don't handle spaces in directory names properly

Status in xdg-utils package in Ubuntu:
  Fix Released

Bug description:
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  xdg-utils: Installed: 1.1.2-1ubuntu2.3

  Environment:
  Shell: bash/fish (happens in both)
  DE: i3
  env:
  
XDG_DATA_DIRS=/home/barnex/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share/:/usr/share/i3:/home/barnex/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop
  XDG_CONFIG_DIRS=/etc/xdg/xdg-i3:/etc/xdg
   
  What I did:
  xdg-open "http://reddit.com; # while having a specific directory structure

  What I expected to happen:
  Open a new tab/window of my browser with the correct URL.

  What happened instead:
  xdg-open froze, and eventually crashed.

  I believe this issue in upstream caused the erratic behavior:
  https://gitlab.freedesktop.org/xdg/xdg-utils/issues/131

  xdg-utils seems to recursively look through directories for the
  .desktop file. In my setup this path includes a directory:

  "/home/barnex/.local/share/applications//wine//Programs//Zone.com
  Deluxe Games/"

  Instead of correctly looking into this directory, the next
  search_desktop_file call goes into the "/home/barnex/Games" - a
  directory outside of the search path.

  /home/barnex/Games in turn has a directory "/home/barnex/Games//epic-
  games-store//dosdevices//c://users//barnex//My Music/" - which again
  has a space, and thus makes the xdg-open go to "/home/barnex/Music" -
  another directory outside of my search path.

  In /home/barnex/Music there's a directory called ' The Final Boss -
  James Harmon - [Ambient - Breakbeat - Lo-Fi -Electronica] [2011]' -
  this just causes an infinite loop of adding more slashes to the path,
  resulting in calls like:

  + search_desktop_file chromium-browser.desktop
  
Music
  The Final Boss - James Harmon - [Ambient - Breakbeat - Lo-Fi
  -Electronica] [2011]/ http://reddit.com

  This eventually leads to a crash.

  Running 'xdg-settings get default-url-scheme-handler' with no
  arguments caused a similar behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xdg-utils 1.1.2-1ubuntu2.3
  ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: i3
  Date: Wed Oct 16 13:45:35 2019
  InstallationDate: Installed on 2016-11-20 (1059 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: xdg-utils
  UpgradeStatus: Upgraded to bionic on 2019-01-23 (265 days

[Desktop-packages] [Bug 1869641] [NEW] Failed to launch ibus daemon in Xwayland + gnome-shell 3.36.0

2020-03-29 Thread Tim Chen

Public bug reported:

Description:Ubuntu Focal Fossa (development branch)
Release:20.04

ibus 1.5.22-2ubuntu1

Steps to reproduce

  1. Upgrade to GNOME 3.36.0.
  2. Restart Ubuntu 20.04 daily with Wayland

What did you expect to happen
  The ibus daemon is launched.

What happened
  The ibus daemon is not running.


I can confirm I have an exact same issue in 
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2341 when login with wayland 
selected.

After applying this:
https://github.com/ibus/ibus/commit/8ce25208c3f4adfd290a032c6aa739d2b7580eb1
patch locally I can confirm it fixed my issue.

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


** Tags: focal gnome-shell ibus wayland

** Tags added: focal gnome-shell ibus wayland

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

Title:
  Failed to launch ibus daemon in Xwayland + gnome-shell 3.36.0

Status in ibus package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ibus 1.5.22-2ubuntu1

  Steps to reproduce

1. Upgrade to GNOME 3.36.0.
2. Restart Ubuntu 20.04 daily with Wayland

  What did you expect to happen
The ibus daemon is launched.

  What happened
The ibus daemon is not running.

  
  I can confirm I have an exact same issue in 
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2341 when login with wayland 
selected.

  After applying this:
  https://github.com/ibus/ibus/commit/8ce25208c3f4adfd290a032c6aa739d2b7580eb1
  patch locally I can confirm it fixed my issue.

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

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

[Desktop-packages] [Bug 1574800] [NEW] Cannot switch between windows by clicking or click OS-related UI

You have been subscribed to a public bug:

I cannot switch between windows by clicking (must use alt+tab); I also
cannot click the user profile on login (must use "Enter" on highlighted
user account). Just updated to Ubuntu 160.4

The problem exists no matter which windows I try to click between
(Chrome, Firefox, Terminal, Settings, etc...). Major productivity bug...

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: evince 3.18.2-1ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Apr 25 14:23:28 2016
InstallationDate: Installed on 2015-10-05 (202 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-desktop3 (Ubuntu)
 Importance: Medium
 Status: Confirmed


** Tags: amd64 apport-bug xenial
-- 
Cannot switch between windows by clicking or click OS-related UI
https://bugs.launchpad.net/bugs/1574800
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-desktop3 in Ubuntu.

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

[Desktop-packages] [Bug 1584716] [NEW] Text corruption in various Gnome apps since Xenial upgrade

You have been subscribed to a public bug:

Description:Ubuntu 16.04 LTS
Release:16.04

Since the Ubuntu Xenial upgrade, I've had various instances of text
corruption. I use a gnome-shell session. I (think) see this only if the
laptop has suspended and restored.

I'm using the intel graphics driver from ppa:oibaf/graphics-drivers (in
a failed attempt to try and upgrade myself out of the issue), but it was
happening before changing to a custom PPA.

This affects such a wide array of parts of the desktop that I suspect
it's likely to be a basic X11 driver or GTK-level bug.

Screenshots attached.

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: xenial
-- 
Text corruption in various Gnome apps since Xenial upgrade
https://bugs.launchpad.net/bugs/1584716
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 1644268] [NEW] GnomeDesktop-WARNING **: Failed to load XKB rules file

You have been subscribed to a public bug:

Reproduce:
open System Settings -> Languages -> External Keyboard

What happens:
No available layouts are shown, an error appears in the log:

(process:11469): GnomeDesktop-WARNING **: Failed to load XKB rules file
/usr/share/X11/xkb/rules/evdev.xml: Failed to open file
'/usr/share/X11/xkb/rules/evdev.xml': No such file or directory

What should happen:
ltinkl | it should be using XKB_CONFIG_ROOT
ltinkl | which we override inside our snappy env

See also: http://paste.ubuntu.com/23482865/

** Affects: canonical-devices-system-image
 Importance: Medium
 Status: In Progress

** Affects: gnome-desktop
 Importance: Medium
 Status: Expired

** Affects: gnome-desktop3 (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: patch
-- 
GnomeDesktop-WARNING **: Failed to load XKB rules file
https://bugs.launchpad.net/bugs/1644268
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-desktop3 in Ubuntu.

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

[Desktop-packages] [Bug 1687245] [NEW] Improper lock screen scaling on 4k monitor

You have been subscribed to a public bug:

I'm using Ubuntu Gnome 17.04, fully up to date. On the lock screen, the
features are much smaller than the normal ones on a 4k monitor, even
with no scaling enabled. I'll give you any other information you'd like
upon request, I just don't know what else you'd need to replicate this.
Please tell me if I should submit this to gnome instead.

** Affects: ubuntu-gnome
 Importance: Undecided
 Status: New

** Affects: gnome-desktop3 (Ubuntu)
 Importance: Undecided
 Status: Won't Fix

-- 
Improper lock screen scaling on 4k monitor
https://bugs.launchpad.net/bugs/1687245
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-desktop3 in Ubuntu.

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

[Desktop-packages] [Bug 1702258] [NEW] aplications don't use tray icons on ubuntu-session

You have been subscribed to a public bug:

After switching from gnome-session to ubuntu-session on 17.10 clipit, remmina, 
seafile and others apps don't show up in tray icons in gnome-shell. 
Switching back to gnome-session in lightdm everything works perfectly.
Only pidgin shows up in gnome-session and ubuntu-session.

** Affects: gnome-desktop3 (Ubuntu)
 Importance: Undecided
 Status: Won't Fix


** Tags: artful
-- 
aplications don't use tray icons on ubuntu-session
https://bugs.launchpad.net/bugs/1702258
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-desktop3 in Ubuntu.

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

[Desktop-packages] [Bug 1726192] [NEW] 17.10 Login To Wayland Fails Unless User Logs Into Unity First

You have been subscribed to a public bug:

After upgrading from 17.04 to 17.10, it's not possible to log into the
default 'Ubuntu' session unless I log into Unity first. If I log into
Unity, immediately log out, then log into Ubuntu, it logs in without
issue.

If I don't log into Unity first, the login attempt to Ubuntu briefly
shows a black screen, then returns immediately to the login prompt.

>From suspend or hibernate, I can continue using the Wayland session
without issue through poweroff. If I reboot or shutdown, the first login
needs to be Unity, then I can log out and back to the Ubuntu session
normally.

Attached is some output from syslog showing gnome-session related
errors. I'm not sure if they show the specific error, but they do appear
at the time a first Ubuntu login is attempted.

** Affects: gnome-desktop3 (Ubuntu)
 Importance: High
 Status: Won't Fix


** Tags: artful bot-comment gdm3 wayland
-- 
17.10 Login To Wayland Fails Unless User Logs Into Unity First
https://bugs.launchpad.net/bugs/1726192
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-desktop3 in Ubuntu.

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

[Desktop-packages] [Bug 1843201] [NEW] Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome

You have been subscribed to a public bug:

When using a Wayland-based Unity session on Ubuntu 19.04:

1. Have ssh-askpass-gnome as your askpass program.
2. ssh-add -c 
3. `ssh` to a host

Each time, before the ssh-askpass prompt is shown, Unity shows this
dialog:

+-+
| |
| ssh-askpass wants to inhibit shortcuts  |
| |
| You can restore Shortcuts by pressing   |
| Super+Escape.   |
| |
|_|
|   Deny | Allow  |
+-+

This is mildly distracting, and it means that you need to hit ,
answer, , instead of just answer .

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ssh-askpass-gnome 1:7.9p1-10
ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep  8 15:04:25 2019
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 
canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1
InstallationDate: Installed on 2019-08-27 (12 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
SourcePackage: openssh
UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: Won't Fix

** Affects: ssh-askpass-fullscreen (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-bug disco wayland-session
-- 
Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome 
https://bugs.launchpad.net/bugs/1843201
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1720465] Re: HiDPI scaling does not hold across reboot in a virtual machine

** Summary changed:

- HiDPI scaling does not hold across reboot
+ HiDPI scaling does not hold across reboot in a virtual machine

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

Title:
  HiDPI scaling does not hold across reboot in a virtual machine

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 17.10 Beta (updated as of 29 Sept 2017) on Parallels Desktop 
13.  When changing the HiDPI scaling to 200% everything looks good, but on 
restart the settings are reset to 100%.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['coherence-gnome-sh...@parallels.com']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-05-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-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/ubuntu/+source/gnome-shell/+bug/1720465/+subscriptions

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

[Desktop-packages] [Bug 1854603] Re: Greek (polytonic) keyboard layout not handling some accent marks

** Changed in: gnome-shell (Ubuntu)
   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/1854603

Title:
  Greek (polytonic) keyboard layout not handling some accent marks

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell
  3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm.

  I’m using a US keyboard which is set up to switch between English and
  polytonic Greek.

  This has been working satisfactorily in 18.04.

  However, in 20.04, I’m noticing that I can’t add the breathing marks
  or diaeresis to lower-case letters in polytonic Greek. When I try to
  type the marks, they appear on the screen but disappear immediately
  once I release the shift key.

  I can add breathing marks and diaeresis to capital letters.

  So far, I've seen this behaviour in LibreOffice, gedit and Firefox.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-29 (38 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191028)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1
  Tags:  focal wayland-session
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1720465] Re: HiDPI scaling does not hold across reboot

** Tags added: eoan

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

Title:
  HiDPI scaling does not hold across reboot

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 17.10 Beta (updated as of 29 Sept 2017) on Parallels Desktop 
13.  When changing the HiDPI scaling to 200% everything looks good, but on 
restart the settings are reset to 100%.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['coherence-gnome-sh...@parallels.com']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-05-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-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/ubuntu/+source/gnome-shell/+bug/1720465/+subscriptions

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

[Desktop-packages] [Bug 1767342] Re: Dosplay scale factor reset after changing screen size or reboot

I think this is probably correct, unfortunately.

Virtual machines implement screen resizing by unplugging the old virtual
screen and plugging in a new virtual screen of a different resolution,
to match the window size. So to gnome-shell it is a new monitor being
plugged in and that should default to scale 100%.

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: gnome-shell (Ubuntu)
   Status: Won't Fix => Invalid

** Changed in: gnome-shell (Ubuntu)
   Status: Invalid => Won't Fix

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

Title:
  Dosplay scale factor reset after changing screen size or reboot

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Steps to reproduce

  1. Take computer with HiDPI monitor
  2. Install bionic in VM, install open-vm-tools && open-vm-tools-desktop and 
enable hi-dpi
  3. Settings-Devices-Display-Scale to 200% and press apply
  4. Drag VM window corner for changing VM screen size or simple reboot VM.

  Scale resets to 100%

  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'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Fri Apr 27 14:20:34 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=203b7377-6f0c-4d39-a33f-db18baece74c ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  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/ubuntu/+source/gnome-shell/+bug/1767342/+subscriptions

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

[Desktop-packages] [Bug 1869610] Re: Desktop resolution will not go above 1024 * 768 (4:3)

It appears the problem here might be that Xorg can't detect your monitor
specs properly when plugged in via analog VGA. Please try:

 * plugging it in again

 * a different VGA cable

 * a digital connection instead like DisplayPort or DVI.

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

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

Title:
  Desktop resolution will not go above 1024 * 768 (4:3)

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Fresh install of Ubuntu 19.10 on an Acer AX3995-EF308 hooked to HP
  2159m, cannot select any higher resolution than 1024*768

  Description:  Ubuntu 19.10
  Release:  19.10

  xorg:
Installed: 1:7.7+19ubuntu12
Candidate: 1:7.7+19ubuntu12
Version table:
   *** 1:7.7+19ubuntu12 500
  500 http://ca.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 15:11:25 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:074f]
  InstallationDate: Installed on 2020-03-22 (6 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Acer Aspire X3995
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=e838af89-e069-4a74-b6c8-2247d6f3f026 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-A3
  dmi.board.name: Aspire X3995
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-A3:bd10/29/2012:svnAcer:pnAspireX3995:pvr:rvnAcer:rnAspireX3995:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Aspire X3995
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  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/xorg-server/+bug/1869610/+subscriptions

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

[Desktop-packages] [Bug 1869358] Re: Gnome Workspaces Show Phantom Windows

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

** This bug has been marked a duplicate of bug 1868911
   Exiting overview causes windows from other workspaces to be visible

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

Title:
  Gnome Workspaces Show Phantom Windows

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  All workspaces in Gnome are showing phantom windows from all other
  workspaces.

  Steps to reproduce:
  1
  - Have any program(s) open on any workspace(s)
  - Switch to another workspace via the Activities Overview
  - Phantom window(s) from all other workspaces are there
  2
  - Switch workspace via ctrl+alt+up/down prevents phantom windows from 
appearing
  - Access the Activities Overview from there without switching workspace 
causes phantom windows to appear

  Xorg:
  Phantom windows cannot be interacted with
  Phantom windows prevents what is behind it from being interacted with

  Wayland:
  Phantom windows can be interacted with
  Phantom windows do not appear to be considered in "focus"
  Phantom windows' title bars don't get highlighted and the close button 
remains gray instead of orange

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  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: Fri Mar 27 04:16:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-23 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  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/1869358/+subscriptions

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

[Desktop-packages] [Bug 1869520] Re: the windows hang after shifting

This sounds like bug 1868911 or bug 1868896. If you don't think so then
please explain in more detail what "shifting" means.

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

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

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

Title:
  the windows hang after shifting

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I want to shift open windows, like files, browsers, etc. they
  freeze and hang and I can neither minimize nor close that window.

  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
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 28 21:05:02 2020
  DistUpgraded: 2020-03-26 22:02:16,208 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed
   virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon RX 560 [1043:04bc]
  InstallationDate: Installed on 2020-02-02 (55 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. AB350M-Gaming 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=5909a9b7-eb21-439d-a04c-2c42bf662b3c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-03-26 (1 days ago)
  dmi.bios.date: 05/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F31
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350M-Gaming 3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF31:bd05/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350M-Gaming 3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-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/1869520/+subscriptions

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

[Desktop-packages] [Bug 1868911] Re: Exiting overview causes windows from other workspaces to be visible

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

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

Title:
  Exiting overview causes windows from other workspaces to be visible

Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  $ dpkg-query -W gnome-shell
  gnome-shell 3.36.0-2ubuntu1
  $ lsb_release -rc
  Release:20.04
  Codename:   focal
  $ _ 

  
  When I toggle in and out of the overview on an empty workspace, windows from 
other workspaces appear.  They are not interactable, so this seems more like a 
rendering bug than the windows really being teleported to another workspace.  
Switching back to another workspace that has windows causes the ghost windows 
to disappear.  Opening a window in the empty workspace makes it appear on top 
of the ghost windows, and I have to switch to another workspace and back again 
to make only the new window be visible.

  I am using the vanilla "GNOME" session type.  I did not observe this
  behaviour with gnome-shell 3.35.91-1ubuntu2.

  As well as the annoyance factor, of course there's a privacy angle to showing 
random windows at surprising times.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2011-11-06 (3062 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 3.36.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Tags: wayland-session focal third-party-packages
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-25 (29 days ago)
  UserGroups: adm admin cdrom dialout docker libvirt lpadmin lxd plugdev 
sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1869414] Re: Running applications always appear on the desktop

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

** This bug has been marked a duplicate of bug 1868911
   Exiting overview causes windows from other workspaces to be visible

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

Title:
  Running applications always appear on the desktop

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04

  No matter which virtual desktop is in focus, applications running on
  other virtual desktop are displayed even if minimized. This makes it
  impossible to interact with desktop icons without closing  all running
  applications. It is not possible to interact with the application
  itself when it's displayed erroneously, unless you return to its
  original virtual desktop.

  I've reinstalled from two different daily images and have been able to
  reproduce the problem each time.

  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: Fri Mar 27 14:22:31 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e1) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1458:2311]
  InstallationDate: Installed on 2020-03-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324)
  MachineType: System76 Thelio
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_4u488c@/vmlinuz-5.4.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_4u488c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2019
  dmi.bios.vendor: System76
  dmi.bios.version: F42a Z5
  dmi.board.asset.tag: Default string
  dmi.board.name: Thelio
  dmi.board.vendor: System76
  dmi.board.version: thelio-r1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76
  dmi.chassis.version: thelio-r1
  dmi.modalias: 
dmi:bvnSystem76:bvrF42aZ5:bd08/22/2019:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:
  dmi.product.family: Default string
  dmi.product.name: Thelio
  dmi.product.sku: Default string
  dmi.product.version: thelio-r1
  dmi.sys.vendor: System76
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  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/xorg/+bug/1869414/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/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 1869488] Re: when launching new app all windows of opened apps appear but are not controllable

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

** This bug has been marked a duplicate of bug 1868896
   Minimized windows reappear when closing the overview

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

Title:
  when launching new app all windows of opened apps appear but are not
  controllable

Status in mutter package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  all available updates installed at time of reporting

   every now and then when I open an Application, all (minimized)
  windows of other running applications appear on the screen and the
  interaction with them is impossible.

   neither the window control buttons nor the window content is reacting
  on mouse interaction - the whole window is in non-focus mode. only
  after clicking on the panel icon of said window to minimize and reopen
  an interaction is possible.

   i have no direct clue where to start further investigation, yet I
  would guess it be an bug in mutter/clutter, x.org or the nvidia-driver

   this is clearly a show stopper!

   i will try to see if this annoyance appears with wayland and/or
  noveau too, yet I'd appreciate any guidance in helping to fix this bug

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

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

[Desktop-packages] [Bug 1869637] Re: hidden windows appear as opened after clicking the "Show Applications" button twice

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

** This bug has been marked a duplicate of bug 1868896
   Minimized windows reappear when closing the overview

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

Title:
  hidden windows appear as opened after clicking the "Show Applications"
  button twice

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce this problem:

  1. Click on the Ubuntu Dock to open any application e.g. Nautilus.
  2. A window with the contents of this application appears.
  3. Click the (-) hide button of the window. The window hides from the desktop.
  4. Click the "Show Applications" button of the Ubuntu Dock.
  5. After the list of available applications appears click the same button 
again. The system returns back to the desktop view.
  6. Notice that the previously hidden window now appears as open on the 
desktop. However, it is only rendered and it is not functional. One cannot 
click on this window to hide it again, move it to another location or use the 
application associated with it. The only way to return to normal is to click 
the icon of this application on the Ubuntu Dock and in this case the window 
opens properly i.e. it is rendered again but this time it can be used.

  Expected behaviour:

  After step (5) one should return to the desktop with the window of the
  opened application still hidden.

  Note that if several applications have been opened and their windows
  hidden then after operation (5) all previously hidden windows are now
  rendered on the desktop but they are not functional, as described
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  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 03:00:40 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-12 (46 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  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/+bug/1869637/+subscriptions

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

[Desktop-packages] [Bug 1869608] Re: Applications are not returning to the correct workspace

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

I'm guessing this is another form of bug 1868911 so let's assume so
until proven otherwise.

** This bug has been marked a duplicate of bug 1868911
   Exiting overview causes windows from other workspaces to be visible

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

Title:
  Applications are not returning to the correct workspace

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I wake my display, all applications are showing on the same
  workspace, regardless of where they actually are. As soon as I switch
  workspaces, they all go to the right workspaces as they should have
  been. It's only when the display first wakes up.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 13:00:32 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-24 (614 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-07 (81 days ago)

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

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

[Desktop-packages] [Bug 1869492] Re: Merge xdg-utils 1.1.3-2 (main) from Debian unstable (main)

2020-03-29 Thread Jeremy Bicha

** Changed in: xdg-utils (Ubuntu)
   Status: New => Fix Released

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

Title:
  Merge xdg-utils 1.1.3-2 (main) from Debian unstable (main)

Status in xdg-utils package in Ubuntu:
  Fix Released

Bug description:
  Please merge xdg-utils 1.1.3-2 (main) from Debian unstable (main)

  Sorry, I cannot work on this merge myself. It fixes LP: #1848335.

  These Ubuntu changes are now in Debian, or not needed anymore, and can be 
dropped:
* Use perl's decode() to ensure we don't pass invalid UTF-8 to D-Bus,
  as doing so triggers an assertion from libdbus which makes us crash.
  LP: #1743216 (Debian #910070, Upstream #108121)
* Drop lp779156-lubuntu.diff:
  - Lubuntu no longer uses LXDE and Sylpheed.
* Drop CVE-2017-18266*.patch:
  - The fixes were applied upstream.
* Drop proper-lxqt-handling.patch:
  - Proper LXQt support was merged upstream.

  Except this change, which is not in Debian:
- Add debian/xdg-utils.links:
  + Symlink /usr/bin/xdg-open to /usr/bin/browse (LP: #1624022)

  Changelog entries since current focal version 1.1.3-1ubuntu2:

  xdg-utils (1.1.3-2) unstable; urgency=medium

[ Debian Janitor ]
* Bump debhelper from old 10 to 12.
* Set debhelper-compat version in Build-Depends.
* Add upstream metadata info.

[ Nicholas Guriev ]
* Shift debian/NEWS content to the left.
* Set Rules-Requires-Root: no in debian/control.
* Obey the nocheck build option.
* Bump Standards-Version to 4.5.0.
* Add machine readable debian/copyright file.
* Now uscan(1) watches FreeDesktop GitLab.
* Add trailing new line into auto-generated patch header.
* Drop redundant invocation dh_installchangelogs in debian/rules.
* Install release notes as NEWS file in according P. 12.7 of the Debian
  policy.
* xdg-mime: Create config directory if it does not exist yet.
  Closes: #652038.

[ Rex Dieter ]
* xdg-open: Do better pcmanfm check, fix AND operator. Closes: #908760,
  Upstream: BR106636, BR106161.

[ Alberto Salvia Novella ]
* xdg-email: Support for Deepin.

[ Mario van der Linde ]
* Enable Cinnamon screensaver for XDG aware desktop environments (e.g. 
LXQt).

[ Iain Lane ]
* xdg-screensaver: Sanitise window name before sending it over the bus.
  Closes: #910070, LP: #1743216, Upstream: BR108121.

[ Andrea Tarocchi ]
* xdg-open: correct handling directories with spaces in the name.
  LP: #1848335, Upstream: #166.

   -- Nicholas Guriev   Fri, 13 Mar 2020 19:17:44 +0300

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1869492/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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] Missing required logs.

2020-03-29 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1860764

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

-- 
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.

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 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen

2020-03-29 Thread 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/1869571

** Tags added: iso-testing

-- 
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 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/ubuntu/+source/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 1845623] Re: on screen keyboard leaves dark marks on screen after being hidden

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

** Tags added: fixed-in-3.36.1 fixed-upstream

-- 
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:
  New
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 1860764] Re: Line out audio device is missing after resume-from-suspend

** Changed in: linux (Ubuntu)
   Status: Expired => New

** Changed in: pulseaudio (Ubuntu)
   Status: Expired => 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/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.

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 1866851] Re: lock screen scaled down backgound image in top left corner

** Tags added: fixed-in-3.36.1 fixed-upstream

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

-- 
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:
  Unknown
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 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen

More detail from #8 test, I had closed the 'displays' setup, and of
course could no longer select anything from applications when clicked
(no icons in selection), but search bar does work; so I used the search
function.

Results in a tiny scroll area which isn't high enough to fully display
"Displays Choose how to use connected.." but is close.. I can scroll
down/up in the tiny window.

Also by entering a single letter (search function) I can have some icons
appear for selection, selections work but icons are larger than window
so it requires a fair amount of scrolling.  My findings are exactly as
per OP (except I have default Ubuntu 20.04 background), and a few apps
(firefox, nautilus, ..) opened in my upper display from earlier QA-
testing..

-- 
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 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/ubuntu/+source/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 1869637] [NEW] hidden windows appear as opened after clicking the "Show Applications" button twice

2020-03-29 Thread Panos Asproulis

Public bug reported:

Steps to reproduce this problem:

1. Click on the Ubuntu Dock to open any application e.g. Nautilus.
2. A window with the contents of this application appears.
3. Click the (-) hide button of the window. The window hides from the desktop.
4. Click the "Show Applications" button of the Ubuntu Dock.
5. After the list of available applications appears click the same button 
again. The system returns back to the desktop view.
6. Notice that the previously hidden window now appears as open on the desktop. 
However, it is only rendered and it is not functional. One cannot click on this 
window to hide it again, move it to another location or use the application 
associated with it. The only way to return to normal is to click the icon of 
this application on the Ubuntu Dock and in this case the window opens properly 
i.e. it is rendered again but this time it can be used.

Expected behaviour:

After step (5) one should return to the desktop with the window of the
opened application still hidden.

Note that if several applications have been opened and their windows
hidden then after operation (5) all previously hidden windows are now
rendered on the desktop but they are not functional, as described above.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.0-2ubuntu1
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 03:00:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-02-12 (46 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-03-27 (2 days ago)

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


** Tags: amd64 apport-bug focal

** Summary changed:

- hidden windows appear as opened after clicking the "Show Applications" button
+ hidden windows appear as opened after clicking the "Show Applications" button 
twice

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

Title:
  hidden windows appear as opened after clicking the "Show Applications"
  button twice

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce this problem:

  1. Click on the Ubuntu Dock to open any application e.g. Nautilus.
  2. A window with the contents of this application appears.
  3. Click the (-) hide button of the window. The window hides from the desktop.
  4. Click the "Show Applications" button of the Ubuntu Dock.
  5. After the list of available applications appears click the same button 
again. The system returns back to the desktop view.
  6. Notice that the previously hidden window now appears as open on the 
desktop. However, it is only rendered and it is not functional. One cannot 
click on this window to hide it again, move it to another location or use the 
application associated with it. The only way to return to normal is to click 
the icon of this application on the Ubuntu Dock and in this case the window 
opens properly i.e. it is rendered again but this time it can be used.

  Expected behaviour:

  After step (5) one should return to the desktop with the window of the
  opened application still hidden.

  Note that if several applications have been opened and their windows
  hidden then after operation (5) all previously hidden windows are now
  rendered on the desktop but they are not functional, as described
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  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 03:00:40 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-12 (46 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  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/+bug/1869637/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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

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

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

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

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

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/ubuntu/+source/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

Ubuntu 20.04 QA-test; using daily on 
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

I saw https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571
last night on #ubuntu-bugs-announce, and I think this box maybe has
similar screen setup, so I thought I'd do some general play, then look
for bug.

adjust displays to match my setup (one monitor above other; what
settings describes as monitor.2 is my lower, also mark the lower (was
right) as my primary display)

on opening menu however - icons come out but quickly disappear (or could
be described as come out from bottom right, shrink (below date on top
panel) then disappear ???  it's very quick but menu is un-operational as
per https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571

Of note - the Frequent-All heading keeps jumping as if being re-drawn
constantly.  However this wasn't always visible, but if left at the menu
position (where no options are shown) the shaking becomes rather obvious
but only images "Frequent  All", happening whichever is underlined
(orange) and keeps shaking when I move mouse.

-- 
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 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/ubuntu/+source/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 1869635] [NEW] the menu "Dash to Dock Settings" is visible

2020-03-29 Thread Panos Asproulis

Public bug reported:

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)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot which displays the problem"
   
https://bugs.launchpad.net/bugs/1869635/+attachment/5343153/+files/Screenshot-20200330023038-402x535.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/1869635

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

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

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 1865351] Re: Update to poppler 0.86.1 in Focal

This bug was fixed in the package poppler - 0.86.1-0ubuntu1

---
poppler (0.86.1-0ubuntu1) focal; urgency=medium

  * New upstream version (lp: #1865351)

 -- Sebastien Bacher   Fri, 27 Mar 2020 17:31:07
+0100

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

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

Title:
  Update to poppler 0.86.1 in Focal

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Please update to poppler 0.86.1 in Focal

  https://gitlab.freedesktop.org/poppler/poppler/-/blob/master/NEWS

  Release 0.86.1:
  core:
  * Fix regression in Browse Link handling
  * Internal code improvements

  Release 0.86.0:
  core:
  * Fix link content exfiltration attack
  * Splash: Implement gouraudTriangleShadedFill for some non parametrized 
shadings
  * Fix case unsensitive search for Old Hungarian, Warang Citi, Medefaidrin and 
Adlam
  * Internal code improvements

  glib:
  * Automatic handle of page's cropbox on annots. Issue #129
  * Fix memory leak if poppler_document_new_from_file fails
  * Minor speed optimization on poppler_page_get_annot_mapping

  utils:
  * pdfdetach: add 'savefile' option
  * pdftoppm/pdftocairo: Fix more odd/even mismatch

  qt5:
  * Fix loading from iodevice

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

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

[Desktop-packages] [Bug 1869357] Re: package libreoffice-math 1:6.4.2-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menub

This bug was fixed in the package libreoffice - 1:6.4.2-0ubuntu2

---
libreoffice (1:6.4.2-0ubuntu2) focal; urgency=medium

  * Merge with debian
  * libreoffice-math: Add Breaks/Replaces libreoffice-common (<< 1:6.4.2~rc1~)
(LP: #1869357)
  * debian/patches/poppler-0.86.diff: Fix build with poppler 0.86.0

libreoffice (1:6.4.2-3) UNRELEASED; urgency=medium

  [ Rene Engelhard ]
  * debian/patches/Fix-build-with-boost-lesser-than-1.68.diff: add from
gerrit, thanks Rico Tschichholz

  * debian/rules:
- use default boost (and thus system-mdds) again and revert
  BOOST_MINVER= (>= 1.68) change
- fix redland dependencies for libreoffice-core-nogui

  [ Jochen Sprickerhof ]
  * debian/control.in:
- Prefer libreoffice-core-nogui for -nogui variants
  Closes: #954319
- Drop -core-nogui in non -nogui packages (if -nogui exists)
- Fix report_builder and firebird nogui depends

libreoffice (1:6.4.2-2) unstable; urgency=medium

  * debian/control.in:
- make libreoffice-common Breaks: libreoffice-core (<< 1:6.4.2~rc1)
  (closes: #954323)
- also add Breaks/Replaces libreoffice-common (<< 1:6.4.2~rc1~) to
  -nogui (for now)
- allow libreoffice-draw-nogui in -impress-noguis Depends:
  (closes: #954318)

 -- Rico Tzschichholz   Fri, 27 Mar 2020 08:31:30
+0100

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

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

Title:
  package libreoffice-math 1:6.4.2-0ubuntu1 failed to install/upgrade:
  trying to overwrite
  
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
  which is also in package libreoffice-common 1:6.4.1-0ubuntu1

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Looks like a file has moved between packages which caused the dpkg
  error. The issue was resolved with "apt --fix-broken install" but
  nevertheless we should make sure nobody sees this on upgrade. Thanks!

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-math 1:6.4.2-0ubuntu1
  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
  Date: Fri Mar 27 11:22:13 2020
  ErrorMessage: trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.1-0ubuntu1
  InstallationDate: Installed on 2019-12-01 (117 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  2.0.1
  SourcePackage: libreoffice
  Title: package libreoffice-math 1:6.4.2-0ubuntu1 failed to install/upgrade: 
trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.1-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1841793] Re: Don't update to 2.63.1

2020-03-29 Thread Jeremy Bicha

** Tags removed: version-skip-2.63.1
** Tags added: version-skip-2.65.3

** Summary changed:

- Don't update to 2.63.1
+ Don't update to 2.65.3

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

Title:
  Don't update to 2.65.3

Status in glibmm2.4 package in Ubuntu:
  Triaged

Bug description:
  The .news entry starts with

  '2.63.1: (unstable):
  Distro packagers should probably not package this yet.'

  Let's follow upstream's advice there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1841793/+subscriptions

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

[Desktop-packages] [Bug 1868019] Re: [FFe] Add method to enable fractional scaling

2020-03-29 Thread Robert Ancell

Messages sent to the documentation and translation mailing lists,
currently awaiting moderation.

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

Title:
  [FFe] Add method to enable fractional scaling

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

Bug description:
  [Impact]
  Fractional scaling is currently requires enabling an experimental feature in 
Mutter to use it. We would like this feature to be easily enabled by users. A 
lot of modern hardware supports high DPI displays and these are often not 
usable without some form of fractional scaling.

  [Test Case]
  1. Open Settings
  2. Select Displays panels

  Expected result:
  Scale can be set to fractional values (e.g. 125%). There is a UI control to 
enable fractional scaling (disabled by default).

  Observed result:
  Scale can only be set to multiples of 100% unless the feature was enabled. No 
UI control is shown for Fractional scaling.

  [Regressional Potential]
  New UI code risks introducing new bugs. Users enabling fractional scaling may 
trigger new bugs.

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

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

[Desktop-packages] [Bug 1869632] Re: AppArmor profile denied access to /etc/mdns.allow

2020-03-29 Thread Rich McAllister

Bug also exists in package version 1.27.3-1 (current version in focal)

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

Title:
  AppArmor profile denied access to /etc/mdns.allow

Status in cups-filters package in Ubuntu:
  New

Bug description:
  Many messages in syslog

  audit: type=1400 audit(1585521672.468:40): apparmor="DENIED"
  operation="open" profile="/usr/sbin/cups-browsed"
  name="/etc/mdns.allow" pid=1323 comm="cups-browsed" requested_mask="r"
  denied_mask="r" fsuid=0 ouid=0

  This is caused by configuring libnss-mdns to resolve local names, with
  /etc/nsswitch.conf containing

  hosts:  files mdns [NOTFOUND=return] dns myhostname

  libnss-mnds reads /etc/mdns.allow to find which domains to resolve,
  but /etc/apparmor.d/usr.sbin.cups-browsed does not allow access.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.11-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: XFCE
  Date: Sun Mar 29 15:48:11 2020
  InstallationDate: Installed on 2019-10-24 (157 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_c53lph@/vmlinuz-5.3.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_c53lph ro quiet splash
  SourcePackage: cups-filters
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1869632/+subscriptions

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

[Desktop-packages] [Bug 1869632] [NEW] AppArmor profile denied access to /etc/mdns.allow

2020-03-29 Thread Rich McAllister

Public bug reported:

Many messages in syslog

audit: type=1400 audit(1585521672.468:40): apparmor="DENIED"
operation="open" profile="/usr/sbin/cups-browsed" name="/etc/mdns.allow"
pid=1323 comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0
ouid=0

This is caused by configuring libnss-mdns to resolve local names, with
/etc/nsswitch.conf containing

hosts:  files mdns [NOTFOUND=return] dns myhostname

libnss-mnds reads /etc/mdns.allow to find which domains to resolve, but
/etc/apparmor.d/usr.sbin.cups-browsed does not allow access.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups-browsed 1.25.11-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
CupsErrorLog:
 
CurrentDesktop: XFCE
Date: Sun Mar 29 15:48:11 2020
InstallationDate: Installed on 2019-10-24 (157 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Papersize: letter
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_c53lph@/vmlinuz-5.3.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_c53lph ro quiet splash
SourcePackage: cups-filters
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-bug eoan

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

Title:
  AppArmor profile denied access to /etc/mdns.allow

Status in cups-filters package in Ubuntu:
  New

Bug description:
  Many messages in syslog

  audit: type=1400 audit(1585521672.468:40): apparmor="DENIED"
  operation="open" profile="/usr/sbin/cups-browsed"
  name="/etc/mdns.allow" pid=1323 comm="cups-browsed" requested_mask="r"
  denied_mask="r" fsuid=0 ouid=0

  This is caused by configuring libnss-mdns to resolve local names, with
  /etc/nsswitch.conf containing

  hosts:  files mdns [NOTFOUND=return] dns myhostname

  libnss-mnds reads /etc/mdns.allow to find which domains to resolve,
  but /etc/apparmor.d/usr.sbin.cups-browsed does not allow access.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.11-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: XFCE
  Date: Sun Mar 29 15:48:11 2020
  InstallationDate: Installed on 2019-10-24 (157 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_c53lph@/vmlinuz-5.3.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_c53lph ro quiet splash
  SourcePackage: cups-filters
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1869632/+subscriptions

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

[Desktop-packages] [Bug 1868019] Re: [FFe] Add method to enable fractional scaling

2020-03-29 Thread Sebastien Bacher

** Summary changed:

- Add method to enable fractional scaling
+ [FFe] Add method to enable fractional scaling

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

Title:
  [FFe] Add method to enable fractional scaling

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

Bug description:
  [Impact]
  Fractional scaling is currently requires enabling an experimental feature in 
Mutter to use it. We would like this feature to be easily enabled by users. A 
lot of modern hardware supports high DPI displays and these are often not 
usable without some form of fractional scaling.

  [Test Case]
  1. Open Settings
  2. Select Displays panels

  Expected result:
  Scale can be set to fractional values (e.g. 125%). There is a UI control to 
enable fractional scaling (disabled by default).

  Observed result:
  Scale can only be set to multiples of 100% unless the feature was enabled. No 
UI control is shown for Fractional scaling.

  [Regressional Potential]
  New UI code risks introducing new bugs. Users enabling fractional scaling may 
trigger new bugs.

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

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

[Desktop-packages] [Bug 1868019] Re: Add method to enable fractional scaling

2020-03-29 Thread Robert Ancell

Requesting a UI freeze exception for this with the rationale being in
the bug description. The wording on the UI might change before this is
released, but no other changes are required.

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

** Description changed:

[Impact]
- Fractional scaling is currently requires enabling an experimental feature in
Mutter to use it. We would like this feature to be easily enabled by users.
+ Fractional scaling is currently requires enabling an experimental feature in
Mutter to use it. We would like this feature to be easily enabled by users. A
lot of modern hardware supports high DPI displays and these are often not
usable without some form of fractional scaling.

[Test Case]
1. Open Settings
2. Select Displays panels

Expected result:
Scale can be set to fractional values (e.g. 125%). There is a UI control to
enable fractional scaling (disabled by default).

Observed result:
Scale can only be set to multiples of 100% unless the feature was enabled. No
UI control is shown for Fractional scaling.

[Regressional Potential]
New UI code risks introducing new bugs. Users enabling fractional scaling may
trigger new bugs.

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

Title:
Add method to enable fractional scaling

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

Bug description:
[Impact]
Fractional scaling is currently requires enabling an experimental feature in
Mutter to use it. We would like this feature to be easily enabled by users. A
lot of modern hardware supports high DPI displays and these are often not
usable without some form of fractional scaling.

[Test Case]
1. Open Settings
2. Select Displays panels

Expected result:
Scale can be set to fractional values (e.g. 125%). There is a UI control to
enable fractional scaling (disabled by default).

Observed result:
Scale can only be set to multiples of 100% unless the feature was enabled. No
UI control is shown for Fractional scaling.

[Regressional Potential]
New UI code risks introducing new bugs. Users enabling fractional scaling may
trigger new bugs.

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

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

[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2020-03-29 Thread Wojciech Migda

I am experiencing the freeze regularly since I attached an external
display through HDMI.

Dell Inc. Inspiron 5558/086DKN, BIOS A18 12/30/2019
Ubuntu 18.04.4

Freeze happens on kernels:
4.15.0-91
4.15.0-34
I didn't try other versions.

I tried the ahci.mobile_lpm_policy={0,1} setting (#58) - with both 0 and 1 
freeze happened again.
I tried the extra X11 Intel settings (#42), but since then I removed the X11 
intel driver package xserver-xorg-video-intel, as it is labeled as discouraged 
for HW newer than 2007, X11 doesn't recognize this configuration section.

Some extra details:
I have docker running.
VirtualBox modules are loaded at boot.

journalctl doesn't show anything right before the freeze.

Can someone point me what sort of extra logging/tracing I can enable to
poinpoint the issue?

Thanks.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1869592] Re: Lubuntu LXQt - Locale fallback fails

2020-03-29 Thread Gunnar Hjalmarsson

Good. Adding a link to it here for reference.

https://discourse.lubuntu.me/t/please-keep-multi-language-support-in-
lxqt-like-in-lxde/877

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

Title:
  Lubuntu LXQt - Locale fallback fails

Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  I have always been a locale-fallback feature user. With Lubuntu 18.04
  LTS I haven't any problem.

  The computer users are fluent in those languages, except in English
  (the default one). If there's a string untranslated in one language,
  it jumps and try to show the string of the next listed language and so
  on.

  In most of the programs the fallback works, but the LXQt menu, some
  details like some dialogs, don't work well, even editing
  /etc/default/locale file:

  LANG="pt_BR.UTF-8"
  LANGUAGE="pt_BR:pt_PT:gl_ES:es_ES:en"
  LC_NUMERIC="pt_PT.UTF-8"
  LC_TIME="pt_PT.UTF-8"
  LC_MONETARY="pt_PT.UTF-8"
  LC_PAPER="pt_PT.UTF-8"
  LC_NAME="pt_PT.UTF-8"
  LC_ADDRESS="pt_PT.UTF-8"
  LC_TELEPHONE="pt_PT.UTF-8"
  LC_MEASUREMENT="pt_PT.UTF-8"
  LC_IDENTIFICATION="pt_PT.UTF-8"

  It doesn't work even installing and configuring locales with language-
  selector-gnome, which is not installed by default on Lubuntu 20.04.

  If I try to change the main language, I see that most of translations
  exist, either in one language or another. So the problem is with the
  fallback, determined by the LANGUAGE = section in /etc/default/locale.

  *Using Spanish as first language:*
  https://emma.cloud.tabdigital.eu/s/X2TRjAnPjJq76JH
  *Using Galician as first language:*
  https://emma.cloud.tabdigital.eu/s/StbkHwFPC27kzLo

  We are not the only ones with this problem, polyglot people or
  inhabitants of regions with languages with two different spelling
  regulations can be combined in this way.

  Thank you for your attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: language-selector-gnome 0.203
  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: LXQt
  Date: Sun Mar 29 18:20:30 2020
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2020-03-29 (0 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200316)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SourcePackage: language-selector
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1869592/+subscriptions

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

[Desktop-packages] [Bug 1869610] [NEW] Desktop resolution will not go above 1024 * 768 (4:3)

2020-03-29 Thread Eric Polley

Public bug reported:

Fresh install of Ubuntu 19.10 on an Acer AX3995-EF308 hooked to HP
2159m, cannot select any higher resolution than 1024*768

Description:Ubuntu 19.10
Release:19.10

xorg:
  Installed: 1:7.7+19ubuntu12
  Candidate: 1:7.7+19ubuntu12
  Version table:
 *** 1:7.7+19ubuntu12 500
500 http://ca.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 29 15:11:25 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:074f]
InstallationDate: Installed on 2020-03-22 (6 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Acer Aspire X3995
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=e838af89-e069-4a74-b6c8-2247d6f3f026 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/29/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P11-A3
dmi.board.name: Aspire X3995
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-A3:bd10/29/2012:svnAcer:pnAspireX3995:pvr:rvnAcer:rnAspireX3995:rvr:cvnAcer:ct3:cvr:
dmi.product.family: Acer Desktop
dmi.product.name: Aspire X3995
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
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

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


** Tags: amd64 apport-bug eoan ubuntu

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

Title:
  Desktop resolution will not go above 1024 * 768 (4:3)

Status in xorg package in Ubuntu:
  New

Bug description:
  Fresh install of Ubuntu 19.10 on an Acer AX3995-EF308 hooked to HP
  2159m, cannot select any higher resolution than 1024*768

  Description:  Ubuntu 19.10
  Release:  19.10

  xorg:
Installed: 1:7.7+19ubuntu12
Candidate: 1:7.7+19ubuntu12
Version table:
   *** 1:7.7+19ubuntu12 500
  500 http://ca.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 15:11:25 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:074f]
  InstallationDate: Installed on 2020-03-22 (6 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Acer Aspire X3995
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=e838af89-e069-4a74-b6c8-2247d6f3f026 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-A3
  dmi.board.name: Aspire X3995
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-A3:bd10/29/2012:svnAcer:pnAspireX3995:pvr:rvnAcer:rnAspireX3995:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Aspire X3995
  dmi.sys.vendor:

[Desktop-packages] [Bug 1869608] [NEW] Applications are not returning to the correct workspace

2020-03-29 Thread Dean Henrichsmeyer

Public bug reported:

When I wake my display, all applications are showing on the same
workspace, regardless of where they actually are. As soon as I switch
workspaces, they all go to the right workspaces as they should have
been. It's only when the display first wakes up.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.0-2ubuntu1
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
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 29 13:00:32 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-07-24 (614 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-07 (81 days ago)

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


** Tags: amd64 apport-bug champagne focal

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

Title:
  Applications are not returning to the correct workspace

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I wake my display, all applications are showing on the same
  workspace, regardless of where they actually are. As soon as I switch
  workspaces, they all go to the right workspaces as they should have
  been. It's only when the display first wakes up.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 13:00:32 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-24 (614 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-07 (81 days ago)

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

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

[Desktop-packages] [Bug 1869592] Re: Lubuntu LXQt - Locale fallback fails

2020-03-29 Thread Pablo César Galdo Regueiro

Thank you.
I've already submitted a report to the Lubuntu team, via forum.

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

Title:
  Lubuntu LXQt - Locale fallback fails

Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  I have always been a locale-fallback feature user. With Lubuntu 18.04
  LTS I haven't any problem.

  The computer users are fluent in those languages, except in English
  (the default one). If there's a string untranslated in one language,
  it jumps and try to show the string of the next listed language and so
  on.

  In most of the programs the fallback works, but the LXQt menu, some
  details like some dialogs, don't work well, even editing
  /etc/default/locale file:

  LANG="pt_BR.UTF-8"
  LANGUAGE="pt_BR:pt_PT:gl_ES:es_ES:en"
  LC_NUMERIC="pt_PT.UTF-8"
  LC_TIME="pt_PT.UTF-8"
  LC_MONETARY="pt_PT.UTF-8"
  LC_PAPER="pt_PT.UTF-8"
  LC_NAME="pt_PT.UTF-8"
  LC_ADDRESS="pt_PT.UTF-8"
  LC_TELEPHONE="pt_PT.UTF-8"
  LC_MEASUREMENT="pt_PT.UTF-8"
  LC_IDENTIFICATION="pt_PT.UTF-8"

  It doesn't work even installing and configuring locales with language-
  selector-gnome, which is not installed by default on Lubuntu 20.04.

  If I try to change the main language, I see that most of translations
  exist, either in one language or another. So the problem is with the
  fallback, determined by the LANGUAGE = section in /etc/default/locale.

  *Using Spanish as first language:*
  https://emma.cloud.tabdigital.eu/s/X2TRjAnPjJq76JH
  *Using Galician as first language:*
  https://emma.cloud.tabdigital.eu/s/StbkHwFPC27kzLo

  We are not the only ones with this problem, polyglot people or
  inhabitants of regions with languages with two different spelling
  regulations can be combined in this way.

  Thank you for your attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: language-selector-gnome 0.203
  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: LXQt
  Date: Sun Mar 29 18:20:30 2020
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2020-03-29 (0 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200316)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SourcePackage: language-selector
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1869592/+subscriptions

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

[Desktop-packages] [Bug 1869605] [NEW] Please remove mozjs60; superseded by mozjs68

2020-03-29 Thread Jeremy Bicha

Public bug reported:

Please remove mozjs60 from Ubuntu focal. The supported version is
mozjs68 (It is the JavaScript engine from Firefox LTS).

mozjs60 has no remaining reverse dependencies in focal.

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


** Tags: focal

** Summary changed:

- Please remove mozjs60; superseded by mozjs69
+ Please remove mozjs60; superseded by mozjs68

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

Title:
  Please remove mozjs60; superseded by mozjs68

Status in mozjs60 package in Ubuntu:
  New

Bug description:
  Please remove mozjs60 from Ubuntu focal. The supported version is
  mozjs68 (It is the JavaScript engine from Firefox LTS).

  mozjs60 has no remaining reverse dependencies in focal.

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

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

[Desktop-packages] [Bug 1869592] Re: Lubuntu LXQt - Locale fallback fails

2020-03-29 Thread Gunnar Hjalmarsson

Thanks for your report!

The fallback language feature, represented by the LANGUAGE environment
variable, is a gettext thing, and should work in all applications which
use gettext to pick the translations.

Non-GNU applications, for instance Firefox, Thunderbird and LibreOffice,
don't use gettext, so the LANGUAGE variable is ignored. As regards LXQt,
I don't really know what the problem may be. Possibly the desktop
includes its own ways to set the display language, in a similar way that
KDE does.

In any case it's not a bug in language-selector, so closing this bug.

I would recommend you to bring up the issue in some Lubuntu and/or LXQt
forum.

** Changed in: language-selector (Ubuntu)
   Status: New => Invalid

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

Title:
  Lubuntu LXQt - Locale fallback fails

Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  I have always been a locale-fallback feature user. With Lubuntu 18.04
  LTS I haven't any problem.

  The computer users are fluent in those languages, except in English
  (the default one). If there's a string untranslated in one language,
  it jumps and try to show the string of the next listed language and so
  on.

  In most of the programs the fallback works, but the LXQt menu, some
  details like some dialogs, don't work well, even editing
  /etc/default/locale file:

  LANG="pt_BR.UTF-8"
  LANGUAGE="pt_BR:pt_PT:gl_ES:es_ES:en"
  LC_NUMERIC="pt_PT.UTF-8"
  LC_TIME="pt_PT.UTF-8"
  LC_MONETARY="pt_PT.UTF-8"
  LC_PAPER="pt_PT.UTF-8"
  LC_NAME="pt_PT.UTF-8"
  LC_ADDRESS="pt_PT.UTF-8"
  LC_TELEPHONE="pt_PT.UTF-8"
  LC_MEASUREMENT="pt_PT.UTF-8"
  LC_IDENTIFICATION="pt_PT.UTF-8"

  It doesn't work even installing and configuring locales with language-
  selector-gnome, which is not installed by default on Lubuntu 20.04.

  If I try to change the main language, I see that most of translations
  exist, either in one language or another. So the problem is with the
  fallback, determined by the LANGUAGE = section in /etc/default/locale.

  *Using Spanish as first language:*
  https://emma.cloud.tabdigital.eu/s/X2TRjAnPjJq76JH
  *Using Galician as first language:*
  https://emma.cloud.tabdigital.eu/s/StbkHwFPC27kzLo

  We are not the only ones with this problem, polyglot people or
  inhabitants of regions with languages with two different spelling
  regulations can be combined in this way.

  Thank you for your attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: language-selector-gnome 0.203
  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: LXQt
  Date: Sun Mar 29 18:20:30 2020
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2020-03-29 (0 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200316)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SourcePackage: language-selector
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1869592/+subscriptions

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

[Desktop-packages] [Bug 1869597] [NEW] FF74.0 in UBudgie 19.10 : LIBDBUSMENU-GTK-CRITICAL dbusmenu_menuitem_property_set_shortcut: assertion 'gtk_accelerator_valid(key, modifier)' failed

2020-03-29 Thread Coeur Noir

Public bug reported:

Hi,

on a freshly installed Ubuntu Budgie 19.10, I've noticed Firefox is kind of 
slow at start : 
⋅ I can launch Firefox but it’s unresponsive for a moment ( no blinking cursor 
anywhere )
⋅ then cursor eventually appears in address bar but blinking slowly and not 
usable,
⋅ still, clicking anywhere has no effect, or effect delayed much later,
⋅ a moment later, cursor blinks at its usual pace and Firefox becomes 
responsive as expected.
The whole process takes 30 seconds to 1 minute and Firefox runs rather ok later 
on with some slow moments though ( sometimes tabs are slow to react, or any 
interactions with buttons in FF menu ).

Same behavior in safe-mode ( without any FF addons )

Same without any Budgie applets regarding app-menu ( such as pixel-saver
or global-menu applets ).

see also :
⋅ 
https://discourse.ubuntubudgie.org/t/firefox-in-19-10-is-kind-of-slow-to-start/3265
⋅ https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/813775




django@ASGARD:~$ firefox --safe-mode 

(firefox:19093): LIBDBUSMENU-GTK-CRITICAL **: 22:08:02.177:
dbusmenu_menuitem_property_set_shortcut: assertion
'gtk_accelerator_valid(key, modifier)' failed

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

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

Title:
  FF74.0 in UBudgie 19.10 : LIBDBUSMENU-GTK-CRITICAL
  dbusmenu_menuitem_property_set_shortcut: assertion
  'gtk_accelerator_valid(key, modifier)' failed

Status in firefox package in Ubuntu:
  New

Bug description:
  Hi,

  on a freshly installed Ubuntu Budgie 19.10, I've noticed Firefox is kind of 
slow at start : 
  ⋅ I can launch Firefox but it’s unresponsive for a moment ( no blinking 
cursor anywhere )
  ⋅ then cursor eventually appears in address bar but blinking slowly and not 
usable,
  ⋅ still, clicking anywhere has no effect, or effect delayed much later,
  ⋅ a moment later, cursor blinks at its usual pace and Firefox becomes 
responsive as expected.
  The whole process takes 30 seconds to 1 minute and Firefox runs rather ok 
later on with some slow moments though ( sometimes tabs are slow to react, or 
any interactions with buttons in FF menu ).

  Same behavior in safe-mode ( without any FF addons )

  Same without any Budgie applets regarding app-menu ( such as pixel-
  saver or global-menu applets ).

  see also :
  ⋅ 
https://discourse.ubuntubudgie.org/t/firefox-in-19-10-is-kind-of-slow-to-start/3265
  ⋅ https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/813775

  

  
  django@ASGARD:~$ firefox --safe-mode 

  (firefox:19093): LIBDBUSMENU-GTK-CRITICAL **: 22:08:02.177:
  dbusmenu_menuitem_property_set_shortcut: assertion
  'gtk_accelerator_valid(key, modifier)' failed

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

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

[Desktop-packages] [Bug 1869599] Re: scp-dbus-service.py crashed with SIGSEGV in __nptl_deallocate_tsd()

2020-03-29 Thread Apport retracing service

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

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

** Package changed: ubuntu => system-config-printer (Ubuntu)

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1867480
   scp-dbus-service.py crashed with SIGSEGV in _PyObject_GC_UNTRACK_impl()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  scp-dbus-service.py crashed with SIGSEGV in __nptl_deallocate_tsd()

Status in system-config-printer package in Ubuntu:
  New

Bug description:
  It happened in the background

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: system-config-printer-common 1.5.12-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Mar 29 15:54:48 2020
  ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py
  InstallationDate: Installed on 2020-03-20 (9 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200319)
  InterpreterPath: /usr/bin/python3.8
  Lpstat:
   device for Kyocera_ECOSYS_M5521cdn: implicitclass://Kyocera_ECOSYS_M5521cdn/
   device for minolta: socket://192.168.2.31:9100
  MachineType: Hewlett-Packard HP Z420 Workstation
  PackageArchitecture: all
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/minolta.ppd', 
'/etc/cups/ppd/Kyocera_ECOSYS_M5521cdn.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/minolta.ppd: Permission denied
   grep: /etc/cups/ppd/Kyocera_ECOSYS_M5521cdn.ppd: Permission denied
  ProcCmdline: /usr/bin/python3 
/usr/share/system-config-printer/scp-dbus-service.py
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=9316ef08-96e9-4d62-ab33-c8cb3d1f2db6 ro quiet splash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x507537:  mov%rcx,(%rdx)
   PC (0x00507537) ok
   source "%rcx" ok
   destination "(%rdx)" (0x0004) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: system-config-printer
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/python3/dist-packages/cups.cpython-38-x86_64-linux-gnu.so
   __nptl_deallocate_tsd () at pthread_create.c:301
   __nptl_deallocate_tsd () at pthread_create.c:256
   start_thread (arg=) at pthread_create.c:488
  Title: scp-dbus-service.py crashed with SIGSEGV in __nptl_deallocate_tsd()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 10/29/2019
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.96
  dmi.board.asset.tag: CZC4123JXT
  dmi.board.name: 1589
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.asset.tag: CZC4123JXT
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family:

[Desktop-packages] [Bug 1869598] [NEW] Gnome software find only snap packages

2020-03-29 Thread corrado venturini

Public bug reported:

On Ubuntu 20.04 installed gnome-software 3.35.91 click on the magnify
glass, enter gnome-tweaks  -> no application found. Same for synaptic
and gparted.

gnome software is missing installing from Ubuntu 20.04 LTS "Focal Fossa"
- Alpha amd64 (20200329)

corrado@corrado-x5-ff-0329:~$ inxi -Fx
System:Host: corrado-x5-ff-0329 Kernel: 5.4.0-18-generic x86_64 bits: 64 
compiler: gcc v: 9.2.1 Desktop: Gnome 3.36.0 
   Distro: Ubuntu 20.04 LTS (Focal Fossa) 
Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: 
 UEFI: American Megatrends 
   v: P1.10 date: 05/11/2017 
CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
   Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 802 
Graphics:  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: 
kernel bus ID: 00:02.0 
   Display: x11 server: X.Org 1.20.7 driver: i915 resolution: 
1920x1080~60Hz 
   OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 
20.0.2 direct render: Yes 
Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
   bus ID: 00:1f.3 
   Device-2: Logitech QuickCam Pro 9000 type: USB driver: 
snd-usb-audio,uvcvideo bus ID: 1-10:5 
   Sound Server: ALSA v: k5.4.0-18-generic 
Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 bus ID: 00:1f.6 
   IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
Drives:Local Storage: total: 2.05 TiB used: 6.17 GiB (0.3%) 
   ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 
232.89 GiB 
   ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
   ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 
GiB 
Partition: ID-1: / size: 31.25 GiB used: 6.16 GiB (19.7%) fs: ext4 dev: 
/dev/nvme0n1p5 
   ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
Sensors:   System Temperatures: cpu: 45.0 C mobo: N/A 
   Fan Speeds (RPM): N/A 
Info:  Processes: 214 Uptime: 1h 45m Memory: 7.49 GiB used: 1.37 GiB 
(18.3%) Init: systemd runlevel: 5 Compilers: 
   gcc: N/A Shell: bash v: 5.0.16 inxi: 3.0.38 
corrado@corrado-x5-ff-0329:~$

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-software 3.35.91-0ubuntu1
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: Sun Mar 29 18:49:57 2020
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2020-03-29 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-snap3.35.91-0ubuntu1
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-03-29 18-49-17.png"
   
https://bugs.launchpad.net/bugs/1869598/+attachment/5343011/+files/Screenshot%20from%202020-03-29%2018-49-17.png

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

Title:
  Gnome software find only snap packages

Status in gnome-software package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04 installed gnome-software 3.35.91 click on the magnify
  glass, enter gnome-tweaks  -> no application found. Same for synaptic
  and gparted.

  gnome software is missing installing from Ubuntu 20.04 LTS "Focal
  Fossa" - Alpha amd64 (20200329)

  corrado@corrado-x5-ff-0329:~$ inxi -Fx
  System:Host: corrado-x5-ff-0329 Kernel: 5.4.0-18-generic x86_64 bits: 64 
compiler: gcc v: 9.2.1 Desktop: Gnome 3.36.0 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: 
 UEFI: American Megatrends 
 v: P1.10 date: 05/11/2017 
  CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT 
MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 802 
  Graphics:  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: 
kernel bus ID: 00:02.0 
 Display: x11 server: X.Org 1.20.7 driver: i915 resolution: 
1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 630 (K

[Desktop-packages] [Bug 813775] Re: LIBDBUSMENU-GTK-CRITICAL **: dbusmenu_menuitem_property_set_shortcut: assertion `gtk_accelerator_valid(key, modifier)' failed

2020-03-29 Thread Coeur Noir

Hello,

I have this message on Ubuntu Budgie 19.10 freshky installed + FF74.0

Same if launched in safe mode with no addons.

Same if I don't use any Budgie applets regarding app-menus ( ie. pixel-
saver or global-menu )

See https://discourse.ubuntubudgie.org/t/firefox-in-19-10-is-kind-of-
slow-to-start/3265

as this bug seems to slow down Firefox starting + tabs management.

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

Title:
  LIBDBUSMENU-GTK-CRITICAL **: dbusmenu_menuitem_property_set_shortcut:
  assertion `gtk_accelerator_valid(key, modifier)' failed

Status in Global menubar extension:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Freshly installed system.  started firefox from gnome-terminal and saw
  this assertion hit.

  However, firefox seems to be running ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 6.0~b2+build1+nobinonly-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
  Uname: Linux 3.0.0-5-generic i686
  Architecture: i386
  Date: Wed Jul 20 13:28:26 2011
  FirefoxPackages:
   firefox 6.0~b2+build1+nobinonly-0ubuntu1
   flashplugin-installer 10.3.181.34ubuntu1
   adobe-flashplugin N/A
   icedtea-plugin 1.1.1-1ubuntu1
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110623)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: Upgraded to oneiric on 2011-07-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/globalmenu-extension/+bug/813775/+subscriptions

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

[Desktop-packages] [Bug 1869592] [NEW] Lubuntu LXQt - Locale fallback fails

2020-03-29 Thread Pablo César Galdo Regueiro

Public bug reported:

I have always been a locale-fallback feature user. With Lubuntu 18.04
LTS I haven't any problem.

The computer users are fluent in those languages, except in English (the
default one). If there's a string untranslated in one language, it jumps
and try to show the string of the next listed language and so on.

In most of the programs the fallback works, but the LXQt menu, some
details like some dialogs, don't work well, even editing
/etc/default/locale file:

LANG="pt_BR.UTF-8"
LANGUAGE="pt_BR:pt_PT:gl_ES:es_ES:en"
LC_NUMERIC="pt_PT.UTF-8"
LC_TIME="pt_PT.UTF-8"
LC_MONETARY="pt_PT.UTF-8"
LC_PAPER="pt_PT.UTF-8"
LC_NAME="pt_PT.UTF-8"
LC_ADDRESS="pt_PT.UTF-8"
LC_TELEPHONE="pt_PT.UTF-8"
LC_MEASUREMENT="pt_PT.UTF-8"
LC_IDENTIFICATION="pt_PT.UTF-8"

It doesn't work even installing and configuring locales with language-
selector-gnome, which is not installed by default on Lubuntu 20.04.

If I try to change the main language, I see that most of translations
exist, either in one language or another. So the problem is with the
fallback, determined by the LANGUAGE = section in /etc/default/locale.

*Using Spanish as first language:*
https://emma.cloud.tabdigital.eu/s/X2TRjAnPjJq76JH
*Using Galician as first language:*
https://emma.cloud.tabdigital.eu/s/StbkHwFPC27kzLo

We are not the only ones with this problem, polyglot people or
inhabitants of regions with languages with two different spelling
regulations can be combined in this way.

Thank you for your attention.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: language-selector-gnome 0.203
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: LXQt
Date: Sun Mar 29 18:20:30 2020
ExecutablePath: /usr/bin/gnome-language-selector
InstallationDate: Installed on 2020-03-29 (0 days ago)
InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200316)
InterpreterPath: /usr/bin/python3.8
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
PythonDetails: N/A
SourcePackage: language-selector
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: language-selector (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  Lubuntu LXQt - Locale fallback fails

Status in language-selector package in Ubuntu:
  New

Bug description:
  I have always been a locale-fallback feature user. With Lubuntu 18.04
  LTS I haven't any problem.

  The computer users are fluent in those languages, except in English
  (the default one). If there's a string untranslated in one language,
  it jumps and try to show the string of the next listed language and so
  on.

  In most of the programs the fallback works, but the LXQt menu, some
  details like some dialogs, don't work well, even editing
  /etc/default/locale file:

  LANG="pt_BR.UTF-8"
  LANGUAGE="pt_BR:pt_PT:gl_ES:es_ES:en"
  LC_NUMERIC="pt_PT.UTF-8"
  LC_TIME="pt_PT.UTF-8"
  LC_MONETARY="pt_PT.UTF-8"
  LC_PAPER="pt_PT.UTF-8"
  LC_NAME="pt_PT.UTF-8"
  LC_ADDRESS="pt_PT.UTF-8"
  LC_TELEPHONE="pt_PT.UTF-8"
  LC_MEASUREMENT="pt_PT.UTF-8"
  LC_IDENTIFICATION="pt_PT.UTF-8"

  It doesn't work even installing and configuring locales with language-
  selector-gnome, which is not installed by default on Lubuntu 20.04.

  If I try to change the main language, I see that most of translations
  exist, either in one language or another. So the problem is with the
  fallback, determined by the LANGUAGE = section in /etc/default/locale.

  *Using Spanish as first language:*
  https://emma.cloud.tabdigital.eu/s/X2TRjAnPjJq76JH
  *Using Galician as first language:*
  https://emma.cloud.tabdigital.eu/s/StbkHwFPC27kzLo

  We are not the only ones with this problem, polyglot people or
  inhabitants of regions with languages with two different spelling
  regulations can be combined in this way.

  Thank you for your attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: language-selector-gnome 0.203
  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: LXQt
  Date: Sun Mar 29 18:20:30 2020
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2020-03-29 (0 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200316)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SourcePackage: language-selector
  UpgradeStatus: No upgrade log

[Desktop-packages] [Bug 1869591] [NEW] After install the window 'ready to go' is locked

2020-03-29 Thread corrado venturini

Public bug reported:

Just installed from Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
gnome-initial-setup shows the window 'ready to go' the window can not be moved 
on screen and click on 'Open software now' has no effect.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-initial-setup 3.36.0-1ubuntu3
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: Sun Mar 29 17:14:57 2020
ExecutablePath: /usr/libexec/gnome-initial-setup
InstallationDate: Installed on 2020-03-29 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  After install the window 'ready to go' is locked

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  Just installed from Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  gnome-initial-setup shows the window 'ready to go' the window can not be 
moved on screen and click on 'Open software now' has no effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-initial-setup 3.36.0-1ubuntu3
  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: Sun Mar 29 17:14:57 2020
  ExecutablePath: /usr/libexec/gnome-initial-setup
  InstallationDate: Installed on 2020-03-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868523] Re: "ERROR couldn't save system state: Current machine isn't Zsys, nothing to create"

2020-03-29 Thread 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/1868523

** Tags added: iso-testing

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

Title:
  "ERROR couldn't save system state: Current machine isn't Zsys, nothing
  to create"

Status in gjs package in Ubuntu:
  Confirmed

Bug description:
  Hi, when I try to update the system I get this error even if the operations 
seem to complete.
  Hello.

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

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

[Desktop-packages] [Bug 1868523] Re: "ERROR couldn't save system state: Current machine isn't Zsys, nothing to create"

2020-03-29 Thread Paul White

** Tags added: focal

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

Title:
  "ERROR couldn't save system state: Current machine isn't Zsys, nothing
  to create"

Status in gjs package in Ubuntu:
  Confirmed

Bug description:
  Hi, when I try to update the system I get this error even if the operations 
seem to complete.
  Hello.

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

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

[Desktop-packages] [Bug 1869578] Re: PCI/internal sound card not detected

2020-03-29 Thread Hui Wang

I have no idea that makes your laptop slower. maybe a dmesg helps to
find the problem.

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  i updated ubuntu 14.04 and now no sound
  i used aplay -l and i've got this message : internal sound card not detected

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sun Mar 29 13:56:20 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2017-10-01 (910 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.product.name: Inspiron 15-3552

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

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

[Desktop-packages] [Bug 1868523] Re: "ERROR couldn't save system state: Current machine isn't Zsys, nothing to create"

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

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

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

Title:
  "ERROR couldn't save system state: Current machine isn't Zsys, nothing
  to create"

Status in gjs package in Ubuntu:
  Confirmed

Bug description:
  Hi, when I try to update the system I get this error even if the operations 
seem to complete.
  Hello.

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

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

[Desktop-packages] [Bug 1869522] Re: Simple Scan doesn't work

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

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

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

Title:
  Simple Scan doesn't work

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  The latest version of Simple Scan released for Ubuntu 18.04 LTS does
  not work.  Version 3.28.0-0ubuntu1 is installed.  When I click to
  launch it nothing happens.

  I initially reported the bug against Simple Scan, but they said it was
  a problem with the Ubuntu 18.04 LTS distribution.

  https://gitlab.gnome.org/GNOME/simple-scan/-/issues/159

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.14
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 28 15:29:05 2020
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2014-08-08 (2059 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.14
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2020-01-05 (82 days ago)

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

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

[Desktop-packages] [Bug 1818247] Re: Please enable remote desktop support in mutter for 19.04

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

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

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

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

Title:
  Please enable remote desktop support in mutter for 19.04

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-remote-desktop is apparently being included in Ubuntu 19.04, so
  mutter should be recompiled with remote desktop support enabled for
  Ubuntu, so people can actually use it.

  Then the comment at the end of the apt package description for gnome-
  remote-desktop saying that needs to be done can be removed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.30.2-6
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 10:10:18 2019
  InstallationDate: Installed on 2019-02-26 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to disco on 2019-02-26 (2 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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] monitors.xml.txt

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1869571/+attachment/5342951/+files/monitors.xml.txt

-- 
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 package in Ubuntu:
  New

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/ubuntu/+source/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] GsettingsChanges.txt

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1869571/+attachment/5342948/+files/GsettingsChanges.txt

-- 
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 package in Ubuntu:
  New

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/ubuntu/+source/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] ShellJournal.txt

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1869571/+attachment/5342950/+files/ShellJournal.txt

-- 
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 package in Ubuntu:
  New

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/ubuntu/+source/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] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1869571/+attachment/5342949/+files/ProcCpuinfoMinimal.txt

-- 
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 package in Ubuntu:
  New

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/ubuntu/+source/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

apport information

** Tags added: apport-collected focal third-party-packages

** Description changed:

  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

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1869571/+attachment/5342947/+files/Dependencies.txt

-- 
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 package in Ubuntu:
  New

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

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