[Touch-packages] [Bug 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status

[Gordon Lack]

I have this issue on an Intel NUC (NUC10i357FN).

The sysfs entry for the power supply does contain a usb_type entry for
it, which contains:

[nuc]: cat usb_type 
[C] PD

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu.
https://bugs.launchpad.net/bugs/1980991

Title:
  /usr/sbin/on_ac_power incorrectly reporting ac power status

Status in powermgmt-base package in Ubuntu:
  Confirmed
Status in powermgmt-base source package in Kinetic:
  Confirmed

Bug description:
  Good afternoon, folks.

  I believe I discovered a bug in the /usr/sbin/on_ac_power script. I
  have a Dell OptiPlex 5090 host that has an entry in
  /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe
  this is the USB-C power delivery port on the front of the chassis. The
  issue I'm encountering is that /usr/sbin/on_ac_power is exiting with
  code 1 which states: (1 (false) if not on AC power) when that isn't
  the case.

  This looks to be because of the ucsi-source-psy-USBC000:001 entry
  reporting the "online" status as 0, presumably because nothing is
  currently connected to that USB-C port.

  This causes /usr/sbin/on_ac_power to incorrectly report that the
  machine isn't connected to AC power and causes other utilities like
  unattended-upgrades to quit when using the default configuration since
  it believes the machine isn't connected to AC power.

  There is a workaround with unattended-upgrades where you can specify
  it to run regardless of if AC power is connected, but as more and more
  chassis implement power-delivery USB-C ports I foresee this becoming
  more of an issue.

  I'm not sure if it's anything to look into, but I figured I would
  share my findings. Please let me know if you have any questions or if
  I can provide any additional information, troubleshooting, or testing.

  Thanks!
  -Kevin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+subscriptions


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

[Touch-packages] [Bug 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status

[Gordon Lack]

Possibly this?

--- /bin/on_ac_power2019-07-20 16:43:51.0 +0100
+++ ./on_ac_power   2022-09-22 01:44:53.412558622 +0100
@@ -28,6 +28,17 @@
type="$(cat "${FN}/type")"
case "${type}" in
Mains|USB*|BrickID|Wireless)
+# If USB, is it input or output?
+#
+   case "${type}" in
+   USB*)
+   if test -r "${FN}/usb_type"; then
+   usb_type=`cat "${FN}/usb_type"`
+   case "${usb_type}" in
+   *PD*)   continue;;
+   esac
+   fi
+   esac
if [ -r "${FN}/online" ]; then
online="$(cat "${FN}/online")"
[ "$online" = 1 ] && exit 0

(sorry - the indentation spaces after any + are being eaten)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu.
https://bugs.launchpad.net/bugs/1980991

Title:
  /usr/sbin/on_ac_power incorrectly reporting ac power status

Status in powermgmt-base package in Ubuntu:
  Confirmed
Status in powermgmt-base source package in Kinetic:
  Confirmed

Bug description:
  Good afternoon, folks.

  I believe I discovered a bug in the /usr/sbin/on_ac_power script. I
  have a Dell OptiPlex 5090 host that has an entry in
  /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe
  this is the USB-C power delivery port on the front of the chassis. The
  issue I'm encountering is that /usr/sbin/on_ac_power is exiting with
  code 1 which states: (1 (false) if not on AC power) when that isn't
  the case.

  This looks to be because of the ucsi-source-psy-USBC000:001 entry
  reporting the "online" status as 0, presumably because nothing is
  currently connected to that USB-C port.

  This causes /usr/sbin/on_ac_power to incorrectly report that the
  machine isn't connected to AC power and causes other utilities like
  unattended-upgrades to quit when using the default configuration since
  it believes the machine isn't connected to AC power.

  There is a workaround with unattended-upgrades where you can specify
  it to run regardless of if AC power is connected, but as more and more
  chassis implement power-delivery USB-C ports I foresee this becoming
  more of an issue.

  I'm not sure if it's anything to look into, but I figured I would
  share my findings. Please let me know if you have any questions or if
  I can provide any additional information, troubleshooting, or testing.

  Thanks!
  -Kevin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+subscriptions


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

[Touch-packages] [Bug 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status

[Gordon Lack]

This is still an issue in Kinetic.

And it's now stopping unattended_upgrades running, as these (now?) have a 
condition of ConditionACPower=true
which is not being met even though the system is running on AC (and has no 
other way of running).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu.
https://bugs.launchpad.net/bugs/1980991

Title:
  /usr/sbin/on_ac_power incorrectly reporting ac power status

Status in powermgmt-base package in Ubuntu:
  Triaged
Status in powermgmt-base source package in Kinetic:
  Triaged

Bug description:
  Good afternoon, folks.

  I believe I discovered a bug in the /usr/sbin/on_ac_power script. I
  have a Dell OptiPlex 5090 host that has an entry in
  /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe
  this is the USB-C power delivery port on the front of the chassis. The
  issue I'm encountering is that /usr/sbin/on_ac_power is exiting with
  code 1 which states: (1 (false) if not on AC power) when that isn't
  the case.

  This looks to be because of the ucsi-source-psy-USBC000:001 entry
  reporting the "online" status as 0, presumably because nothing is
  currently connected to that USB-C port.

  This causes /usr/sbin/on_ac_power to incorrectly report that the
  machine isn't connected to AC power and causes other utilities like
  unattended-upgrades to quit when using the default configuration since
  it believes the machine isn't connected to AC power.

  There is a workaround with unattended-upgrades where you can specify
  it to run regardless of if AC power is connected, but as more and more
  chassis implement power-delivery USB-C ports I foresee this becoming
  more of an issue.

  I'm not sure if it's anything to look into, but I figured I would
  share my findings. Please let me know if you have any questions or if
  I can provide any additional information, troubleshooting, or testing.

  Thanks!
  -Kevin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+subscriptions


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

[Touch-packages] [Bug 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status

[Gordon Lack]

Actually, it turns out that systemd has its own code to check for AC
power (same/similar logic - perhaps this should be done in a single
system service rather than duplicated between sub-systems?).

So I'll open a bug for this against systemd as well and cross-reference
them.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu.
https://bugs.launchpad.net/bugs/1980991

Title:
  /usr/sbin/on_ac_power incorrectly reporting ac power status

Status in powermgmt-base package in Ubuntu:
  Triaged
Status in powermgmt-base source package in Kinetic:
  Triaged

Bug description:
  Good afternoon, folks.

  I believe I discovered a bug in the /usr/sbin/on_ac_power script. I
  have a Dell OptiPlex 5090 host that has an entry in
  /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe
  this is the USB-C power delivery port on the front of the chassis. The
  issue I'm encountering is that /usr/sbin/on_ac_power is exiting with
  code 1 which states: (1 (false) if not on AC power) when that isn't
  the case.

  This looks to be because of the ucsi-source-psy-USBC000:001 entry
  reporting the "online" status as 0, presumably because nothing is
  currently connected to that USB-C port.

  This causes /usr/sbin/on_ac_power to incorrectly report that the
  machine isn't connected to AC power and causes other utilities like
  unattended-upgrades to quit when using the default configuration since
  it believes the machine isn't connected to AC power.

  There is a workaround with unattended-upgrades where you can specify
  it to run regardless of if AC power is connected, but as more and more
  chassis implement power-delivery USB-C ports I foresee this becoming
  more of an issue.

  I'm not sure if it's anything to look into, but I figured I would
  share my findings. Please let me know if you have any questions or if
  I can provide any additional information, troubleshooting, or testing.

  Thanks!
  -Kevin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+subscriptions


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

[Touch-packages] [Bug 1998872] [NEW] unattended-updates failing in kinetic as AC power detection is bugged

[Gordon Lack]

Public bug reported:

The ConditionACPower testing code does not work correctly on some
systems. This prevents the unattended-updates systemd service running as
it thinks that a system (a NUC10i3FNYHN) is running on battery. It isn't
- it just has  a power supply that can *provide* power over USB.

This (unattended-updrades) was OK in Jammy, but started to fail when I
upgraded to Kinetic.

(A systemd override file to remove the condition gets the service
working again.)

The problem is similar (or perhaps identical) to the problem with the
on_ac_power script (from the powermgmt-base package).

That has been reported in bug #1980991.  There are more details there.

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

** Package changed: powermgmt-base (Ubuntu) => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu.
https://bugs.launchpad.net/bugs/1998872

Title:
  unattended-updates failing in kinetic as AC power detection is bugged

Status in systemd package in Ubuntu:
  New

Bug description:
  The ConditionACPower testing code does not work correctly on some
  systems. This prevents the unattended-updates systemd service running
  as it thinks that a system (a NUC10i3FNYHN) is running on battery. It
  isn't - it just has  a power supply that can *provide* power over USB.

  This (unattended-updrades) was OK in Jammy, but started to fail when I
  upgraded to Kinetic.

  (A systemd override file to remove the condition gets the service
  working again.)

  The problem is similar (or perhaps identical) to the problem with the
  on_ac_power script (from the powermgmt-base package).

  That has been reported in bug #1980991.  There are more details there.

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


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

[Touch-packages] [Bug 1998872] Re: unattended-updates failing in kinetic as AC power detection is bugged

[Gordon Lack]

This also affects various other services.

apt-daily
e2scrub_all
logrotate
man-db
plocate-updatedb


** Description changed:

  The ConditionACPower testing code does not work correctly on some
  systems. This prevents the unattended-updates systemd service running as
  it thinks that a system (a NUC10i3FNYHN) is running on battery. It isn't
  - it just has  a power supply that can *provide* power over USB.
  
  This (unattended-updrades) was OK in Jammy, but started to fail when I
  upgraded to Kinetic.
  
- (A systemd override file to remove the condition gets the service
- working again.)
+ (A systemd override file for apt-daily-upgrade.service to remove the
+ condition gets the service working again.)
  
  The problem is similar (or perhaps identical) to the problem with the
  on_ac_power script (from the powermgmt-base package).
  
  That has been reported in bug #1980991.  There are more details there.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1998872

Title:
  unattended-updates failing in kinetic as AC power detection is bugged

Status in e2fsprogs package in Ubuntu:
  New
Status in logrotate package in Ubuntu:
  New
Status in man-db package in Ubuntu:
  New
Status in plocate package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  The ConditionACPower testing code does not work correctly on some
  systems. This prevents the unattended-updates systemd service running
  as it thinks that a system (a NUC10i3FNYHN) is running on battery. It
  isn't - it just has  a power supply that can *provide* power over USB.

  This (unattended-updrades) was OK in Jammy, but started to fail when I
  upgraded to Kinetic.

  (A systemd override file for apt-daily-upgrade.service to remove the
  condition gets the service working again.)

  The problem is similar (or perhaps identical) to the problem with the
  on_ac_power script (from the powermgmt-base package).

  That has been reported in bug #1980991.  There are more details there.

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


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

[Touch-packages] [Bug 1998872] Re: unattended-updates failing in kinetic as AC power detection is bugged

[Gordon Lack]

This has (apparently) been fixed by
https://github.com/systemd/systemd/pull/24220

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

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

** Also affects: man-db (Ubuntu)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1998872

Title:
  unattended-updates failing in kinetic as AC power detection is bugged

Status in e2fsprogs package in Ubuntu:
  New
Status in logrotate package in Ubuntu:
  New
Status in man-db package in Ubuntu:
  New
Status in plocate package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  The ConditionACPower testing code does not work correctly on some
  systems. This prevents the unattended-updates systemd service running
  as it thinks that a system (a NUC10i3FNYHN) is running on battery. It
  isn't - it just has  a power supply that can *provide* power over USB.

  This (unattended-updrades) was OK in Jammy, but started to fail when I
  upgraded to Kinetic.

  (A systemd override file for apt-daily-upgrade.service to remove the
  condition gets the service working again.)

  The problem is similar (or perhaps identical) to the problem with the
  on_ac_power script (from the powermgmt-base package).

  That has been reported in bug #1980991.  There are more details there.

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


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

[Touch-packages] [Bug 1998872] Re: unattended-updates failing in kinetic as AC power detection is bugged

[Gordon Lack]

** Also affects: unattended-upgrades (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1998872

Title:
  unattended-updates failing in kinetic as AC power detection is bugged

Status in e2fsprogs package in Ubuntu:
  New
Status in logrotate package in Ubuntu:
  New
Status in man-db package in Ubuntu:
  New
Status in plocate package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The ConditionACPower testing code does not work correctly on some
  systems. This prevents the unattended-updates systemd service running
  as it thinks that a system (a NUC10i3FNYHN) is running on battery. It
  isn't - it just has  a power supply that can *provide* power over USB.

  This (unattended-updrades) was OK in Jammy, but started to fail when I
  upgraded to Kinetic.

  (A systemd override file for apt-daily-upgrade.service to remove the
  condition gets the service working again.)

  The problem is similar (or perhaps identical) to the problem with the
  on_ac_power script (from the powermgmt-base package).

  That has been reported in bug #1980991.  There are more details there.

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


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

[Touch-packages] [Bug 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status

[Gordon Lack]

This is a problem in Mantic too.

And if you never fix it it will be a problem in the next LTS release.
Just as it is a problem in the current LTS release.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu.
https://bugs.launchpad.net/bugs/1980991

Title:
  /usr/sbin/on_ac_power incorrectly reporting ac power status

Status in powermgmt-base package in Ubuntu:
  Triaged
Status in powermgmt-base source package in Kinetic:
  Won't Fix
Status in powermgmt-base source package in Lunar:
  Won't Fix

Bug description:
  Good afternoon, folks.

  I believe I discovered a bug in the /usr/sbin/on_ac_power script. I
  have a Dell OptiPlex 5090 host that has an entry in
  /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe
  this is the USB-C power delivery port on the front of the chassis. The
  issue I'm encountering is that /usr/sbin/on_ac_power is exiting with
  code 1 which states: (1 (false) if not on AC power) when that isn't
  the case.

  This looks to be because of the ucsi-source-psy-USBC000:001 entry
  reporting the "online" status as 0, presumably because nothing is
  currently connected to that USB-C port.

  This causes /usr/sbin/on_ac_power to incorrectly report that the
  machine isn't connected to AC power and causes other utilities like
  unattended-upgrades to quit when using the default configuration since
  it believes the machine isn't connected to AC power.

  There is a workaround with unattended-upgrades where you can specify
  it to run regardless of if AC power is connected, but as more and more
  chassis implement power-delivery USB-C ports I foresee this becoming
  more of an issue.

  I'm not sure if it's anything to look into, but I figured I would
  share my findings. Please let me know if you have any questions or if
  I can provide any additional information, troubleshooting, or testing.

  Thanks!
  -Kevin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+subscriptions


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

[Touch-packages] [Bug 1949615] [NEW] Notify method not working correctly in 21.10 (impish)

[Gordon Lack]

Public bug reported:

The replaces_id parameter to org.freedesktop.Notifications.Notify no longer 
works correctly at 21.10.
It is OK on 21.04.

At 21.10 if a message with replaces_id === x ever times out then any
further message sent with that replaces_id never gets shown.  The
timeout-over seems to become permanent for that replaces_id.

Example program to follow

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: dbus 1.12.20-2ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Nov  3 16:49:18 2021
InstallationDate: Installed on 2020-08-13 (447 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: dbus
UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago)

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


** Tags: amd64 apport-bug impish

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1949615

Title:
  Notify method not working correctly in 21.10 (impish)

Status in dbus package in Ubuntu:
  New

Bug description:
  The replaces_id parameter to org.freedesktop.Notifications.Notify no longer 
works correctly at 21.10.
  It is OK on 21.04.

  At 21.10 if a message with replaces_id === x ever times out then any
  further message sent with that replaces_id never gets shown.  The
  timeout-over seems to become permanent for that replaces_id.

  Example program to follow

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: dbus 1.12.20-2ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Nov  3 16:49:18 2021
  InstallationDate: Installed on 2020-08-13 (447 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: dbus
  UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago)

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


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

[Touch-packages] [Bug 1949615] Re: Notify method not working correctly in 21.10 (impish)

[Gordon Lack]

This python program shows the problem

*=*=* Cut here *=*=*
#!/usr/bin/python3
# -*- coding: utf-8 -*-
#
from pydbus import SessionBus
from time import sleep

# Global constants
#
item= "org.freedesktop.Notifications"
path= "/org/freedesktop/Notifications"
interface   = "org.freedesktop.Notifications"
app_name= "NotifyTest"
icon= "/usr/share/icons/breeze/devices/64/camera-web.svg"
actions_list= []
hint= {}

bus = SessionBus()
notifications = bus.get('.Notifications')

# Global variables
#
our_notify_id = 0
timeout = 3000  # ms
wait4 = 0   # s
body = "from NotifyTest.py"

while wait4 < 6:
wait4 += 1
message = "The next wait will be %ss" % wait4

# This should replace any previous notification still there...
# (can do this with notify-send command, but doing it in python allows
# us to use a fixed id for replacement).
#
our_notify_id = notifications.Notify(app_name, our_notify_id, icon,
   message, body, actions_list, hint, timeout)
print("our_notify_id:", our_notify_id)

# At Ubuntu 21.10 we have to change this to get the new message seen...
#
#our_notify_id += 1
print(message)

sleep(wait4)

print("Done")
*=*=* Cut here *=*=*

On 21.04 after the sleep exceeds the 3s timeout a new info message box
is displayed.

On 21.10 after the sleep exceeds the 3s timeout nothing is shown.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1949615

Title:
  Notify method not working correctly in 21.10 (impish)

Status in dbus package in Ubuntu:
  New

Bug description:
  The replaces_id parameter to org.freedesktop.Notifications.Notify no longer 
works correctly at 21.10.
  It is OK on 21.04.

  At 21.10 if a message with replaces_id === x ever times out then any
  further message sent with that replaces_id never gets shown.  The
  timeout-over seems to become permanent for that replaces_id.

  Example program to follow

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: dbus 1.12.20-2ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Nov  3 16:49:18 2021
  InstallationDate: Installed on 2020-08-13 (447 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: dbus
  UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago)

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


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

[Touch-packages] [Bug 1949615] Re: Notify method not working correctly in 21.10 (impish)

[Gordon Lack]

** Description changed:

  The replaces_id parameter to org.freedesktop.Notifications.Notify no longer 
works correctly at 21.10.
  It is OK on 21.04.
  
- At 21.10 if a message with replaces_id === x ever times out then any
+ At 21.10 if a message with replaces_id == x ever times out then any
  further message sent with that replaces_id never gets shown.  The
  timeout-over seems to become permanent for that replaces_id.
  
  Example program to follow
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: dbus 1.12.20-2ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Nov  3 16:49:18 2021
  InstallationDate: Installed on 2020-08-13 (447 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: dbus
  UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1949615

Title:
  Notify method not working correctly in 21.10 (impish)

Status in dbus package in Ubuntu:
  New

Bug description:
  The replaces_id parameter to org.freedesktop.Notifications.Notify no longer 
works correctly at 21.10.
  It is OK on 21.04.

  At 21.10 if a message with replaces_id == x ever times out then any
  further message sent with that replaces_id never gets shown.  The
  timeout-over seems to become permanent for that replaces_id.

  Example program to follow

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: dbus 1.12.20-2ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Nov  3 16:49:18 2021
  InstallationDate: Installed on 2020-08-13 (447 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: dbus
  UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago)

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


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

[Touch-packages] [Bug 1941752]

[Gordon Lack]

Created attachment 144559
New crash information added by DrKonqi

gwenview (21.08.1) using Qt 5.15.2

- What I was doing when the application crashed:

Browsing through images with Dolphin. Select to open one in Gwenview.
Crashes every time.

-- Backtrace (Reduced):
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140466192913600) 
at pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=140466192913600) at 
pthread_kill.c:80
#6  __GI___pthread_kill (threadid=140466192913600, signo=signo@entry=6) at 
pthread_kill.c:91
#7  0x7fc0dafab476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#8  0x7fc0daf917b7 in __GI_abort () at abort.c:79

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1941752

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Unknown
Status in exiv2 package in Ubuntu:
  Confirmed
Status in gwenview package in Ubuntu:
  Confirmed

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching a crash report hinting that this is related to exiv2.

  Temporary workaround:
  If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so 
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.

  I don't know if the underlying cause is actually some bug in exiv2,
  Gwenview or darktable.

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libexiv2-27 0.27.3-3ubuntu1.5
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug 26 15:16:47 2021
  InstallationDate: Installed on 2021-08-26 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: exiv2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1941752]

[Gordon Lack]

(In reply to Gordon Lack from comment #21)

Seems to be related to how old the jpegs are.

2016 and earlier it crashes.
2017 and late its OK.
Roughly.

If I run gwenview on the command line for a failing one this is what I
see reported:


[gmllaptop]: gwenview DSCN1657.JPG 
org.kde.kdegraphics.gwenview.lib: Unresolved mime type  "image/x-mng"
org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type  "image/x-nikon-nrw"
org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type  
"image/x-samsung-srw"
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::at: __n (which is 19) >= this->size() (which is 19)
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = gwenview path = /usr/bin pid = 15230
KCrash: Arguments: /usr/bin/gwenview DSCN1657.JPG 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi

[1]+  Stopped gwenview DSCN1657.JPG
[gmllaptop]: fg
gwenview DSCN1657.JPG
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 18 and type 'Read', disabling...

;
^C
[gmllaptop]: fg
bash: fg: current: no such job
[gmllaptop]: gwenview DSCN1657.JPG 
org.kde.kdegraphics.gwenview.lib: Unresolved mime type  "image/x-mng"
org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type  "image/x-nikon-nrw"
org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type  
"image/x-samsung-srw"
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::at: __n (which is 19) >= this->size() (which is 19)
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = gwenview path = /usr/bin pid = 15230
KCrash: Arguments: /usr/bin/gwenview DSCN1657.JPG 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi

[1]+  Stopped gwenview DSCN1657.JPG
[gmllaptop]: fg
gwenview DSCN1657.JPG
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 18 and type 'Read', disabling...

;
^C
[gmllaptop]: fg
bash: fg: current: no such job


-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1941752

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Unknown
Status in exiv2 package in Ubuntu:
  Confirmed
Status in gwenview package in Ubuntu:
  Confirmed

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching a crash report hinting that this is related to exiv2.

  Temporary workaround:
  If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so 
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.

  I don't know if the underlying cause is actually some bug in exiv2,
  Gwenview or darktable.

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libexiv2-27 0.27.3-3ubuntu1.5
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug 26 15:16:47 2021
  InstallationDate: Installed on 2021-08-26 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: exiv2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1941752]

[Gordon Lack]

(In reply to Lukáš Karas from comment #24)
> Here is my proposed fix in Gwenview:
> https://invent.kde.org/graphics/gwenview/-/merge_requests/125

Do we need a prod on the libexiv2 package as well to indicate that it
needs an update to fix the cause of the crash? (The fix for gwenview to
handle such crashes better is welcome, but not sufficient).

I can't see any bug report with libexiv2 as the product.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1941752

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Fix Released
Status in exiv2 package in Ubuntu:
  Confirmed
Status in gwenview package in Ubuntu:
  Confirmed

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching a crash report hinting that this is related to exiv2.

  Temporary workaround:
  If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so 
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.

  I don't know if the underlying cause is actually some bug in exiv2,
  Gwenview or darktable.

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libexiv2-27 0.27.3-3ubuntu1.5
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug 26 15:16:47 2021
  InstallationDate: Installed on 2021-08-26 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: exiv2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2015513] [NEW] apt list --upgradeable does not show what can be upgraded!

[Gordon Lack]

Public bug reported:

Packages are now being released in Phased updates.

However, it seems that whereas apt (and apt-get, and even Discover?) are
aware of this, the command, "apt list --upgradeable" is unaware of it
and will report that there are upgradable packages which apt(-get)
upgrade will *not* in fact install.

This makes it impossible(?) to script update notifications, which are
needed as Plasma 5.27 no longer has an Updates entry in the System Tray
- see bug #2009761.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: apt 2.5.3
ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
ApportVersion: 2.23.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Fri Apr  7 00:19:33 2023
InstallationDate: Installed on 2022-05-04 (337 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
SourcePackage: apt
UpgradeStatus: Upgraded to kinetic on 2022-11-12 (145 days ago)
mtime.conffile..etc.cron.daily.apt-compat: 2022-05-04T17:22:10.420246

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


** Tags: amd64 apport-bug kinetic

** Attachment added: "Log of 3 consecutive apt commands showing the problem."
   https://bugs.launchpad.net/bugs/2015513/+attachment/5661768/+files/bug.log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2015513

Title:
  apt list --upgradeable does not show what can be upgraded!

Status in apt package in Ubuntu:
  New

Bug description:
  Packages are now being released in Phased updates.

  However, it seems that whereas apt (and apt-get, and even Discover?)
  are aware of this, the command, "apt list --upgradeable" is unaware of
  it and will report that there are upgradable packages which apt(-get)
  upgrade will *not* in fact install.

  This makes it impossible(?) to script update notifications, which are
  needed as Plasma 5.27 no longer has an Updates entry in the System
  Tray - see bug #2009761.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apt 2.5.3
  ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Apr  7 00:19:33 2023
  InstallationDate: Installed on 2022-05-04 (337 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: apt
  UpgradeStatus: Upgraded to kinetic on 2022-11-12 (145 days ago)
  mtime.conffile..etc.cron.daily.apt-compat: 2022-05-04T17:22:10.420246

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


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

[Touch-packages] [Bug 2015513] Re: apt list --upgradeable does not show what can be upgraded!

[Gordon Lack]

Doesn't alter the point that if "apt --list --uprgadeable" doesn't
report what "apt update" would update then it makes it impossible to
script a check for whether there is anything to update.

And given that KDE no longer has any update warning in the System Tray
such a facility is needed, otherwise you'll never know that *any* update
is pending.

Since "apt update" is able to decide *not* to update a package it should
be possible for "apt --list --uprgadeable" to *not* report that it is
upgradeable.

As for phasing, "aptitude safe-upgrade" totally ignores it all anyway.
(Perhaps that's a bug?).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2015513

Title:
  apt list --upgradeable does not show what can be upgraded!

Status in apt package in Ubuntu:
  Opinion

Bug description:
  Packages are now being released in Phased updates.

  However, it seems that whereas apt (and apt-get, and even Discover?)
  are aware of this, the command, "apt list --upgradeable" is unaware of
  it and will report that there are upgradable packages which apt(-get)
  upgrade will *not* in fact install.

  This makes it impossible(?) to script update notifications, which are
  needed as Plasma 5.27 no longer has an Updates entry in the System
  Tray - see bug #2009761.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apt 2.5.3
  ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Apr  7 00:19:33 2023
  InstallationDate: Installed on 2022-05-04 (337 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: apt
  UpgradeStatus: Upgraded to kinetic on 2022-11-12 (145 days ago)
  mtime.conffile..etc.cron.daily.apt-compat: 2022-05-04T17:22:10.420246

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


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

[Touch-packages] [Bug 1998872] Re: unattended-updates failing in kinetic as AC power detection is bugged

[Gordon Lack]

I've tested /lib/systemd/systemd-ac-power on my laptop (which gives 0/1
for mains/battery) and it now returns 0 (mains) for my NUC10i3FNYHN.

(But the fix isn't in Lunar for on_ac_power.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1998872

Title:
  unattended-updates failing in kinetic as AC power detection is bugged

Status in e2fsprogs package in Ubuntu:
  New
Status in logrotate package in Ubuntu:
  New
Status in man-db package in Ubuntu:
  New
Status in plocate package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  New
Status in e2fsprogs source package in Kinetic:
  New
Status in logrotate source package in Kinetic:
  New
Status in man-db source package in Kinetic:
  New
Status in plocate source package in Kinetic:
  New
Status in systemd source package in Kinetic:
  Won't Fix
Status in unattended-upgrades source package in Kinetic:
  New

Bug description:
  The ConditionACPower testing code does not work correctly on some
  systems. This prevents the unattended-updates systemd service running
  as it thinks that a system (a NUC10i3FNYHN) is running on battery. It
  isn't - it just has  a power supply that can *provide* power over USB.

  This (unattended-updrades) was OK in Jammy, but started to fail when I
  upgraded to Kinetic.

  (A systemd override file for apt-daily-upgrade.service to remove the
  condition gets the service working again.)

  The problem is similar (or perhaps identical) to the problem with the
  on_ac_power script (from the powermgmt-base package).

  That has been reported in bug #1980991.  There are more details there.

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


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

[Touch-packages] [Bug 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status

[Gordon Lack]

/lib/systemd/systemd-ac-power works (on lunar). on_ac_power still does
not.

Perhaps on_ac_power should just be made a symlink to this - or the
script should exec that systemd executable if it exists?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu.
https://bugs.launchpad.net/bugs/1980991

Title:
  /usr/sbin/on_ac_power incorrectly reporting ac power status

Status in powermgmt-base package in Ubuntu:
  Triaged
Status in powermgmt-base source package in Kinetic:
  Triaged

Bug description:
  Good afternoon, folks.

  I believe I discovered a bug in the /usr/sbin/on_ac_power script. I
  have a Dell OptiPlex 5090 host that has an entry in
  /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe
  this is the USB-C power delivery port on the front of the chassis. The
  issue I'm encountering is that /usr/sbin/on_ac_power is exiting with
  code 1 which states: (1 (false) if not on AC power) when that isn't
  the case.

  This looks to be because of the ucsi-source-psy-USBC000:001 entry
  reporting the "online" status as 0, presumably because nothing is
  currently connected to that USB-C port.

  This causes /usr/sbin/on_ac_power to incorrectly report that the
  machine isn't connected to AC power and causes other utilities like
  unattended-upgrades to quit when using the default configuration since
  it believes the machine isn't connected to AC power.

  There is a workaround with unattended-upgrades where you can specify
  it to run regardless of if AC power is connected, but as more and more
  chassis implement power-delivery USB-C ports I foresee this becoming
  more of an issue.

  I'm not sure if it's anything to look into, but I figured I would
  share my findings. Please let me know if you have any questions or if
  I can provide any additional information, troubleshooting, or testing.

  Thanks!
  -Kevin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+subscriptions


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

[Touch-packages] [Bug 1759846] Re: Incorrect test used for anacron being active

[Gordon Lack]

This is *still* an issue nearly a year on.

A better test line is actually this, which checks for anacron being
present before checking whether it is enabled:

( test -x /usr/sbin/anacron && systemctl -q is-enabled anacron )

The () are needed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1759846

Title:
  Incorrect test used for anacron being active

Status in cron package in Ubuntu:
  New

Bug description:
  /etc/crontab uses

 test -x /usr/sbin/anacron

  for whether anacron is handling the daily/weekly/monthly cron jobs on a 
system.
  This means that if anacron is installed it is assumed to be running.
  However, this is a service, and can be disabled and since the package is 
installed by default it's simpler to just disable it on systems where you don't 
want it running rather then remove it.

  Changing the test to be:

  systemctl --no-pager is-enabled anacron 2>/dev/null

  (and changing the || to be &&, since the login is now reversed) caters
  for either case by checking what you really wish to know - is it
  active, not just installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cron 3.0pl1-128ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Mar 29 13:33:47 2018
  InstallationDate: Installed on 2017-11-01 (147 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

[Gordon Lack]

I had a problem with a *missing* internal microphone today (well, I spotted it 
today - probably been like this for ages...).
Note that this was PulseAudio saying that there were no input devices.

The problem (as I eventually spotted) was that I'd set the Profile to be
Analgue Stereo Output (under Configuration in PA Volume Control).

Setting this to Analogue Stereo Duplex made the internal mic show up.

Might not be the problem for most people, but you never know.
I did notice that if I plugged in an *external* mic the Profile switched to 
Duplex automatically.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1523100

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+subscriptions

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

[Touch-packages] [Bug 1807286] Re: systemd SEGV freezing on install of virtualbox

[Gordon Lack]

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1807286

Title:
  systemd SEGV freezing on install of virtualbox

Status in systemd package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  most of the information has been reported at VBox here:
  https://forums.virtualbox.org/viewtopic.php?f=7&t=90643

  when installing VBox this happens:
  _
  sudo ./VirtualBox-5.2.23-126798-Linux_amd64.run
  [sudo] password for kinghat: 
  Verifying archive integrity... All good.
  Uncompressing VirtualBox for Linux installation.
  VirtualBox Version 5.2.23 r126798 (2018-11-20T16:12:47Z) installer
  Installing VirtualBox to /opt/VirtualBox
  Python found: python, installing bindings...

  Broadcast message from systemd-journald@kinghat-kubuntu (Thu
  2018-12-06 16:33:50 CST):

  systemd[1]: Caught , dumped core as pid 5201.

  
  Broadcast message from systemd-journald@kinghat-kubuntu (Thu 2018-12-06 
16:33:50 CST):

  systemd[1]: Freezing execution.

  Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': 
timed out (service_start_timeout=25000ms)
  Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': 
timed out (service_start_timeout=25000ms)
  Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': 
timed out (service_start_timeout=25000ms)
  Failed to enable unit: Connection timed out
  Failed to start vboxdrv.service: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
  See system logs and 'systemctl status vboxdrv.service' for details.
  Failed to start vboxballoonctrl-service.service: Connection timed out
  See system logs and 'systemctl status vboxballoonctrl-service.service' for 
details.
  Failed to start vboxautostart-service.service: Connection timed out
  See system logs and 'systemctl status vboxautostart-service.service' for 
details.
  Failed to start vboxweb-service.service: Connection timed out
  See system logs and 'systemctl status vboxweb-service.service' for details.

  VirtualBox has been installed successfully.

  You will find useful information about using VirtualBox in the user manual
/opt/VirtualBox/UserManual.pdf
  and in the user FAQ
http://www.virtualbox.org/wiki/User_FAQ

  We hope that you enjoy using VirtualBox.
  _

  VB then starts fine. after reboot none of the VMs fail to launch. ive
  had weird install issues with VBox on 18.10 for many months.

  Description:Ubuntu 18.10
  Release:18.10

  VirtualBox-5.2.23-126798-Linux_amd64.run

  http://paste.debian.net/hidden/ee22b12a/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: virtualbox (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Dec  6 17:21:15 2018
  InstallationDate: Installed on 2018-08-20 (108 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: virtualbox
  UpgradeStatus: Upgraded to cosmic on 2018-10-10 (57 days ago)

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

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

[Touch-packages] [Bug 1790613] Re: Regression: packagekit crashes updating itself to a new version

[Gordon Lack]

>> I don't think there is a solution for this problem.

So why has it only started to happen recently?

What about treating it like a kernel update - don't restart the process
but schedule/request a reboot?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1790613

Title:
  Regression: packagekit crashes updating itself to a new version

Status in packagekit package in Ubuntu:
  Triaged
Status in plasma-discover package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Triaged
Status in plasma-discover source package in Bionic:
  Confirmed

Bug description:
  Bionic: 18.04
  Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1

  Updating with pkcon upgrade or plasma-discover crashes packagekit mid
  transaction, requiring user intervention on the command line.

  In plasma-discover the gui reports the crash briefly, but then stalls
  in apparent mid update, requiring the user to force close it and again
  resolve the issue on the command line.

  Example transactions:

  $ pkcon update
  Getting updates   [=] 
  Finished  [=] 
  Loading cache [=] 
  Testing changes   [=] 
  Finished  [ ] (0%)  
  The following packages have to be updated:
   gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection 
data for the PackageKit GLib library
   libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing 
PackageKit using GLib
   packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management 
service
   packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64  Provides PackageKit 
command-line tools
  Proceed with changes? [N/y] y

[=] 
  Updating packages [=] 
  Waiting for authentication[=] 
  Loading cache [=] 
  Running   [=] 
  Installing packages   [ ] (80%)  The daemon 
crashed mid-transaction!

  $ sudo apt-get upgrade 
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  and obviously after that doing anything meaningful with packagekit
  like installing a package fails

  $pkcon install kaffeine
  Resolving [=] 
  Testing changes   [=] 
  Finished  [ ] (0%)  
  The following packages have to be installed:
   kaffeine-2.0.14-1.amd64versatile media player for KDE
  Proceed with changes? [N/y] y

[=] 
  Installing[=] 
  Waiting for authentication[=] 
  Waiting for package manager lock[=] 
  Finished  [=] 
  Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure 
-a' to correct the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-26 (69 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Package: packagekit 1.1.9-1ubuntu2.18.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1790613] Re: Regression: packagekit crashes updating itself to a new version

[Gordon Lack]

Has it been fixed in/checked for 18.10 (Cosmic)?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1790613

Title:
  Regression: packagekit crashes updating itself to a new version

Status in packagekit package in Ubuntu:
  Fix Released
Status in plasma-discover package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Fix Released
Status in plasma-discover source package in Bionic:
  Confirmed

Bug description:
  [Impact]
  Bionic: 18.04
  Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1

  Updating with pkcon upgrade or plasma-discover crashes packagekit mid
  transaction, requiring user intervention on the command line.

  In plasma-discover the gui reports the crash briefly, but then stalls
  in apparent mid update, requiring the user to force close it and again
  resolve the issue on the command line.

  Example transactions:

  $ pkcon update
  Getting updates   [=]
  Finished  [=]
  Loading cache [=]
  Testing changes   [=]
  Finished  [ ] (0%)
  The following packages have to be updated:
   gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection 
data for the PackageKit GLib library
   libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing 
PackageKit using GLib
   packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management 
service
   packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64  Provides PackageKit 
command-line tools
  Proceed with changes? [N/y] y

    [=]
  Updating packages [=]
  Waiting for authentication[=]
  Loading cache [=]
  Running   [=]
  Installing packages   [ ] (80%)  The daemon 
crashed mid-transaction!

  $ sudo apt-get upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  and obviously after that doing anything meaningful with packagekit
  like installing a package fails

  $pkcon install kaffeine
  Resolving [=]
  Testing changes   [=]
  Finished  [ ] (0%)
  The following packages have to be installed:
   kaffeine-2.0.14-1.amd64versatile media player for KDE
  Proceed with changes? [N/y] y

    [=]
  Installing[=]
  Waiting for authentication[=]
  Waiting for package manager lock[=]
  Finished  [=]
  Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure 
-a' to correct the problem.

  [Test case]
  Upgrade packagekit using pkcon, make sure it does not "crash".

  [Regression potential]
  It could only lead to old packagekitd processes not restarting. packagekit 
will still be told to restart itself like before, the restart being added was 
unintended.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-26 (69 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Package: packagekit 1.1.9-1ubuntu2.18.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1878519] [NEW] Unable to use TLSv1.1 to connect to external servers

[Gordon Lack]

Public bug reported:

I'm on 20.04 LTS (Focal Fossa). (Kubuntu)

openssl (I'm on 1.1.1f-1ubuntu2) appears to now be set to use a minimum
of TLSv1.2

This is despite the fact that the Changelog 
(https://launchpad.net/ubuntu/+source/openssl/+changelog) says:
  Revert "Enable system default config to enforce TLS1.2 as a
  minimum" & "Increase default security level from 1 to 2".

As a result of this I can't get fetchmail to connect to an external IMPA
server I use, which only uses TLSv1.1

I *can* get:
  openssl s_client -state -cipher "DEFAULT:@SECLEVEL=1" -connect ... -starttls 
imap
to open a connexion, but I can find no way of getting that option into a 
configuration file such that it is used.

Consequently I cannot use a secure connexion to retrieve my emails.

All was fine in 19.10.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1878519

Title:
  Unable to use TLSv1.1 to connect to external servers

Status in openssl package in Ubuntu:
  New

Bug description:
  I'm on 20.04 LTS (Focal Fossa). (Kubuntu)

  openssl (I'm on 1.1.1f-1ubuntu2) appears to now be set to use a
  minimum of TLSv1.2

  This is despite the fact that the Changelog 
(https://launchpad.net/ubuntu/+source/openssl/+changelog) says:
Revert "Enable system default config to enforce TLS1.2 as a
minimum" & "Increase default security level from 1 to 2".

  As a result of this I can't get fetchmail to connect to an external
  IMPA server I use, which only uses TLSv1.1

  I *can* get:
openssl s_client -state -cipher "DEFAULT:@SECLEVEL=1" -connect ... 
-starttls imap
  to open a connexion, but I can find no way of getting that option into a 
configuration file such that it is used.

  Consequently I cannot use a secure connexion to retrieve my emails.

  All was fine in 19.10.

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

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

[Touch-packages] [Bug 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox

[Gordon Lack]

>> You can override this via command-line, a system config file, or a
local config file + environment variable pointing to it.

Some hints as to how to achieve that "local config file + environment variable" 
would be extremely useful.
I've tried it and got nowhere, although I know that setting SECLEVEL=1 would 
fix my immediate problem, as I can set it on a command line for openssl 
s_client.

See: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1878519

Forcing a minimum SECLEVEL of 2 by default is fine, but there has to be
some-way of letting users reduce this when they are talking to external
services, or providing services for external clients that cannot, for
some reason,change at the moment.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689

Title:
  openssl in 20.04 can't connect to site that was fine in 19.10 and is
  fine in Chrome and Firefox

Status in OpenSSL:
  Unknown
Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
  openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
  connect to.

  Reproduce with: `curl -v https://www.toodledo.com/'

  or: `openssl s_client -connect www.toodledo.com:443`

  or: `python3 -c 'import requests;
  requests.get("https://www.toodledo.com/";)'`

  or: `wget https://www.toodledo.com/`

  These worked in Ubuntu 19.10 and don't work in 20.04.

  I've tried all sorts of things to debug this further and I've just run
  into walls. I hope someone who understands more about this stuff will
  be able to figure it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1d-2ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 25 13:01:22 2020
  InstallationDate: Installed on 2019-08-16 (192 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)

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

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

[Touch-packages] [Bug 1733070] Re: ntp apparmor profile problem

[Gordon Lack]

It's not new. This has been reported before.
See:
   https://bugs.launchpad.net/mos/+bug/1475019

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1733070

Title:
  ntp apparmor profile problem

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  the apparmor logs shows a couple of problems:

  Nov 18 13:07:45 carol kernel: [107615.254389] audit: type=1400
  audit(1511010465.396:304): apparmor="DENIED" operation="sendmsg"
  info="Failed name lookup - disconnected path" error=-13
  profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=16818
  comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  
  and

  Nov 18 13:07:45 carol kernel: [107615.253441] audit: type=1400
  audit(1511010465.395:300): apparmor="DENIED" operation="open"
  profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=16815 comm="ntpd"
  requested_mask="r" denied_mask="r" fsuid=0 ouid=0


  I fixed these by amending /etc/apparmor.d/usr.sbin.ntpd...

  change the opening to this:
/usr/sbin/ntpd flags=(attach_disconnected) {

  
  add these:
# syslog
/run/systemd/journal/dev-log w,

# not sure why it needs this
/usr/local/bin/ r,

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

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

[Touch-packages] [Bug 1733070] Re: ntp apparmor profile problem

[Gordon Lack]

Oh, and there is also:
   https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202
with a proposed fix from a few a days ago, at least for some of this.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1733070

Title:
  ntp apparmor profile problem

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  the apparmor logs shows a couple of problems:

  Nov 18 13:07:45 carol kernel: [107615.254389] audit: type=1400
  audit(1511010465.396:304): apparmor="DENIED" operation="sendmsg"
  info="Failed name lookup - disconnected path" error=-13
  profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=16818
  comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  
  and

  Nov 18 13:07:45 carol kernel: [107615.253441] audit: type=1400
  audit(1511010465.395:300): apparmor="DENIED" operation="open"
  profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=16815 comm="ntpd"
  requested_mask="r" denied_mask="r" fsuid=0 ouid=0


  I fixed these by amending /etc/apparmor.d/usr.sbin.ntpd...

  change the opening to this:
/usr/sbin/ntpd flags=(attach_disconnected) {

  
  add these:
# syslog
/run/systemd/journal/dev-log w,

# not sure why it needs this
/usr/local/bin/ r,

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

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

[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

[Gordon Lack]

This isn't a 17.10 regression - it's been happening for a few years,
e.g.:

https://bugs.launchpad.net/mos/+bug/1475019

And, FWIW, I added the flags=(attach_disconnected) to the config file
yesterday on one of my systems and whereas it does seem to have removed
the operation="sendmsg" reports, I still get this at boot time:

Dec 28 14:15:53 parent kernel: [   24.127330] audit: type=1400 
audit(1514470553.526:18): apparmor="DENIED" operation="open" 
profile="/usr/sbin/ntpd" name="/usr/local/sbin/" pid=1086 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Dec 28 14:15:53 parent kernel: [   24.127335] audit: type=1400 
audit(1514470553.527:19): apparmor="DENIED" operation="open" 
profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=1086 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1727202

Title:
  [17.10 regression] AppArmor ntp denial: Failed name lookup -
  disconnected path

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Artful:
  Fix Committed
Status in ntp source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * NTP has new isolation features which makes it trigger apparmor issues.
   * Those apparmor issues not only clutter the log and make other things
     less readable, they also prevent ntp from reporting its actual
     messages.
   * Fix is opening the apparmor profile to follow ntp through the
     disconnect by the isolation feature.

  [Test Case]

   * This is hard to trigger, but then also not. Which means it is not
     entirely sorted out when it triggers and when not, but the following
     does trigger it in tests of Pitti and also mine (while at the same time
     sometimes it does not - mabye I had other guests or kvm instead of lxd)

   * First install ntp in Artful (or above unless fixed)
     * Install ntp and check demsg for denies
     * Once an issue triggers instead of the error in syslog you'll see the
   apparmor Deny like:
     apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
     disconnected path" error=-13 profile="/usr/sbin/ntpd"
     name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
     requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  [Regression Potential]

   * We are slightly opening up the apparmor profile which is far lower risk
     than adding more constraints. So safe from that POV.

   * OTOH one could think this might be a security issue, but in fact this
     isn't a new suggestion if you take a look at [1] with an ack by Seth of
     the Security Team.

  [Other Info]

   * n/a

  [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html

  

  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1759846] [NEW] Incorrect test used for anacron being active

[Gordon Lack]

Public bug reported:

/etc/crontab uses

   test -x /usr/sbin/anacron

for whether anacron is handling the daily/weekly/monthly cron jobs on a system.
This means that if anacron is installed it is assumed to be running.
However, this is a service, and can be disabled and since the package is 
installed by default it's simpler to just disable it on systems where you don't 
want it running rather then remove it.

Changing the test to be:

systemctl --no-pager is-enabled anacron 2>/dev/null

(and changing the || to be &&, since the login is now reversed) caters
for either case by checking what you really wish to know - is it active,
not just installed.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: cron 3.0pl1-128ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Mar 29 13:33:47 2018
InstallationDate: Installed on 2017-11-01 (147 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
SourcePackage: cron
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1759846

Title:
  Incorrect test used for anacron being active

Status in cron package in Ubuntu:
  New

Bug description:
  /etc/crontab uses

 test -x /usr/sbin/anacron

  for whether anacron is handling the daily/weekly/monthly cron jobs on a 
system.
  This means that if anacron is installed it is assumed to be running.
  However, this is a service, and can be disabled and since the package is 
installed by default it's simpler to just disable it on systems where you don't 
want it running rather then remove it.

  Changing the test to be:

  systemctl --no-pager is-enabled anacron 2>/dev/null

  (and changing the || to be &&, since the login is now reversed) caters
  for either case by checking what you really wish to know - is it
  active, not just installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cron 3.0pl1-128ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Mar 29 13:33:47 2018
  InstallationDate: Installed on 2017-11-01 (147 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1759846] Re: Incorrect test used for anacron being active

[Gordon Lack]

Actually
systemctl -q is-enabled anacron 2>/dev/null
works to, and is shorter (and more intuitive).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1759846

Title:
  Incorrect test used for anacron being active

Status in cron package in Ubuntu:
  New

Bug description:
  /etc/crontab uses

 test -x /usr/sbin/anacron

  for whether anacron is handling the daily/weekly/monthly cron jobs on a 
system.
  This means that if anacron is installed it is assumed to be running.
  However, this is a service, and can be disabled and since the package is 
installed by default it's simpler to just disable it on systems where you don't 
want it running rather then remove it.

  Changing the test to be:

  systemctl --no-pager is-enabled anacron 2>/dev/null

  (and changing the || to be &&, since the login is now reversed) caters
  for either case by checking what you really wish to know - is it
  active, not just installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cron 3.0pl1-128ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Mar 29 13:33:47 2018
  InstallationDate: Installed on 2017-11-01 (147 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 73398] Re: crontab in /var/spool/cron/crontabs are stored by username

[Gordon Lack]

> A lot of the time, people's login name gets renamed from a central
authority...

Another solution would be to get that policy changed, as it's not a good one.
Such a policy would be a nightmare in any industry that has to track who does 
what for regulatory purposes, where user ids should be constant and unique to 
an individual.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/73398

Title:
  crontab in /var/spool/cron/crontabs are stored by username

Status in cron package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cron

  File in /var/spool/cron/crontabs are created with the name of the user
  who owns it when running 'crontab -e'. Their permissions are set
  properly. However, when a user is renamed, his access to these files
  is not properly preserved by the cron system.

  There are two solutions:

  a) name the files with an assigned immutable identifier, specifically the 
POSIX uid
  b) open and locate files by enumerating the owner permission

  Either solution solves the problem. Solution (a) is easier to code and
  leads to less overall confusion on the users (why is foo a file for
  foo2, and foo a file for bar?).

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

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

[Touch-packages] [Bug 1766932] [NEW] packagekit daemon crashed from Discover. Requires a manual 'dpkg --configure -a' to correct.

[Gordon Lack]

Public bug reported:

The packagekit package has just been updated by discover (Kubuntu) from 1.1.7-1 
to 1.1.7-1ubuntu0.1.
Discover reported that the packagekit daemon had crashed.

The resulting dpkg status is:

[parent]: dpkg-query -l 'packagekit*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
iF  packagekit 1.1.7-1ubunt amd64Provides a package management ser
un  packagekit-bac   (no description available)
un  packagekit-bac   (no description available)
un  packagekit-bac   (no description available)
un  packagekit-off   (no description available)
un  packagekit-plu   (no description available)
iU  packagekit-too 1.1.7-1ubunt amd64Provides PackageKit command-line 

and apt-get upgrade reports:

root@parent:~# apt-get upgrade
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct 
the problem. 

Running that command does tidy things up, but the daemon should not
crash.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: packagekit 1.1.7-1ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Apr 25 17:47:49 2018
InstallationDate: Installed on 2017-11-19 (157 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
SourcePackage: packagekit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1766932

Title:
  packagekit daemon crashed from Discover. Requires a manual 'dpkg
  --configure -a' to correct.

Status in packagekit package in Ubuntu:
  New

Bug description:
  The packagekit package has just been updated by discover (Kubuntu) from 
1.1.7-1 to 1.1.7-1ubuntu0.1.
  Discover reported that the packagekit daemon had crashed.

  The resulting dpkg status is:

  [parent]: dpkg-query -l 'packagekit*'
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  iF  packagekit 1.1.7-1ubunt amd64Provides a package management ser
  un  packagekit-bac   (no description available)
  un  packagekit-bac   (no description available)
  un  packagekit-bac   (no description available)
  un  packagekit-off   (no description available)
  un  packagekit-plu   (no description available)
  iU  packagekit-too 1.1.7-1ubunt amd64Provides PackageKit command-line 

  and apt-get upgrade reports:

  root@parent:~# apt-get upgrade
  E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to 
correct the problem. 

  Running that command does tidy things up, but the daemon should not
  crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: packagekit 1.1.7-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 25 17:47:49 2018
  InstallationDate: Installed on 2017-11-19 (157 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 688148] Re: Unexpected behaviour when choosing "Other problem"

[Gordon Lack]

This is still a bug in 18.04 (and was in 17.10 as well).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/688148

Title:
  Unexpected behaviour when choosing "Other problem"

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: apport

  Using Kubuntu 10.04, tested both on a real machine and in a VirtualBox.
  After executing "ubuntu-bug" without any arguments, I was prompted for:
"What kind of problem do you want to report?".
  When choosing "Other problem", I got a dialog titled
"What display problem do you observe?"
  (see attached screenshot) or sometimes:
"What other problem do you observe?"
  Remember, I'd choosed: "Other problem"
  -> In Kubuntu 10.04 I'd got the Dialog "What particular problem do you 
observe?"
  Now I click to "Cancel" and the application ubuntu-bug (or apport?) hangs 
until I kill it down.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: apport 1.14.1-0ubuntu8
  ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
  Uname: Linux 2.6.35-23-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Thu Dec  9 17:33:59 2010
  ExecutablePath: /usr/bin/apport-bug
  InterpreterPath: /bin/dash
  PackageArchitecture: all
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   LANGUAGE=
  SourcePackage: apport

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

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

[Touch-packages] [Bug 1766932] Re: packagekit daemon crashed from Discover. Requires a manual 'dpkg --configure -a' to correct.

[Gordon Lack]

Happened again last night when:

gir1.2-packagekitglib-1.0
libpackagekit-glib2-18
packagekit
packagekit-tools

went from 1.1.9-1ubuntu2 to 1.1.9-1ubuntu2.18.04.1.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1766932

Title:
  packagekit daemon crashed from Discover. Requires a manual 'dpkg
  --configure -a' to correct.

Status in packagekit package in Ubuntu:
  Confirmed

Bug description:
  The packagekit package has just been updated by discover (Kubuntu) from 
1.1.7-1 to 1.1.7-1ubuntu0.1.
  Discover reported that the packagekit daemon had crashed.

  The resulting dpkg status is:

  [parent]: dpkg-query -l 'packagekit*'
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  iF  packagekit 1.1.7-1ubunt amd64Provides a package management ser
  un  packagekit-bac   (no description available)
  un  packagekit-bac   (no description available)
  un  packagekit-bac   (no description available)
  un  packagekit-off   (no description available)
  un  packagekit-plu   (no description available)
  iU  packagekit-too 1.1.7-1ubunt amd64Provides PackageKit command-line 

  and apt-get upgrade reports:

  root@parent:~# apt-get upgrade
  E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to 
correct the problem. 

  Running that command does tidy things up, but the daemon should not
  crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: packagekit 1.1.7-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 25 17:47:49 2018
  InstallationDate: Installed on 2017-11-19 (157 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1949615] Re: Notify method not working correctly in 21.10 (impish)

[Gordon Lack]

This is still an issue in 23.04 (lunar)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1949615

Title:
  Notify method not working correctly in 21.10 (impish)

Status in dbus package in Ubuntu:
  New

Bug description:
  The replaces_id parameter to org.freedesktop.Notifications.Notify no longer 
works correctly at 21.10.
  It is OK on 21.04.

  At 21.10 if a message with replaces_id == x ever times out then any
  further message sent with that replaces_id never gets shown.  The
  timeout-over seems to become permanent for that replaces_id.

  Example program to follow

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: dbus 1.12.20-2ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Nov  3 16:49:18 2021
  InstallationDate: Installed on 2020-08-13 (447 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: dbus
  UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago)

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


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