[17:13] mattymo: just for completeness, I run eeebotu === Logan_ is now known as UtopicUnicorn === roadmr is now known as roadmr_afk === roadmr_afk is now known as roadmr [18:48] bdmurray <> Sinistrad [18:48] Greetings! [18:49] Sinistrad: is there a file ~/.cache/update-manager-core/meta-release on system? if not what about /var/lib/update-manager/meta-release [18:50] bdmurray: checking [18:51] bdmurray: Both are there. They have the same file size too [18:51] Sinistrad: okay and does it look like this? http://changelogs.ubuntu.com/meta-release [18:51] if not just delete them and try again [18:53] They look nothing like that. Lots of html with xml tags [18:54] Sinistrad: probably from some captive web portal somewhere [18:54] bdmurray: If the files are useful, I can add them to the bug tracker [18:55] Sinistrad: nope, not really the problem is understood [18:56] bdmurray: Very well then. Thanks for the workaround! I'll test it out and leave to keep your channel clean if it works. [18:56] thanks though [18:58] bdmurray: The rest of the files in there look the same...I'll delete those as well. === roadmr is now known as roadmr_afk [19:12] bdmurray: That didn't work. I deleted those files, did an apt-get update, upgrade (no packages to upgrade), and then tried do-release-upgrade. "No new release found" [19:14] Sinistrad: and did those files appear again? [19:15] Some did [19:16] and are they plain text or xml / html? [19:17] ./var/lib/update-manager/meta-release-development appeared and it was the xml/html [19:19] meta-release-development should only matter if you are using the 'do-release-upgrade -d' [19:19] if you aren't we are curious about meta-release [19:30] if the cached meta-release files are currently getting saved as html then you are currently on a network that is causing the issue [19:32] I'm off for lunch but will be happy to continue working on this with you after that === roadmr_afk is now known as roadmr [20:03] bdmurray: Looking through the files, it has lots of info about the corporate firewall. I'll have to take this home and try it. [20:09] Sinistrad: okay, be sure to clear the cache after you change networks [20:16] bdmurray: Will do! Thanks for helping me out. === bschaefer_ is now known as bschaefer [21:16] Woah. I found a slightly nasty bug, and just reported it today, but I may need assistance classifying it under the correct package. [21:16] https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1311847?comments=all [21:16] Launchpad bug 1311847 in unity-settings-daemon (Ubuntu) "Neither Print, SHIFT+Print, nor CTRL+Print keyboard shortcuts work on Trusty" [Undecided,New] [21:17] A lot of Googling has revealed it affects multiple desktop environments, and also mainly a subset of HP laptops, and may be systemd or something else causing it. [21:18] I know how to describe the bug perfectly, but I may need assistance filing it under the correct package. [21:19] I've tried #ubuntu, but everyone's educated guesses were just as my initial thoughts. I think it may be stemming from something deeper. [21:30] MikeRL: IDK either, but unity-settings-daemon is a good start (it can be changed later). It is probably that the folks at #ubuntu-desktop would know more, though [21:31] hggdh: Thanks. I'll try there. [21:37] isn't the key called PrintScreen? [21:38] Well, technically yes. [21:40] Happy now? Refresh the page. === NoNameYet_xnox is now known as xnox [22:50] I was just momentarily confused because my keyboard has "Print" on top of the F12 key and F12 on the front of it.