from:"Stephen"

Sebastien, thx - I've uploaded hopefully the stuff you suggested.

Initially I tried using the "Print Screen" button - but as soon as I 
pressed it, the desktop screen fixed itself!  :-(

Stephen

On 14/12/2020 10:12, Sebastien Bacher wrote:
> Thank you for your bug report, could to a screenshot or video showing
> the issue it's a bit difficult to understand as described. Please also
> include the 'journalctl -b 0' log after triggering the issue. Nautilus
> doesn't handle the desktop anymore so reassigning to gnome-shell which
> is a better start point for rendering issues
>
> ** Package changed: nautilus (Ubuntu) => gnome-shell (Ubuntu)
>
> ** Changed in: gnome-shell (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: gnome-shell (Ubuntu)
> Status: New => Incomplete
>


** Description changed:

  More generally, desktop mis-displays
  
  3 Variations:
  
  a)
  0) open a window/app
  1) minimise a window/application, causing Desktop to be visible
  2) move cursor to dock (to open new app)
  
- As soon as cursor hits dock, the graphic of the minimised window
- (graphic that would be shown by activating "Activities") appears. It can
- be cleared by sweeping a window over the desktop. It only happens once,
- once for every time you minimise a window.
+ As soon as cursor moves over the dock, a small version of the graphic of
+ the minimised window (ie what would be shown by opening "Activities")
+ appears. It can be cleared by opening another window and sweeping this
+ over the desktop. It only happens once, once for every time you minimise
+ a window.
  
- b) Click "Acivities" - then click again to restore view
+ b) Click on "Activities" then click again to restore view
  As soon as cursor hits dock, desktop goes corrupt (large parts blank out)
  
  c) Close window
  As b)
  
- By attempting to move an icon on the Desktop, the Desktop repairs
- itself.
+ By attempting to move an icon on the Desktop, or pressing "Print Scrn"
+ button, the Desktop repairs itself.
  
  
  Ubuntu 20.04.1 LTS
  Gnome 3.36.3
  64-bit
  
  nautilus:
    Installed: 1:3.36.3-0ubuntu1
    Candidate: 1:3.36.3-0ubuntu1
    Version table:
   *** 1:3.36.3-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.36.1.1-1ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  6 12:11:40 2020
  InstallationDate: Installed on 2016-09-01 (1556 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-12-05 (1 days ago)
  usr_lib_nautilus: dropbox 2018.11.08

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

Title:
  moving cursor to dock causes desktop graphic garbage

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

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

[Bug 1906977] Re: moving cursor to dock causes desktop graphic garbage

Screenshots (video)
I enable video, close/minimise a number of windows until the desktop appears, 
then move cursor to dock, and spurious graphic then appears


** Attachment added: "Screenshot video"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1906977/+attachment/5443433/+files/desktopbug-2020-12-14_13.15.51.mkv

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

Title:
  moving cursor to dock causes desktop graphic garbage

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

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

[Bug 1906977] Re: moving cursor to dock causes desktop graphic garbage

Screenshots (video)
I enable video, close/minimise a number of windows until the desktop appears, 
then move cursor to dock, and spurious graphic then appears

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

Title:
  moving cursor to dock causes desktop graphic garbage

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

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

[Bug 1906977] Re: moving cursor to dock causes desktop graphic garbage

Video of screen leading to bug - attached

Journalctl Log:
-- Logs begin at Tue 2019-06-04 14:30:15 BST, end at Mon 2020-12-14 13:17:01 
GMT. --
Dec 14 12:12:46 stephen-Inspiron-545 kernel: microcode: microcode updated early 
to revision 0xa0b, date = 2>
Dec 14 12:12:46 stephen-Inspiron-545 kernel: Linux version 5.4.0-58-generic 
(buildd@lcy01-amd64-004) (gcc v>
Dec 14 12:12:46 stephen-Inspiron-545 kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=U>
Dec 14 12:12:46 stephen-Inspiron-545 kernel: KERNEL supported cpus:
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   Intel GenuineIntel
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   AMD AuthenticAMD
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   Hygon HygonGenuine
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   Centaur CentaurHauls
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   zhaoxin   Shanghai  
Dec 14 12:12:46 stephen-Inspiron-545 kernel: x86/fpu: Supporting XSAVE feature 
0x001: 'x87 floating point r>
Dec 14 12:12:46 stephen-Inspiron-545 kernel: x86/fpu: Supporting XSAVE feature 
0x002: 'SSE registers'
Dec 14 12:12:46 stephen-Inspiron-545 kernel: x86/fpu: Enabled xstate features 
0x3, context size is 576 byte>
Dec 14 12:12:46 stephen-Inspiron-545 kernel: BIOS-provided physical RAM map:
Dec 14 12:12:46 stephen-Inspiron-545 kernel: BIOS-e820: [mem 
0x-0x0009e7ff] usable
Dec 14 12:12:46 stephen-Inspiron-545 kernel: BIOS-e820: [mem 
0x0009e800-0x0009] reserved
Dec 14 12:12:46 stephen-Inspiron-545 kernel: BIOS-e820: [mem 
0x000f-0x000f] reserved
Dec 14 12:12:46 stephen-Inspiron-545 kernel: BIOS-e820: [mem 
0x0010-0xcf58] usable
Dec 14 12:12:46 stephen-Inspiron-545 kernel: BIOS-e820: [mem 
0xcf59-0xcf5d] reserved
Dec 14 12:12:46 stephen-Inspiron-545 kernel: BIOS-e820: [mem 
0xcf5e-0xcf5e2fff] ACPI NVS
Dec 14 12:12:46 stephen-Inspiron-545 kernel: BIOS-e820: [mem 
0xcf5e3000-0xcf5e] ACPI da>
Dec 14 12:12:46 stephen-Inspiron-545 kernel: BIOS-e820: [mem 
0xcf5f-0xcf5f] reserved
Dec 14 12:12:46 stephen-Inspiron-545 kernel: BIOS-e820: [mem 
0xe000-0xefff] reserved
Dec 14 12:12:46 stephen-Inspiron-545 kernel: BIOS-e820: [mem 
0xfec0-0x] reserved
Dec 14 12:12:46 stephen-Inspiron-545 kernel: BIOS-e820: [mem 
0x0001-0x00016fff] usable
Dec 14 12:12:46 stephen-Inspiron-545 kernel: NX (Execute Disable) protection: 
active
Dec 14 12:12:46 stephen-Inspiron-545 kernel: SMBIOS 2.5 present.
Dec 14 12:12:46 stephen-Inspiron-545 kernel: DMI: Dell Inc. Inspiron 
545/0N826N, BIOS A12 11/17/2009
Dec 14 12:12:46 stephen-Inspiron-545 kernel: tsc: Fast TSC calibration using PIT
Dec 14 12:12:46 stephen-Inspiron-545 kernel: tsc: Detected 2925.911 MHz 
processor
Dec 14 12:12:46 stephen-Inspiron-545 kernel: e820: update [mem 
0x-0x0fff] usable ==> reserved
Dec 14 12:12:46 stephen-Inspiron-545 kernel: e820: remove [mem 
0x000a-0x000f] usable
Dec 14 12:12:46 stephen-Inspiron-545 kernel: last_pfn = 0x17 max_arch_pfn = 
0x4
Dec 14 12:12:46 stephen-Inspiron-545 kernel: MTRR default type: uncachable
Dec 14 12:12:46 stephen-Inspiron-545 kernel: MTRR fixed ranges enabled:
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   0-9 write-back
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   A-B uncachable
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   C-CAFFF write-protect
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   CB000-E uncachable
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   F-F write-through
Dec 14 12:12:46 stephen-Inspiron-545 kernel: MTRR variable ranges enabled:
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   0 base 1 mask FC000 
write-back
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   1 base 14000 mask FE000 
write-back
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   2 base 16000 mask FF000 
write-back
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   3 base 0 mask F8000 
write-back
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   4 base 08000 mask FC000 
write-back
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   5 base 0C000 mask FF000 
write-back
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   6 base 0CF70 mask 0 
uncachable
Dec 14 12:12:46 stephen-Inspiron-545 kernel:   7 base 0CF80 mask FFF80 
uncachable
Dec 14 12:12:46 stephen-Inspiron-545 kernel: x86/PAT: Configuration [0-7]: WB  
WC  UC- UC  WB  WP  UC- WT  
Dec 14 12:12:46 stephen-Inspiron-545 kernel: total RAM covered: 5111M
Dec 14 12:12:46 stephen-Inspiron-545 kernel: Found optimal setting for mtrr 
clean up
Dec 14 12:12:46 stephen-Inspiron-545 kernel:  gran_size: 64K 
chunk_size: 1G num_reg: 7     >
Dec 14 12:12:46 stephen-Inspiron-545 kernel: e820: update [mem 
0xcf70-0x] usable ==>

[Bug 1906977] Re: moving cursor to dock causes desktop graphic garbage

2020-12-13 Thread Stephen Lawrence

** Summary changed:

- moving cursor over dock causes old window to appear
+ moving cursor to dock causes desktop graphic garbage

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

Title:
  moving cursor to dock causes desktop graphic garbage

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

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

[Bug 1906977] Re: moving cursor over dock causes old window to appear

2020-12-11 Thread Stephen Lawrence

** Description changed:

  More generally, desktop mis-displays
  
  3 Variations:
  
  a)
  0) open a window/app
  1) minimise a window/application, causing Desktop to be visible
  2) move cursor to dock (to open new app)
  
  As soon as cursor hits dock, the graphic of the minimised window
  (graphic that would be shown by activating "Activities") appears. It can
  be cleared by sweeping a window over the desktop. It only happens once,
  once for every time you minimise a window.
  
  b) Click "Acivities" - then click again to restore view
  As soon as cursor hits dock, desktop goes corrupt (large parts blank out)
  
  c) Close window
  As b)
+ 
+ By attempting to move an icon on the Desktop, the Desktop repairs
+ itself.
  
  
  Ubuntu 20.04.1 LTS
  Gnome 3.36.3
  64-bit
  
  nautilus:
    Installed: 1:3.36.3-0ubuntu1
    Candidate: 1:3.36.3-0ubuntu1
    Version table:
   *** 1:3.36.3-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.36.1.1-1ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  6 12:11:40 2020
  InstallationDate: Installed on 2016-09-01 (1556 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-12-05 (1 days ago)
  usr_lib_nautilus: dropbox 2018.11.08

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

Title:
  moving cursor over dock causes old window to appear

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

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

[Bug 1906977] Re: moving cursor over dock causes old window to appear

2020-12-08 Thread Stephen Lawrence

Sorry, not sure whether this is nautilus or desktop :-\

** Description changed:

- Steps:
+ More generally, desktop mis-displays
+ 
+ 3 Variations:
+ 
+ a)
  0) open a window/app
  1) minimise a window/application, causing Desktop to be visible
  2) move cursor to dock (to open new app)
  
  As soon as cursor hits dock, the graphic of the minimised window
  (graphic that would be shown by activating "Activities") appears. It can
  be cleared by sweeping a window over the desktop. It only happens once,
  once for every time you minimise a window.
  
+ b) Click "Acivities" - then click again to restore view
+ As soon as cursor hits dock, desktop goes corrupt (large parts blank out)
+ 
+ c) Close window
+ As b)
+ 
+ 
  Ubuntu 20.04.1 LTS
  Gnome 3.36.3
  64-bit
  
  nautilus:
-   Installed: 1:3.36.3-0ubuntu1
-   Candidate: 1:3.36.3-0ubuntu1
-   Version table:
-  *** 1:3.36.3-0ubuntu1 500
- 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  1:3.36.1.1-1ubuntu2 500
- 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
+   Installed: 1:3.36.3-0ubuntu1
+   Candidate: 1:3.36.3-0ubuntu1
+   Version table:
+  *** 1:3.36.3-0ubuntu1 500
+ 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  1:3.36.1.1-1ubuntu2 500
+ 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  6 12:11:40 2020
  InstallationDate: Installed on 2016-09-01 (1556 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-12-05 (1 days ago)
  usr_lib_nautilus: dropbox 2018.11.08

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

Title:
  moving cursor over dock causes old window to appear

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

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

[Bug 1906977] [NEW] moving cursor over dock causes old window to appear

2020-12-06 Thread Stephen Lawrence

Public bug reported:

Steps:
0) open a window/app
1) minimise a window/application, causing Desktop to be visible
2) move cursor to dock (to open new app)

As soon as cursor hits dock, the graphic of the minimised window
(graphic that would be shown by activating "Activities") appears. It can
be cleared by sweeping a window over the desktop. It only happens once,
once for every time you minimise a window.

Ubuntu 20.04.1 LTS
Gnome 3.36.3
64-bit

nautilus:
  Installed: 1:3.36.3-0ubuntu1
  Candidate: 1:3.36.3-0ubuntu1
  Version table:
 *** 1:3.36.3-0ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:3.36.1.1-1ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec  6 12:11:40 2020
InstallationDate: Installed on 2016-09-01 (1556 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to focal on 2020-12-05 (1 days ago)
usr_lib_nautilus: dropbox 2018.11.08

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


** Tags: amd64 apport-bug focal

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

Title:
  moving cursor over dock causes old window to appear

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

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

Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."

2020-06-22 Thread Stephen Holden

Thanks.  I thought just replacing gnutls-bin would be enough.  Now that I've 
updated all three .deb files, Evolution is once again pulling emails, etc from 
my ISP's rogers-yahoo server!
Thanks to all who worked on fixing the problem.  I know a few people on this 
mailing list will be very happy, myself included.
Regards,Stephen

Stephen Holden
Ontario, Canada 

On Monday, June 22, 2020, 3:11:05 p.m. EDT, Rod Rivers 
<1876...@bugs.launchpad.net> wrote:  
 
 @@stephenholden both of these have to be updated.  This is where the
code change was made:

ii  libgnutls30:amd64                    3.5.18-1ubuntu1.3                      
                                    amd64        GNU TLS library - main runtime 
library
ii  libgnutls30:i386                      3.5.18-1ubuntu1.3                     
                                     i386        GNU TLS library - main runtime 
library

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1876286

Title:
  Evolution reports "Error performing TLS handshake: Internal error in
  memory allocation."

Status in Gnutls:
  Unknown
Status in claws-mail package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnutls28 package in Ubuntu:
  Fix Released
Status in gnutls28 source package in Xenial:
  Fix Committed
Status in gnutls28 source package in Bionic:
  Fix Committed
Status in claws-mail source package in Focal:
  Invalid
Status in evolution source package in Focal:
  Invalid
Status in gnutls28 source package in Focal:
  Fix Committed
Status in claws-mail source package in Groovy:
  Invalid
Status in evolution source package in Groovy:
  Invalid
Status in gnutls28 source package in Groovy:
  Fix Released
Status in gnutls28 package in CentOS:
  Unknown

Bug description:
  [Impact]

  Evolution and Claws email clients stopped connecting to Yahoo, AOL,
  Verizon, AT, Bell South, etc email servers which are run by the same
  group. Users are unable to get to their email.

  The underlying problem is that GnuTLS does not support zero length
  session tickets.  The fix works by checking that that ticket_len > 0
  prior to calling gnutls_realloc_fast().

  Nominating for SRU, fulfills: "Updates that need to be applied to
  Ubuntu packages to adjust to changes in the environment, server
  protocols, web services, and similar, i. e. where the current version
  just ceases to work."

  
  [testcase]

  GnuTLS 3.6:
  $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995
  [...]
  - Status: The certificate is trusted.
  *** Fatal error: Internal error in memory allocation.

  the error should be fixed with the update

  GnuTLS 3.5:
  $ gnutls-cli pop.verizon.net:995

  GnuTLS 3.4:
  $ gnutls-cli -p 995 pop.verizon.net

  
  [regression potential]

  The fix works by checking that that ticket_len > 0 prior to calling
  gnutls_realloc_fast().  This creates two separate execution paths:

  1) If the session ticket length > 0, which is the primary use case,
  the original code block will be executed.

  2) If the session ticket len is 0, then the original code block will
  be skipped.

  Testing will need to include connections to servers that return
  session ticket length > 0 as well as ones that return session ticket
  length of 0.  Wireshark can be used to look at the NewSessionTicket
  handshake message to confirm the session ticket length.

  
  [Other Info]

  The GnuTLS project's merge request 1260 fixes this bug.  It was reviewed and 
approved by Daiki Ueno:
  https://gitlab.com/gnutls/gnutls/-/merge_requests/1260

  According to the GnuTLS project: "We utilize two continuous integration 
systems, the gitlab-ci and travis.  Gitlab-CI is used to test most of the Linux 
systems (see .gitlab-ci.yml), and is split in two phases, build image creation 
and compilation/test. The build image creation is done at the 
gnutls/build-images subproject and uploads the image at the gitlab.com 
container registry. The compilation/test phase is on every commit to gnutls 
project."
  Here are the results of the gitlab-ci pipeline showing all 19 tests passed 
for merge request 1260:
  https://gitlab.com/rrivers2/gnutls/-/pipelines/149155018

  Page 8, section 3.3 of RFC5077 describes the NewSessionTicket handshake 
message and indicates that a zero length session ticket is a legitimate value:
  https://tools.ietf.org/pdf/rfc5077.pdf

  --

  When GnuTLS connects to servers that return zero length session
  tickets using older TLS versions it returns the error code
  GNUTLS_E_MEMORY_ERROR and the connection is closed.  This prevents
  Evolution and Claws email clients from connecting to Yahoo, AOL,
  Verizon, AT, Bell South, etc email servers.  Evolution displays the
  message "Error performing TLS handshake: Internal error in memory
  allocation"

  
  ProblemType: Bug
  DistroRele

Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."

2020-06-22 Thread Stephen Holden

Sure thing.  Pasted below and attached .txt with same content as well...
Regards,Stephen

Rogers Email Account:  address: stephenhol...@rogers.com
  imap server: imap.broadband.rogers.com:993
  username: stephenhol...@rogers.com
  password: 
  smtp:  similar as above, replace "imap." with "smtp.", port 465, same 
user/pass


$gnutls-cli pop.verizon.net:995
Processed 127 CA certificate(s).
Resolving 'pop.verizon.net:995'...
Connecting to '66.218.85.35:995'...
- Certificate type: X.509
- Got a certificate list of 3 certificates.
- Certificate[0] info:
 - subject `CN=pop.verizon.net,O=Verizon Data Services LLC,L=Temple 
Terrace,ST=Florida,C=US', issuer `CN=DigiCert Baltimore CA-2 
G2,OU=www.digicert.com,O=DigiCert Inc,C=US', serial 
0x0128e5987aac5428187b44269bcc4722, RSA key 2048 bits, signed using RSA-SHA256, 
activated `2020-01-17 00:00:00 UTC', expires `2021-12-07 12:00:00 UTC', 
pin-sha256="aNhhzcfwYqhSipKi6Wxk4Gs9+tKNo8L76OEHVxi9wxw="
    Public Key ID:
        sha1:4ebacc7c149d8ba94aaf0ce3909b6d695e19a625
        sha256:68d861cdc7f062a8528a92a2e96c64e06b3dfad28da3c2fbe8e1075718bdc31c
    Public Key PIN:
        pin-sha256:aNhhzcfwYqhSipKi6Wxk4Gs9+tKNo8L76OEHVxi9wxw=
    Public key's random art:
        +--[ RSA 2048]+
        | |
        | |
        | . . |
        |    . o  |
        |  E +   S+ . |
        | . = o ++ .  |
        |o +.+ .o.    |
        | *+* =...    |
        |o++ +o*. |
        +-+

- Certificate[1] info:
 - subject `CN=DigiCert Baltimore CA-2 G2,OU=www.digicert.com,O=DigiCert 
Inc,C=US', issuer `CN=Baltimore CyberTrust 
Root,OU=CyberTrust,O=Baltimore,C=IE', serial 
0x0182f8098ea2e626b91a3b27841fb9af, RSA key 2048 bits, signed using RSA-SHA256, 
activated `2015-12-08 12:05:07 UTC', expires `2025-05-10 12:00:00 UTC', 
pin-sha256="56higu/MFWb/c2b0avLE5oN2ECS2C43RvzSUgx/2xIE="
- Certificate[2] info:
 - subject `CN=Baltimore CyberTrust Root,OU=CyberTrust,O=Baltimore,C=IE', 
issuer `CN=Baltimore CyberTrust Root,OU=CyberTrust,O=Baltimore,C=IE', serial 
0x02b9, RSA key 2048 bits, signed using RSA-SHA1 (broken!), activated 
`2000-05-12 18:46:00 UTC', expires `2025-05-12 23:59:00 UTC', 
pin-sha256="Y9mvm0exBk1JoQ57f9Vm28jKo5lFm/woKcVxrYxu80o="
- Status: The certificate is trusted. 
*** Fatal error: Internal error in memory allocation.
*** handshake has failed: Internal error in memory allocation.


$dpkg -l | grep gnutls
ii  gnutls-bin    3.5.18-1ubuntu1.4 
  amd64    GNU TLS library - 
commandline utilities
ii  libcurl3-gnutls:amd64 7.58.0-2ubuntu3.8 
  amd64    easy-to-use client-side URL 
transfer library (GnuTLS flavour)
ii  libcurl4-gnutls-dev:amd64 7.58.0-2ubuntu3.8 
  amd64    development files and 
documentation for libcurl (GnuTLS flavour)
ii  libgnutls-dane0:amd64 3.5.18-1ubuntu1.3 
  amd64    GNU TLS library - DANE 
security support
ii  libgnutls-openssl27:amd64 3.5.18-1ubuntu1.3 
  amd64    GNU TLS library - OpenSSL 
wrapper
ii  libgnutls30:amd64 3.5.18-1ubuntu1.3 
  amd64    GNU TLS library - main 
runtime library
ii  libgnutls30:i386  3.5.18-1ubuntu1.3 
  i386 GNU TLS library - main 
runtime library
ii  libneon27-gnutls:amd64    0.30.2-3~ubuntu18.04.1
  amd64    HTTP and WebDAV client 
library (GnuTLS enabled)$

Stephen Holden
Ontario, Canada 

On Monday, June 22, 2020, 2:35:53 p.m. EDT, Rod Rivers 
<1876...@bugs.launchpad.net> wrote:  
 
 @stephenholden could you provide:

1) details on your connection type (pop/imap), server and port (in my
case this was pop to pop.verizon.net on port 995).

2) output of "dpkg -l | grep gnutls"

3) test my server using "gnutls-cli pop.verizon.net:995" (you may need
to install the gnutls-bin package) and let me know if you see the error
or a message that ends with "+OK Hello from jpop-0.1"

I just tried with the proposed repo and was able to connect, details in
another comment.

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1876286

Title:
  Evolution reports "Error performing TLS handshake: Internal error in
  memory allocation."

Status in Gnutls:
  Unknown
Status in claws-mail package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnutls2

Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."

2020-06-22 Thread Stephen Holden

I have installed on bionic and still have TLS memory error when trying to 
connect to my Rogers-Yahoo account.  No change.  Confirmed that new package is 
installed...Tried creating new Rogers-Yahoo account and it fails as well.
Dang.  Pls let me know what I can do to help diagnose further!
Appreciate the work to date.

Stephen Holden
Ontario, Canada 

On Monday, June 22, 2020, 11:20:55 a.m. EDT, Łukasz Zemczak 
<1876...@bugs.launchpad.net> wrote:  
 
 Hello Rod, or anyone else affected,

Accepted gnutls28 into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/gnutls28/3.5.18-1ubuntu1.4 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnutls28 (Ubuntu Bionic)
      Status: New => Fix Committed

** Tags added: verification-needed-bionic

** Changed in: gnutls28 (Ubuntu Xenial)
      Status: New => Fix Committed

** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1876286

Title:
  Evolution reports "Error performing TLS handshake: Internal error in
  memory allocation."

Status in Gnutls:
  Unknown
Status in claws-mail package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnutls28 package in Ubuntu:
  Fix Released
Status in gnutls28 source package in Xenial:
  Fix Committed
Status in gnutls28 source package in Bionic:
  Fix Committed
Status in claws-mail source package in Focal:
  Invalid
Status in evolution source package in Focal:
  Invalid
Status in gnutls28 source package in Focal:
  Fix Committed
Status in claws-mail source package in Groovy:
  Invalid
Status in evolution source package in Groovy:
  Invalid
Status in gnutls28 source package in Groovy:
  Fix Released
Status in gnutls28 package in CentOS:
  Unknown

Bug description:
  [Impact]

  Evolution and Claws email clients stopped connecting to Yahoo, AOL,
  Verizon, AT, Bell South, etc email servers which are run by the same
  group. Users are unable to get to their email.

  The underlying problem is that GnuTLS does not support zero length
  session tickets.  The fix works by checking that that ticket_len > 0
  prior to calling gnutls_realloc_fast().

  Nominating for SRU, fulfills: "Updates that need to be applied to
  Ubuntu packages to adjust to changes in the environment, server
  protocols, web services, and similar, i. e. where the current version
  just ceases to work."

  
  [testcase]

  GnuTLS 3.6:
  $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995
  [...]
  - Status: The certificate is trusted.
  *** Fatal error: Internal error in memory allocation.

  the error should be fixed with the update

  GnuTLS 3.5:
  $ gnutls-cli pop.verizon.net:995

  GnuTLS 3.4:
  $ gnutls-cli -p 995 pop.verizon.net

  
  [regression potential]

  The fix works by checking that that ticket_len > 0 prior to calling
  gnutls_realloc_fast().  This creates two separate execution paths:

  1) If the session ticket length > 0, which is the primary use case,
  the original code block will be executed.

  2) If the session ticket len is 0, then the original code block will
  be skipped.

  Testing will need to include connections to servers that return
  session ticket length > 0 as well as ones that return session ticket
  length of 0.  Wireshark can be used to look at the NewSessionTicket
  handshake message to confirm the session ticket length.

  
  [Other Info]

  The GnuTLS project's merge request 1260 fixes this bug.  It was reviewed and 
approved by Daiki Ueno:
  https://gitlab.com/gnutls/gnutls/-/merge_requests/1260

  According to the GnuTLS project: "We utilize two continuous integration 
systems, the gitlab-ci and travis.  Gitlab-CI is used to test most of the Linux 
systems (see .gitlab-ci.yml), and is split in two phases, build image creation 
and compilation/test. The

[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."

2020-06-12 Thread Stephen Holden

It suddenly started a few weeks ago in bionic.  Official gnutls-bin 
3.15.18-1ubuntu1.3.  No changes to my system, where it was working for over a 
year, just suddenly started getting this error. Does affect Evolution on 18.04.
Also affects it on CentOS 7, which I have on another machine.

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

Title:
  Evolution reports "Error performing TLS handshake: Internal error in
  memory allocation."

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

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

Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."

2020-06-12 Thread Stephen Holden

Can I install this version on 18.04 without causing other issues?  First
time had to go outside simply adding a PPA and installing...

Stephen Holden
Ontario, Canada 

On Friday, June 12, 2020, 11:25:46 a.m. EDT, Sebastien Bacher 
<1876...@bugs.launchpad.net> wrote:  
 
 It's unclear to me, if that issue new and what created it? If it has
been existing in Xenial and Bionic and not reported in years, is it
really important enough to justify a stable update?

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1876286

Title:
  Evolution reports "Error performing TLS handshake: Internal error in
  memory allocation."

Status in Gnutls:
  Unknown
Status in claws-mail package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnutls28 package in Ubuntu:
  Fix Released
Status in claws-mail source package in Focal:
  Invalid
Status in evolution source package in Focal:
  Invalid
Status in gnutls28 source package in Focal:
  Triaged
Status in claws-mail source package in Groovy:
  Invalid
Status in evolution source package in Groovy:
  Invalid
Status in gnutls28 source package in Groovy:
  Fix Released
Status in gnutls28 package in CentOS:
  Unknown

Bug description:
  [testcase]

  $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995
  [...]
  - Status: The certificate is trusted.
  *** Fatal error: Internal error in memory allocation.


  When Evolution checks my verizon.net account it displays the message
  "Error performing TLS handshake: Internal error in memory allocation"
  and doesn't download any new email messages.  This started happening
  two days ago shortly after updates were applied.  Normally it would
  download the new email messages.  Searching the web I found a Linux
  Mint forum with users having the same issue.  Some users felt it maybe
  an expired certificate while others thought it might be related to the
  recent update.  What can I do to get more information about this
  issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evolution 3.28.5-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  1 07:03:51 2020
  InstallationDate: Installed on 2017-12-12 (870 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: Upgraded to bionic on 2018-12-28 (489 days ago)

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

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

Title:
  Evolution reports "Error performing TLS handshake: Internal error in
  memory allocation."

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

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

Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."

2020-06-10 Thread Stephen Holden

Will the update be back-ported to 18.04 and/or 18.10 of Ubuntu
automatically as well?  Not sure how the process works...

Stephen Holden
Ontario, Canada 

On Wednesday, June 10, 2020, 9:11:28 a.m. EDT, Sebastien Bacher 
<1876...@bugs.launchpad.net> wrote:  
 
 The issue has been fixed in the current serie now

https://launchpad.net/ubuntu/+source/gnutls28/3.6.13-4ubuntu1


** Changed in: gnutls28 (Ubuntu Groovy)
      Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1876286

Title:
  Evolution reports "Error performing TLS handshake: Internal error in
  memory allocation."

Status in Gnutls:
  Unknown
Status in claws-mail package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnutls28 package in Ubuntu:
  Fix Released
Status in claws-mail source package in Focal:
  Invalid
Status in evolution source package in Focal:
  Invalid
Status in gnutls28 source package in Focal:
  Triaged
Status in claws-mail source package in Groovy:
  Invalid
Status in evolution source package in Groovy:
  Invalid
Status in gnutls28 source package in Groovy:
  Fix Released
Status in gnutls28 package in CentOS:
  Unknown

Bug description:
  [testcase]

  $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995
  [...]
  - Status: The certificate is trusted.
  *** Fatal error: Internal error in memory allocation.


  When Evolution checks my verizon.net account it displays the message
  "Error performing TLS handshake: Internal error in memory allocation"
  and doesn't download any new email messages.  This started happening
  two days ago shortly after updates were applied.  Normally it would
  download the new email messages.  Searching the web I found a Linux
  Mint forum with users having the same issue.  Some users felt it maybe
  an expired certificate while others thought it might be related to the
  recent update.  What can I do to get more information about this
  issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evolution 3.28.5-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  1 07:03:51 2020
  InstallationDate: Installed on 2017-12-12 (870 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: Upgraded to bionic on 2018-12-28 (489 days ago)

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

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

Title:
  Evolution reports "Error performing TLS handshake: Internal error in
  memory allocation."

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

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

Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."

2020-06-07 Thread Stephen Holden

Hear hear!

Thanks all.

On Jun. 7, 2020, 5:15 p.m., at 5:15 p.m., Rod Rivers 
<1876...@bugs.launchpad.net> wrote:
>Big shout out to Daiki Ueno and Andreas Metzler of the GnuTLS project
>and everyone on this thread for helping out!  Testing with Debian
>Bullseye and Ubuntu Groovy + proposed repo was successful.  Both
>included version 3.6.13-4 of GnuTLS.  Hopefully it won't be much longer
>before this fix is pushed out to a wider audience.
>
>-- 
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/1876286
>
>Title:
>  Evolution reports "Error performing TLS handshake: Internal error in
>  memory allocation."
>
>Status in Gnutls:
>  Unknown
>Status in claws-mail package in Ubuntu:
>  Invalid
>Status in evolution package in Ubuntu:
>  Invalid
>Status in gnutls28 package in Ubuntu:
>  Fix Committed
>Status in claws-mail source package in Focal:
>  Invalid
>Status in evolution source package in Focal:
>  Invalid
>Status in gnutls28 source package in Focal:
>  Triaged
>Status in claws-mail source package in Groovy:
>  Invalid
>Status in evolution source package in Groovy:
>  Invalid
>Status in gnutls28 source package in Groovy:
>  Fix Committed
>Status in gnutls28 package in CentOS:
>  Unknown
>
>Bug description:
>  [testcase]
>
>  $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995
>  [...]
>  - Status: The certificate is trusted.
>  *** Fatal error: Internal error in memory allocation.
>
>
>  When Evolution checks my verizon.net account it displays the message
>  "Error performing TLS handshake: Internal error in memory allocation"
>  and doesn't download any new email messages.  This started happening
>  two days ago shortly after updates were applied.  Normally it would
>  download the new email messages.  Searching the web I found a Linux
> Mint forum with users having the same issue.  Some users felt it maybe
> an expired certificate while others thought it might be related to the
>  recent update.  What can I do to get more information about this
>  issue?
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: evolution 3.28.5-0ubuntu0.18.04.2
>  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
>  Uname: Linux 5.3.0-51-generic x86_64
>  ApportVersion: 2.20.9-0ubuntu7.14
>  Architecture: amd64
>  CurrentDesktop: ubuntu:GNOME
>  Date: Fri May  1 07:03:51 2020
>  InstallationDate: Installed on 2017-12-12 (870 days ago)
>InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
>(20170801)
>  ProcEnviron:
>   PATH=(custom, no username)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  SourcePackage: evolution
>  UpgradeStatus: Upgraded to bionic on 2018-12-28 (489 days ago)
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions

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

Title:
  Evolution reports "Error performing TLS handshake: Internal error in
  memory allocation."

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

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

[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."

2020-05-08 Thread Stephen Holden

Started here yesterday accessing Rogers/Yahoo email using imap.  Worked
fine for the last year until yesterday...Gmail is still working.

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

Title:
  Evolution reports "Error performing TLS handshake: Internal error in
  memory allocation."

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

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

[Bug 1867302] Re: gnome-calendar:32235): GcalEvent-CRITICAL : 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:32235): GcalEvent-CRITICAL : 21:08:09.86

2020-04-10 Thread Stephen Allen

Fixed for me as the reporter of the bug - Thus it can be closed. Thanks!

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

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

Title:
  gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
  gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
  (gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
  gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
  Segmentation fault (core dumped)

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

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

Re: [Bug 1867302] Re: gnome-calendar:32235): GcalEvent-CRITICAL : 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:32235): GcalEvent-CRITICAL : 21:08:0

2020-04-10 Thread Stephen Allen

Hi, Evolution Calendar is working fine on my end. Just a data point in case
you don't have the latest updates installed. I haven't tested
Gnome-Calendar yet - I'll do that next and report back.

On Fri, Apr 10, 2020 at 11:25 AM Bicet <1867...@bugs.launchpad.net>
wrote:

> Same happening here with an exchange calendar and multi-day events
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1867302
>
> Title:
>   gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
>   gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
>   (gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
>   gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
>   Segmentation fault (core dumped)
>
> Status in gnome-calendar package in Ubuntu:
>   New
>
> Bug description:
>   It core dumped.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-calendar 3.36.0-1
>   Uname: Linux 5.5.8-xanmod6 x86_64
>   ApportVersion: 2.20.11-0ubuntu20
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Mar 12 21:08:46 2020
>   InstallationDate: Installed on 2019-02-23 (383 days ago)
>   InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181017.3)
>   SourcePackage: gnome-calendar
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1867302/+subscriptions
>


-- 
"It is through science that we prove, but through intuition that we
discover."

- Henri Poincare

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

Title:
  gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
  gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
  (gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
  gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
  Segmentation fault (core dumped)

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

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

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

2020-03-24 Thread Stephen Allen

Thanks fellas, it's fixed for me. Great release!

@Daniel this desktop version definitely appears quicker and smoother! No
doubt due to your extensive work in that regard.

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

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

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

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

[Bug 1867302] [NEW] gnome-calendar:32235): GcalEvent-CRITICAL : 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:32235): GcalEvent-CRITICAL : 21:08:09.

2020-03-12 Thread Stephen Allen

Public bug reported:

It core dumped.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-calendar 3.36.0-1
Uname: Linux 5.5.8-xanmod6 x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 12 21:08:46 2020
InstallationDate: Installed on 2019-02-23 (383 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-calendar (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-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1867302

Title:
  gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
  gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
  (gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
  gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
  Segmentation fault (core dumped)

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

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

[Bug 1867017] Re: Cursor Invisible, but there.

2020-03-11 Thread Stephen Allen

I just noticed that GDM hasn't been updated to 3.26, so this shouldn't
be reported yet as the new gnome packages haven't obviously been
released yet. So pardon the interruption.

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

** Changed in: gdm3 (Ubuntu)
 Assignee: (unassigned) => Stephen Allen (stephen-d-allen)

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

Title:
  Cursor Invisible, but there.

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

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

[Bug 1867017] [NEW] Cursor Invisible, but there.

2020-03-11 Thread Stephen Allen

Public bug reported:

Further to my previous bug for XWayland same issue. I should probably
note that this isn't a clean install but an upgrade from 19.10 on bare
metal. HTH.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
Uname: Linux 5.5.8-xanmod6 x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 11 11:37:49 2020
InstallationDate: Installed on 2019-02-23 (381 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Cursor Invisible, but there.

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

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

Re: [Bug 1822075] Re: tooltips and combo boxes in webbrowsers are all garbage in xserver-xorg-video-radeon 1:19.0.0-1

2019-08-28 Thread Stephen Waines

Hi Dan
I did not report this bug

Steve

On August 28, 2019 3:26:09 AM Daniel van Vugt 
 wrote:

> Returned in bug 1841718?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1821552).
> https://bugs.launchpad.net/bugs/1822075
>
> Title:
>  tooltips and combo boxes in webbrowsers are all garbage in xserver-
>  xorg-video-radeon 1:19.0.0-1
>
> Status in gtk+3.0 package in Ubuntu:
>  Invalid
> Status in mesa package in Ubuntu:
>  Invalid
> Status in mutter package in Ubuntu:
>  Invalid
> Status in xserver-xorg-video-ati package in Ubuntu:
>  Fix Released
>
> Bug description:
>  Disco up to date
>
>  With Chrome and Firefox tooltips and combo boxes are all garbage and
>  make the browser unusable. Cf screenshots.
>
>  Graphics card:
>  Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770]
>
>  I tried gtk2 and gtk3 demos and the combo boxes are broken in the same
>  way.
>
>  I also tried FF as a snap and as a deb and the problem is the same.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 19.04
>  Package: gnome-shell 3.32.0-1ubuntu1
>  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
>  Uname: Linux 5.0.0-7-generic x86_64
>  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>  ApportVersion: 2.20.10-0ubuntu23
>  Architecture: amd64
>  CurrentDesktop: ubuntu:GNOME
>  Date: Thu Mar 28 11:51:41 2019
>  DisplayManager: gdm3
>  InstallationDate: Installed on 2014-07-15 (1717 days ago)
>  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
>  SourcePackage: gnome-shell
>  UpgradeStatus: Upgraded to disco on 2018-03-24 (368 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1822075/+subscriptions

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

Title:
  tooltips and combo boxes in webbrowsers are all garbage in xserver-
  xorg-video-radeon 1:19.0.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1822075/+subscriptions

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

[Bug 1832141] Re: Panel applets crashing on start

2019-06-10 Thread Stephen Boston

Same error reported for The program 'mate-sensors-applet' received an X
Window System error.

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

Title:
  Panel applets crashing on start

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

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

[Bug 1825623] Re: [AppIndicatorSupport-FATAL] unable to update overlay icon

2019-05-22 Thread Stephen Phillips

I get the same error in my log, and I was researching thinking it had to
do with the KeepAwake Gnome-Shell extension:

[AppIndicatorSupport-FATAL] unable to update overlay icon

The KeepAwake icon no longer appears after I installed Ubuntu 19.04.  Here's 
the issue on the extension:
https://github.com/jenspfahl/KeepAwake/issues/22

I get the message in the log when I press Alt-F2 and type r.

If I disable the extension and restart Gnome, I still get the message in
the log, so I'm thinking it's not related.

FYI, I'm viewing the log with:
journalctl /usr/bin/gnome-shell -f -o cat

Hopefully, that provides some clues.

** Bug watch added: github.com/jenspfahl/KeepAwake/issues #22
   https://github.com/jenspfahl/KeepAwake/issues/22

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

Title:
  [AppIndicatorSupport-FATAL] unable to update overlay icon

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

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

[Bug 1829458] Re: [ubuntu 19.04]All .desktop configuration files are not opening in nautilus

2019-05-21 Thread Ron Stephen Mathew

Now  I've modified this bug report and hopefully waiting for an answer.

** Description changed:

- All .desktop configuration files are opening in text editor. Because of
- that we can't creat custom shortcuts and having troubles while
- application making. Please fix this bug on next update. I have an Ubuntu
- 19.04.
+ Error : Desktop configuration files are not launching from nautilus but its 
working from desktop.
+ Occured Error while : made a shortcut and tried to open from nautilus
+ {
+ [Desktop Entry]
+ Name=Install Niram
+ Exec=/usr/share/niram/NiramStock/install.sh
+ Type=Application
+ StartupNotify=true
+ Comment=Install Stock Niram Theme
+ Path=/usr/share
+ Icon=/home/newtron/Documents/NiramStock/20190107_201717.png
+ }
+ but it's opening in text editor. Also ubuntu's default examples have this 
error and showing it as a normal text file.
+ 
+ What I've expected : On older versions of nautilus and all versions of
+ nemo it directly opens .desktop files from file manager.
+ 
+ Now  I've modified this bug report and hopefully waiting for an answer.
  
  Tanks

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

Title:
  [ubuntu 19.04]All .desktop configuration files are not opening in
  nautilus

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1829458/+subscriptions

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

[Bug 1829458] Re: [ubuntu 19.04]All .desktop configuration files are not opening in nautilus

2019-05-21 Thread Ron Stephen Mathew

** Summary changed:

- [ubuntu 19.04]All .desktop configuration files are opening in text editor
+ [ubuntu 19.04]All .desktop configuration files are not opening in nautilus

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

Title:
  [ubuntu 19.04]All .desktop configuration files are not opening in
  nautilus

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1829458/+subscriptions

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

[Bug 1829458] [NEW] [ubuntu 19.04]All .desktop configuration files are opening in text editor

2019-05-16 Thread Ron Stephen Mathew

Public bug reported:

All .desktop configuration files are opening in text editor. Because of
that we can't creat custom shortcuts and having troubles while
application making. Please fix this bug on next update. I have an Ubuntu
19.04.

Tanks

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [ubuntu 19.04]All .desktop configuration files are opening in text
  editor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1829458/+subscriptions

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

[Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

2019-03-02 Thread Stephen Turley

Confirmed fixed in Pop_OS 18.10 using the test case provided.

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

Title:
  144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

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

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

Re: [Bug 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings

2018-09-12 Thread Stephen Allen

I found that in my situation it was the upgrade not working good with some
config settings in my ~/home. When I was beta testing, I don't think the
Ubuntu developers considered that many problems are associated with
upgrades. Once I did a clean install, this situation was gone.

On Wed, Sep 12, 2018 at 8:35 PM Leoncio de Queiroz Maya <
1758...@bugs.launchpad.net> wrote:

> Thank you Cas.
> Let me answer to your suggestions.
>
> Check all updates are installed? Try proposed updates?
> I always install all updates.
>
> Is this with mouse or trackpad?
> I only use the trackpad.
>
> Have you checked what gsettings is reporting?
>
> gsettings get org.gnome.desktop.peripherals.mouse left-handed
> true
>
> Perhaps try a booting with a livecd ubuntu and test mouse there. I don't
> have a CD with Ubuntu 18.04.
>
> I started using Ubuntu with version 12.04 and I have updated it to
> versions 14.04 and 16.04. The left-handed mode always worked fine. A
> couple of weeks ago, I was offered to install version 18.04. The bug
> started after the installation of this new version. I must say it is
> very annoying.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button to Right (left-handed) in Settings
>
> Status in gnome-control-center package in Ubuntu:
>   Fix Released
> Status in xserver-xorg-input-libinput package in Ubuntu:
>   Invalid
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button to Right (left-handed) in Settings

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

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

[Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

2018-07-31 Thread Stephen Early

I've just experienced this problem again.

The following packages were just updated (from /var/log/apt/history.log):
Start-Date: 2018-07-31  09:48:46
Commandline: aptdaemon role='role-commit-packages' sender=':1.2928'
Upgrade: intel-microcode:amd64 (3.20180425.1~ubuntu0.18.04.1, 
3.20180425.1~ubuntu0.18.04.2), console-setup-linux:amd64 (1.178ubuntu2.2, 
1.178ubuntu2.3), console-setup:amd64 (1.178ubuntu2.2, 1.178ubuntu2.3), 
libmysqlclient20:amd64 (5.7.22-0ubuntu18.04.1, 5.7.23-0ubuntu0.18.04.1), 
keyboard-configuration:amd64 (1.178ubuntu2.2, 1.178ubuntu2.3)
End-Date: 2018-07-31  09:49:23

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

Title:
  Input falls through to gdm3 and terminates the session on Ctrl+C after
  udevadm trigger is executed under wayland

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

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

[Bug 1780468] Re: Blurry titlebar font when window is not maximized

2018-07-08 Thread Stephen Karanja

Here you go.

** Attachment added: "Theme"
   
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468/+attachment/5160985/+files/Hardy.tar.gz

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

Title:
  Blurry titlebar font when window is not maximized

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

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

[Bug 1780468] Re: Blurry titlebar font when window is not maximized

2018-07-08 Thread Stephen Karanja

** Attachment added: "metacity-theme-viewer focused unmaximized window"
   
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468/+attachment/5160983/+files/metacity_theme_viewer_focused_unmaximized.png

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

Title:
  Blurry titlebar font when window is not maximized

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

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

[Bug 1780468] Re: Blurry titlebar font when window is not maximized

2018-07-08 Thread Stephen Karanja

It's not visible in metacity-theme-viewer. What is visible here is the
first character rendered differently in the maximized state.

See the attached images.

** Attachment added: "metacity-theme-viewer focused maximized window"
   
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468/+attachment/5160982/+files/metacity_theme_viewer_focused_maximized.png

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

Title:
  Blurry titlebar font when window is not maximized

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

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

[Bug 1780468] Re: Blurry titlebar font when window is not maximized

2018-07-07 Thread Stephen Karanja

Thanks for the heads up about metacity-theme-viewer!

I've opened an upstream issue:
https://gitlab.gnome.org/GNOME/metacity/issues/2

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

Title:
  Blurry titlebar font when window is not maximized

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

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

[Bug 1780468] Re: Blurry titlebar font when window is not maximized

2018-07-07 Thread Stephen Karanja

** Attachment added: "metacity-theme-viewer with different titlebar"
   
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468/+attachment/5160766/+files/metacity-theme-viewer.png

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

Title:
  Blurry titlebar font when window is not maximized

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

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

[Bug 1780468] Re: Blurry titlebar font when window is not maximized

2018-07-07 Thread Stephen Karanja

To answer your questions:

I've just tested with Metacity window manager and the blurry font
rendering occurs, just like with gtk-window-decorator. The issue is not
present in Marco window manager because it doesn't include the
clip_to_rounded_corners() function.

The issue occurs similarly for several MATE themes that I have tested
with e.g. TraditionalOK, TraditionalGreen, Ambiant-MATE, BlueMenta etc.

metacity-theme-viewer draws a different titlebar than what is specified
in the Metacity themes. It doesn't display the titlebar as a themed
window would. See the attached images in which the VLC window has a blue
titlebar as specified in the TraditionalOK theme while metacity-theme-
viewer renders a different titlebar.

** Attachment added: "VLC with TraditionalOK theme titlebar"
   
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468/+attachment/5160765/+files/vlc.png

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

Title:
  Blurry titlebar font when window is not maximized

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

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

[Bug 1780468] [NEW] Blurry titlebar font when window is not maximized

2018-07-06 Thread Stephen Karanja

Public bug reported:

What happens

I've configured Compiz window manager to use gtk-window-decorator so that it 
may apply my Metacity theme for the titlebars. With this decorator, I've 
noticed that Compiz renders slightly blurry titlebar fonts when a window is not 
maximized. Once the window is maximized, sharp fonts are rendered.

When a window is not maximized, the font seems to lack sub-pixel hinting
or anti-aliasing, hence the slightly blurry appearance. I zoomed in on
the font when the window was maximized and observed bluish lines around
the characters. When a window was not maximized, the zoomed-in
characters didn't have the bluish lines.

I've tested and seen that the Marco window manager and the Emerald
decorator (used with Compiz) both render sharp titlebar fonts regardless
of whether a window is maximized or not.

The image in the below link shows the slight difference in font
rendering when Compiz is used with gtk-window-decorator. Firefox's
window was maximized, with sharp text, while VLC's window was not
maximized, with slightly blurry text.

https://i.stack.imgur.com/5BalZ.png

Upon switching to Marco window manager, both texts are sharp.

https://i.stack.imgur.com/9Gzli.png

When the "Compiz with gtk-window-decorator" setup is zoomed-in, blue
lines around the maximized Firefox window titlebar text are visible (it
looks like sub-pixel rendering to me). The blue lines are completely
lacking in the un-maximized VLC window titlebar text.

https://i.stack.imgur.com/XDSAU.png

What I expect to happen
---
The titlebar font rendering should be sharp for both maximized and un-maximized 
windows.

The cause (clip_to_rounded_corners)
---
Upon investigating, I've discovered that Compiz's gtk-window-decorator uses the 
libmetacity library. The clip_to_rounded_corners() function in 
"meta-theme-metacity.c" is called to draw rounded corners for the un-maximized 
windows in my theme. It seems the call to draw rounded corners by cairo_arc() 
in that function somehow affects the font rendering. When windows are 
maximized, the drawing of rounded corners is not performed, hence the sharp 
font rendering.

I rebuilt the libmetacity library with the clip_to_rounded_corners()
call commented out and achieved sharp fonts for un-maximized windows.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: metacity 1:3.28.0-1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Jul  6 19:52:03 2018
InstallationDate: Installed on 2018-05-06 (61 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
SourcePackage: metacity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Blurry titlebar font when window is not maximized

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

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

Re: [Bug 1776901] Re: Startup or Reboot GDM3 Keyboard/Mouse Not Working

2018-06-15 Thread Stephen Allen

I can click, just no response to that action. I'll close this if you think
it's already represented.

On Thu, Jun 14, 2018 at 11:15 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> It sounds like you mean you just can't click on things.
>
> There is a whole family of those bugs to check out here:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=noclick
> https://bugs.launchpad.net/ubuntu/+source/mutter/+bugs?field.tag=noclick
>
> ** Tags added: noclick
>
> ** Also affects: mutter (Ubuntu)
>Importance: Undecided
>Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1776901
>
> Title:
>   Startup or Reboot GDM3 Keyboard/Mouse Not Working
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   New
>
> Bug description:
>   I don't reboot often due to running LTS. However over the past month
>   or so, on subsequent reboots after upgrades, GDM3 accepts focus but
>   won't accept any input either from keyboard or mouse.
>
>   The work-a-round that works for me is to 'Ctl+Alt+F(number) to get to
>   a console, which won't give me a login prompt until I hit the 'return'
>   key. Then I can go back to the GDM3 session and login normally.
>
>   I'm reporting this from Vanilla Gnome Ubuntu 18.04, all current
>   updates applied.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.2-0ubuntu1.2
>   ProcVersionSignature: Ubuntu
> 4.15.0-20201805060708.0+mediatree+hauppauge-generic 4.15.17
>   Uname: Linux 4.15.0-20201805060708-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Thu Jun 14 08:44:36 2018
>   InstallationDate: Installed on 2018-01-19 (146 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gdm3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776901/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.


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

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

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

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

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

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

Re: [Bug 1776901] Re: Startup or Reboot GDM3 Keyboard/Mouse Not Working

2018-06-14 Thread Stephen Allen

Yes it does accept focus but doesn't activate. Did a Cold Boot up this
afternoon and the problem doesn't occur - seems only to happen on warm
reboots. I'll look at the other bug in the am my time. Bedtime now.

On Thu, Jun 14, 2018 at 10:20 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Also, this sounds contradictory:
>
> "GDM3 accepts focus but won't accept any input either from keyboard or
> mouse."
>
> You can't set focus without using a keyboard or mouse. So can you
> clarify what that means?
>
> ** Changed in: gdm3 (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1776901
>
> Title:
>   Startup or Reboot GDM3 Keyboard/Mouse Not Working
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I don't reboot often due to running LTS. However over the past month
>   or so, on subsequent reboots after upgrades, GDM3 accepts focus but
>   won't accept any input either from keyboard or mouse.
>
>   The work-a-round that works for me is to 'Ctl+Alt+F(number) to get to
>   a console, which won't give me a login prompt until I hit the 'return'
>   key. Then I can go back to the GDM3 session and login normally.
>
>   I'm reporting this from Vanilla Gnome Ubuntu 18.04, all current
>   updates applied.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.2-0ubuntu1.2
>   ProcVersionSignature: Ubuntu
> 4.15.0-20201805060708.0+mediatree+hauppauge-generic 4.15.17
>   Uname: Linux 4.15.0-20201805060708-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Thu Jun 14 08:44:36 2018
>   InstallationDate: Installed on 2018-01-19 (146 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gdm3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776901/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

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

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

[Bug 1776901] [NEW] Startup or Reboot GDM3 Keyboard/Mouse Not Working

2018-06-14 Thread Stephen Allen

Public bug reported:

I don't reboot often due to running LTS. However over the past month or
so, on subsequent reboots after upgrades, GDM3 accepts focus but won't
accept any input either from keyboard or mouse.

The work-a-round that works for me is to 'Ctl+Alt+F(number) to get to a
console, which won't give me a login prompt until I hit the 'return'
key. Then I can go back to the GDM3 session and login normally.

I'm reporting this from Vanilla Gnome Ubuntu 18.04, all current updates
applied.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.2-0ubuntu1.2
ProcVersionSignature: Ubuntu 
4.15.0-20201805060708.0+mediatree+hauppauge-generic 4.15.17
Uname: Linux 4.15.0-20201805060708-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Jun 14 08:44:36 2018
InstallationDate: Installed on 2018-01-19 (146 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic gnome3-ppa third-party-packages

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

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

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

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

Re: [Bug 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings

2018-06-03 Thread Stephen Allen

Well it's fixed, that's the important thing.

On Sat, Jun 2, 2018 at 9:30 PM Trish1274 <1758...@bugs.launchpad.net>
wrote:

> Make that 4.13 kernel. Can't type today.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button to Right (left-handed) in Settings
>
> Status in gnome-control-center package in Ubuntu:
>   Fix Released
> Status in xserver-xorg-input-libinput package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button to Right (left-handed) in Settings

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

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

[Bug 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings

2018-06-02 Thread Stephen Allen

Trish, run this in a terminal as one line:

gsettings get org.gnome.desktop.peripherals.mouse left-handed

What does it return? True or false?

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

Title:
  Cannot switch mouse primary button to Right (left-handed) in Settings

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

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

[Bug 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings

2018-06-02 Thread Stephen Allen

It was fixed some time ago before 18.04 was released. Do you have all
repos activated, including /contrib & /universe?

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

Title:
  Cannot switch mouse primary button to Right (left-handed) in Settings

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

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

Re: [Bug 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings

2018-05-31 Thread Stephen Allen

If  I recall correctly it might have been a libinput update? I'm sure the
developer will answer soon. Trish I assume you've rebooted?

On Thu, May 31, 2018 at 7:01 PM Trish1274 <1758...@bugs.launchpad.net>
wrote:

> Actually, I just tried plugging in my office wireless mouse into the
> personal laptop, and the buttons work fine on that. So it's JUST the
> buttons with the track pad. In every previous version of Ubuntu I've
> used, I've always just changed the touchpad buttons through GCC under
> the mouse settings. Is there another way to change settings for the
> touchpad?
>
> If it helps, my personal laptop is a Lenovo Ideapad 300.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button to Right (left-handed) in Settings
>
> Status in gnome-control-center package in Ubuntu:
>   Fix Released
> Status in xserver-xorg-input-libinput package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button to Right (left-handed) in Settings

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

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

[Bug 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings

2018-04-14 Thread Stephen Allen

Confirm that as of Saturday April 14/18 update: the issue is resolved
for me.

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

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

Title:
  Cannot switch mouse primary button to Right (left-handed) in Settings

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

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

Re: [Bug 1758306] Re: Cannot switch mouse primary button in GCC

2018-04-11 Thread Stephen Allen

Thanks a lot! Been driving me nuts and afraid that I'll get used to this
and not able to go back.

On Wed, Apr 11, 2018 at 4:15 PM Launchpad Bug Tracker <
1758...@bugs.launchpad.net> wrote:

> Status changed to 'Confirmed' because the bug affects multiple users.
>
> ** Changed in: gnome-control-center (Ubuntu)
>Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button in GCC
>
> Status in gnome-control-center package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

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

Re: [Bug 1758306] Re: Cannot switch mouse primary button in GCC

Well I don't know what to say - I'm using Ubuntu's environment. Somehow
over time I didn't notice that the vanilla-gnome-session was
removed/replaced. Now I have packages that I didn't have before. I'll
delete the gnome environment settings I have in my ~/home and see what
happens. These wouldn't have any effect on the plymouth-bug or losing
keyboard and mouse focus on gdm3. This iteration isn't worthy of a 'LTS'
release.

On Tue, Apr 3, 2018 at 6:11 PM Gunnar Hjalmarsson <
1758...@bugs.launchpad.net> wrote:

> I'm using real installs, not virtual.
>
> I suppose you are talking about the vanilla-gnome-desktop package, then,
> i.e. a meta package whose purpose is to install GNOME packages. The
> login options are provided by the gnome-session package, and the options
> are:
>
> GNOME
> GNOME on Xorg
>
> I had gnome-session installed already, chose the GNOME option (which
> means GNOME on Wayland), and could still successfully change the mouse
> behavior via g-c-c.
>
> So I couldn't reproduce the issue you described this time either, and
> I'm out of ideas.
>
> ** Changed in: gnome-control-center (Ubuntu)
>Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button in GCC
>
> Status in gnome-control-center package in Ubuntu:
>   New
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

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

Re: [Bug 1758306] Re: Cannot switch mouse primary button in GCC

No Vanilla Gnome means 'Vanilla-Gnome-Session'.

On Tue, Apr 3, 2018 at 4:39 PM Stephen <stephen.d.al...@gmail.com>
wrote:

> Well I'm using bare metal and my ~/home is in good shape, from backups.
> In  terms of my system I'm running a vanilla Ubuntu-Gnome and the reason
> it's not in 'Good Shape' is Ubuntu bugs. ;-) quite Frankly!
> Are you running your instance on bare metal or emulation?
>
> On Tue, Apr 3, 2018 at 3:11 PM Gunnar Hjalmarsson <
> 1758...@bugs.launchpad.net> wrote:
>
>> My 'problem' is that I can't reproduce the issue.
>>
>> You now mentioned a few things, which indicate that your system isn't in
>> the best shape.
>>
>> While I have tested this on "Ubuntu with Xorg", you mentioned that you
>> use "vanilla GNOME" (I suppose that vanilla GNOME means Wayland). Any
>> chance you can log in to an "Ubuntu with Xorg" session and check if the
>> problem is present for you there?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1758306
>>
>> Title:
>>   Cannot switch mouse primary button in GCC
>>
>> Status in gnome-control-center package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
>> configured for left handed use. That is the mouse primary button being
>> switched to the right. GCC doesn't seem to work for this now. I don't know
>> if it's related to evdev or what.
>>   Held back reporting this in case it was fixed by changes overnight.
>> Updated this morning and problem persists.
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 18.04
>>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>>   ProcVersionSignature: Ubuntu
>> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>>   ApportVersion: 2.20.8-0ubuntu10
>>   Architecture: amd64
>>   CurrentDesktop: GNOME
>>   Date: Fri Mar 23 07:07:02 2018
>>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
>> (20170920)
>>   SourcePackage: gnome-control-center
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+subscriptions
>>
> --
>
> This email is printed from 100% recycled electrons.
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

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

Re: [Bug 1758306] Re: Cannot switch mouse primary button in GCC

Well I'm using bare metal and my ~/home is in good shape, from backups. In
terms of my system I'm running a vanilla Ubuntu-Gnome and the reason it's
not in 'Good Shape' is Ubuntu bugs. ;-) quite Frankly!
Are you running your instance on bare metal or emulation?

On Tue, Apr 3, 2018 at 3:11 PM Gunnar Hjalmarsson <
1758...@bugs.launchpad.net> wrote:

> My 'problem' is that I can't reproduce the issue.
>
> You now mentioned a few things, which indicate that your system isn't in
> the best shape.
>
> While I have tested this on "Ubuntu with Xorg", you mentioned that you
> use "vanilla GNOME" (I suppose that vanilla GNOME means Wayland). Any
> chance you can log in to an "Ubuntu with Xorg" session and check if the
> problem is present for you there?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button in GCC
>
> Status in gnome-control-center package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

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

[Bug 1758306] Re: Cannot switch mouse primary button in GCC

Gunnar I'm on Xorg Vanilla-Gnome-Session. Jeremy had mentioned a few
weeks back that he needed testing on 'vanilla-gnome-session'(thats an
installable package, Gunnar) so I installed and am reporting bugs on it.
Hope this clears up any misunderstanding. Cheers.

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

Title:
  Cannot switch mouse primary button in GCC

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

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

Re: [Bug 1758306] Re: Cannot switch mouse primary button in GCC

Makes sense.
OK I had already tried a new user account, but tried again (just in case).
Doesn't affect the issue - it still remains (I can change it in G-C-C but
doesn't change mouse behaviour). Complicating trouble shooting is
continuously running into the 'plymouth corruption bug' at login making it
difficult to choose the new user! As well the bug in gdm3 'losing keyboard
and mouse control' when I logout necessitates a hard reboot each time.
Annoying. lol
In terms of the left handed mouse issue, it doesn't make much sense that it
would be my home settings - as stated this worked several days ago fine, a
recent update borked it, so a regression somewhere.

On Mon, Apr 2, 2018 at 12:00 PM Gunnar Hjalmarsson <
1758...@bugs.launchpad.net> wrote:

> Thanks. Then the question is why it doesn't have any effect for you.
>
> Another test: Can you please create an additional user, log in to that
> user, and test it there? If it works for the other user, the problem is
> somewhere in the $HOME of your first user.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button in GCC
>
> Status in gnome-control-center package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

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

Re: [Bug 1758306] Re: Cannot switch mouse primary button in GCC

2018-04-02 Thread Stephen Allen

Er, sorry I posted the wrong output, I had toggled it. It's showing as true
when switched to left handed in G-C-C:
'gsettings get org.gnome.desktop.peripherals.mouse left-handed
true'

On Mon, Apr 2, 2018 at 7:23 AM Stephen <stephen.d.al...@gmail.com>
wrote:

> Thanks Gunnar. It's sticking in 'gsettings': gsettings get
> org.gnome.desktop.peripherals.mouse left-handed
> false
> Yet the left handed primary button (right button on mouse) still shows me
> a contextual menu.
> So, yes, the value is changed, but doesn't have any affect.
>
> On Sun, Apr 1, 2018 at 9:20 PM Gunnar Hjalmarsson <
> 1758...@bugs.launchpad.net> wrote:
>
>> @Simon: What makes you think that modifications of the GUI for the
>> region panel has anything to do with whether the primary button setting
>> is effective?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1758306
>>
>> Title:
>>   Cannot switch mouse primary button in GCC
>>
>> Status in gnome-control-center package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
>> configured for left handed use. That is the mouse primary button being
>> switched to the right. GCC doesn't seem to work for this now. I don't know
>> if it's related to evdev or what.
>>   Held back reporting this in case it was fixed by changes overnight.
>> Updated this morning and problem persists.
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 18.04
>>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>>   ProcVersionSignature: Ubuntu
>> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>>   ApportVersion: 2.20.8-0ubuntu10
>>   Architecture: amd64
>>   CurrentDesktop: GNOME
>>   Date: Fri Mar 23 07:07:02 2018
>>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
>> (20170920)
>>   SourcePackage: gnome-control-center
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+subscriptions
>>
> --
>
> This email is printed from 100% recycled electrons.
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

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

Re: [Bug 1758306] Re: Cannot switch mouse primary button in GCC

2018-04-02 Thread Stephen Allen

Thanks Gunnar. It's sticking in 'gsettings': gsettings get
org.gnome.desktop.peripherals.mouse left-handed
false
Yet the left handed primary button (right button on mouse) still shows me a
contextual menu.
So, yes, the value is changed, but doesn't have any affect.

On Sun, Apr 1, 2018 at 9:20 PM Gunnar Hjalmarsson <
1758...@bugs.launchpad.net> wrote:

> @Simon: What makes you think that modifications of the GUI for the
> region panel has anything to do with whether the primary button setting
> is effective?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button in GCC
>
> Status in gnome-control-center package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

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

[Bug 1758306] Re: Cannot switch mouse primary button in GCC

2018-04-01 Thread Stephen Allen

 Thanks SQ.

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

Title:
  Cannot switch mouse primary button in GCC

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

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

[Bug 1758306] Re: Cannot switch mouse primary button in GCC

2018-04-01 Thread Stephen Allen

Still happening - surely I'm not the only person that uses a mouse left
handed?! Can someone look at this please?

** Description changed:

- Prior to yesterday's Bionic update, I had my mouse configured for left handed
use. That is the mouse primary button being switched to the right. GCC doesn't
seem to work for this now. I don't know if it's related to evdev or what.
+ Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured
for left handed use. That is the mouse primary button being switched to the
right. GCC doesn't seem to work for this now. I don't know if it's related to
evdev or what.
Held back reporting this in case it was fixed by changes overnight. Updated
this morning and problem persists.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.0-0ubuntu3
ProcVersionSignature: Ubuntu
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
Uname: Linux 4.13.0-36201803011620-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 23 07:07:02 2018
InstallationDate: Installed on 2018-01-19 (62 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
Cannot switch mouse primary button in GCC

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

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

[Bug 1758677] Re: Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

2018-03-30 Thread Stephen Allen

Thanks. Thursday's March 29/18 updates seemed to have fixed it! Thank-
you.

** Changed in: gnome-session (Ubuntu)
   Status: New => Fix Released

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

Title:
  Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

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

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

Re: [Bug 1758677] Re: Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

2018-03-26 Thread Stephen Allen

Not really a duplicate - this doesn't kick me into a terminal session and
this isn't the 'Live' edition but an installed on metal situation.

On Mon, Mar 26, 2018 at 3:50 AM Jean-Baptiste Lallement <
jean-baptiste.lallem...@ubuntu.com> wrote:

> *** This bug is a duplicate of bug 1750995 ***
> https://bugs.launchpad.net/bugs/1750995
>
> ** This bug has been marked a duplicate of bug 1750995
>Logging out live session takes several minutes
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758677
>
> Title:
>   Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout
>
> Status in gnome-session package in Ubuntu:
>   New
>
> Bug description:
>   When manually logging out, it often takes over 30 seconds to give me
> logout dialogue.
>   Been happening for the past week.
>
>   Additionally When I complete the logout - Mouse or keyboard input isn't
> registered forcing a hard reboot.
>   Happens in both vanilla-gnome-session and ubuntu-session.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-session 3.28.0-0ubuntu1
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Mar 25 10:32:33 2018
>   InstallationDate: Installed on 2018-01-19 (65 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gnome-session
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1758677/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

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

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

[Bug 1758677] Re: Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

2018-03-26 Thread Stephen Allen

Circumstances are somewhat different than the duplicate bug.

** This bug is no longer a duplicate of bug 1750995
   Logging out live session takes several minutes

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

Title:
  Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

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

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

[Bug 1758677] [NEW] Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

2018-03-25 Thread Stephen Allen

Public bug reported:

When manually logging out, it often takes over 30 seconds to give me logout 
dialogue. 
Been happening for the past week.

Additionally When I complete the logout - Mouse or keyboard input isn't 
registered forcing a hard reboot.
Happens in both vanilla-gnome-session and ubuntu-session.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-session 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
Uname: Linux 4.13.0-36201803011620-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 25 10:32:33 2018
InstallationDate: Installed on 2018-01-19 (65 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic gnome3-ppa third-party-packages

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

Title:
  Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

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

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

[Bug 1758306] Re: Cannot switch mouse primary button in GCC

2018-03-23 Thread Stephen Allen

Forgot to add that this is 'vanilla gnome'.

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

Title:
  Cannot switch mouse primary button in GCC

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

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

[Bug 1758306] [NEW] Cannot switch mouse primary button in GCC

2018-03-23 Thread Stephen Allen

Public bug reported:

Prior to yesterday's Bionic update, I had my mouse configured for left handed 
use. That is the mouse primary button being switched to the right. GCC doesn't 
seem to work for this now. I don't know if it's related to evdev or what.
Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.0-0ubuntu3
ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
Uname: Linux 4.13.0-36201803011620-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 23 07:07:02 2018
InstallationDate: Installed on 2018-01-19 (62 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Cannot switch mouse primary button in GCC

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

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

[Bug 1751892] Re: Unable to set different Scale on different Monitors

correct notation:  bug 1735986

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

Title:
  Unable to set different Scale on different Monitors

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

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

[Bug 1751892] Re: Unable to set different Scale on different Monitors

It looks like this bug may be a duplicate of the 1735986

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

Title:
  Unable to set different Scale on different Monitors

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

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

[Bug 1756073] Re: Display scaling doesn't work properly on second display

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

It looks like this is also a duplicate of the bug 1735986

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

Title:
  Display scaling doesn't work properly on second display

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

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

[Bug 1751892] Re: Unable to set different Scale on different Monitors

Another note, I'm able to make chrome usable on my external monitor by
opening it using the following command. Obviously if I move chrome to my
4k laptop monitor it becomes unusable. But just documenting it as
another avenue.

GDK_DPI_SCALE=.5 google-chrome

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

Title:
  Unable to set different Scale on different Monitors

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

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

[Bug 1751892] Re: Unable to set different Scale on different Monitors

Just a follow up. I've gotten some good information from this AskUbuntu
post at https://askubuntu.com/questions/875832/how-to-set-per-monitor-
scaling-on-wayland

Following these directions seem to help with certain applications (e.g.
gnome-terminal, gedit, nautilus); however, it does not work for others
(e.g. thunderbird, pidgin, google-chrome).

It apears it's an issue with XWayland.

I would further mention even though applications like nautilus look
correct, things like their context menu are blown up. I assume that some
other application is handling that (gnome?) - I'm unsure of how that
part of the rendering works.

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

Title:
  Unable to set different Scale on different Monitors

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

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

[Bug 1745440] Re: "Apply" button is missing from Displays

I've now reported this directly to gnome-control-center here
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/18

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

Title:
  "Apply" button is missing from Displays

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

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

[Bug 1751892] Re: Unable to set different Scale on different Monitors