[Bug 1279021] Re: CacheDir setting ignored
I can confirm this is still there with 0.7.27-1. Just create a directory somewhere else, assign the correct permissions, put it into the CacheDir setting of ACNG, restart the service - the new dir won't be used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279021 Title: CacheDir setting ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1279021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1163184] Re: New upstream microreleases 9.1.9, 8.4.17
I don't see why the urgency is set to low here. The news entry on the PostgreSQL website states clearly All users of the affected versions are strongly urged to apply the update *immediately*. And the definition of urgency in the Debian policies (unofortunately I haven't been able to find something corresponding on ubuntu.com) is rather clear as well: http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Urgency -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1163184 Title: New upstream microreleases 9.1.9, 8.4.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/1163184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1163184] Re: New upstream microreleases 9.1.9, 8.4.17
Alright, thanks for the clarification Martin. I'm still used to my old Debian world ;) Thanks for having the updated packages ready by now. How long do you expect to take them until they hit the repositories? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1163184 Title: New upstream microreleases 9.1.9, 8.4.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/1163184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610125] Re: pam_motd runs commands as root with unsanitised environment
Could we get an update here, please? There's a fix available for almost one and a half years now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/610125 Title: pam_motd runs commands as root with unsanitised environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/610125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579112] Re: compiz crashes on alt-tab when gitk is running
** Bug watch added: Debian Bug tracker #612560 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612560 ** Also affects: compiz (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612560 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/579112 Title: compiz crashes on alt-tab when gitk is running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/579112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579112] Re: compiz crashes on alt-tab when gitk is running
I can reproduce this issue on my Maverick system here as well, with one special point worth being mentioned: this happens *only* if I manually configure wish to be provided by /usr/bin/wish8.5 instead of the default /usr/bin/wish8.4 using this command (and selecting the appropriate version): sudo update-alternatives --config wish gitk has to be restarted after switching wish of course... If I switch it back to the default, compiz doesn't crash on alt-tab anymore. I really hope this isn't one of the bugs where a solution is well known and available, but Ubuntu simply doesn't provide fixed packages. After all, Maverick is still in the middle of its regular support lifecycle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/579112 Title: compiz crashes on alt-tab when gitk is running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/579112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721320] Re: DKIM-related failures should not end up in the panic log
Ok, so what's the plan regarding the long term in LTS? There is a fix released upstream, but nothing happened with the exim4 package in lucid. To quote the inital reporter of this bug: Can we please have a backport of this fix for Lucid - it makes running an Exim mailserver painful on that release. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to exim4 in Ubuntu. https://bugs.launchpad.net/bugs/721320 Title: DKIM-related failures should not end up in the panic log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/721320/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 721320] Re: DKIM-related failures should not end up in the panic log
** Bug watch added: Debian Bug tracker #567876 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567876 ** Also affects: exim4 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567876 Importance: Unknown Status: Unknown ** Bug watch added: bugs.exim.org/ #966 http://bugs.exim.org/show_bug.cgi?id=966 ** Also affects: exim via http://bugs.exim.org/show_bug.cgi?id=966 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to exim4 in Ubuntu. https://bugs.launchpad.net/bugs/721320 Title: DKIM-related failures should not end up in the panic log To manage notifications about this bug go to: https://bugs.launchpad.net/exim/+bug/721320/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 721320] Re: DKIM-related failures should not end up in the panic log
Ok, so what's the plan regarding the long term in LTS? There is a fix released upstream, but nothing happened with the exim4 package in lucid. To quote the inital reporter of this bug: Can we please have a backport of this fix for Lucid - it makes running an Exim mailserver painful on that release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721320 Title: DKIM-related failures should not end up in the panic log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/721320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721320] Re: DKIM-related failures should not end up in the panic log
** Bug watch added: Debian Bug tracker #567876 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567876 ** Also affects: exim4 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567876 Importance: Unknown Status: Unknown ** Bug watch added: bugs.exim.org/ #966 http://bugs.exim.org/show_bug.cgi?id=966 ** Also affects: exim via http://bugs.exim.org/show_bug.cgi?id=966 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721320 Title: DKIM-related failures should not end up in the panic log To manage notifications about this bug go to: https://bugs.launchpad.net/exim/+bug/721320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 508545] Re: Aptitude ignores /etc/apt/preferences.d/*
** Tags added: maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/508545 Title: Aptitude ignores /etc/apt/preferences.d/* -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769595] Re: Encrypted home not mountable under chroot
Thanks a lot guys for finding the solution to this issue. Behavious is identical as described above on Maverick/10.10 (both, bug + solution). ** Tags added: maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/769595 Title: Encrypted home not mountable under chroot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 592891] Re: mountall: Assertion failed in main: udev_monitor = udev_monitor_new_from_netlink (udev, udev)
*** This bug is a duplicate of bug 516684 *** https://bugs.launchpad.net/bugs/516684 I think this is very likely a duplicate of bug #516684 ** This bug has been marked a duplicate of bug 516684 After upgrade from Karmic boot fails, mountall and udevd fail * You can subscribe to bug 516684 by following this link: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/516684/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/592891 Title: mountall: Assertion failed in main: udev_monitor = udev_monitor_new_from_netlink (udev, udev) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581566] Re: udevd inotify_add_watch no such directory error for physical volumes
** Tags added: boot -- udevd inotify_add_watch no such directory error for physical volumes https://bugs.launchpad.net/bugs/581566 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 581566] Re: udevd inotify_add_watch no such directory error for physical volumes
This bug makes my boot-process stop for about 10-15 seconds, so it is really bugging me - what can be done to improve the situation? -- udevd inotify_add_watch no such directory error for physical volumes https://bugs.launchpad.net/bugs/581566 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 563805] Re: mount.cifs won't mount shares; set uid bit not set
I think Dietmar's comment #5 is pretty interesting: the binaries in 9.10 did *NOT* have the suid-bit set, but it definitely worked for me back then (and for others too, as they reported). So there must have been a way to make this work. Have there been any of the mechanisms mentioned by Wladimir involved in 9.10? -- mount.cifs won't mount shares; set uid bit not set https://bugs.launchpad.net/bugs/563805 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 581566] Re: udevd inotify_add_watch no such directory error for physical volumes
Confirming this bug, similar situation here with multiple partitions defined as LVM physical volumes belonging to a volume group. sudo fdisk -l /dev/sda Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xae329394 Device Boot Start End Blocks Id System /dev/sda1 * 1633250861758+ 7 HPFS/NTFS Partition 1 does not end on cylinder boundary. /dev/sda26333 38913 261706882+ 5 Extended Partition 2 does not end on cylinder boundary. /dev/sda563337087 6056473+ 83 Linux /dev/sda67087 1073429294496 83 Linux /dev/sda7 28470 3369141945683+ 8e Linux LVM /dev/sda8 33692 3891341945683+ 8e Linux LVM /dev/sda9 23248 2846941945683+ 8e Linux LVM /dev/sda10 18026 2324741945683+ 8e Linux LVM /dev/sda11 12804 1802541945683+ 8e Linux LVM /dev/sda12 10735 1280316619211 83 Linux Partition table entries are not in disk order ** Tags added: amd64 -- udevd inotify_add_watch no such directory error for physical volumes https://bugs.launchpad.net/bugs/581566 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 441367] Re: inotify_add_watch(6, (null), 10) failed: Bad address
There has recently been reported a similar bug to this one (although I suppose it is *not* a real duplicate of this one), concerning partitions declared as physical volumes for LVMs: #581566 -- inotify_add_watch(6, (null), 10) failed: Bad address https://bugs.launchpad.net/bugs/441367 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 581566] Re: udevd inotify_add_watch no such directory error for physical volumes
bug 441367 could be related, although it does not seem to be a real duplicate -- udevd inotify_add_watch no such directory error for physical volumes https://bugs.launchpad.net/bugs/581566 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 563805] Re: mount.cifs won't mount shares; set uid bit not set
I think Dietmar's comment #5 is pretty interesting: the binaries in 9.10 did *NOT* have the suid-bit set, but it definitely worked for me back then (and for others too, as they reported). So there must have been a way to make this work. Have there been any of the mechanisms mentioned by Wladimir involved in 9.10? -- mount.cifs won't mount shares; set uid bit not set https://bugs.launchpad.net/bugs/563805 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 569543] Re: Could not identify preference: username Could not identify preference: session_key failure yet authed for services
The conclusion from my last report seems to me that it should be problematic to register the same facebook-account on multiple gwibber clients (should be verified, I think...) -- Could not identify preference: username Could not identify preference: session_key failure yet authed for services https://bugs.launchpad.net/bugs/569543 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 569543] Re: Could not identify preference: username Could not identify preference: session_key failure yet authed for services
Well, so I had to learn how to debug python myself... If you're not interested in details, jump straight to the bottom of this message. To see what's going on, I added the python-debugger to /usr/share/pyshared/gwibber/lib/gtk/facebook.py by adding import pdb at the end of the other import statements at the top of the file. After fiddling around a bit, I discovered the crucial point in on_facebook_auth_title_change(), so I added a pdb.set_trace() right after the first try: statement in that function (see the attached diff if unclear). This makes python stop just after the facebook-connect has returned Success (which causes the facebook authorized state described in earlier posts). Here's the debugger's trace from that very position: /usr/lib/python2.6/dist-packages/gwibber/lib/gtk/facebook.py(115)on_facebook_auth_title_change() - url = web.get_main_frame().get_uri() (Pdb) (Pdb) n /usr/lib/python2.6/dist-packages/gwibber/lib/gtk/facebook.py(116)on_facebook_auth_title_change() - data = json.loads(urlparse.parse_qs(url.split(?, 1)[1])[session][0]) (Pdb) n IndexError: 'list index out of range' /usr/lib/python2.6/dist-packages/gwibber/lib/gtk/facebook.py(116)on_facebook_auth_title_change() - data = json.loads(urlparse.parse_qs(url.split(?, 1)[1])[session][0]) (Pdb) n /usr/lib/python2.6/dist-packages/gwibber/lib/gtk/facebook.py(151)on_facebook_auth_title_change() - except: (Pdb) p url 'http://www.facebook.com/connect/login_success.html' (Pdb) p data 'Success' This explains why the Add button does not show up, the split-statement fails since the url variable does not contain any of the expected information. So the try-except block stops right after the data=... line which clearly explains why the Add button still is missing. So the reason is that facebook returns an URI in a format quite different from what expected from gwibber. First idea (already mentioned in an earlier post): language-related. Turns out to be the wrong direction, switching facebook to english doesn't make a difference. But: clicking through my fb-settings, I discovered that Gwitter is already registered as an application having access to the fb-profile, even though the registration process never completed successfully in my gwibber client. Must be due to an earlier registration attempt failing (in gwibber, but not in facebook!) due to the keyring-bug (LP: #571224). So the SOLUTION was to me: remove Gwibber from the list of applications (in your facebook-profile), then start all over with gwibber-client. Now the URI returned after completing the login contains all the information expected by gwibber and registration works! Wohoo. Enjoy. ** Patch added: statements added for debugging (not meant to be integrated in the package) http://launchpadlibrarian.net/48447526/debug-gwibber-fb.diff -- Could not identify preference: username Could not identify preference: session_key failure yet authed for services https://bugs.launchpad.net/bugs/569543 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 569543] Re: Could not identify preference: username Could not identify preference: session_key failure yet authed for services
Ping, I'd really like to continue debugging this. No suggestions, nobody? -- Could not identify preference: username Could not identify preference: session_key failure yet authed for services https://bugs.launchpad.net/bugs/569543 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 501479] Re: Codec Error - Cannot select the MPEG-4 SP codec
Confirming this bug in Lucid. Works fine with avidemux-qt, fails with the Gtk-version. -- Codec Error - Cannot select the MPEG-4 SP codec https://bugs.launchpad.net/bugs/501479 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 569543] Re: Could not identify preference: username Could not identify preference: session_key failure yet authed for services
Magnus, I'm pretty sure this is still the old package (I ran into the same issue earlier today). aptitude changelog gwibber shows nothing about this bug, so we probably have to be patient until the new package is ready... -- Could not identify preference: username Could not identify preference: session_key failure yet authed for services https://bugs.launchpad.net/bugs/569543 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 569543] Re: Could not identify preference: username Could not identify preference: session_key failure yet authed for services
Ah well, my mistake. There is no changelog available yet through aptitude since http://changelogs.ubuntu.com/changelogs/pool/main/g/gwibber/ only has changelogs for the 0ubuntu2 version. Looking into the .diff.gz from http://archive.ubuntu.com/ubuntu/pool/main/g/gwibber/gwibber_2.30.0.1-0ubuntu3.diff.gz reveals the following changelog though: +gwibber (2.30.0.1-0ubuntu3) lucid-proposed; urgency=low + + * debian/patches/lp_569543.patch +- Don't allow people to click Add before we have enough information + from facebook to add the account (LP: #569543) + + -- Ken VanDine ken.vand...@canonical.com Mon, 03 May 2010 10:58:47 -0400 -- Could not identify preference: username Could not identify preference: session_key failure yet authed for services https://bugs.launchpad.net/bugs/569543 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 569543] Re: Could not identify preference: username Could not identify preference: session_key failure yet authed for services
Reset tags to verification-needed as it does not work for Magnus Stefanus and myself. ** Tags added: verification-needed ** Tags removed: verification-done -- Could not identify preference: username Could not identify preference: session_key failure yet authed for services https://bugs.launchpad.net/bugs/569543 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 569543] Re: Could not identify preference: username Could not identify preference: session_key failure yet authed for services
Ken, I still suffer from the above problem described by Magnus Stefanus, though you're right with your interpretation of the german localized message Mit Facebook verbunden (it reads Facebook authorized on my system here since I don't like to live in a localized Linux, apart from being a native german speaker). How can I help do debug this any further? Maybe it *is* language- related, since my facebook-account is localized in german, as well as it is probably for Magnus' account (just my personal guess). Nevertheless, don't know if this makes any difference at all... (Btw, I didn't click on the Add button in the version shipped with lucid-vanilla until it showed the Facebook authorized message, yet the behaviour was the same as described in this bug. Just to be precise.) -- Could not identify preference: username Could not identify preference: session_key failure yet authed for services https://bugs.launchpad.net/bugs/569543 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
