Trying to access the nsILoginManager generates errors. Also, site passwords not saved in Tb Password Manager.  Master password appears to be saved, but I'm never prompted to enter it when accessing password fields.
By "site passwords" I should say "password fields".  For instance, I am trying to save a site's password in my extension's options dialog window.
However we will more than likely be switching Thunderbird to toolkit's password manager for beta 2. Although your extension would then work with 2.x builds.
%configure used to copy config.sub and config.guess files from /usr/share/libtool/config into the top source directory. That's not a good idea when you try to build a newer libtooll to update those files...  I haven't checked for a while if %configure still does that, though.
Hmm, according to the build logs %configure is just a macro that exports compiler flags and calls ./configure with a bunch of arguments that set destinations, for example on rawhide i586 the arguments are
The spelling errors can be ignored as spell doesn't know about auto{conf,make} tools and marks their names as errors.
libtool is an arch package as it has some paths to arch dependend gcc stuff in it, it cannot be a noarch package even though it has no binaries. 
I'm not sure about the debuginfo errors/warnings. libtool ships no .libs subdir and doesn't create /usr/lib/debug, so this might be a rpmlint bug. My umask is set to 0002, which is quite common and shouldn't lead to rpmlint errors.
Should rpmlint be run on the debuginfo packages, btw ? I couldn't find anything about it on our wiki.
shared-lib-calls-exit: There's exactly one exit call in libltdl and that one is in the alloc_die_default function with the comment '/* Unless overridden, exit on memory failure.  */' This function isn't called by anything in libtool-* and is used as some kind of template which should be overwritten when required. 
So the real fixes in -19 are the conversion of the changelogs to utf8, the move of some documentation to the ltdl-devel subpackage and the selfchecks are now enabled
I have just discovered BZ 817187 which supplies a solution to my missing grub2 menu during boot.  Either the solution of Comment 15 or 16 restores my menu.
Of course, this offers no solution to the brain-dead construction of menuitems that combine kernels and root partitions that are incompatible.
I am happy to have a working menu that at least allows me to choose which kernel to boot, even if many of the choices simply cannot work.
You should not share the same /boot across distros. In most cases you shouldn't need separate /boot at all. If you do need you can have a partition with /fX directories and make the /boot symlinks to them. As for video problem can you try an explicit GFXMODE? What does videoinfo say? It's similar to 827003.
> You should not share the same /boot across distros. In most cases you shouldn't > need separate /boot at all.
I have 'always' used a single boot partition with multiple root partitions specifically so that the boot menu could allow me to choose which kernel, old or new, to boot.  That, after all, is the explicit purpose of grub.  
If I have separate, different /boot directories within each of several root partitions, please explain to me how the Master Boot Record will be able to transfer control to a single menu that will permit me to choose one of the several kernels housed within the multiple root partitions.
My current grub.cfg is heavily edited to remove the many non-functional entries.  This took hours of work because I dared not make a mistake, and  grub.cfg is very hard to read.
If so, based on prior experience, I think it will render my system unbootable again, and I'll be unable to repair the damage.  
Sorry for the multiple comments.  Bugzilla gave me this error message and there was no obvious way to overcome it.
So Vladimir, if you wanted to install F17 alongside of F16, (two root file systems) sharing /home, how would YOU do it? Where, exactly, would YOU put the boot information for the multiple roots other than in a shared boot partition? Since the info for the two systems needs to be shared, commonly available to the boot mechanism, how do you do it without sharing it? Telling me "I shouldn't do it" is not helpful, but is condescending.
It really would be nice if the Fedora developers realized that they're making so many huge changes to the system (grub2, systemd, now F18's messed up Ubuntu-wanna-be attention-deficit-disorder installer, and gnome3) that it would be nice if their "improvements" didn't wreak havoc on pre-existing installations. Since there is a significant chance that the new system won work well, it's nice to be able to boot back into the old system. This whole "we don't care about what was/is on your system" mentality is juvenile. Fedora used to show the user a modicum of respect.
In 3 or 4 iterations of grub2, Fedora STILL can't made it so that multiple FEDORA versions can EASILY coexist? WHY NOT?!?!? My father's comments about grub2 being a mess are absolutely correct.
If this sample app is launched with a network connection and a request is sent, the request succeeds. If then connection to the internet is lost, the request of course fails, but upon reconnecting to the internet the request sent succeeds right away. 
In contrast, if after app launch the first request is sent with no internet connection you get a NameResolutionFailure exception for obvious reasons (no network). However if you then reconnect to the internet subsequent requests will continue to fail with NameResolutionFailure  exception for a couple of minutes, but eventually will succeed. 
As stated, eventually if you keep sending requests the after step 8 above, the request will work after a couple of minutes. 
The  attached sample is using a HttpWebRequest however I have other customers reporting the same issue  using HttpClient.  
This issue initially was reported against Xamarin Android (bug #45383, marking as a duplicate of this bug). I initially I thought this was a DNS caching issue and was able to resolve in another customers test case by making sure no request was sent when the network was not available. I found some posts that Android caches bad DNS queries and thought that was the issue. But upon discovering that XA 6.1.2.21 does not display this issue, I reconsidered. Also, upon further reading and investigation, I found out that the bad DNS query should only be cached for 10 seconds while the NameResolutionFailure exception persists for a couple of minutes after restoring network connection. But after reports of this occurring on iOS, I tested with a Mono console app and was able to reproduce. 
The workaround for this would seem to be to test for network connectivity before sending your request, and to use a different url to test for connectivity than the one you need to send requests to.
Any update on this? this has been highlighted as a priority issue by our senior management, as it's regression bug it's very hard to explain away!
unfortunately, this fix has missed the cutoff for C8SR2 (which is to hit stable on Dec 22). It will, however, be included in the next C9 Alpha refresh (if I recall correctly, this will be the 7th Alpha).
In reading the release notes for C9 I don't see this bugzilla referenced but perhaps I missed it. Can you confirm?
Just ran some tests on latest C9 from beta channel and appears fix rolled out although I don't see it listed in release notes either. :)
I have double checked and this bug is resolved in the current Cycle 9 stable builds. I tested Mono Console app, iOS and Android. All worked as expected. 
I suspect you are hitting a different issue. You did not even mention getting the nameResolutionFailure. Please note that I have seen many cases where Apple rejected an app on IPv6 compatibility grounds when the issue was actually something completely different. For example one app was rejected by Apple stating IPv6 Compatibility problems when the actual issue was the app crashing on startup due to a missing permission description for microphone usage. So I would suggest contacting Apple for a better assessment of what they found in your app to cause the rejection.
Last technology detected on 17th March 2016. We know of 9 technologies on this page and 7 technologies removed from luo.be since 3rd September 2012. Link to this page.