[Touch-packages] [Bug 1943637] [NEW] Screensaver is invisible when activated by lid close
Public bug reported: My power management settings are set to lock screen when the lid is closed. When this happens, the screensaver activates, but is not visible (desktop can't be interacted with, typing password and pressing enter unlocks it). I'm running Xubuntu and have tried: * xscreensaver instead of xfce4-screensaver * slick-greeter instead of lightdm-gtk-greeter Which made no difference. I'm now using sddm instead of lightdm and no longer having this problem, so I believe the bug is in lightdm. This is possible a duplicate of #1853709, but I'm unsure as that one is specifically talking about suspend, mine is set to lock, not suspend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1 Uname: Linux 5.13.0-1012-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 14 21:10:01 2021 InstallationDate: Installed on 2021-07-01 (75 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: My power management settings are set to lock screen when the lid is closed. When this happens, the screensaver activates, but is not visible (desktop can't be interacted with, typing password and pressing enter unlocks it). - I'm running Xubuntu and have tried: * xscreensaver instead of xfce4-screensaver * slick-greeter instead of lightdm-gtk-greeter Which made no difference. I'm now using sddm instead of lightdm and no - longer having this problem, so I believe the bug is in lightdm. + longer having this problem, so I believe the bug is in lightdm. This is + possible a duplicate of #1853709, but I'm unsure as that one is + specifically talking about suspend, mine is set to lock, not suspend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1 Uname: Linux 5.13.0-1012-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 14 21:10:01 2021 InstallationDate: Installed on 2021-07-01 (75 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1943637 Title: Screensaver is invisible when activated by lid close Status in lightdm package in Ubuntu: New Bug description: My power management settings are set to lock screen when the lid is closed. When this happens, the screensaver activates, but is not visible (desktop can't be interacted with, typing password and pressing enter unlocks it). I'm running Xubuntu and have tried: * xscreensaver instead of xfce4-screensaver * slick-greeter instead of lightdm-gtk-greeter Which made no difference. I'm now using sddm instead of lightdm and no longer having this problem, so I believe the bug is in lightdm. This is possible a duplicate of #1853709, but I'm unsure as that one is specifically talking about suspend, mine is set to lock, not suspend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1 Uname: Linux 5.13.0-1012-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 14 21:10:01 2021 InstallationDate: Installed on 2021-07-01 (75 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1943637/+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 1535840] Re: systemd ignoring /etc/modules due to blacklist
This issue makes it annoying to load watchdog drivers, as systemd now supports hardware watchdogs they'd have to be added to rc.local or a custom service. The pre-systemd behaviour only applied the blacklist with udev, not when processing /etc/modules(-load.d) so that they could be prevented from loading automatically unless explicitly listed by the user. So this is more of a regression due to behaviour change than opinion. -- 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/1535840 Title: systemd ignoring /etc/modules due to blacklist Status in systemd package in Ubuntu: Opinion Bug description: I tried the daily build of 16.04 32-bit to test out the watchdog daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in /etc/modules so it is loaded at boot-time, as watchdog timer modules are not normally auto-loaded due to the risk of an unexpected reboot. However I now find that systemd is choosing to ignore my command to load the module in /etc/modules since it appears in the watchdog blacklist. Typical syslog entries look like this: Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is blacklisted Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is blacklisted This is just dumb! I have explicitly told the system to load the module, an action that works perfectly well using modprobe or by adding it to the start script for the watchdog, and yet systemd chooses to override that because of the blacklist for auto-loaded modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf). $ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 $ apt-cache policy systemd systemd: Installed: 228-4ubuntu1 Candidate: 228-4ubuntu1 Version table: *** 228-4ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status What I expect to happen is modules added to /etc/modules are loaded at boot time, and not subject to the blacklist for hardware detect / automatic loading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1535840/+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 1877762] Re: 1360x768 Vega graphics display staggered
Seeing this too with a fresh install of Xubuntu 20.04.2 on a Ryzen Embedded V1605B I've tested kernel 5.11, 5.12.13 and 5.13, only 5.13 was working correctly. Booting with nomodeset also corrected the display ** Attachment added: "Xubuntu 20.04.2 live CD (5.8 kernel with default options)" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1877762/+attachment/5508817/+files/IMG_20210703_202121_424.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1877762 Title: 1360x768 Vega graphics display staggered Status in Ubuntu MATE: New Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This was the go-to resolution pre-update. All of the other modes seem to work. Release 20.04 LTS (Focal Fossa) 64-bit Kernel Linux 5.4.0-29-generic x86_64 MATE 1.24.0 Processor: AMD Ryzen 3 2200G with Radeon Vega Graphics × 4 Graphics: AMD RAVEN (DRM 3.35.0, 5.4.0-29-generic, LLVM 9.0.1) lspci output: 38:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8) As you can see from the attached image, the display shifts to the right every few lines. Still working on installing the full amdgpu package (libffs 6 required, 7 installed so I'm working on the bits). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1877762/+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 1447654] Re: installing policykit-1 hangs under systemd
Yes, policykit-1 0.105-8ubuntu4 fixes this for me. Same steps as before: apt-get purge apport policykit-1: apt-get install apport policykit-1 ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1447654 Title: installing policykit-1 hangs under systemd Status in policykit-1 package in Ubuntu: Fix Released Status in policykit-1 source package in Vivid: Fix Committed Status in policykit-1 package in Debian: Fix Committed Bug description: I've installed 15.04 using the current amd64 netboot.tar.gz (MD5 = 6566065bf73a9c81feeddf5520dda122). It installs fine, but I'm getting errors installing packages (such as lubuntu-core). Last few lines from apt-get: Processing triggers for systemd (219-7ubuntu3) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for libglib2.0-0:amd64 (2.44.0-1ubuntu3) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for mime-support (3.58ubuntu1) ... Processing triggers for udev (219-7ubuntu3) ... Processing triggers for dbus (1.8.12-1ubuntu5) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) I've done a second install using the server iso and lubuntu-core installs fine on that. The only thing different was my install media. SRU TEST CASE: - Boot a minimal VM and purge "apport policykit-1", or do the above netboot installation. - sudo apt-get install policykit-1 apport - The above hangs on the systemd triggers and eventually fails. It should succeed fine with this update. Regression potential: Very low: This update avoids that systemd tries to start up polkit while it's unpacked but not configured, which is exactly the case that can't work. If there's anything wrong with the postinst and the rm for the temporary masking symlink does not get run for some reason, the next reboot will clean it up anyway. So the fix is a no-change operation for anything but first install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1447654/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
This is actually in systemd, not systemd-shim. I patched systemd-shim to ignore unknown unit warning, so then I get a warning from systemd-logind: systemd-logind[1414]: Failed to start user service: Message did not receive a reply (timeout by message bus) So it's being started by the login manager once pam-systemd registers the session. pam_systemd manpage: A new systemd scope unit is created for the session. If this is the first concurrent session of the user, an implicit slice below user.slice is automatically created and the scope placed into it. An instance of the system service user@.service, which runs the systemd user manager instance, is started. I'm guessing user@.service is generated at runtime by systemd (which would require systemd is init, not upstart). Suggestions for fixing this: 1. Move /etc/pam.d/systemd-user to the systemd-sysv package (assuming none of systemd-logind's features are required) 2. Patch systemd-logind to not start the user service if the system wasn't booted with systemd I'll take a look at patching systemd-logind. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in systemd-shim package in Ubuntu: Triaged Status in systemd-shim package in Debian: New Bug description: ATTENTION: This bug is fully understood, there is *no need* to add even more comments about "me too" here. [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+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 1442970] [NEW] Connecting to TLSv1.2 only servers fails without explicitly specifying protocol
Public bug reported: Package version: 1.0.1-4ubuntu5.25 Recently one of my IRC networks changed to TLSv1.2 only and I was unable to connect. The version of OpenSSL in precise appears to have problems connecting to servers that only accept TLSv1.2. ZNC: <*status> Disconnected from IRC (error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure). Reconnecting... irssi: 22:15 -!- Irssi: warning SSL handshake failed: sslv3 alert handshake failure 22:15 -!- Irssi: Connection lost to irc.p2p-network.net OpenSSL: $ openssl s_client -connect irc.p2p-network.net:6697 CONNECTED(0005) 139964049446560:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:732: Explicitly specifying TLSv1.2 works: $ openssl s_client -connect irc.p2p-network.net:6697 -tls1_2 CONNECTED(0005) ... New, TLSv1/SSLv3, Cipher is AES256-GCM-SHA384 Server public key is 4096 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1.2 Cipher: AES256-GCM-SHA384 In vivid (openssl 1.0.1f-1ubuntu11): $ openssl s_client -connect irc.p2p-network.net:6697 CONNECTED(0003) ... New, TLSv1/SSLv3, Cipher is AES256-GCM-SHA384 Server public key is 4096 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1.2 Cipher: AES256-GCM-SHA384 ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: precise -- 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/1442970 Title: Connecting to TLSv1.2 only servers fails without explicitly specifying protocol Status in openssl package in Ubuntu: New Bug description: Package version: 1.0.1-4ubuntu5.25 Recently one of my IRC networks changed to TLSv1.2 only and I was unable to connect. The version of OpenSSL in precise appears to have problems connecting to servers that only accept TLSv1.2. ZNC: <*status> Disconnected from IRC (error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure). Reconnecting... irssi: 22:15 -!- Irssi: warning SSL handshake failed: sslv3 alert handshake failure 22:15 -!- Irssi: Connection lost to irc.p2p-network.net OpenSSL: $ openssl s_client -connect irc.p2p-network.net:6697 CONNECTED(0005) 139964049446560:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:732: Explicitly specifying TLSv1.2 works: $ openssl s_client -connect irc.p2p-network.net:6697 -tls1_2 CONNECTED(0005) ... New, TLSv1/SSLv3, Cipher is AES256-GCM-SHA384 Server public key is 4096 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1.2 Cipher: AES256-GCM-SHA384 In vivid (openssl 1.0.1f-1ubuntu11): $ openssl s_client -connect irc.p2p-network.net:6697 CONNECTED(0003) ... New, TLSv1/SSLv3, Cipher is AES256-GCM-SHA384 Server public key is 4096 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1.2 Cipher: AES256-GCM-SHA384 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1442970/+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 1447654] Re: installing policykit-1 hangs under systemd
Same error unfortunately. Selecting previously unselected package policykit-1. Preparing to unpack .../policykit-1_0.105-8ubuntu3_amd64.deb ... Unpacking policykit-1 (0.105-8ubuntu3) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for systemd (219-7ubuntu4) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1447654 Title: installing policykit-1 hangs under systemd Status in policykit-1 package in Ubuntu: Fix Committed Status in policykit-1 source package in Vivid: Fix Committed Bug description: I've installed 15.04 using the current amd64 netboot.tar.gz (MD5 = 6566065bf73a9c81feeddf5520dda122). It installs fine, but I'm getting errors installing packages (such as lubuntu-core). Last few lines from apt-get: Processing triggers for systemd (219-7ubuntu3) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for libglib2.0-0:amd64 (2.44.0-1ubuntu3) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for mime-support (3.58ubuntu1) ... Processing triggers for udev (219-7ubuntu3) ... Processing triggers for dbus (1.8.12-1ubuntu5) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) I've done a second install using the server iso and lubuntu-core installs fine on that. The only thing different was my install media. SRU INFORMATION === Test case: - Boot a minimal VM and purge "apport policykit-1", or do the above netboot installation. - sudo apt-get install policykit-1 apport - The above hangs on the systemd triggers and eventually fails in vivid final. It should succeed fine with this update. Regression potential: Very low: polkitd does not keep state, so one can restart it fine. The postinst shell modification is simple and obvious. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1447654/+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 1447654] Re: installing policykit-1 hangs under systemd
Alright, looked at it some more. Installing policykit-1, then apport works fine. But if I install them together, it hangs. Works: apt-get install policykit-1; apt-get install apport Hangs on systemd triggers: apt-get purge apport policykit-1; apt-get install apport policykit-1 I've managed to reproduce this every time I've rebooted and tried again. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1447654/+attachment/4386888/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1447654 Title: installing policykit-1 hangs under systemd Status in policykit-1 package in Ubuntu: Fix Committed Status in policykit-1 source package in Vivid: Fix Committed Bug description: I've installed 15.04 using the current amd64 netboot.tar.gz (MD5 = 6566065bf73a9c81feeddf5520dda122). It installs fine, but I'm getting errors installing packages (such as lubuntu-core). Last few lines from apt-get: Processing triggers for systemd (219-7ubuntu3) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for libglib2.0-0:amd64 (2.44.0-1ubuntu3) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for mime-support (3.58ubuntu1) ... Processing triggers for udev (219-7ubuntu3) ... Processing triggers for dbus (1.8.12-1ubuntu5) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) I've done a second install using the server iso and lubuntu-core installs fine on that. The only thing different was my install media. SRU INFORMATION === Test case: - Boot a minimal VM and purge "apport policykit-1", or do the above netboot installation. - sudo apt-get install policykit-1 apport - The above hangs on the systemd triggers and eventually fails in vivid final. It should succeed fine with this update. Regression potential: Very low: polkitd does not keep state, so one can restart it fine. The postinst shell modification is simple and obvious. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1447654/+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 1447654] Re: installing policykit-1 hangs under systemd
Just tested wily (20150613), still hangs. Same steps as before: Install apt-get purge apport policykit-1 reboot apt-get install apport policykit-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1447654 Title: installing policykit-1 hangs under systemd Status in policykit-1 package in Ubuntu: Confirmed Status in policykit-1 source package in Vivid: Fix Released Bug description: I've installed 15.04 using the current amd64 netboot.tar.gz (MD5 = 6566065bf73a9c81feeddf5520dda122). It installs fine, but I'm getting errors installing packages (such as lubuntu-core). Last few lines from apt-get: Processing triggers for systemd (219-7ubuntu3) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for libglib2.0-0:amd64 (2.44.0-1ubuntu3) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for mime-support (3.58ubuntu1) ... Processing triggers for udev (219-7ubuntu3) ... Processing triggers for dbus (1.8.12-1ubuntu5) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) I've done a second install using the server iso and lubuntu-core installs fine on that. The only thing different was my install media. SRU INFORMATION === Test case: - Boot a minimal VM and purge "apport policykit-1", or do the above netboot installation. - sudo apt-get install policykit-1 apport - The above hangs on the systemd triggers and eventually fails in vivid final. It should succeed fine with this update. Regression potential: Very low: polkitd does not keep state, so one can restart it fine. The postinst shell modification is simple and obvious. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1447654/+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 1982108] Re: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS
I can confirm this resolves the issue of embedded interpreters crashing (tested with Kodi). Versions used: ii libpython3-dev:amd64 3.10.6-1~22.04 amd64header files and a static library for Python (default) ii libpython3-stdlib:amd64 3.10.6-1~22.04 amd64interactive high-level object-oriented language (default python3 version) ii libpython3.10:amd64 3.10.6-1~22.04 amd64Shared Python runtime library (version 3.10) ii libpython3.10-dev:amd64 3.10.6-1~22.04 amd64Header files and a static library for Python (v3.10) ii libpython3.10-minimal:amd64 3.10.6-1~22.04 amd64Minimal subset of the Python language (version 3.10) ii libpython3.10-stdlib:amd643.10.6-1~22.04 amd64Interactive high-level object-oriented language (standard library, version 3.10) ii python3 3.10.6-1~22.04 amd64interactive high-level object-oriented language (default python3 version) ii python3-dev 3.10.6-1~22.04 amd64header files and a static library for Python (default) ii python3-distutils 3.10.6-1~22.04 all distutils package for Python 3.x ii python3-lib2to3 3.10.6-1~22.04 all Interactive high-level object-oriented language (lib2to3) ii python3-minimal 3.10.6-1~22.04 amd64minimal subset of the Python language (default python3 version) ii python3-venv 3.10.6-1~22.04 amd64venv module for python3 (default python3 version) ii python3.103.10.6-1~22.04 amd64Interactive high-level object-oriented language (version 3.10) ii python3.10-dev3.10.6-1~22.04 amd64Header files and a static library for Python (v3.10) ii python3.10-minimal3.10.6-1~22.04 amd64Minimal subset of the Python language (version 3.10) ii python3.10-venv 3.10.6-1~22.04 amd64Interactive high-level object-oriented language (pyvenv binary, version 3.10) ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1982108 Title: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Confirmed Status in python3.10 package in Ubuntu: Confirmed Status in python3-defaults source package in Jammy: Fix Committed Status in python3-stdlib-extensions source package in Jammy: Fix Committed Status in python3.10 source package in Jammy: Fix Committed Bug description: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS we are doing a test rebuild of 22.04 main to check for regressions. test rebuilds at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html the first one is the reference test rebuild, the second one the rebuild using updated binutils, GCC and python packages. Analysis: regressions on riscv64 (caused by enabling the tests) are: abseil adsys colord dovecot glib-networking glibc gnome-bluetooth3 gnome-control-center google-perftools json-glib libfprint libgdata memcached mir openvswitch ovn pmdk power-profiles-daemon strace swtpm vim devscripts is not a regression, introduced by a custom dpkg- buildpackage wrapper. binutils and python3-stdlib-extensions are superseded which are part of the planned updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1982108/+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 1973642] [NEW] [REGRESSION] Unable to connect to EAP-TLS networks
Public bug reported: Fresh install of Xubuntu 22.04, currently with network-manager 1.36.4-2ubuntu1 Attempting to connect to an EAP-TLS network fails with: NetworkManager[703]: [1652732829.9142] device (wlp0s12f0): Activation: (wifi) connection 'AP' has security, and secrets exist. No new secrets needed. NetworkManager[703]: [1652732829.9143] Config: added 'ssid' value 'AP' NetworkManager[703]: [1652732829.9143] Config: added 'scan_ssid' value '1' NetworkManager[703]: [1652732829.9144] Config: added 'bgscan' value 'simple:30:-65:300' NetworkManager[703]: [1652732829.9144] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256' NetworkManager[703]: [1652732829.9144] Config: added 'eap' value 'TLS' NetworkManager[703]: [1652732829.9144] Config: added 'fragment_size' value '1266' NetworkManager[703]: [1652732829.9144] Config: added 'ca_cert' value '' NetworkManager[703]: [1652732829.9144] Config: added 'domain_suffix_match' value '' NetworkManager[703]: [1652732829.9145] Config: added 'private_key' value '.key' NetworkManager[703]: [1652732829.9145] Config: added 'private_key_passwd' value '' NetworkManager[703]: [1652732829.9145] Config: added 'client_cert' value '.crt' NetworkManager[703]: [1652732829.9145] Config: added 'identity' value '' NetworkManager[703]: [1652732829.9146] Config: added 'proactive_key_caching' value '1' NetworkManager[703]: [1652732829.9178] sup-iface[c392e32eb812390f,0,wlp0s12f0]: assoc[473f0d33ad3574e9]: failure to add network: invalid message format NetworkManager[703]: [1652732829.9179] device (wlp0s12f0): state change: config -> failed (reason 'supplicant-failed', sys-iface-state: 'managed') Caused by NM providing an empty domain_suffix_match option Upstream commit fixing this (also attached): https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8df79f60d616e183257ae1a2c2b48beaf29e5eec Upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/973 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: jammy patch ** Patch added: "8df79f60d616e183257ae1a2c2b48beaf29e5eec.patch" https://bugs.launchpad.net/bugs/1973642/+attachment/5590156/+files/8df79f60d616e183257ae1a2c2b48beaf29e5eec.patch ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973642 Title: [REGRESSION] Unable to connect to EAP-TLS networks Status in network-manager package in Ubuntu: New Bug description: Fresh install of Xubuntu 22.04, currently with network-manager 1.36.4-2ubuntu1 Attempting to connect to an EAP-TLS network fails with: NetworkManager[703]: [1652732829.9142] device (wlp0s12f0): Activation: (wifi) connection 'AP' has security, and secrets exist. No new secrets needed. NetworkManager[703]: [1652732829.9143] Config: added 'ssid' value 'AP' NetworkManager[703]: [1652732829.9143] Config: added 'scan_ssid' value '1' NetworkManager[703]: [1652732829.9144] Config: added 'bgscan' value 'simple:30:-65:300' NetworkManager[703]: [1652732829.9144] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256' NetworkManager[703]: [1652732829.9144] Config: added 'eap' value 'TLS' NetworkManager[703]: [1652732829.9144] Config: added 'fragment_size' value '1266' NetworkManager[703]: [1652732829.9144] Config: added 'ca_cert' value '' NetworkManager[703]: [1652732829.9144] Config: added 'domain_suffix_match' value '' NetworkManager[703]: [1652732829.9145] Config: added 'private_key' value '.key' NetworkManager[703]: [1652732829.9145] Config: added 'private_key_passwd' value '' NetworkManager[703]: [1652732829.9145] Config: added 'client_cert' value '.crt' NetworkManager[703]: [1652732829.9145] Config: added 'identity' value '' NetworkManager[703]: [1652732829.9146] Config: added 'proactive_key_caching' value '1' NetworkManager[703]: [1652732829.9178] sup-iface[c392e32eb812390f,0,wlp0s12f0]: assoc[473f0d33ad3574e9]: failure to add network: invalid message format NetworkManager[703]: [1652732829.9179] device (wlp0s12f0): state change: config -> failed (reason 'supplicant-failed', sys-iface-state: 'managed') Caused by NM providing an empty domain_suffix_match option Upstream commit fixing this (also attached): https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8df79f60d616e183257ae1a2c2b48beaf29e5eec Upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/973 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973642/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.
[Touch-packages] [Bug 1403982] Re: mini.iso installer cannot load additional components
Installer hasn't been rebuilt yet. Hopefully someone will do it soon. ** Also affects: debian-installer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1403982 Title: mini.iso installer cannot load additional components Status in debian-installer package in Ubuntu: New Status in gnupg package in Ubuntu: Fix Released Bug description: system: Ubuntu Vivid 32-bit current daily mini.iso Computer: http://www.toshiba.se/laptops/satellite-pro/c850/satellite- pro-c850-19w/ Dialogue: "Choose a mirror to use and press enter. If you have a http proxy type its details now, otherwise just press enter." The installer does not start loading additional components. Instead it complains: "Downloading a file failed" Retry Change mirror Cancel I have tried several national mirrors, and also 'archive.ubuntu.com' No mirror can provide that file, and the installation gets stuck here. Failing process: udpkg, net-retriever, or maybe missing files in the mirrors? There is nothing wrong with my internet connection: ping ubuntu.com works (from this Vivid alpha mini.iso) Ubuntu 14.04 LTS mini.iso works, can install systems The automatically attached files have nothing to do with the bug. They were created in another computer because I could not create the report in the simple system running in the beginning of the mini.iso installation process. So they were removed. ProblemType: Bug DistroRelease: Ubuntu mini.iso 15.04 version 20101020ubuntu356/ 16-Dec-2014 01:28 Architecture: i386 Date: Thu Dec 18 19:23:55 2014 MarkForUpload: True PackageArchitecture: all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1403982/+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 1027760] Re: utmp records do not have X display address in host field
Is this still going to be included in precise? It's not in 12.04.5 $ apt-cache policy lightdm lightdm: Installed: 1.2.3-0ubuntu2.5 Candidate: 1.2.3-0ubuntu2.5 Version table: *** 1.2.3-0ubuntu2.5 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.1-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages $ lsb_release -d Description:Ubuntu 12.04.5 LTS $ w 18:31:49 up 3 days, 9:01, 8 users, load average: 0.31, 0.39, 0.45 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT administ tty7 17:363days 1:02 0.40s /usr/bin/lxsession -s Lubuntu -e LXDE The display missing from the host field is preventing me from shadowing the session with WinSwitch and currently it's not practical for me to update to 14.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1027760 Title: utmp records do not have X display address in host field Status in Light Display Manager: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Precise: Triaged Bug description: Impact: utmp records generated by LightDM do not have the X display address in the ut_host field. Test Case: - log into a desktop session - run "w" and see if there is a display associated with the session - should work with the update Regression potential: The utmp,wtmp records could be wrong --- utmp records generated by LightDM do not have the X display address in the ut_host field. It is not documented that this field should be used in this way, but this is what GDM does. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1027760/+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 1196693] Re: Cannot boot degraded RAID1 array with LUKS partition
I'm currently testing this in a 14.04.1 virtual machine. After disconnecting one HDD, boot stays on "Waiting for encrypted source device...", then drops to a shell (tried a few times before looking into it). /proc/mdstat shows the array is assembled, but not been started. Manually starting it (with `mdadm -R`) was successful, so I rebooted to try again.. it booted fine degraded has done every boot since (below output is after booting degraded). My setup is: 2 HDDs. Each contains 1 partition which is part of a RAID1 array (md0). md0 is LVM with a VG called "system". "system" contains 2 LVs, boot (unencrypted), root (LUKS) # mount | grep /dev/m /dev/mapper/system-root_crypt on / type xfs (rw) /dev/mapper/system-boot on /boot type ext4 (rw) # mdadm --detail /dev/md0 /dev/md0: Version : 1.2 Creation Time : Mon Jan 5 20:56:33 2015 Raid Level : raid1 Array Size : 20952960 (19.98 GiB 21.46 GB) Used Dev Size : 20952960 (19.98 GiB 21.46 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Wed Jan 7 16:28:18 2015 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : ubuntu-raid1:0 (local to host ubuntu-raid1) UUID : 66eefd8b:ad7f449d:73d180a0:cbcabb44 Events : 187 Number Major Minor RaidDevice State 0 810 active sync /dev/sda1 1 001 removed ** Tags added: trusty -- 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/1196693 Title: Cannot boot degraded RAID1 array with LUKS partition Status in initramfs-tools package in Ubuntu: Confirmed Bug description: When pulling out a disk on my 12.04.2 RAID1 setup, which contains a LUKS container inside an md device, my system won't boot. Plugging the second disk back in worked, but I wanted to replace my disks, and if a disk is broken you don't have that option... Debugging the initramfs boot sequence seems to indicate that the crypto handling is done before degraded array handing, rendering the BOOTDEGRADED flag ineffective. I've looked at other bugs (#1077650 #1003309 #728435 #106215) but I think it's a different problem. Situation I've got a LVM-in-LUKS-in-RAID1 setup, with a separate, RAID'ed bootpartition. # cat /proc/mdstat Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sda2[0] sdb2[2] 523968 blocks super 1.2 [2/2] [UU] md127 : active raid1 sda1[0] sdb1[2] 976106048 blocks super 1.2 [2/2] [UU] unused devices: md127 contains a LUKS container, called ugh2_lvm. ugh2_lvm contains an LVM with a volume group called ugh2_vg. ugh2_vg contains LV's called "root" (the root filesystem) and "swap". # mount | grep /dev/m /dev/mapper/ugh2_vg-root on / type ext4 (rw,relatime) /dev/md126 on /boot type ext4 (rw) # cat crypttab ugh2_lvm UUID=69ade3d3-817d-42ee-991b-ebf86e9fe685 none luks # grep 'DEGRADED=' /etc/initramfs-tools/conf.d/mdadm BOOT_DEGRADED=true Symptoms Booting seems to hang with a message "evms_activate is not available". I'm not using EVMS so the message is not really indicative of the problem. Perhaps you get dropped to a shell after a lot of time (3 minutes? I saw a time-out of 180 seconds in the scripts somewhere) but that took too long for me. Diagnosis Interrupting the boot process with break=premount let me take a look at the situation. Turns out the degraded arrays assembled, but inactive; the BOOT_DEGRADED handling activates the degraded arrays (scripts/local-premount/mdadm). However, it does not get the chance to do so before the scripts try to open the LUKS device with the configured UUID, since this is done by scripts/local-top/cryptroot. "*-top" scripts are run before "*-premount" scripts. Workaround / solution I made it work again by linking /usr/share/initramfs-tools/scripts /local-premount/mdadm -> /etc/initramfs-tools/scripts/local- top/mdadm, then rebuilding my initramfs (update-initramfs -u). It seems to work well. Not sure if it's the best or even a clean approach. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1196693/+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 1196693] Re: Cannot boot degraded RAID1 array with LUKS partition
** Tags added: utopic -- 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/1196693 Title: Cannot boot degraded RAID1 array with LUKS partition Status in initramfs-tools package in Ubuntu: Confirmed Bug description: When pulling out a disk on my 12.04.2 RAID1 setup, which contains a LUKS container inside an md device, my system won't boot. Plugging the second disk back in worked, but I wanted to replace my disks, and if a disk is broken you don't have that option... Debugging the initramfs boot sequence seems to indicate that the crypto handling is done before degraded array handing, rendering the BOOTDEGRADED flag ineffective. I've looked at other bugs (#1077650 #1003309 #728435 #106215) but I think it's a different problem. Situation I've got a LVM-in-LUKS-in-RAID1 setup, with a separate, RAID'ed bootpartition. # cat /proc/mdstat Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sda2[0] sdb2[2] 523968 blocks super 1.2 [2/2] [UU] md127 : active raid1 sda1[0] sdb1[2] 976106048 blocks super 1.2 [2/2] [UU] unused devices: md127 contains a LUKS container, called ugh2_lvm. ugh2_lvm contains an LVM with a volume group called ugh2_vg. ugh2_vg contains LV's called "root" (the root filesystem) and "swap". # mount | grep /dev/m /dev/mapper/ugh2_vg-root on / type ext4 (rw,relatime) /dev/md126 on /boot type ext4 (rw) # cat crypttab ugh2_lvm UUID=69ade3d3-817d-42ee-991b-ebf86e9fe685 none luks # grep 'DEGRADED=' /etc/initramfs-tools/conf.d/mdadm BOOT_DEGRADED=true Symptoms Booting seems to hang with a message "evms_activate is not available". I'm not using EVMS so the message is not really indicative of the problem. Perhaps you get dropped to a shell after a lot of time (3 minutes? I saw a time-out of 180 seconds in the scripts somewhere) but that took too long for me. Diagnosis Interrupting the boot process with break=premount let me take a look at the situation. Turns out the degraded arrays assembled, but inactive; the BOOT_DEGRADED handling activates the degraded arrays (scripts/local-premount/mdadm). However, it does not get the chance to do so before the scripts try to open the LUKS device with the configured UUID, since this is done by scripts/local-top/cryptroot. "*-top" scripts are run before "*-premount" scripts. Workaround / solution I made it work again by linking /usr/share/initramfs-tools/scripts /local-premount/mdadm -> /etc/initramfs-tools/scripts/local- top/mdadm, then rebuilding my initramfs (update-initramfs -u). It seems to work well. Not sure if it's the best or even a clean approach. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1196693/+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 1403982] Re: mini.iso installer cannot load additional components
I've just hit this trying to do a netinstall of vivid. Looking at the source, algorithm 10 is sha512. The binary for the installer is built with --enable-minimal, which disables sha512, but then it isn't specifically enabled. Attached patch to enable it. I've tested this by building it myself and using wget to replace the included binary with mine, I successfully completed the install. ** Patch added: "gnupg-1.4.18 enable sha512 for minimal.patch" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1403982/+attachment/4294018/+files/gnupg-1.4.18%20enable%20sha512%20for%20minimal.patch ** Also affects: gnupg (Ubuntu) Importance: Undecided Status: New ** Changed in: gnupg (Ubuntu) Status: New => Confirmed ** Tags removed: precise ** Tags added: vivid ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1403982 Title: mini.iso installer cannot load additional components Status in gnupg package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Bug description: system: Ubuntu Vivid 32-bit current daily mini.iso Computer: http://www.toshiba.se/laptops/satellite-pro/c850/satellite- pro-c850-19w/ Dialogue: "Choose a mirror to use and press enter. If you have a http proxy type its details now, otherwise just press enter." The installer does not start loading additional components. Instead it complains: "Downloading a file failed" Retry Change mirror Cancel I have tried several national mirrors, and also 'archive.ubuntu.com' No mirror can provide that file, and the installation gets stuck here. Failing process: udpkg, net-retriever, or maybe missing files in the mirrors? There is nothing wrong with my internet connection: ping ubuntu.com works (from this Vivid alpha mini.iso) Ubuntu 14.04 LTS mini.iso works, can install systems The automatically attached files have nothing to do with the bug. They were created in another computer because I could not create the report in the simple system running in the beginning of the mini.iso installation process. So they were removed. ProblemType: Bug DistroRelease: Ubuntu mini.iso 15.04 version 20101020ubuntu356/ 16-Dec-2014 01:28 Architecture: i386 Date: Thu Dec 18 19:23:55 2014 MarkForUpload: True PackageArchitecture: all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1403982/+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 1086783] Re: New PolicyKit 0.106 changes configuration file format
Could policykit be updated if it was ported to mozjs45? It would be good if we could see it updated eventually as the javascript rules are much more flexible (one use would be restricting users to specific domains with libvirt). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1086783 Title: New PolicyKit 0.106 changes configuration file format Status in policykit-1 package in Ubuntu: Triaged Status in policykit-1 package in Debian: Fix Released Bug description: From the NEWS file: This is polkit 0.106. There's a major change in this release which is a switch from .pkla files (keyfile-format) to .rules files (JavaScript). We may want to hold off on the new version because it requires rewriting the configuration files, and adds a dependency on mozjs185, which will need a MIR (and getting a MIR may be problematic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1086783/+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
