[Bug 577302] Re: ubiquity crashes with error: "InstallStepError: Plugin usersetup failed with code 32"
I finally got around to testing the patch, and I'm pleased to say that it works. Merci beaucoup, Alex! -- ubiquity crashes with error: "InstallStepError: Plugin usersetup failed with code 32" https://bugs.launchpad.net/bugs/577302 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 560415] Re: Lubuntu 10.04 installation crashes
Question: did you try to encrypt your $HOME directory when installing? I'm trying to track down a similar crash (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/577302), except that crashes with a code 32, not 1. -- Lubuntu 10.04 installation crashes https://bugs.launchpad.net/bugs/560415 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577302] Re: ubiquity crashes with error: "InstallStepError: Plugin usersetup failed with code 32"
Here is the relevant portion of /var/log/syslog, although it doesn't seem to report much more than what was in the original error message. One thing of note are the lines: --- May 8 09:50:56 ubuntu user-setup: WARNING: [/dev/sda3] does not appear to be swap space, skipping. May 8 09:50:56 ubuntu user-setup: WARNING: There were no usable swap devices to be encrypted. Exiting. May 8 09:50:57 ubuntu user-setup: mount: mount point /dev/shm does not exist --- /dev/sda3 is definitely my swap partition. It may be worth noting that my older Kubuntu install (Hardy) encrypts the swap space. ** Attachment added: "syslog" http://launchpadlibrarian.net/48041209/syslog -- ubiquity crashes with error: "InstallStepError: Plugin usersetup failed with code 32" https://bugs.launchpad.net/bugs/577302 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577302] Re: ubiquity crashes with error: "InstallStepError: Plugin usersetup failed with code 32"
** Attachment added: "partman" http://launchpadlibrarian.net/48041124/partman -- ubiquity crashes with error: "InstallStepError: Plugin usersetup failed with code 32" https://bugs.launchpad.net/bugs/577302 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577302] [NEW] ubiquity crashes with error: "InstallStepError: Plugin usersetup failed with code 32"
Public bug reported: Binary package hint: ubiquity When installing Kubuntu with the option set for an encrypted $HOME, I get to the "Creating user" stage and I get this error: --- Traceback (most recent call last): File "/usr/lib/ubiquity/bin/ubiquity", line 524, in main(oem_config) File "/usr/lib/ubiquity/bin/ubiquity", line 509, in main install(args[0], query=options.query) File "/usr/lib/ubiquity/bin/ubiquity", line 242, in install ret = wizard.run() File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 460, in run self.progress_loop() File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 863, in progress_loop (ret, realtb)) RuntimeError: Install failed with exit code 1 Traceback (most recent call last): File "/usr/share/ubiquity/install.py", line 2566, in install.run() File "/usr/share/ubiquity/install.py", line 388, in run self.configure_plugins() File "/usr/share/ubiquity/install.py", line 1088, in configure_plugins raise InstallStepError("Plugin %s failed with code %s" % (plugin.NAME, ret)) InstallStepError: Plugin usersetup failed with code 32 --- However, when I install Kubuntu without setting the option for encrypted $HOME, it installs successfully. I have tried searching both the ubiquity source and the ecryptfs source for code 32, but without any luck. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- ubiquity crashes with error: "InstallStepError: Plugin usersetup failed with code 32" https://bugs.launchpad.net/bugs/577302 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 472176] [NEW] No option to encrypt a new user's home directory in KUser
Public bug reported: Binary package hint: kdeadmin I appreciate the option in the new installer in Karmic to encrypt the first user's home directory. However, there doesn't seem to be a similar option in KUser when creating subsequent users. An option to encrypt the home directories of additional users should be included in KUser. ** Affects: kdeadmin (Ubuntu) Importance: Undecided Status: New -- No option to encrypt a new user's home directory in KUser https://bugs.launchpad.net/bugs/472176 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 176675] Re: apt-transport-https: Errors with private repository and GPG keys
Yes, it works now. I took this upstream to Debian, and they fixed it a while ago. Sorry that I didn't report it back here. -- apt-transport-https: Errors with private repository and GPG keys https://bugs.launchpad.net/bugs/176675 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 198841] Re: PKCS #12 Error Importing Client Certificates
Using torbutton-extension 1.2.0rc6 here. -- PKCS #12 Error Importing Client Certificates https://bugs.launchpad.net/bugs/198841 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 198841] Re: PKCS #12 Error Importing Client Certificates
For those of you who have the TorButton extension installed and are running into this problem, disable TorButton entirely (through Tools -> Add-Ons), restart Firefox, install the certificate, and then re-enable TorButton. This worked for me. For other cases, http://groups.google.com/group/mozilla.dev.tech.crypto/browse_thread/thread/f83eff33951b80bf has some insights about PSM, the Firefox code that provides the GUI for the crypto stuff. -- PKCS #12 Error Importing Client Certificates https://bugs.launchpad.net/bugs/198841 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226707] Re: zeroconf service discovery does not work
I stumbled across this bug today and dug around a bit. Apparently, the way that System Settings interacts with Avahi is rather broken. I'm not going to point fingers, but just read the changelog for avahi; it seems as though the left hand doesn't know what the right hand is doing, as one developer applies patches so that the control module interacts one way, while another developer changes the fundamental way that avahi checks itself, so that you get the resulting bug. I haven't bothered to read up on the design policy, but the old enable_avahi script's way of doing things appears to have been deprecated, except someone forgot to remove the checkbox when removing the script. I found a copy of the script (for entertainment purposes, see frode.kde.no/misc/avahi-dapper/enable_avahi and frode.kde.no/misc /avahi-dapper/avahi_status (the other script that was removed)), but those don't work because, as I said, that's now deprecated. But, we still have that annoying checkbox. So let's make it work, shall we? Of course, clicking on the checkbox doesn't make a permanent change, but it does give instructions on how to make those changes permanent. Script 1: /usr/share/avahi/avahi_status #!/bin/sh -e # This is thrown into the public domain; do as thou wilt. # Save (as root, or via sudo) this file as /usr/share/avahi/avahi_status # and set it as executable (sudo chmod a+x /usr/share/avahi/avahi_status) # Simple but effective way to see if Avahi is running: if ps ax | grep "avahi-daemon: running" | grep -v grep 1> /dev/null; then exit 1 # Avahi is running else exit 0 # Avahi is not running fi Script 2: /usr/share/avahi/enable_avahi #!/bin/sh # This is thrown into the public domain; all copyright is disavowed; do as thou wilt. # Save (as root, or via sudo) this file as /usr/share/avahi/enable_avahi # and set it as executable (sudo chmod a+x /usr/share/avahi/enable_avahi) /usr/share/avahi/avahi_status 2> /dev/null; case "$?" in 0) kdialog --title "Starting Zeroconf" --msgbox "Zeroconf is started; to always start Zeroconf on login, make sure that avahi-daemon is set to start at boot in System Settings -> Advanced -> System Services" && /usr/sbin/invoke-rc.d avahi-daemon start ;; 1) kdialog --title "Starting Zeroconf" --msgbox "Zeroconf is stopped; to always prevent Zeroconf from starting on login, make sure that avahi-daemon is set to not start at boot in System Settings -> Advanced -> System Services" && /usr/sbin/invoke-rc.d avahi-daemon stop ;; esac -- zeroconf service discovery does not work https://bugs.launchpad.net/bugs/226707 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 176675] apt-transport-https: Errors with private repository and GPG keys
Public bug reported: Binary package hint: apt-transport-https Package: apt-transport-https Version: 0.7.6ubuntu14 Severity: important I've set up a private apt repository and signed my own packages with my own key. Furthermore, on the client computers I installed apt-transport-https. When I 'apt-get update', however, 50% of the time I get the following warnings: W: Bizarre Error - File size is not what the server reported 0 728 W: GPG error: https://packages.mydomain.org unstable Release: The following signatures were invalid: BADSIG 6A3E7382C8A7B074 Peter Clark <[EMAIL PROTECTED]> W: You may want to run apt-get update to correct these problems When I run 'apt-get update' again, these problems do disappear...only to reappear the next time. So the error appears very consistently, 50% of the time. When I change the relevant line in /etc/apt/sources.list from: deb https://packages.mydomain.org unstable main to: deb http://packages.mydomain.org unstable main everything works fine; no weird file sizes, no GPG errors. I therefore interpret this to mean that the repository and my GPG key are not the problem, which leaves apt-transport-https as the only remaining possibility. Additional note: the SSL certificate served by mydomain.org is self-signed; I don't know if that makes a difference or not. -- System Information: Debian Release: lenny/sid APT prefers gutsy-updates APT policy: (500, 'gutsy-updates'), (500, 'gutsy-security'), (500, 'gutsy') Architecture: i386 (i686) Kernel: Linux 2.6.22-14-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt-transport-https depends on: ii apt [libapt-pkg-libc6.6 0.7.6ubuntu14Advanced front-end for dpkg ii libc6 2.6.1-1ubuntu10 GNU C Library: Shared libraries ii libcurl3-gnutls 7.16.4-2ubuntu1 Multi-protocol file transfer libra ii libgcc1 1:4.2.1-5ubuntu4 GCC support library ii libstdc++6 4.2.1-5ubuntu4 The GNU Standard C++ Library v3 apt-transport-https recommends no packages. -- no debconf information ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- apt-transport-https: Errors with private repository and GPG keys https://bugs.launchpad.net/bugs/176675 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs