[Desktop-packages] [Bug 2011471] Re: Unable to authenticate to Google Gmail mail servers: Secure connection failed

2023-10-23 Thread Todd Taft
With thunderbird 1:115.3.1+build1-0ubuntu0.20.04.1 the error message has
changed to a security error about accessing files on localhost.  See
attached image.

** Attachment added: "Screenshot from 2023-10-24 00-53-37.png"
   
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2011471/+attachment/5712803/+files/Screenshot%20from%202023-10-24%2000-53-37.png

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

Title:
  Unable to authenticate to Google Gmail mail servers: Secure connection
  failed

Status in thunderbird package in Ubuntu:
  New

Bug description:
  I get an error "Secure connection failed" whenever I attempt to
  authenticate to accounts that are hosted by Google.  This affects
  gmail.com addresses and addresses in other domains that use Google
  Workspaces.  I am able to connect to other mail servers (e.g. ones
  running dovecot).

  In order to make sure the problem wasn't caused by any plugin, etc.
  that I had installed, I reinstalled the packages and moved aside the
  ~/.thundirbird directory.

  The problem still occurs doing the account setup phase for the Google
  accounts.  I enter the name, address, password in the main Thunderbird
  window, and then get a pop-up window that asks for account name and
  password again.  After entering that, it proceeds to ask me if I want
  to allow Thunderbird permission to access mail, calendars, etc., and
  it then asks me to do the two-factor authentication.  It's after I do
  the two-factor authentication and click the button to indicate that I
  have done so that I get the error.

  There should not be any outbound firewall rules blocking connections
  to Google servers. IPv6 does not work properly from this network, but
  I don't have any known problems with IPv4 connections to Google.

  Ubuntu 20.04
  thunderbird 1:102.8.0+build2-0ubuntu0.20.04.1
  thunderbird-gnome-support :102.8.0+build2-0ubuntu0.20.04.1

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


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


[Desktop-packages] [Bug 2011471] [NEW] Unable to authenticate to Google Gmail mail servers: Secure connection failed

2023-03-13 Thread Todd Taft
Public bug reported:

I get an error "Secure connection failed" whenever I attempt to
authenticate to accounts that are hosted by Google.  This affects
gmail.com addresses and addresses in other domains that use Google
Workspaces.  I am able to connect to other mail servers (e.g. ones
running dovecot).

In order to make sure the problem wasn't caused by any plugin, etc. that
I had installed, I reinstalled the packages and moved aside the
~/.thundirbird directory.

The problem still occurs doing the account setup phase for the Google
accounts.  I enter the name, address, password in the main Thunderbird
window, and then get a pop-up window that asks for account name and
password again.  After entering that, it proceeds to ask me if I want to
allow Thunderbird permission to access mail, calendars, etc., and it
then asks me to do the two-factor authentication.  It's after I do the
two-factor authentication and click the button to indicate that I have
done so that I get the error.

There should not be any outbound firewall rules blocking connections to
Google servers. IPv6 does not work properly from this network, but I
don't have any known problems with IPv4 connections to Google.

Ubuntu 20.04
thunderbird 1:102.8.0+build2-0ubuntu0.20.04.1
thunderbird-gnome-support :102.8.0+build2-0ubuntu0.20.04.1

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

** Attachment added: "Screenshot from 2023-03-07 03-02-57.png"
   
https://bugs.launchpad.net/bugs/2011471/+attachment/5654222/+files/Screenshot%20from%202023-03-07%2003-02-57.png

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

Title:
  Unable to authenticate to Google Gmail mail servers: Secure connection
  failed

Status in thunderbird package in Ubuntu:
  New

Bug description:
  I get an error "Secure connection failed" whenever I attempt to
  authenticate to accounts that are hosted by Google.  This affects
  gmail.com addresses and addresses in other domains that use Google
  Workspaces.  I am able to connect to other mail servers (e.g. ones
  running dovecot).

  In order to make sure the problem wasn't caused by any plugin, etc.
  that I had installed, I reinstalled the packages and moved aside the
  ~/.thundirbird directory.

  The problem still occurs doing the account setup phase for the Google
  accounts.  I enter the name, address, password in the main Thunderbird
  window, and then get a pop-up window that asks for account name and
  password again.  After entering that, it proceeds to ask me if I want
  to allow Thunderbird permission to access mail, calendars, etc., and
  it then asks me to do the two-factor authentication.  It's after I do
  the two-factor authentication and click the button to indicate that I
  have done so that I get the error.

  There should not be any outbound firewall rules blocking connections
  to Google servers. IPv6 does not work properly from this network, but
  I don't have any known problems with IPv4 connections to Google.

  Ubuntu 20.04
  thunderbird 1:102.8.0+build2-0ubuntu0.20.04.1
  thunderbird-gnome-support :102.8.0+build2-0ubuntu0.20.04.1

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


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


[Desktop-packages] [Bug 1952164] Re: cups.path repeatedly goes into systemd failed state

2021-11-24 Thread Todd Taft
Discovered this was a system-wide problem, not specifically related to cups.
Backup program was holding open a very high number if inotify watches and this 
was causing issues for other programs (including cups).
Solution was to add a conf file in /etc/sysctl.d that set a higher value for 
fs.inotify.max_user_watches than the default (and then force a reload).

In my case, this seems to work:
echo "fs.inotify.max_user_watches=131072" >> /etc/sysctl.d/999-local.conf
sysctl -p /etc/sysctl.d/999-local.conf

Note that this solution may cause other issues on systems with low
memory.

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

Title:
  cups.path repeatedly goes into systemd failed state

Status in cups package in Ubuntu:
  Invalid

Bug description:
  cups.path is repeatedly entering a failed state in systemd.  Attempts
  to restart the unit or even reboot the machine are, at best, temporary
  solutions.

  # systemctl status cups.path
  ● cups.path - CUPS Scheduler
   Loaded: loaded (/lib/systemd/system/cups.path; enabled; vendor preset: 
enabled)
   Active: failed (Result: resources)
 Triggers: ● cups.service

  Nov 24 04:33:31 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.
  # journalctl -u cups.path
  -- Logs begin at Tue 2021-11-23 22:54:38 EST, end at Wed 2021-11-24 21:42:42 
EST. --
  Nov 23 22:54:51 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
  Nov 23 23:19:17 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
  Nov 23 23:19:17 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.
  -- Reboot --
  Nov 24 04:33:31 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.

  Despite what the log messages suggest, none of my (non-snap) filesystems are 
full (or even close to full):
  # df
  Filesystem
 1K-blocks  Used   Available Use% Mounted on
  udev  
  32731616 032731616   0% /dev
  tmpfs 
   6556256  2536 6553720   1% /run
  /dev/mapper/kangaroovg-rootlv 
   5095040553996 4262516  12% /
  
/dev/disk/by-id/dm-uuid-LVM-kxWkbFRXPo6GoeQURytO8JUpXOtGnGzNRQG28DNWnEi0JYl1Vkx1r7uvSiDwfZDb
20511312   724339212202960  38% /usr
  tmpfs 
  32781264  102432780240   1% /dev/shm
  tmpfs 
  5120 45116   1% /run/lock
  tmpfs 
  32781264 032781264   0% /sys/fs/cgroup
  none  
   4194304  3504 4190800   1% /tmp
  /dev/mapper/kangaroovg-varlv  
   5095040   1743876 3072636  37% /var
  /dev/nvme1n1p2
999320246420  684088  27% /boot
  /dev/mapper/kangaroovg-srvlv  
   5095040 20520 4795992   1% /srv
  /dev/mapper/kangaroovg-usrlocallv 
   5095040 31820 4784692   1% /usr/local
  /dev/mapper/kangaroovg-homelv 
  51343840  1300229235703724  27% /home
  /dev/mapper/kangaroovg-varliblv   
   5095040   1306604 3509908  28% /var/lib
  /dev/nvme1n1p1
523248  5360  517888   2% /boot/efi
  /dev/loop0
 56832 56832   0 100% /snap/core18/2128
  /dev/loop2
 33152 33152   0 100% /snap/snapd/12883
  /dev/loop1

[Desktop-packages] [Bug 1952164] Re: cups.path repeatedly goes into systemd failed state

2021-11-24 Thread Todd Taft
** Changed in: cups (Ubuntu)
   Status: New => Invalid

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

Title:
  cups.path repeatedly goes into systemd failed state

Status in cups package in Ubuntu:
  Invalid

Bug description:
  cups.path is repeatedly entering a failed state in systemd.  Attempts
  to restart the unit or even reboot the machine are, at best, temporary
  solutions.

  # systemctl status cups.path
  ● cups.path - CUPS Scheduler
   Loaded: loaded (/lib/systemd/system/cups.path; enabled; vendor preset: 
enabled)
   Active: failed (Result: resources)
 Triggers: ● cups.service

  Nov 24 04:33:31 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.
  # journalctl -u cups.path
  -- Logs begin at Tue 2021-11-23 22:54:38 EST, end at Wed 2021-11-24 21:42:42 
EST. --
  Nov 23 22:54:51 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
  Nov 23 23:19:17 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
  Nov 23 23:19:17 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.
  -- Reboot --
  Nov 24 04:33:31 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.

  Despite what the log messages suggest, none of my (non-snap) filesystems are 
full (or even close to full):
  # df
  Filesystem
 1K-blocks  Used   Available Use% Mounted on
  udev  
  32731616 032731616   0% /dev
  tmpfs 
   6556256  2536 6553720   1% /run
  /dev/mapper/kangaroovg-rootlv 
   5095040553996 4262516  12% /
  
/dev/disk/by-id/dm-uuid-LVM-kxWkbFRXPo6GoeQURytO8JUpXOtGnGzNRQG28DNWnEi0JYl1Vkx1r7uvSiDwfZDb
20511312   724339212202960  38% /usr
  tmpfs 
  32781264  102432780240   1% /dev/shm
  tmpfs 
  5120 45116   1% /run/lock
  tmpfs 
  32781264 032781264   0% /sys/fs/cgroup
  none  
   4194304  3504 4190800   1% /tmp
  /dev/mapper/kangaroovg-varlv  
   5095040   1743876 3072636  37% /var
  /dev/nvme1n1p2
999320246420  684088  27% /boot
  /dev/mapper/kangaroovg-srvlv  
   5095040 20520 4795992   1% /srv
  /dev/mapper/kangaroovg-usrlocallv 
   5095040 31820 4784692   1% /usr/local
  /dev/mapper/kangaroovg-homelv 
  51343840  1300229235703724  27% /home
  /dev/mapper/kangaroovg-varliblv   
   5095040   1306604 3509908  28% /var/lib
  /dev/nvme1n1p1
523248  5360  517888   2% /boot/efi
  /dev/loop0
 56832 56832   0 100% /snap/core18/2128
  /dev/loop2
 33152 33152   0 100% /snap/snapd/12883
  /dev/loop1
 72064 72064   0 100% /snap/lxd/21029
  /dev/mapper/disharmony--kangaroo--qsan--vg-disharmony--kangaroo--qsan--lv 
5325329320 198368460  4858509228   4% /srv/disharmony
  /dev/mapper/git--kangaroo--qsan--vg-git--kangaroo--qsan--lv   
1055836596 77852  1002055476   1% /srv/git
  /dev/mapper/qsaniscsiunisonvg-unisonlv
5366618112 385871460  4980746652   

[Desktop-packages] [Bug 1952164] [NEW] cups.path repeatedly goes into systemd failed state

2021-11-24 Thread Todd Taft
Public bug reported:

cups.path is repeatedly entering a failed state in systemd.  Attempts to
restart the unit or even reboot the machine are, at best, temporary
solutions.

# systemctl status cups.path
● cups.path - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.path; enabled; vendor preset: 
enabled)
 Active: failed (Result: resources)
   Triggers: ● cups.service

Nov 24 04:33:31 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.
# journalctl -u cups.path
-- Logs begin at Tue 2021-11-23 22:54:38 EST, end at Wed 2021-11-24 21:42:42 
EST. --
Nov 23 22:54:51 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
Nov 23 23:19:17 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
Nov 23 23:19:17 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.
-- Reboot --
Nov 24 04:33:31 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.

Despite what the log messages suggest, none of my (non-snap) filesystems are 
full (or even close to full):
# df
Filesystem  
   1K-blocks  Used   Available Use% Mounted on
udev
32731616 032731616   0% /dev
tmpfs   
 6556256  2536 6553720   1% /run
/dev/mapper/kangaroovg-rootlv   
 5095040553996 4262516  12% /
/dev/disk/by-id/dm-uuid-LVM-kxWkbFRXPo6GoeQURytO8JUpXOtGnGzNRQG28DNWnEi0JYl1Vkx1r7uvSiDwfZDb
20511312   724339212202960  38% /usr
tmpfs   
32781264  102432780240   1% /dev/shm
tmpfs   
5120 45116   1% /run/lock
tmpfs   
32781264 032781264   0% /sys/fs/cgroup
none
 4194304  3504 4190800   1% /tmp
/dev/mapper/kangaroovg-varlv
 5095040   1743876 3072636  37% /var
/dev/nvme1n1p2  
  999320246420  684088  27% /boot
/dev/mapper/kangaroovg-srvlv
 5095040 20520 4795992   1% /srv
/dev/mapper/kangaroovg-usrlocallv   
 5095040 31820 4784692   1% /usr/local
/dev/mapper/kangaroovg-homelv   
51343840  1300229235703724  27% /home
/dev/mapper/kangaroovg-varliblv 
 5095040   1306604 3509908  28% /var/lib
/dev/nvme1n1p1  
  523248  5360  517888   2% /boot/efi
/dev/loop0  
   56832 56832   0 100% /snap/core18/2128
/dev/loop2  
   33152 33152   0 100% /snap/snapd/12883
/dev/loop1  
   72064 72064   0 100% /snap/lxd/21029
/dev/mapper/disharmony--kangaroo--qsan--vg-disharmony--kangaroo--qsan--lv   
  5325329320 198368460  4858509228   4% /srv/disharmony
/dev/mapper/git--kangaroo--qsan--vg-git--kangaroo--qsan--lv 
  1055836596 77852  1002055476   1% /srv/git
/dev/mapper/qsaniscsiunisonvg-unisonlv  
  5366618112 385871460  4980746652   8% /srv/unison
/dev/mapper/qsaniscsilinuxbackupvg-linuxbackuplv
  5366618112  96643028  5269975084   2% /srv/linux-backup
/dev/mapper/qsaniscsisystemarchivevg-systemarchivelv
  5366618112 745069628  4621548484  14% /srv/system-archive
tmpfs   

[Desktop-packages] [Bug 1778082] Re: Language Support Is Incomplete dialog must show package list to install

2020-06-06 Thread Todd Taft
I've also observed this behavior on Kubuntu 20.04.

This command appears to fix the issue: sudo apt install $(check-
language-support)

Reference: https://unix.stackexchange.com/questions/421066/popup-
language-support-is-incomplete-what-packages-does-it-want-to-install

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

Title:
  Language Support Is Incomplete dialog must show package list to
  install

Status in kde-runtime package in Ubuntu:
  Confirmed
Status in language-selector package in Ubuntu:
  Confirmed

Bug description:
  When Ubuntu have missing language packages, it shows in tray System
  Notification Helper message with text "Language support is incomplete,
  additional packages are required".

  But when user do one simple mouse click on this notification - Ubuntu
  immediately asks user password with "Authentication Required" popup
  window, without describing what is planned to do, which packages are
  missing and will be installed.

  After typing password - user will not see any useful info too - only
  small window with unnamed progress bar and standard text phrases.

  After process finished - there are also zero useful info, only that
  process is finished.

  
  Please show more information about this process, before ask user password!

  Very useful info will be:

  - How this missed packages are detected?

  - Why those packages are missed?

  - What packages will planned to install/upgrade (package names,
  versions)?

  - Total size of planned downloads.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: language-selector-common 0.188.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jun 21 17:51:49 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: language-selector
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1778082/+subscriptions

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


[Desktop-packages] [Bug 1020770] [NEW] gdm install prompts about dm when debconf value set

2012-07-03 Thread Todd Taft
Public bug reported:

When installing gdm 3.0.4-0ubuntu15 on a 12.04 system via aptitude, I
get prompted as to which dm I want to use, even if I have already set
the appropriate debconf values before attempting the install.

Steps to reproduce:
echo "gdm shared/default-x-display-manager select lightdm" 
|debconf-set-selections
aptitude -y install gdm

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

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

Title:
  gdm install prompts about dm when debconf value set

Status in “gdm” package in Ubuntu:
  New

Bug description:
  When installing gdm 3.0.4-0ubuntu15 on a 12.04 system via aptitude, I
  get prompted as to which dm I want to use, even if I have already set
  the appropriate debconf values before attempting the install.

  Steps to reproduce:
  echo "gdm shared/default-x-display-manager select lightdm" 
|debconf-set-selections
  aptitude -y install gdm

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

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