[Bug 79371] Re: saslauthd init script does not allow movement of PID

There is an undocumented option to imapd.conf ``sasl_saslauthd_path'' which instructs the daemon to look in a non-standard location for the socket. I've opened a bug upstream with the Cyrus maintainers. Perhaps Ubuntu should update the imapd and imap.conf manpages to reflect this useful option?

[Bug 138931] Re: Can't use saslauthd to authenticate both postfix and cyrus due to /var/run/saslauthd being on tmpfs

There is an undocumented option to imapd.conf ``sasl_saslauthd_path'' which instructs the daemon to look in a non-standard location for the socket. I've opened a bug upstream with the Cyrus maintainers. Perhaps Ubuntu should update the imapd and imap.conf manpages to reflect this useful option? --

[Bug 107149] Re: python 2.5.1c1 version mismatch with libapache2-mod-python on feisty

This is unbelievable. When will a fix be available!? -- python 2.5.1c1 version mismatch with libapache2-mod-python on feisty https://bugs.launchpad.net/bugs/107149 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs ma

[Bug 109887] Re: ipw3945: Error sending LEDS_CMD. Random driver crash.

One more thing: These hangs seem to only happen at the office, where our wireless infrastructure is built on Apple AirPorts. I can't recall ever seeing this hang at home (non-Apple wireless). How does this correlate with others' experiences? -- ipw3945: Error sending LEDS_CMD. Random driver cr

[Bug 109887] Re: ipw3945: Error sending LEDS_CMD. Random driver crash.

razboinik writes that the following works: /etc/init.d/networking stop ; modprobe -r ipw3945 ieee80211 ; sleep 2 ; modprobe ipw3945 ieee80211 I can confirm that this works -- but first I have to switch off the wireless card using the hardware switch. I repeat -- if you can't get the module t

[Bug 159432] Re: python-mode does not autoload on emacs21

I have this problem on a clean install of gutsy; the fix above works. I've attached a patch to the file; if you want to try the fix and don't know enough Lisp to do it yourself, apply the patch as follows: sudo patch -p0 < patch ** Attachment added: "patch" http://launchpadlibrarian.net/10

[Bug 62346] Re: Missing libobrender.so.1 -> unable to launch obconf

Does this mean that the fix will be backported to edgy? -- Missing libobrender.so.1 -> unable to launch obconf https://launchpad.net/bugs/62346 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 68663] Re: [Edgy] Incompatible with Google Toolbar.

Ah, silly me. My lockups were due to a botched Flash plugin. My above workaround appears to be just fine. -- [Edgy] Incompatible with Google Toolbar. https://launchpad.net/bugs/68663 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 68663] Re: [Edgy] Incompatible with Google Toolbar.

So I'm seeing lockups in Firefox. I've disabled Google Toolbar, if I lockup again (i.e. due to "something else") I'll report back. Until then, perhaps somebody can replicate my above procedure and verify whether it works or causes problems? -- [Edgy] Incompatible with Google Toolbar. https://la

[Bug 68663] Re: [Edgy] Incompatible with Google Toolbar.

Here's a (mostly) pain-free workaround. I *suspect* this won't cause undue problems; would somebody with more understanding of Moz plugins please validate? Go to www.getfirefox.com. Download version 2.0. Untar it (tar -xzvf firefox-whatever version). Change to the new directory, and run the fi

[Bug 73651] xearth unmet dependencies

Public bug reported: xearth: Depends: libice6 but it is not going to be installed or xlibs (> 4.1.0) but it is not installable Depends: libsm6 but it is not going to be installed or xlibs (> 4.1.0) but it is not installable Depends: libx1