[Bug 1779871] [NEW] Ubuntu automatically suspends the laptop for the background user when switching back to it from the foreground user.
Public bug reported: To reproduce: 1. Install Ubuntu 18.04 on a laptop 2. Create two user accounts 3. Login to the first account and switch to the second account 4. Disconnect the power plug and work (while on the battery) from one (or the other) account for some time (more than 20 minutes which is default according to the "gsettings get org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout" CLI command) 5. When switching a user back to the other account, it will automatically suspend the laptop. Workaround: For each(!) user disable "Automatic suspend" in the Power settings or same with the CLI command: gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'nothing' Bug? I think it is as having the multiuser session, switching back to the background user it should not immediately force the laptop sleep due to the background user inactivity. How to solve it? gnome-settings-daemon should probably not take into account the inactivity timer (or rather reset it) when there are other foreground users are using Ubuntu. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: bionic xenial ** Summary changed: - Ubuntu automatically suspends the laptop for the background user when switching back to it from the other user. + Ubuntu automatically suspends the laptop for the background user when switching back to it from the foreground user. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779871 Title: Ubuntu automatically suspends the laptop for the background user when switching back to it from the foreground user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1779871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667838] Re: zpool export mpu1pool cannot export 'mpu1pool': pool is busy
Hi, sorry, I have missed your reply of 2018-07-17. I wanted to highlight that ZFS's export was blocked until "swapoff -a" command was ran. Then, I have mentioned in the OP that the filesystem was unmounted, hence there was no possibility for any file to be opened. And what information was requested in the comment #1? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667838 Title: zpool export mpu1pool cannot export 'mpu1pool': pool is busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1667838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787712] Re: 16.04 to 18.04 do-release-upgrade fails with "Command terminated with exit status 1"
I've had this issue: # do-release-upgrade -f DistUpgradeViewNonInteractive Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1240 kB] Fetched 1241 kB in 0s (0 B/s) authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg' extracting 'bionic.tar.gz' MarkInstall libpam-cap [ amd64 ] < none -> 1:2.25-1.2 > ( libs ) FU=1 No candidate ver: linux-image-4.4.0-131-generic No candidate ver: linux-image-4.4.0-135-generic No candidate ver: linux-image-extra-4.4.0-131-generic No candidate ver: linux-image-extra-4.4.0-135-generic No candidate ver: linux-signed-image-4.4.0-131-generic No candidate ver: linux-signed-image-4.4.0-135-generic # echo $? 1 Then it worked after I ran: apt-get autoremove Not sure, though, whether that was the issue... I'd rather blame that had something to do with the network/mirror. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787712 Title: 16.04 to 18.04 do-release-upgrade fails with "Command terminated with exit status 1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1787712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603600] Re: NetworkManager ignores pushed openvpn routes
The same issue :-/ Ubuntu 16.04.4 LTS network-manager-openvpn 1.1.93-1ubuntu1.1 network-manager-openvpn-gnome 1.1.93-1ubuntu1.1 I am usually setting: VPN connection settings -> IPv4 Settings -> Routes... -> [x] Use this connection only for resources on its network. So that my default GW is not changed as I need only the VPN routes. Except that with this bug, the VPN routes are not really applied on my system. When running openvpn on its own, everything is working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603600 Title: NetworkManager ignores pushed openvpn routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1603600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
*** This bug is a duplicate of bug 1751252 *** https://bugs.launchpad.net/bugs/1751252 This patch worked for me https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1751252/comments/37 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
The patch https://code.launchpad.net/~azzar1/ubiquity/+git/ubiquity/+merge/345056 did work for me on my mid-2017 MacBookPro (HW, not VM). Thank you, Andrea! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
Each time I am upgrading Xenial to Bionic I'm getting exactly the same message after few minutes: "*** ntp.conf (Y/I/N/O/D/Z) [default=N] ? " Can this fix get delivered to Ubuntu Xenial? ubuntu-release-upgrader-core 1:16.04.26 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667838] Re: zpool export mpu1pool cannot export 'mpu1pool': pool is busy
Hum, just came across the same issue again: # modinfo zfs | head -2 filename: /lib/modules/4.15.0-43-generic/kernel/zfs/zfs/zfs.ko version:0.7.5-1ubuntu16.4 # sync # echo 3 > /proc/sys/vm/drop_caches # zfs unmount -a # swapoff -a # zpool export WD4Gpool cannot export 'WD4Gpool': pool is busy # lsof nor fuser do not show anything related to the WD4Gpool mountpoints. # dmsetup table does not show anything related to ZFS as expected (I do not have the volume datasets) Please re-open this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667838 Title: zpool export mpu1pool cannot export 'mpu1pool': pool is busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1667838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667838] Re: zpool export mpu1pool cannot export 'mpu1pool': pool is busy
Actually I've just figured why I could not export the pool. One of my docker containers was using the FS, so I could not see it with the "lsof" :/ (mount namespace). I figured when I saw multiple zfs kernel calls with bpftrace :-) I am wondering what would be required for the "zfs unmount -a" to actually fail when its FS is actually used in some other namespace? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667838 Title: zpool export mpu1pool cannot export 'mpu1pool': pool is busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1667838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667838] Re: zpool export mpu1pool cannot export 'mpu1pool': pool is busy
Ok, this is not limited to ZFS. So that's solely due to namespace isolation. "It's not a bug, it's a feature" (c) :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667838 Title: zpool export mpu1pool cannot export 'mpu1pool': pool is busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1667838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809819] [NEW] Ubuntu won't unlock all LUKS devices when booting without "splash" kernel argument
Public bug reported: Ubuntu won't unlock all LUKS devices (with the same passphrase) when booting without "splash" kernel argument. Please see the video I've recorded (in VirtualBox) https://my.nixaid.com/s/epxpwHckGipcB6D It feels like systemd-ask-password-plymouth is trying to use the same passphrase to unlock the rest of the LUKS devices, whilst systemd-ask- password-console isn't. Ubuntu 18.04.1 64-bit ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809819 Title: Ubuntu won't unlock all LUKS devices when booting without "splash" kernel argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1809819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371425] Re: linux-firmware 1.127.5, 1.127.6 causes unstable network connection (likely due to iwlwifi-7260-8.ucode)
** Summary changed: - linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode) + linux-firmware 1.127.5, 1.127.6 causes unstable network connection (likely due to iwlwifi-7260-8.ucode) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371425 Title: linux-firmware 1.127.5, 1.127.6 causes unstable network connection (likely due to iwlwifi-7260-8.ucode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809819] Re: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument
** Summary changed: - Ubuntu won't unlock all LUKS devices when booting without "splash" kernel argument + Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809819 Title: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1809819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809819] Re: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument
** Description changed: - Ubuntu won't unlock all LUKS devices (with the same passphrase) when - booting without "splash" kernel argument. + Ubuntu will not unlock non-root LUKS devices (with the same passphrase) + when booting without "splash" kernel argument. Please see the video I've recorded (in VirtualBox) https://my.nixaid.com/s/epxpwHckGipcB6D It feels like systemd-ask-password-plymouth is trying to use the same passphrase to unlock the rest of the LUKS devices, whilst systemd-ask- password-console isn't. - Ubuntu 18.04.1 64-bit + Ubuntu 18.04.1 64-bit. + + /etc/crypttab: + sda5_crypt UUID=5ba77327-4680-45d1-ba03-ab1b4fc12abb none luks,discard + c4129022-9a34-4eee-9971-0464d92881e0 UUID=c4129022-9a34-4eee-9971-0464d92881e0 none luks + luks-b7e017d7-53c4-4503-b376-c62a1d383f17 UUID=b7e017d7-53c4-4503-b376-c62a1d383f17 none luks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809819 Title: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1809819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
This should fix the issue: # EDITOR=vim systemctl edit apport-autoreport.service [Unit] After=whoopsie.service Wants=whoopsie.service Save. Or instead of doing "systemctl edit", you can just drop these 3 lines to the "/etc/systemd/system/apport-autoreport.service.d/override.conf" file and issue "systemctl daemon-reload" command. Tested: systemctl stop whoopsie.service systemctl stop apport-autoreport.service systemctl start apport-autoreport.service This worked for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Just got the same, shortly after I logged in, I opened VirtualBox (haven't started the VM yet), then Google Chrome -> went to my mails and ... just got logged out of my session! Ubuntu 18.04; gnome-session-bin 3.28.1-0ubuntu3. Logs: Jan 08 10:21:27 REDACTED gnome-session[4856]: gnome-session-binary[4856]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Jan 08 10:21:27 REDACTED gnome-session[4856]: gnome-session-binary[4856]: CRITICAL: We failed, but the fail whale is dead. Sorry Jan 08 10:21:27 REDACTED gnome-session-binary[4856]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Keyboard.desktop Jan 08 10:21:27 REDACTED gnome-session-binary[4856]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Jan 08 10:21:27 REDACTED gnome-session-binary[4856]: CRITICAL: We failed, but the fail whale is dead. Sorry Jan 08 10:21:27 REDACTED virtualbox.desktop[5400]: ICE default IO error handler doing an exit(), pid = 5400, errno = 11 Jan 08 10:21:27 REDACTED bluetoothd[2624]: Endpoint unregistered: sender=:1.107 path=/MediaEndpoint/A2DPSource Jan 08 10:21:27 REDACTED bluetoothd[2624]: Endpoint unregistered: sender=:1.107 path=/MediaEndpoint/A2DPSink Jan 08 10:21:27 REDACTED kernel: rfkill: input handler enabled Jan 08 10:21:27 REDACTED gnome-shell[4958]: gnome-shell: Fatal IO error 0 (Success) on X server :1. Jan 08 10:21:27 REDACTED polkitd(authority=local)[2802]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.100, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_U Jan 08 10:21:27 REDACTED at-spi-bus-launcher[4934]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1" Jan 08 10:21:27 REDACTED at-spi-bus-launcher[4934]: after 145 requests (145 known processed) with 0 events remaining. Jan 08 10:21:27 REDACTED gsd-power[5096]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-wacom[5117]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-xsettings[5118]: gsd-xsettings: Fatal IO error 104 (Connection reset by peer) on X server :1. Jan 08 10:21:27 REDACTED gsd-color[5141]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-clipboard[5137]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-media-keys[5149]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gnome-terminal-[5507]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-color[4623]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_BenQ_Corporation_ZOWIE_XL_LCD_BCH00737SL0_arno_1000 Jan 08 10:21:27 REDACTED systemd[4821]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE Jan 08 10:21:27 REDACTED systemd[4821]: gnome-terminal-server.service: Failed with result 'exit-code'. Jan 08 10:21:28 REDACTED acpid[2618]: client 4841[0:0] has disconnected Jan 08 10:21:28 REDACTED acpid[2618]: client connected from 3353[0:0] Jan 08 10:21:28 REDACTED acpid[2618]: 1 client rule loaded Jan 08 10:21:31 REDACTED gnome-shell[3400]: JS ERROR: TypeError: this._currentWindow is null _setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13 Jan 08 10:21:31 REDACTED gnome-shell[3400]: JS ERROR: TypeError: this._currentWindow is null _setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13 Jan 08 10:21:32 REDACTED gnome-shell[3400]: g_array_unref: assertion 'array' failed Jan 08 10:21:32 REDACTED gnome-shell[3400]: g_array_unref: assertion 'array' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- ubuntu-bugs mail
[Bug 1483989] Re: apt prints wrong duration after update
Ubuntu 18.04.2 LTS here.. got same # apt update && apt -y upgrade && apt -y dist-upgrade && apt -y autoremove Hit:1 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://ppa.launchpad.net/nextcloud-devs/client/ubuntu bionic InRelease Get:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:5 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:7 http://archive.ubuntu.com/ubuntu disco InRelease [243 kB] Hit:8 http://archive.ubuntu.com/ubuntu disco-updates InRelease Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11 Metadata [278 kB] Hit:10 http://security.ubuntu.com/ubuntu disco-security InRelease Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 48x48 Icons [66.6 kB] Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 64x64 Icons [123 kB] Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 DEP-11 Metadata [202 kB] Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 48x48 Icons [176 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 64x64 Icons [348 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 DEP-11 Metadata [2,468 B] Get:17 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 DEP-11 Metadata [7,352 B] Get:18 http://archive.ubuntu.com/ubuntu disco/universe i386 Packages [9,115 kB] Get:19 http://security.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 Metadata [204 B] Get:20 http://archive.ubuntu.com/ubuntu disco/universe amd64 Packages [9,171 kB] Get:21 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 Metadata [20.8 kB] Get:22 http://security.ubuntu.com/ubuntu bionic-security/universe DEP-11 48x48 Icons [12.2 kB] Get:23 http://security.ubuntu.com/ubuntu bionic-security/universe DEP-11 64x64 Icons [45.2 kB] Get:24 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 DEP-11 Metadata [2,464 B] Get:25 http://archive.ubuntu.com/ubuntu disco/universe amd64 DEP-11 Metadata [3,492 kB] Get:26 http://archive.ubuntu.com/ubuntu disco/universe DEP-11 48x48 Icons [2,757 kB] Get:27 http://archive.ubuntu.com/ubuntu disco/universe DEP-11 64x64 Icons [8,459 kB] Fetched 34.8 MB in 213503982334601d 6h 0min 21s (0 B/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. ... apt 1.6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1483989 Title: apt prints wrong duration after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1483989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015819] Re: sb_sasl_generic_pkt_length: received illegal packet length when using Active Directory and ldapsearch and sasl with ssl or tls
Exact same error here in 2019. I set Windows Server 2019 up, default AD DS & AD CS (for TLS). Clients tried: Ubuntu 18.04: libsasl2-modules-gssapi-mit:amd64 2.1.27~101-g0780600+dfsg-3ubuntu2 Alpine Edge: cyrus-sasl-gssapiv2-2.1.27-r1 Have anyone tried asking in Cyrus SASL mailing list? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015819 Title: sb_sasl_generic_pkt_length: received illegal packet length when using Active Directory and ldapsearch and sasl with ssl or tls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1015819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015819] Re: sb_sasl_generic_pkt_length: received illegal packet length when using Active Directory and ldapsearch and sasl with ssl or tls
Thank you, Johnny Westerlund! At least adding "sasl_secprops minssf=0,maxssf=0" to /etc/openldap/ldap.conf works around the error, so things seem to work for me. Not sure whether it is different now for Michael Osipov. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015819 Title: sb_sasl_generic_pkt_length: received illegal packet length when using Active Directory and ldapsearch and sasl with ssl or tls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1015819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809819] Re: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument
** Description changed: Ubuntu will not unlock non-root LUKS devices (with the same passphrase) when booting without "splash" kernel argument. Please see the video I've recorded (in VirtualBox) - https://my.nixaid.com/s/epxpwHckGipcB6D + https://my.nixaid.com/s/odG8zEJ2Z75TdHG It feels like systemd-ask-password-plymouth is trying to use the same passphrase to unlock the rest of the LUKS devices, whilst systemd-ask- password-console isn't. Ubuntu 18.04.1 64-bit. /etc/crypttab: sda5_crypt UUID=5ba77327-4680-45d1-ba03-ab1b4fc12abb none luks,discard c4129022-9a34-4eee-9971-0464d92881e0 UUID=c4129022-9a34-4eee-9971-0464d92881e0 none luks luks-b7e017d7-53c4-4503-b376-c62a1d383f17 UUID=b7e017d7-53c4-4503-b376-c62a1d383f17 none luks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809819 Title: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
