[Touch-packages] [Bug 1832967] [NEW] /etc/resolv.conf does not include the local domain name
Public bug reported: When I rebooted my system after an update, `/etc/resolv.conf` was symlinked to `/run/resolvconf/resolv.conf`. That file did not have my local domain name in the search even though it is supplied by the dhcp server. The systemd resolv.conf file (in `/run/systemd/resolve/resolv.conf`) had the correct search information. Please ensure that the search is correctly added. This is also described here: https://askubuntu.com/a/1041631/326601 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 15 22:18:05 2019 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: Upgraded to bionic on 2018-08-21 (299 days ago) ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1832967 Title: /etc/resolv.conf does not include the local domain name Status in resolvconf package in Ubuntu: New Bug description: When I rebooted my system after an update, `/etc/resolv.conf` was symlinked to `/run/resolvconf/resolv.conf`. That file did not have my local domain name in the search even though it is supplied by the dhcp server. The systemd resolv.conf file (in `/run/systemd/resolve/resolv.conf`) had the correct search information. Please ensure that the search is correctly added. This is also described here: https://askubuntu.com/a/1041631/326601 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 15 22:18:05 2019 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: Upgraded to bionic on 2018-08-21 (299 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1832967/+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 1832933] Re: upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 breaks ejabbrd
** Description changed: Hello! After upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 openssl 1.1.1-1ubuntu2.1~18.04.2 on Ubuntu 18.04 server clients can't connect to ejabberd server: 2019-06-15 15:56:26.431 [warning] <0.858.0>@ejabberd_c2s:process_terminated:290 (tls|<0.858.0>) Failed to secure c2s connection: TLS failed: client renegotiations forbidden - ejabberd version is18.01-2 which is from Ubuntu 18.04. - As far as I know ejabberd can work with openssl 1.1.1 only from 18.09 + As far as I know ejabberd can work with openssl 1.1.1 only from 18.09 https://blog.process-one.net/ejabberd-18-09/ OpenSSL 1.1.1 support Either ejabberd in 18.04 should be updated or openssl should not be upgraded to 1.1.1 on 18.04 . Thank you! + + + == erlang-p1-tls == + + Looking at all upstream patches since 1.0.20 (current bionic) these are + the useful ones: + + 0002-Specify-accepted-Client-CAs-during-handshake.patch + - quite small fixes Client CA negotiation + + 0013-Update-cert-used-by-test-to-use-sha256-signature.patch + - updates test cert to a stronger one + + 0014-Add-no_tlsv1_3-option-parsing-from-openssl1.1.patch + - tiny, andd "no_tlsv1_3" option + + 0016-Improve-tests-to-make-them-work-with-openssl1.1.patch + - testsuite fixes + + 0022-Use-SSL_OP_NO_RENEGOTIATION-when-available.patch + - needed to fix this bug, do not attempt renegotiation as that is no longer supported. Just ifdefs. + + + There are also patches that add new apis, to rebuild cert caches, and query negotiated protocols, but meh. ** Also affects: openssl (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ejabberd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: erlang-p1-tls (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: erlang-p1-tls (Ubuntu) Status: Confirmed => Fix Released ** No longer affects: openssl (Ubuntu Bionic) ** No longer affects: openssl (Ubuntu) ** No longer affects: ejabberd (Ubuntu Bionic) ** No longer affects: ejabberd (Ubuntu) ** Changed in: erlang-p1-tls (Ubuntu Bionic) Status: New => Confirmed -- 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/1832933 Title: upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 breaks ejabbrd Status in erlang-p1-tls package in Ubuntu: Fix Released Status in erlang-p1-tls source package in Bionic: Confirmed Bug description: Hello! After upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 openssl 1.1.1-1ubuntu2.1~18.04.2 on Ubuntu 18.04 server clients can't connect to ejabberd server: 2019-06-15 15:56:26.431 [warning] <0.858.0>@ejabberd_c2s:process_terminated:290 (tls|<0.858.0>) Failed to secure c2s connection: TLS failed: client renegotiations forbidden ejabberd version is18.01-2 which is from Ubuntu 18.04. As far as I know ejabberd can work with openssl 1.1.1 only from 18.09 https://blog.process-one.net/ejabberd-18-09/ OpenSSL 1.1.1 support Either ejabberd in 18.04 should be updated or openssl should not be upgraded to 1.1.1 on 18.04 . Thank you! == erlang-p1-tls == Looking at all upstream patches since 1.0.20 (current bionic) these are the useful ones: 0002-Specify-accepted-Client-CAs-during-handshake.patch - quite small fixes Client CA negotiation 0013-Update-cert-used-by-test-to-use-sha256-signature.patch - updates test cert to a stronger one 0014-Add-no_tlsv1_3-option-parsing-from-openssl1.1.patch - tiny, andd "no_tlsv1_3" option 0016-Improve-tests-to-make-them-work-with-openssl1.1.patch - testsuite fixes 0022-Use-SSL_OP_NO_RENEGOTIATION-when-available.patch - needed to fix this bug, do not attempt renegotiation as that is no longer supported. Just ifdefs. There are also patches that add new apis, to rebuild cert caches, and query negotiated protocols, but meh. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/erlang-p1-tls/+bug/1832933/+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 1832933] Re: upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 breaks ejabbrd
** Also affects: erlang-p1-tls (Ubuntu) Importance: Undecided Status: New ** Changed in: erlang-p1-tls (Ubuntu) Status: New => Confirmed -- 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/1832933 Title: upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 breaks ejabbrd Status in ejabberd package in Ubuntu: New Status in erlang-p1-tls package in Ubuntu: Confirmed Status in openssl package in Ubuntu: New Bug description: Hello! After upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 openssl 1.1.1-1ubuntu2.1~18.04.2 on Ubuntu 18.04 server clients can't connect to ejabberd server: 2019-06-15 15:56:26.431 [warning] <0.858.0>@ejabberd_c2s:process_terminated:290 (tls|<0.858.0>) Failed to secure c2s connection: TLS failed: client renegotiations forbidden ejabberd version is18.01-2 which is from Ubuntu 18.04. As far as I know ejabberd can work with openssl 1.1.1 only from 18.09 https://blog.process-one.net/ejabberd-18-09/ OpenSSL 1.1.1 support Either ejabberd in 18.04 should be updated or openssl should not be upgraded to 1.1.1 on 18.04 . Thank you! == erlang-p1-tls == Looking at all upstream patches since 1.0.20 (current bionic) these are the useful ones: 0002-Specify-accepted-Client-CAs-during-handshake.patch - quite small fixes Client CA negotiation 0013-Update-cert-used-by-test-to-use-sha256-signature.patch - updates test cert to a stronger one 0014-Add-no_tlsv1_3-option-parsing-from-openssl1.1.patch - tiny, andd "no_tlsv1_3" option 0016-Improve-tests-to-make-them-work-with-openssl1.1.patch - testsuite fixes 0022-Use-SSL_OP_NO_RENEGOTIATION-when-available.patch - needed to fix this bug, do not attempt renegotiation as that is no longer supported. Just ifdefs. There are also patches that add new apis, to rebuild cert caches, and query negotiated protocols, but meh. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1832933/+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 1759950] Re: Lid-close suspend: blank screen when switching to user session
Launchpad has imported 2 comments from the remote bug at https://bugzilla.xfce.org/show_bug.cgi?id=15151. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-02-20T17:25:46+00:00 Carlos Pita wrote: No matter how I configure xfce4 power manager lid close on battery/ac events, the ones configured in logind.conf win. If I set logind to ignore all lid events, nothing really happens, so that logind again wins (the ignore settings take precedence over xfce4 power manager). This is the ignore logind config: HandleLidSwitch=ignore HandleLidSwitchExternalPower=ignore LidSwitchIgnoreInhibited=no The LidSwitchIgnoreInhibited flag seems to be irrelevant, since both values result in the same behavior. This is my power manager config: ~:: xfconf-query -c xfce4-power-manager -vl /xfce4-power-manager/blank-on-battery 3 /xfce4-power-manager/brightness-on-battery 9 /xfce4-power-manager/brightness-switch 1 /xfce4-power-manager/brightness-switch-restore-on-exit 0 /xfce4-power-manager/critical-power-action 2 /xfce4-power-manager/critical-power-level 5 /xfce4-power-manager/dpms-on-battery-off9 /xfce4-power-manager/dpms-on-battery-sleep 6 /xfce4-power-manager/general-notification true /xfce4-power-manager/handle-brightness-keys false /xfce4-power-manager/inactivity-on-ac 15 /xfce4-power-manager/inactivity-on-battery 15 /xfce4-power-manager/lid-action-on-ac 3 /xfce4-power-manager/lid-action-on-battery 1 /xfce4-power-manager/logind-handle-lid-switch true /xfce4-power-manager/power-button-action2 Reply at: https://bugs.launchpad.net/ubuntu/+source/light- locker/+bug/1759950/comments/3 On 2019-02-20T18:06:48+00:00 Carlos Pita wrote: Btw, I tested this with mate-power-manager and it works straight out of the box, without even changing the default logind settings. Reply at: https://bugs.launchpad.net/ubuntu/+source/light- locker/+bug/1759950/comments/4 ** Changed in: xfce4-power-manager Status: Unknown => Confirmed ** Changed in: xfce4-power-manager Importance: Unknown => Medium -- 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/1759950 Title: Lid-close suspend: blank screen when switching to user session Status in Light-Locker: New Status in Xfce4 Power Manager: Confirmed Status in light-locker package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in xfce4-power-manager package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: I'm currently testing Xubuntu 18.04 after a do-release-upgrade from 16.04. I discovered a very weird issue. When doing S3 sleep via closing the lid, on resume the lock screen appears, I authenticate, but as soon as it switches to the user session the screen goes blank - not even a backlight. Switching to other ttys works and they display correctly but the GUI user session remains blank. If the system is manually suspended (not using the lid), then resumed either by opening the lid or pressing the power button, the GUI user session is fine. I narrowed it down to xfce4-power-manager and discovered disabling the lock-screen cured the issue. I cloned the repository and reviewed commits between 1.7 and 1.8. Fortunately there aren't many. Looking at 6365683 "Proper exit status for light-locker-command" I suspected the change in the SetActive return value, and reverted it. After a build/install cycle I've found the system now behaves correctly so I think the change should be reverted. I've created an issue upstream for this at https://github.com/the-cavalry/light-locker/issues/108 To manage notifications about this bug go to: https://bugs.launchpad.net/light-locker/+bug/1759950/+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 1832933] Re: upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 breaks ejabbrd
I wonder if https://github.com/processone/fast_tls/commit/9b25543cf1200e3b216996598771962461ea51c8 is enough to fix connectivity. Things to test: - ejabberd server works and accepts various clients - ejabberd clinet works and connects to various servers -- 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/1832933 Title: upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 breaks ejabbrd Status in ejabberd package in Ubuntu: New Status in openssl package in Ubuntu: New Bug description: Hello! After upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 openssl 1.1.1-1ubuntu2.1~18.04.2 on Ubuntu 18.04 server clients can't connect to ejabberd server: 2019-06-15 15:56:26.431 [warning] <0.858.0>@ejabberd_c2s:process_terminated:290 (tls|<0.858.0>) Failed to secure c2s connection: TLS failed: client renegotiations forbidden ejabberd version is18.01-2 which is from Ubuntu 18.04. As far as I know ejabberd can work with openssl 1.1.1 only from 18.09 https://blog.process-one.net/ejabberd-18-09/ OpenSSL 1.1.1 support Either ejabberd in 18.04 should be updated or openssl should not be upgraded to 1.1.1 on 18.04 . Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1832933/+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 1832933] Re: upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 breaks ejabbrd
** Also affects: ejabberd (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/1832933 Title: upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 breaks ejabbrd Status in ejabberd package in Ubuntu: New Status in openssl package in Ubuntu: New Bug description: Hello! After upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 openssl 1.1.1-1ubuntu2.1~18.04.2 on Ubuntu 18.04 server clients can't connect to ejabberd server: 2019-06-15 15:56:26.431 [warning] <0.858.0>@ejabberd_c2s:process_terminated:290 (tls|<0.858.0>) Failed to secure c2s connection: TLS failed: client renegotiations forbidden ejabberd version is18.01-2 which is from Ubuntu 18.04. As far as I know ejabberd can work with openssl 1.1.1 only from 18.09 https://blog.process-one.net/ejabberd-18-09/ OpenSSL 1.1.1 support Either ejabberd in 18.04 should be updated or openssl should not be upgraded to 1.1.1 on 18.04 . Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1832933/+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 1832964] [NEW] Suggested fix/enhancement for wireless-tools.if-pre-up script
Public bug reported:
I've been experiencing an issue with my wireless card and ifup relating
to this script. I have a fix for it and thought the devs here might be
interested.
This is the issue: If a setting fails to be applied, the script brings
the card up and then tries to apply the setting again. This is fine, but
it leaves the card up. Later on in the ifup process other scripts try to
access the card and if the card is up it will respond that it's busy and
ifup fails.
My solution has been to alter the wireless-tools if-pre-up script so
that it ends by running ifconfig down in this case. Here is the patch:
--- ./wireless-tools.if-pre-up 2017-04-22 10:15:05.0 -0400
+++ ./wireless-tools2019-06-03 22:39:24.314725863 -0400
@@ -6,7 +6,7 @@
exit 0
fi
-# check if this is a 802.11 device we're supposed to be effecting
+# check if this is a 802.11 device we're supposed to be affecting
case "${IF_WIRELESS:-enable}" in
wireless-tools|iwconfig)
# *we* and not some other 802.11 tool should be used
@@ -140,4 +140,5 @@
FAIL=
ifconfig "$IFACE" up
apply_settings
+ ifconfig "$IFACE" down
fi
** Affects: wireless-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wireless-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1832964
Title:
Suggested fix/enhancement for wireless-tools.if-pre-up script
Status in wireless-tools package in Ubuntu:
New
Bug description:
I've been experiencing an issue with my wireless card and ifup
relating to this script. I have a fix for it and thought the devs here
might be interested.
This is the issue: If a setting fails to be applied, the script brings
the card up and then tries to apply the setting again. This is fine,
but it leaves the card up. Later on in the ifup process other scripts
try to access the card and if the card is up it will respond that it's
busy and ifup fails.
My solution has been to alter the wireless-tools if-pre-up script so
that it ends by running ifconfig down in this case. Here is the patch:
--- ./wireless-tools.if-pre-up2017-04-22 10:15:05.0 -0400
+++ ./wireless-tools 2019-06-03 22:39:24.314725863 -0400
@@ -6,7 +6,7 @@
exit 0
fi
-# check if this is a 802.11 device we're supposed to be effecting
+# check if this is a 802.11 device we're supposed to be affecting
case "${IF_WIRELESS:-enable}" in
wireless-tools|iwconfig)
# *we* and not some other 802.11 tool should be used
@@ -140,4 +140,5 @@
FAIL=
ifconfig "$IFACE" up
apply_settings
+ ifconfig "$IFACE" down
fi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-tools/+bug/1832964/+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 1759950] Re: Lid-close suspend: blank screen when switching to user session
More search seems to point to a 2015 commit that integrated light-locker
into xfce4-power-manager. This patch in particular appears to attempt to
work with logind Lid handling too:
commit 10076da7caa49320b3e907d319a9f27ee6702969
Author: Sean Davis
Date: Sat Feb 7 11:49:31 2015 +0300
Light Locker Integration (Bug #11488)
Integrate Light Locker configuration into Xfce Power Manager. This
allows proper settings synchronization between the two applications
and eliminates some of the hackiness used in Light Locker Settings
to accomplish the same effect, and streamlines similar tools into
a single location. This depends on light-locker 1.5.1 configured
with the GSettings backend.
Signed-off-by: Eric Koegel
...
+/* Light Locker Integration */
+void
+xfpm_update_logind_handle_lid_switch (XfconfChannel *channel)
+{
+gboolean lock_on_suspend = xfconf_channel_get_bool (channel,
PROPERTIES_PREFIX LOCK_SCREEN_ON_SLEEP, TRUE);
+guint lid_switch_on_ac = xfconf_channel_get_uint (channel,
PROPERTIES_PREFIX LID_SWITCH_ON_AC_CFG, LID_TRIGGER_LOCK_SCREEN);
+guint lid_switch_on_battery = xfconf_channel_get_uint (channel,
PROPERTIES_PREFIX LID_SWITCH_ON_BATTERY_CFG, LID_TRIGGER_LOCK_SCRE
EN);
+
+// logind-handle-lid-switch = true when: lock_on_suspend == true and
(lid_switch_on_ac == suspend or lid_switch_on_battery == suspend)
+xfconf_channel_set_bool (channel, PROPERTIES_PREFIX
LOGIND_HANDLE_LID_SWITCH, lock_on_suspend && (lid_switch_on_ac == 1 ||
lid_switch_on_battery == 1));
+}
+/* END Light Locker Integration */
+
** Changed in: light-locker (Ubuntu)
Status: Invalid => Confirmed
** Also affects: xubuntu-default-settings (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/1759950
Title:
Lid-close suspend: blank screen when switching to user session
Status in Light-Locker:
New
Status in Xfce4 Power Manager:
Unknown
Status in light-locker package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in xfce4-power-manager package in Ubuntu:
Confirmed
Status in xubuntu-default-settings package in Ubuntu:
New
Bug description:
I'm currently testing Xubuntu 18.04 after a do-release-upgrade from
16.04.
I discovered a very weird issue. When doing S3 sleep via closing the
lid, on resume the lock screen appears, I authenticate, but as soon as
it switches to the user session the screen goes blank - not even a
backlight.
Switching to other ttys works and they display correctly but the GUI
user session remains blank.
If the system is manually suspended (not using the lid), then resumed
either by opening the lid or pressing the power button, the GUI user
session is fine.
I narrowed it down to xfce4-power-manager and discovered disabling the
lock-screen cured the issue.
I cloned the repository and reviewed commits between 1.7 and 1.8.
Fortunately there aren't many. Looking at 6365683 "Proper exit status
for light-locker-command" I suspected the change in the SetActive
return value, and reverted it.
After a build/install cycle I've found the system now behaves
correctly so I think the change should be reverted.
I've created an issue upstream for this at
https://github.com/the-cavalry/light-locker/issues/108
To manage notifications about this bug go to:
https://bugs.launchpad.net/light-locker/+bug/1759950/+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 1759950] Re: Lid-close suspend: blank screen when switching to user session
To check on current systemd-logind properties including these: $ loginctl -a show-session -- 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/1759950 Title: Lid-close suspend: blank screen when switching to user session Status in Light-Locker: New Status in Xfce4 Power Manager: Unknown Status in light-locker package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in xfce4-power-manager package in Ubuntu: Confirmed Bug description: I'm currently testing Xubuntu 18.04 after a do-release-upgrade from 16.04. I discovered a very weird issue. When doing S3 sleep via closing the lid, on resume the lock screen appears, I authenticate, but as soon as it switches to the user session the screen goes blank - not even a backlight. Switching to other ttys works and they display correctly but the GUI user session remains blank. If the system is manually suspended (not using the lid), then resumed either by opening the lid or pressing the power button, the GUI user session is fine. I narrowed it down to xfce4-power-manager and discovered disabling the lock-screen cured the issue. I cloned the repository and reviewed commits between 1.7 and 1.8. Fortunately there aren't many. Looking at 6365683 "Proper exit status for light-locker-command" I suspected the change in the SetActive return value, and reverted it. After a build/install cycle I've found the system now behaves correctly so I think the change should be reverted. I've created an issue upstream for this at https://github.com/the-cavalry/light-locker/issues/108 To manage notifications about this bug go to: https://bugs.launchpad.net/light-locker/+bug/1759950/+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 1759950] Re: Lid-close suspend: blank screen when switching to user session
** Bug watch added: Xfce Bugzilla #15151 https://bugzilla.xfce.org/show_bug.cgi?id=15151 ** Also affects: systemd via https://bugzilla.xfce.org/show_bug.cgi?id=15151 Importance: Unknown Status: Unknown ** Changed in: xfce4-power-manager (Ubuntu) Status: New => Confirmed ** Changed in: light-locker (Ubuntu) Status: Confirmed => Invalid ** Project changed: systemd => xfce4-power-manager -- 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/1759950 Title: Lid-close suspend: blank screen when switching to user session Status in Light-Locker: New Status in Xfce4 Power Manager: Unknown Status in light-locker package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in xfce4-power-manager package in Ubuntu: Confirmed Bug description: I'm currently testing Xubuntu 18.04 after a do-release-upgrade from 16.04. I discovered a very weird issue. When doing S3 sleep via closing the lid, on resume the lock screen appears, I authenticate, but as soon as it switches to the user session the screen goes blank - not even a backlight. Switching to other ttys works and they display correctly but the GUI user session remains blank. If the system is manually suspended (not using the lid), then resumed either by opening the lid or pressing the power button, the GUI user session is fine. I narrowed it down to xfce4-power-manager and discovered disabling the lock-screen cured the issue. I cloned the repository and reviewed commits between 1.7 and 1.8. Fortunately there aren't many. Looking at 6365683 "Proper exit status for light-locker-command" I suspected the change in the SetActive return value, and reverted it. After a build/install cycle I've found the system now behaves correctly so I think the change should be reverted. I've created an issue upstream for this at https://github.com/the-cavalry/light-locker/issues/108 To manage notifications about this bug go to: https://bugs.launchpad.net/light-locker/+bug/1759950/+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 1759950] Re: Lid-close suspend: blank screen when switching to user session
Turns out this *is* systemd-logind and xfce4-power-manager fighting over the lid close event. It can be solved with: echo "HandleLidSwitch=ignore" | sudo tee -a /etc/systemd/logind.conf echo "HandleLidSwitchExternalPower=ignore" | sudo tee -a /etc/systemd/logind.conf If you're doing this change from a TTY console whilst the GUI session has gone dark, then simply: $ sudo systemctl restart lightdm ** 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/1759950 Title: Lid-close suspend: blank screen when switching to user session Status in Light-Locker: New Status in Xfce4 Power Manager: Unknown Status in light-locker package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in xfce4-power-manager package in Ubuntu: Confirmed Bug description: I'm currently testing Xubuntu 18.04 after a do-release-upgrade from 16.04. I discovered a very weird issue. When doing S3 sleep via closing the lid, on resume the lock screen appears, I authenticate, but as soon as it switches to the user session the screen goes blank - not even a backlight. Switching to other ttys works and they display correctly but the GUI user session remains blank. If the system is manually suspended (not using the lid), then resumed either by opening the lid or pressing the power button, the GUI user session is fine. I narrowed it down to xfce4-power-manager and discovered disabling the lock-screen cured the issue. I cloned the repository and reviewed commits between 1.7 and 1.8. Fortunately there aren't many. Looking at 6365683 "Proper exit status for light-locker-command" I suspected the change in the SetActive return value, and reverted it. After a build/install cycle I've found the system now behaves correctly so I think the change should be reverted. I've created an issue upstream for this at https://github.com/the-cavalry/light-locker/issues/108 To manage notifications about this bug go to: https://bugs.launchpad.net/light-locker/+bug/1759950/+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 1832959] [NEW] Wrong cursor size after screensaver
Public bug reported: Hi all, I have a HiDPI screen (2880x1620) with 2x scaling (default). Everything worked well for months until some of the upgrades broke something. The problem is with cursor size. It has 2x or even 4x less size (very small) after returning from screensaver/locking screen. So, for example, if i suspend and then resume my laptop or just lock the screen and then type the password to unlock. Curiously, but the problem becomes fixed if i take a screenshot by pressing Print Screen. In this case the cursor size immediately becomes the correct size. Some more tips: 1. If i press Ctrl-Alt-F1 (where the gdm is running) the cursor has correct size. 2. If i then press Ctrl-Alt-F2 and switch back to my current session, it again becomes 2x-4x less size. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 00:24:41 2019 DistUpgraded: 2019-04-02 21:54:52,265 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 430.26, 5.0.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor Integrated Graphics Controller [1462:10fd] Subsystem: Micro-Star International Co., Ltd. [MSI] GK104M [GeForce GTX 870M] [1462:10fd] InstallationDate: Installed on 2018-11-13 (214 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Micro-Star International Co., Ltd. GS60 2PE ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=bc6d974d-dac7-4fef-a6ad-c78c6be040e4 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-02 (74 days ago) dmi.bios.date: 05/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H2IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.106:bd05/13/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GS60 2PE dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1832959 Title: Wrong cursor size after screensaver Status in xorg package in Ubuntu: New Bug description: Hi all, I have a HiDPI screen (2880x1620) with 2x scaling (default). Everything worked well for months until some of the upgrades broke something. The problem is with cursor size. It has 2x or even 4x less size (very small) after returning from screensaver/locking screen. So, for example, if i suspend and then resume my laptop or just lock the screen and then type the password to unlock. Curiously, but the problem becomes fixed if i take a screenshot by pressing Print Screen. In this case the cursor size immediately becomes the correct size. Some more tips: 1. If i press Ctrl-Alt-F1 (where the gdm is running) the cursor has correct size. 2. If i then press Ctrl-Alt-F2 and switch back to my current session, it again becomes 2x-4x less size. Thank you. ProblemType: Bug DistroRelease:
[Touch-packages] [Bug 1832882] Re: libcurl-gnutls segfaults spotify client
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: curl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1832882 Title: libcurl-gnutls segfaults spotify client Status in curl package in Ubuntu: Confirmed Bug description: The latest release of Spotify client segfaults in libcurl-gnutls as can be read in this thread on spotify support forum: https://community.spotify.com/t5/Desktop-Linux/Ubuntu-19-04-deb-package-segfault/td-p/4761479 According to one participant the work-around is to install debian packages libgnutls30_3.6.8-1_amd64.deb and libcurl3-gnutls_7.64.0-3_amd64.deb Ubuntu 19.04 version of the packages: libgnutls30 3.6.5-2ubuntu1.1 libcurl3-gnutls 7.64.0-2ubuntu1.1 As the bug can be resolved by installing debian packages, I assume Ubuntu's version of the packages is at fault and should be upgraded to match debian's level as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882/+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 1070873] Re: kde-telepathy, impossible to connect to gmail accounts
In my case, I am not using a proxy server of any sort. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1070873 Title: kde-telepathy, impossible to connect to gmail accounts Status in meta-kde-telepathy package in Ubuntu: Confirmed Status in signon-ui package in Ubuntu: Confirmed Bug description: Im running ubuntu 12.10 quantal and i have installed kde, when running kde-telepathy i have added a gmail account, and after entering the password it has revealed impossible to connect to it, it always says that the password is wrong when that is false. When using empathy, i have removed the gmail account and have added it again, now appears a XMLL window asking ubuntu permission to conenct to it, and now i was able to conenct to the gmail account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+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 1832903] Re: 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver
*** This bug is a duplicate of bug 1832138 *** https://bugs.launchpad.net/bugs/1832138 Only when using v4.15, if I use the hwe kernel 4.18 on Bionic it passes. I have strong belief this kernel fix to be a potential good candidate, but I need to run a bisection to confirm my assumption : commit 140bcaa23a1c37b694910424075a15e009120dbe Author: Thomas Hellstrom Date: Thu Mar 8 10:07:37 2018 +0100 drm/vmwgfx: Fix black screen and device errors when running without fbdev When we are running without fbdev, transitioning from the login screen to X or gnome-shell/wayland will cause a vt switch and the driver will disable svga mode, losing all modesetting resources. However, the kms atomic state does not reflect that and may think that a crtc is still turned on, which will cause device errors when we try to bind an fb to the crtc, and the screen will remain black. Fix this by turning off all kms resources before disabling svga mode. Cc: Signed-off-by: Thomas Hellstrom Reviewed-by: Sinclair Yeh ** This bug has been marked a duplicate of bug 1832138 Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1832903 Title: 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in wayland package in Ubuntu: New Bug description: After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login screen doesn't work if 'Wayland' is in use (default) and if video kernel driver is 'vgwfx'. It looks like the login screen got stuck, doesn't exit, and doesn't fallback to 'x11' by itself in case of failure. Workaround: - Access the machine via ssh or any other recovery approaches. - Force the login screen to use x11: File: /etc/gdm3/custom.conf [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false I tried to reproduce the behaviour on my personal laptop, KVM guest, ... without success. So far it is only reproducible when the 'vgwfx' driver is in use in combination with Wayland. lspci -nnvvv 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Capabilities: [44] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: vmwgfx Kernel modules: vmwgfx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832903/+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 1382054] Re: Add support for configuring VLAN interfaces in the initrd
This bug was fixed in the package initramfs-tools - 0.133ubuntu9 --- initramfs-tools (0.133ubuntu9) eoan; urgency=medium * Add support for creating VLANs via vlan=eth0.1:eth0 on kernel commandline, and as VLAN= conf.d snippet. LP: #1382054 -- Dimitri John Ledkov Fri, 14 Jun 2019 14:46:05 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Fix Released Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+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 1832919] Re: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10
Workaround recovered me as well, thanks! -- 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/1832919 Title: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 Status in openssl package in Ubuntu: Incomplete Bug description: The error happens when trying to configure libssl1.1:amd64 (dpkg --configure -D 2 libssl1.1) dpkg: error processing package libssl1.1:amd64 (--configure): installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 D02: post_script_tasks - ensure_diversions D02: post_script_tasks - trig_incorporate D02: check_triggers_cycle pnow=libc-bin:amd64 first Processing triggers for libc-bin (2.27-3ubuntu1) ... D02: post_postinst_tasks - trig_incorporate Errors were encountered while processing: libssl1.1:amd64 [ WORKAROUND TO RECOVER YOUR SYSTEM ] $ sudo dpkg-reconfigure libc6 $ sudo dpkg --configure libssl1.1 [ Reproducer steps ] # DO NOT DO THIS ON PRODUCTION MACHINES # # echo PURGE | debconf-communicate libpam0g:amd64 0 # echo PURGE | debconf-communicate libpam0g 0 # echo PURGE | debconf-communicate libc6:amd64 0 # echo PURGE | debconf-communicate libc6 0 # sh -x /var/lib/dpkg/info/libssl1.1\:amd64.postinst configure 1.1.1 + . /usr/share/debconf/confmodule + [ ! ] + PERL_DL_NONLAZY=1 + export PERL_DL_NONLAZY + [ ] + exec /usr/share/debconf/frontend /var/lib/dpkg/info/libssl1.1:amd64.postinst configure 1.1.1 Checking for services that may need to be restarted...done. Checking for services that may need to be restarted...done. Checking init scripts... # echo $? 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832919/+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 1829968] Re: motd [on at least some instances] does not auto-update daily
This bug was fixed in the package base-files - 10.2ubuntu3 --- base-files (10.2ubuntu3) eoan; urgency=medium * debian/motd-news.timer: Switch the timer from OnUnitActiveSec to OnUnitSec as the latter is correct for oneshot services. (LP: #1829968) -- Brian Murray Thu, 13 Jun 2019 12:12:22 -0700 ** Changed in: base-files (Ubuntu Eoan) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1829968 Title: motd [on at least some instances] does not auto-update daily Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Bionic: Triaged Status in base-files source package in Cosmic: New Status in base-files source package in Disco: New Status in base-files source package in Eoan: Fix Released Bug description: I have a VM running on AWS. It was launched on May 9th: $ uptime 05:26:21 up 12 days, 6:34, 1 user, load average: 0.00, 0.00, 0.00 $ date Wed May 22 05:26:24 UTC 2019 I touched none of the system defaults, and yet the motd has not updated automatically. $ ls -l /var/cache/motd-news -rw-r--r-- 1 root root 0 May 9 22:53 /var/cache/motd-news The systemd timer unit looks like this: $ systemctl status motd-news.timer ● motd-news.timer - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 days ago Trigger: n/a May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the Day. If I run /etc/update-motd.d/50-motd-news --force manually, the file does update correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1829968/+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 1832933] [NEW] upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 breaks ejabbrd
Public bug reported: Hello! After upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 openssl 1.1.1-1ubuntu2.1~18.04.2 on Ubuntu 18.04 server clients can't connect to ejabberd server: 2019-06-15 15:56:26.431 [warning] <0.858.0>@ejabberd_c2s:process_terminated:290 (tls|<0.858.0>) Failed to secure c2s connection: TLS failed: client renegotiations forbidden ejabberd version is18.01-2 which is from Ubuntu 18.04. As far as I know ejabberd can work with openssl 1.1.1 only from 18.09 https://blog.process-one.net/ejabberd-18-09/ OpenSSL 1.1.1 support Either ejabberd in 18.04 should be updated or openssl should not be upgraded to 1.1.1 on 18.04 . Thank you! ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: ejabberd openssl -- 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/1832933 Title: upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 breaks ejabbrd Status in openssl package in Ubuntu: New Bug description: Hello! After upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 openssl 1.1.1-1ubuntu2.1~18.04.2 on Ubuntu 18.04 server clients can't connect to ejabberd server: 2019-06-15 15:56:26.431 [warning] <0.858.0>@ejabberd_c2s:process_terminated:290 (tls|<0.858.0>) Failed to secure c2s connection: TLS failed: client renegotiations forbidden ejabberd version is18.01-2 which is from Ubuntu 18.04. As far as I know ejabberd can work with openssl 1.1.1 only from 18.09 https://blog.process-one.net/ejabberd-18-09/ OpenSSL 1.1.1 support Either ejabberd in 18.04 should be updated or openssl should not be upgraded to 1.1.1 on 18.04 . Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832933/+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 1832882] Re: libcurl-gnutls segfaults spotify client
Can confirm. Installing libcurl3-gnutls_7.64.0-3_amd64.deb and libgnutls30_3.6.8-1_amd64.deb from the debian repositories solves the issue on Ubuntu 19.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1832882 Title: libcurl-gnutls segfaults spotify client Status in curl package in Ubuntu: New Bug description: The latest release of Spotify client segfaults in libcurl-gnutls as can be read in this thread on spotify support forum: https://community.spotify.com/t5/Desktop-Linux/Ubuntu-19-04-deb-package-segfault/td-p/4761479 According to one participant the work-around is to install debian packages libgnutls30_3.6.8-1_amd64.deb and libcurl3-gnutls_7.64.0-3_amd64.deb Ubuntu 19.04 version of the packages: libgnutls30 3.6.5-2ubuntu1.1 libcurl3-gnutls 7.64.0-2ubuntu1.1 As the bug can be resolved by installing debian packages, I assume Ubuntu's version of the packages is at fault and should be upgraded to match debian's level as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882/+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 1832919] Re: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10
It works: sudo dpkg-reconfigure libc6 sudo dpkg --configure libssl1.1 sudo dpkg-reconfigure libssl1.1 ___ I did: sudo dpkg-reconfigure libc6 sudo dpkg-reconfigure libssl1.1 happened: /usr/sbin/dpkg-reconfigure: libssl1.1 is broken or not fully installed than: sudo dpkg --configure libssl1.1 happened: Setting up libssl1.1:amd64 (1.1.1-1ubuntu2.1~18.04.2) ... Checking for services that may need to be restarted...done. Checking for services that may need to be restarted...done. Checking init scripts... Restarting services possibly affected by the upgrade: Services restarted successfully. Processing triggers for libc-bin (2.27-3ubuntu1) ... than: sudo dpkg-reconfigure libssl1.1 -- 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/1832919 Title: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 Status in openssl package in Ubuntu: Incomplete Bug description: The error happens when trying to configure libssl1.1:amd64 (dpkg --configure -D 2 libssl1.1) dpkg: error processing package libssl1.1:amd64 (--configure): installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 D02: post_script_tasks - ensure_diversions D02: post_script_tasks - trig_incorporate D02: check_triggers_cycle pnow=libc-bin:amd64 first Processing triggers for libc-bin (2.27-3ubuntu1) ... D02: post_postinst_tasks - trig_incorporate Errors were encountered while processing: libssl1.1:amd64 [ WORKAROUND TO RECOVER YOUR SYSTEM ] $ sudo dpkg-reconfigure libc6 $ sudo dpkg --configure libssl1.1 [ Reproducer steps ] # DO NOT DO THIS ON PRODUCTION MACHINES # # echo PURGE | debconf-communicate libpam0g:amd64 0 # echo PURGE | debconf-communicate libpam0g 0 # echo PURGE | debconf-communicate libc6:amd64 0 # echo PURGE | debconf-communicate libc6 0 # sh -x /var/lib/dpkg/info/libssl1.1\:amd64.postinst configure 1.1.1 + . /usr/share/debconf/confmodule + [ ! ] + PERL_DL_NONLAZY=1 + export PERL_DL_NONLAZY + [ ] + exec /usr/share/debconf/frontend /var/lib/dpkg/info/libssl1.1:amd64.postinst configure 1.1.1 Checking for services that may need to be restarted...done. Checking for services that may need to be restarted...done. Checking init scripts... # echo $? 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832919/+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 1832882] Re: libcurl-gnutls segfaults spotify client
I can confirm this bug. Installing libcurl3-gnutls_7.64.0-3_amd64.deb or loading the libraries of libcurl3-gnutls_7.64.0-3_amd64.deb from the Debian will solve the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1832882 Title: libcurl-gnutls segfaults spotify client Status in curl package in Ubuntu: New Bug description: The latest release of Spotify client segfaults in libcurl-gnutls as can be read in this thread on spotify support forum: https://community.spotify.com/t5/Desktop-Linux/Ubuntu-19-04-deb-package-segfault/td-p/4761479 According to one participant the work-around is to install debian packages libgnutls30_3.6.8-1_amd64.deb and libcurl3-gnutls_7.64.0-3_amd64.deb Ubuntu 19.04 version of the packages: libgnutls30 3.6.5-2ubuntu1.1 libcurl3-gnutls 7.64.0-2ubuntu1.1 As the bug can be resolved by installing debian packages, I assume Ubuntu's version of the packages is at fault and should be upgraded to match debian's level as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882/+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
