[Desktop-packages] [Bug 1764137] Re: [bionic][beta][nvidia] gnome-shell high CPU utilization when using Nvidia driver

2019-04-10 Thread Mateusz Mikuła
It was long time ago but IIRC after upgrading from Ubuntu 17.10 to 18.04
GDM would try to start on Wayland. With proprietary Nvidia driver it
would then fallback to software rendering haence the CPU usage.

Disabling Wayland in /etc/gdm/custom.conf or doing clean install fixes
the issue.

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

Title:
  [bionic][beta][nvidia] gnome-shell high CPU utilization when using
  Nvidia driver

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

Bug description:
  I am experiencing 60% - 200% CPU utilization after an upgrade from
  ubuntu artful to bionic.

  Pretty much any drawing results in a sluggish behavior due to high CPU
  utilization.

  The same combination of kernel/drivers did not result in the issue on
  17.10 so gnome-shell seems a good candidate to blame.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  Uname: Linux 4.16.0-041600-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 15 16:53:34 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-02-27 (412 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago)
  ---
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-02-27 (412 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux-image-4.16.0-041600-generic 4.16.0-041600.201804012230 
[origin: unknown]
  PackageArchitecture: amd64
  Tags: third-party-packages bionic
  Uname: Linux 4.16.0-041600-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo 
systemd-journal ubridge
  _MarkForUpload: True

  ➜  ~ dpkg -l | grep -P 'ii.*?nvidia'
  ii  nvidia-390  
390.48-0ubuntu0~gpu17.10.2 amd64
NVIDIA binary driver - version 390.48
  ii  nvidia-opencl-icd-390   
390.48-0ubuntu0~gpu17.10.2 amd64
NVIDIA OpenCL ICD
  ii  nvidia-prime0.8.7 
 all  Tools to 
enable NVIDIA's Prime
  ii  nvidia-settings 
396.18-0ubuntu0~gpu17.10.1 amd64
Tool for configuring the NVIDIA graphics driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1764137/+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 1808980] Re: Ubuntu/Debian Firefox packages are built without SIMD

2019-02-07 Thread Mateusz Mikuła
** Changed in: firefox (Debian)
   Status: New => Invalid

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

Title:
  Ubuntu/Debian Firefox packages are built without SIMD

Status in firefox package in Ubuntu:
  Fix Released
Status in firefox package in Debian:
  Invalid

Bug description:
  Official Firefox releases and other distributions packages are built
  with `--enable-rust-simd` to  improve performance. Official build
  option: https://github.com/mozilla/gecko-
  dev/blob/13788edbabb04d004e4a1ceff41d4de68a8320a2/build/mozconfig.rust#L12

  `--enable-rust-simd` enables runtime detection of CPU features such as
  SSE and AVX in Rust written components.

  To check if Firefox is built with simd open `about:buildconfig` and
  look for `--enable-rust-simd`.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1808980/+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 1710858] Re: totem crashed with SIGSEGV in in __GI_____strtoul_l_internal() from __GI___strtoul_l() from g_ascii_strtoull() from _cogl_gpu_info_parse_version_string() from chec

2019-01-02 Thread Mateusz Mikuła
Fixied in Bionic, Artful is EOL.

** Changed in: totem (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  totem crashed with SIGSEGV in in __GI_strtoul_l_internal() from
  __GI___strtoul_l() from g_ascii_strtoull() from
  _cogl_gpu_info_parse_version_string() from check_mesa_driver_package()

Status in totem package in Ubuntu:
  Fix Released
Status in totem package in Debian:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/8c8cfc48195ee610b89b3b2fa352c622b507d073

  ---

  crashed trying to open .avi video

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu1
  Uname: Linux 4.12.6-041206-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Tue Aug 15 12:20:00 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2016-05-20 (451 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe5160f1bf5 <__GI_strtoul_l_internal+53>:   
movsbq (%r14),%rax
   PC (0x7fe5160f1bf5) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff97eb9aa8, base=10, 
group=, loc=0x7fe516474820 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:293
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom colord dialout dip libvirt libvirtd lpadmin 
netdev pico plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1710858/+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 1808980] Re: Ubuntu/Debian Firefox packages are built without SIMD

2019-01-02 Thread Mateusz Mikuła
** Also affects: firefox (Debian)
   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/1808980

Title:
  Ubuntu/Debian Firefox packages are built without SIMD

Status in firefox package in Ubuntu:
  New
Status in firefox package in Debian:
  New

Bug description:
  Official Firefox releases and other distributions packages are built
  with `--enable-rust-simd` to  improve performance. Official build
  option: https://github.com/mozilla/gecko-
  dev/blob/13788edbabb04d004e4a1ceff41d4de68a8320a2/build/mozconfig.rust#L12

  `--enable-rust-simd` enables runtime detection of CPU features such as
  SSE and AVX in Rust written components.

  To check if Firefox is built with simd open `about:buildconfig` and
  look for `--enable-rust-simd`.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1808980/+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 1808980] [NEW] Ubuntu/Debian Firefox packages are built without SIMD

2018-12-18 Thread Mateusz Mikuła
Public bug reported:

Official Firefox releases and other distributions packages are built
with `--enable-rust-simd` to  improve performance. Official build
option: https://github.com/mozilla/gecko-
dev/blob/13788edbabb04d004e4a1ceff41d4de68a8320a2/build/mozconfig.rust#L12

`--enable-rust-simd` enables runtime detection of CPU features such as
SSE and AVX in Rust written components.

To check if Firefox is built with simd open `about:buildconfig` and look
for `--enable-rust-simd`.

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

** Description changed:

  Official Firefox releases and other distributions packages are built
- with `--enable-rust-simd` to  improve performance.
+ with `--enable-rust-simd` to  improve performance. Official build
+ option: https://github.com/mozilla/gecko-
+ dev/blob/13788edbabb04d004e4a1ceff41d4de68a8320a2/build/mozconfig.rust#L12
  
  `--enable-rust-simd` enables runtime detection of CPU features such as
  SSE and AVX in Rust written components.
  
  To check if Firefox is built with simd open `about:buildconfig` and look
  for `--enable-rust-simd`.

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

Title:
  Ubuntu/Debian Firefox packages are built without SIMD

Status in firefox package in Ubuntu:
  New

Bug description:
  Official Firefox releases and other distributions packages are built
  with `--enable-rust-simd` to  improve performance. Official build
  option: https://github.com/mozilla/gecko-
  dev/blob/13788edbabb04d004e4a1ceff41d4de68a8320a2/build/mozconfig.rust#L12

  `--enable-rust-simd` enables runtime detection of CPU features such as
  SSE and AVX in Rust written components.

  To check if Firefox is built with simd open `about:buildconfig` and
  look for `--enable-rust-simd`.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1808980/+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 1798790] Re: Ubuntu 18.10 login screen never appears when using the Nvidia driver

2018-11-06 Thread Mateusz Mikuła
Another workaround is adding `nvidia-drm.modeset=1` to the kernel
command line.

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

Title:
  Ubuntu 18.10 login screen never appears when using the Nvidia driver

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/435

  ---

  The boot process hangs with the last message being "started bpfilter".
  There is unusual Network activity during that time. The light of the
  WiFi adapter is blinking a lot.

  I am not sure the problem is with the gdm3 package. As a matter of
  fact, I would remove it and let someone more experienced to set it.
  I'm afraid I might break something, though.

  The specific steps or actions you took that caused you to encounter the 
problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers
  installed.

  The behavior you expected: I expected Ubuntu 18.10 to boot normally.

  The behavior you actually encountered: The computer gets stuck in a
  command-like environment with the last message being "started
  bpfilter". You can't type any commands.

  I have found that uninstalling the Nvidia proprietary drivers by going
  into recovery mode fixes the issue.

  Booting with the earlier kernel doesn't fix the issue. Installing the
  earlier v.340 driver also doesn't fix the issue.

  This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-
  boot-after-starting-gnome-display-manager-on-intel-graphic) seems
  relevant. This is where I found the "solution".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+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 1710858] Re: totem crashed with SIGSEGV in __GI_____strtoul_l_internal()

2017-12-03 Thread Mateusz Mikuła
Created backport requrest for fixed version of apparmor-profiles-extra
https://bugs.launchpad.net/artful-backports/+bug/1736039

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

Title:
  totem crashed with SIGSEGV in __GI_strtoul_l_internal()

Status in totem package in Ubuntu:
  Confirmed
Status in totem package in Debian:
  Unknown

Bug description:
  crashed trying to open .avi video

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu1
  Uname: Linux 4.12.6-041206-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Tue Aug 15 12:20:00 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2016-05-20 (451 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe5160f1bf5 <__GI_strtoul_l_internal+53>:   
movsbq (%r14),%rax
   PC (0x7fe5160f1bf5) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff97eb9aa8, base=10, 
group=, loc=0x7fe516474820 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:293
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom colord dialout dip libvirt libvirtd lpadmin 
netdev pico plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1710858/+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 1710858] Re: totem crashed with SIGSEGV in __GI_____strtoul_l_internal()

2017-12-03 Thread Mateusz Mikuła
** Bug watch added: Debian Bug tracker #879900
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879900

** Also affects: totem (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879900
   Importance: Unknown
   Status: Unknown

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

Title:
  totem crashed with SIGSEGV in __GI_strtoul_l_internal()

Status in totem package in Ubuntu:
  Confirmed
Status in totem package in Debian:
  Unknown

Bug description:
  crashed trying to open .avi video

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu1
  Uname: Linux 4.12.6-041206-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Tue Aug 15 12:20:00 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2016-05-20 (451 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe5160f1bf5 <__GI_strtoul_l_internal+53>:   
movsbq (%r14),%rax
   PC (0x7fe5160f1bf5) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff97eb9aa8, base=10, 
group=, loc=0x7fe516474820 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:293
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom colord dialout dip libvirt libvirtd lpadmin 
netdev pico plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1710858/+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 1710858] Re: totem crashed with SIGSEGV in __GI_____strtoul_l_internal()

2017-12-03 Thread Mateusz Mikuła
Crash happens only if `usr.bin.totem` AppArmor profile from `apparmor-
profiles-extra` is enabled.

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

Title:
  totem crashed with SIGSEGV in __GI_strtoul_l_internal()

Status in totem package in Ubuntu:
  Confirmed
Status in totem package in Debian:
  Unknown

Bug description:
  crashed trying to open .avi video

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu1
  Uname: Linux 4.12.6-041206-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Tue Aug 15 12:20:00 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2016-05-20 (451 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe5160f1bf5 <__GI_strtoul_l_internal+53>:   
movsbq (%r14),%rax
   PC (0x7fe5160f1bf5) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff97eb9aa8, base=10, 
group=, loc=0x7fe516474820 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:293
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom colord dialout dip libvirt libvirtd lpadmin 
netdev pico plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1710858/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

2017-04-30 Thread Mateusz Mikuła
** Also affects: gnome-online-accounts (Arch Linux)
   Importance: Undecided
   Status: New

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Arch Linux:
  New

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

2017-04-29 Thread Mateusz Mikuła
It's probably upstream issue as GNOME on Arch Linux also have this bug.

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+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