[Bug 1900063] Re: Sync flatpak 1.8.2-3 (universe) from Debian sid (main)

2020-10-16 Thread Thomas Ward
Hello.

According to the tool to indicate whether a package is seeded or not,
Flatpak is currently seeded in Ubuntu Budgie and Xubuntu:

$ seeded-in-ubuntu flatpak
flatpak (from flatpak) is seeded in:
  ubuntu-budgie: supported
  xubuntu: supported
gir1.2-flatpak-1.0 (from flatpak) is seeded in:
  ubuntu-budgie: supported
  xubuntu: supported
libflatpak-dev (from flatpak) is seeded in:
  ubuntu-budgie: supported
  xubuntu: supported
libflatpak0 (from flatpak) is seeded in:
  ubuntu-budgie: supported
  xubuntu: supported

Ubuntu is now in Final Freeze - per the Final Freeze announcement [1],
packages need to fit one of these two categories:


1) Release critical bugs that affect ISOs, installers, or otherwise
   can't be fixed easily post-release.

2) Bug fixes that would be suitable for post-release SRUs, which we may
   choose to accept, reject, or shunt to -updates for 0-day SRUs on a
   case-by-case basis.  This second case should have SRU-style bugs filed
   with the appropriate template, referenced in changelog.


I don't see a justification included on the sync request that would put this 
request into either of the categories as this does not have any SRU template.

The only new changes I can see here are that it has a dependency on
DBus, but that you fix an issue with Parental Control checks.  That's
likely SRUable post-release.

However, I don't see justification to sync this at this time given we
are in Final Freeze.

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

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

Title:
  Sync flatpak 1.8.2-3 (universe) from Debian sid (main)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1900196] [NEW] Caribou on-screen keyboard can't be disabled on touchscreen laptop

2020-10-16 Thread Chris Combs
Public bug reported:

On my Dell E7470, the on-screen keyboard from Caribou appears when I
interact with a text entry box using the touchscreen. I have disabled
the keyboard in Universal Access and have tried several versions of a
third-party GNOME Shell extension, "Block Caribou," without success.

My understanding is that this may be a regression of #1723857.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Fri Oct 16 17:28:39 2020
DisplayManager: lightdm
InstallationDate: Installed on 2018-01-21 (999 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-08-10 (67 days ago)

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  Caribou on-screen keyboard can't be disabled on touchscreen laptop

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time

2020-10-16 Thread Andre_H
Same issue here with R-Go split
Interestingly I found one configuration that works, but horribly breaks other 
things:

first, have a look with xinput

$ xinput 
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
...
⎜   ↳ Hantick USB Keyboard Consumer Control id=20   [slave  pointer  (2)]
⎜   ↳ HID 0911:2188 Consumer Controlid=22   [slave  pointer  (2)]
⎜   ↳ HID 0911:2188 Mouse   id=24   [slave  pointer  (2)]
⎜   ↳ Hantick USB Keyboard Mouseid=25   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
...
↳ Hantick USB Keyboard  id=16   [slave  keyboard (3)]
↳ HID 0911:2188 System Control  id=17   [slave  keyboard (3)]
↳ HID 0911:2188 id=18   [slave  keyboard (3)]
↳ Hantick USB Keyboard System Control   id=19   [slave  keyboard (3)]
↳ Hantick USB Keyboard Consumer Control id=21   [slave  keyboard (3)]
↳ HID 0911:2188 Consumer Controlid=23   [slave  keyboard (3)]
↳ Hantick USB Keyboard Wireless Radio Control   id=26   [slave  
keyboard (3)]


The Hantick devices as well as the 0911:2188 devices are the R-Go Split (why so 
many?)
interestingly there is a wireless radio control???
Anyway, let's create a new group

$ xinput create-master rgosplit 0
$ xinput
⎡ Virtual core pointer  id=2[master pointer  (3)]
...
⎡ rgosplit pointer  id=27   [master pointer  (28)]
⎜   ↳ rgosplit XTEST pointerid=29   [slave  pointer  (27)]
⎣ rgosplit keyboard id=28   [master keyboard (27)]
↳ rgosplit XTEST keyboard   id=30   [slave  keyboard (28)]

and now add those 0911:2188 keyboard devices to it (note that you need
to replace the numbers in the commands)

$ xinput reattach 17 28
$ xinput reattach 18 28
$ xinput reattach 23 28
$ xinput
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
...
⎜   ↳ Hantick USB Keyboard Consumer Control id=20   [slave  pointer  (2)]
⎜   ↳ HID 0911:2188 Consumer Controlid=22   [slave  pointer  (2)]
⎜   ↳ HID 0911:2188 Mouse   id=24   [slave  pointer  (2)]
⎜   ↳ Hantick USB Keyboard Mouseid=25   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
...
↳ Hantick USB Keyboard  id=16   [slave  keyboard (3)]
↳ Hantick USB Keyboard System Control   id=19   [slave  keyboard (3)]
↳ Hantick USB Keyboard Consumer Control id=21   [slave  keyboard (3)]
↳ Hantick USB Keyboard Wireless Radio Control   id=26   [slave  
keyboard (3)]
⎡ rgosplit pointer  id=27   [master pointer  (28)]
⎜   ↳ rgosplit XTEST pointerid=29   [slave  pointer  (27)]
⎣ rgosplit keyboard id=28   [master keyboard (27)]
↳ HID 0911:2188 System Control  id=17   [slave  keyboard (28)]
↳ HID 0911:2188 id=18   [slave  keyboard (28)]
↳ HID 0911:2188 Consumer Controlid=23   [slave  keyboard (28)]
↳ rgosplit XTEST keyboard   id=30   [slave  keyboard (28)]

Now I can type with both keyboard halfs simultaneously in a gnome-terminal!
But when I switch to other applications, e.g. firefox, only one half can type...
Maybe someone can build up on this?

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

Title:
  Desktop briefly becomes unresponsive when typing on 2 keyboards at the
  same time

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1900167] [NEW] gnome-software Unable to install updates

2020-10-16 Thread corrado venturini
Public bug reported:

Click on 'Updates' and then on 'Restart & Update' I have a message:
Unable to install updates: GDBus.error... Prepared update not 
found:/var/lib/PackageKit/prepared-update

corrado@corrado-x2-gg-1009:~$ apt policy gnome-software
gnome-software:
  Installed: 3.38.0-2build1
  Candidate: 3.38.0-2build1
  Version table:
 *** 3.38.0-2build1 500
500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
100 /var/lib/dpkg/status
corrado@corrado-x2-gg-1009:~$ inxi -Fx
System:
  Host: corrado-x2-gg-1009 Kernel: 5.8.0-23-generic x86_64 bits: 64 
  compiler: gcc v: 10.2.0 Desktop: N/A Distro: Ubuntu 20.10 (Groovy Gorilla) 
Machine:
  Type: Desktop Mobo: ASRock model: H110M-G/M.2 
  serial:  UEFI: American Megatrends v: P1.10 
  date: 05/11/2017 
CPU:
  Info: 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: 800 
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.8 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.2.0 
  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-8:4 
  Sound Server: ALSA v: k5.8.0-23-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: 9.42 GiB (0.4%) 
  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: 9.41 GiB (30.1%) fs: ext4 
  dev: /dev/nvme0n1p2 
Swap:
  ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) 
  dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 43.5 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 224 Uptime: 3h 13m Memory: 7.48 GiB used: 1.66 GiB (22.2%) 
  Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1874 Shell: Bash 
  v: 5.0.17 inxi: 3.1.07 
corrado@corrado-x2-gg-1009:~$

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-software 3.38.0-2build1
ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
Uname: Linux 5.8.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 16 18:20:00 2020
InstallationDate: Installed on 2020-10-10 (6 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-snap3.38.0-2build1
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy

** Attachment added: "Screenshot from 2020-10-16 18-27-18.png"
   
https://bugs.launchpad.net/bugs/1900167/+attachment/5423086/+files/Screenshot%20from%202020-10-16%2018-27-18.png

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

Title:
  gnome-software Unable to install updates

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2020-10-16 Thread Sebastien Bacher
Right, as pointed out in previous comments the configuration as it is
today isn't workin on Debian/Ubuntu systems, the first step would be to
have someone understand those pam details working out those parts

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

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1866286] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/x11/group.c:75:meta_group_new: assertion failed: (g_hash_table_lookup (x11_display->groups_by_leader, _leader) == NULL)

2020-10-16 Thread Launchpad Bug Tracker
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1866286

Title:
  gnome-shell crashed with SIGABRT:
  mutter:ERROR:../src/x11/group.c:75:meta_group_new: assertion failed:
  (g_hash_table_lookup (x11_display->groups_by_leader, _leader) ==
  NULL)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1900157] [NEW] nautilus crashes xserver on rapid mount and unmount of network shares or google drive

2020-10-16 Thread Mark-Daniel Lüthje
Public bug reported:

I have two local samba shares and my google drive connected to Nautilus. When I 
mount or unmount any combination of them the GNOME session randomly freezes and 
the xserver restarts and I can continue in Nautilus just like normal.
Terminal output:
(org.gnome.Nautilus:14697): Gtk-CRITICAL **: 16:49:28.683: 
gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: nautilus 1:3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
Uname: Linux 5.8.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 16 16:50:57 2020
GsettingsChanges:
 b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'"
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'277'
 b'org.gnome.nautilus.window-state' b'initial-size' b'(1217, 735)'
InstallationDate: Installed on 2020-10-13 (3 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 evince3.38.0-1
 file-roller   3.38.0-1
 nautilus-extension-brasero3.12.2-6ubuntu1
 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1
 nautilus-share0.7.3-2ubuntu3

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


** Tags: amd64 apport-bug groovy

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

Title:
  nautilus crashes xserver on rapid mount and unmount of network shares
  or google drive

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2020-10-16 Thread Eric Desrochers
# git clone https://gitlab.gnome.org/GNOME/gdm.git

# find . -name "gdm-smartcard*"
./data/pam-arch/gdm-smartcard.pam
./data/pam-redhat/gdm-smartcard.pam
./data/pam-exherbo/gdm-smartcard.pam
./data/pam-lfs/gdm-smartcard.pam

It seems like Ubuntu/Debian will have to start by having a 'compatible'
PAM stack config.

So far looking upstream, it seems to only be defined for 4 specific distros:
- Archlinux
- Redhat
- Exherbo
- Linux From Scratch (LFS)

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

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1896393] Re: gedit not responding to keystrokes

2020-10-16 Thread Cliff Carson
Problem is indeed intermittent.  Dumped systemctl -b 0 | tail -n 100
after noticing the failure/delay and see nothing in the messages (many
time no messages at all at the time of delay).  Another indicator of a
delay failure is when starting to edit new script then mouse wheel
(trying to page down in the file) fails to react for several seconds
(5-10 sec) then the screen pages.  The system monitor running at the
time shows normal low activity.

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

Title:
  gedit not responding to keystrokes

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1900009] Re: Window tiled to monitor where most of the window is in instead of where the mouse is.

2020-10-16 Thread Christian
Issue id is 3290.
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3290

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

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

Title:
  Window tiled to monitor where most of the window is in instead of
  where the mouse is.

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

2020-10-16 Thread Dan Streetman
** Description changed:

+ [impact]
+ 
+ autopkgtests are failing/flaky and prevent other packages from migrating
+ to -updates
+ 
+ [test case]
+ 
+ check systemd autopkgtest history
+ 
+ [regression potential]
+ 
+ in regard to the changed test cases, any regression would likely result
+ in either an incorrectly passed test, or an incorrectly failed test.
+ 
+ [scope]
+ 
+ this is needed for x, b, and f.
+ 
+ tests in g appear to be mostly stable, but I've opened MR (linked from
+ this bug) to update the tests there as well.
+ 
+ i don't plan to update x, as it's reaching ESM in ~6 months, and
+ backporting the test fixes is more work than just a simple code copy,
+ since there are additional differences/changes needed in the older
+ version of systemd (and python3). the failing/flaky tests in x have been
+ like that forever, and people have just retried them; we can keep
+ retrying them until x moves into ESM next year.
+ 
+ [original description]
+ 
  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.
  
  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to
  be flaky before, but got even worse.
  
  Here stats of the last 40 runs, it might be a coincidences that this is
  after 246-2ubuntu1 landed. Could as well be any other change
  
  groovy
-   amd64
+   amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
-   ppc64el
+   ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
-   s390x
+   s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% B  0% => P 67%/) 
FFF..FF..F.FF..F
  root-unittests (F 10% S  0% B  0% => P 90%/) 
FFF...F.
-   arm64
+   arm64
  tests-in-lxd   (F 40% S  0% B  2% => P 57%/) 
F.B...FFF.FF..F..F.FFF.F
  logind (F  2% S  0% B  2% => P 95%/) 
..B...F.
  upstream   (F 22% S  0% B  2% => P 75%/) 
...F.FB.F.F.F..FFF.F
  root-unittests (F 12% S  0% B  2% => P 85%/) 
..B.F...F.FF...F
  
  (I'm sure LP will make this unreadable, but is is nice in monospace)
  
  Whatever the root cause is - the success rate of these has reduced so
  much that the (even formerly questionable) practice of retry-until-
  success won't work anymore.
  
- 
- I have run the two tests in a local VM and systemd-fsckd works there while 
tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services".
+ I have run the two tests in a local VM and systemd-fsckd works there
+ while tests-in-lxd seems to trip over the old flaky fellow being "boot-
+ and-services".
  
  We had the discussion in the past, but I think I need to again bring up
  the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are
  on reasonable success rates.

** Changed in: systemd (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu 

[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

2020-10-16 Thread Dan Streetman
** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/392373

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1892358

Title:
  autopkgtest success rate dropped inhibiting proposed migration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

2020-10-16 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/392368

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1892358

Title:
  autopkgtest success rate dropped inhibiting proposed migration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1708201] Re: gnome-calendar does not use the proper system timezone

2020-10-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  gnome-calendar does not use the proper system timezone

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1872159] Re: Boot animation never finishes when external monitors (or just more than one) are connected

2020-10-16 Thread Daniel van Vugt
I will keep my comments in the upstream bug for now:

https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/118

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

Title:
  Boot animation never finishes when external monitors (or just more
  than one) are connected

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1900057] Re: ThinkPad T400 sleeps immediately after login

2020-10-16 Thread davileon
Thanks! The same problem does not happen if I select 'Ubuntu on Wayland'
from the login screen.

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

Title:
  ThinkPad T400 sleeps immediately after login

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1900057] Re: ThinkPad T400 sleeps immediately after login

2020-10-16 Thread Daniel van Vugt
** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- ThinkPad T400 sleeps immediately after login
+ ThinkPad T400 sleeps immediately after login in Xorg sessions, but not Wayland

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

Title:
  ThinkPad T400 sleeps immediately after login in Xorg sessions, but not
  Wayland

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1872159] Re: Boot animation never finishes when external monitors (or just more than one) are connected

2020-10-16 Thread Daniel van Vugt
** Changed in: plymouth (Ubuntu)
   Status: Triaged => In Progress

** Also affects: plymouth (Ubuntu Groovy)
   Importance: High
 Assignee: Daniel van Vugt (vanvugt)
   Status: In Progress

** Also affects: gdm3 (Ubuntu Groovy)
   Importance: High
   Status: Confirmed

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

Title:
  Boot animation never finishes when external monitors (or just more
  than one) are connected

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1889102] Re: [ubuntu-dock] App grid has too many page dots on right

2020-10-16 Thread Akbarkhon Variskhanov
Here is that short screencast showcasing the bug:
https://launchpadlibrarian.net/502131812/show-all-apps.webm

** Attachment added: "show-all-apps.webm"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889102/+attachment/5422847/+files/show-all-apps.webm

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

Title:
  [ubuntu-dock] App grid has too many page dots on right

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1894627] Re: [nvidia] Web browser distorted after hibernation/power save when idle

2020-10-16 Thread Daniel van Vugt
OK, I will assume the same bug is in Chromium. Because we can't track
Chrome here.

** Package changed: ubuntu => chromium-browser (Ubuntu)

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

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

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

Title:
  [nvidia] Web browser distorted after hibernation/power save when idle

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend

2020-10-16 Thread Daniel van Vugt
Kashad, I will reopen your bug 1894627 and clarify that is about web
browsers. This one is about the background wallpaper.

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

Title:
  [nvidia] Background image corrupted after standby or resume from
  suspend

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs