[00:02] <ahoneybun> arthurfiggis: not that I'm aware of
[00:02] <ahoneybun> btw darkxst I sent a reply email, also thanks for sending it in the first place :)
[00:11] <arthurfiggis> ahoneybun: there doesn't seem to be any mention of any similar sort of feature that i can find, checking around in the privacy options doesn't show anything either...then again, just because it's not mentioned doesn't mean it's not there I suppose :/ thanks though, i'll have to keep searching to see if there's a clearer or official answer...ubuntu has the dash lens, kubuntu now has their "diagnostics" which sends off error
[00:11] <arthurfiggis> reports with unknown content and is enabled by default...i really hope that ubuntu gnome isn't going down the same route :(
[00:12] <ahoneybun> arthurfiggis: I mean it can search though the Settings in the Dash but nothing it sent that I know of
[00:15] <arthurfiggis> ahoneybun: oh yes, i noticed that as well...by default the "search" goes through just about everything, even virtual machines in gnome-boxes :/ there's just no indication anywhere of whether or not that information is sent off to a third party...i suspect it probably isn't like you say! it'd be nice to know for sure though
[00:16] <arthurfiggis> on the other hand i'd probably just be happy if the backup tool didn't cause gnome's settings panel to crash when you try to open it in 14.10 :) started using backintime instead, that works rather well
[00:19] <darkxst> arthurfiggis, we don't have any amazon cruft in Ubuntu GNOME
[00:23] <arthurfiggis> darkxst: ahh...interesting, thanks for weighing in :) there really isn't much information available on the website regarding ubuntu gnome's "privacy policy" or whether or not it collects any information that it indexes, so it's nice to hear from someone who's attached to the project
[00:24] <arthurfiggis> i tried to get a similar question answered about the "error reports" that kubuntu automatically sends off by default now, but even the people involved don't seem to know what they contain...even if you have a launchpad account you can't actually read them, until you sign up for a completely separate legal document? if they're error reports on your own system i don't see why your access would be limited to them :(
[00:25] <darkxst> arthurfiggis, the error reports can contain personal information if that happened to be in memory at the time of the crash
[00:26] <darkxst> hence why their access is rather restricted
[00:26] <darkxst> the reports themselves are entirely anonymous though (the ones that goto errors.u.c anyway)
[00:28] <arthurfiggis> darkxst, strange, if they're completely anonymous i would think that they wouldn't contain personal information? makes sense that they would want to wall them off a bit if they do, though :)
[00:28] <arthurfiggis> still, the fact that by default it's collecting information on your PC or the like that you're not allowed to read is a bit unnnerving...glad that ubuntu gnome isn't similar in that regard
[00:31] <darkxst> arthurfiggis, I believe all the offical flavours including Ubuntu GNOME send errors reports, and how are you meant to view yours via the web if they are anonymous!
[00:32] <darkxst> the core dump, that would most likely contain useful data though is never publicly available via errors.u.c, it gets processed to generate a backtrace and then deleted
[00:38] <darkxst> launchpad crash reports on the other hand a entire different kettle of fish, which is why they are disabled by default on all stable releases
[00:39] <arthurfiggis> darkxst, oh yes, that's definitely true...even the ubuntu server "spin" has whoopsie and that sends error reports off by default if i remember correctly :) in kubuntu at least, even after a reformat, if you click on the "diagnostics" option in system settings and follow the link it will lead  you to a page full of links of previous error reports, but if you click on -those- links you can't actually read them...so i assume that
[00:39] <arthurfiggis> they're tracked based on some sort of unique identifier and can't be entirely anonymous in that case
[00:40] <arthurfiggis> all the same, if the error reports contain core dumps then it's probably a good thing that they can't be easily accessed by anyone who signs up for launchpad...since obviously they could contain whatever happened to be in memory at the time :)
[00:40] <darkxst> they sound like launchpad crash reports with links to "private" bugs on Launchpad
[00:42] <darkxst> but still access to the coredumps is limited (provided the user doesn't mark their own bug public without removing the coredump)
[00:42] <arthurfiggis> darkxst: yep as far as i know that is the case, you need to sign up for launchpad to get access to them at all, but once you do there's a separate legal document you have to agree to before you're allowed to read them...makes sense, but it also prevents the user from actually determining if they've accidentally uploaded some personal information as well :( if it were a matter of signing up, agreeing and then being able to remove
[00:42] <arthurfiggis> anything that you considered sensitive, i don't think it would be such a problem...but when you can't even read them by default that's a bit...odd
[00:42] <darkxst> arthurfiggis, if you file a crash report on launchpad you can read your own bug
[00:44] <arthurfiggis> darkxst: oh yes, that's no problem at all if you file a crash report yourself :) the kubuntu "feature" i'm referring to seems to be something different entirely...at least different enough that you have to agree to a legally-binding document to even read the things :( filing a crash report on launchpad by comparison is straightforward and you have complete access to it
[00:44] <darkxst> and its entirely up to you wether you actually file a bug for it
[00:45] <darkxst> arthurfiggis, it really sounds like you are mixing up the 2 services however
[00:46] <arthurfiggis> darkxst: possibly, it's a bit dodgy to actually get to the reports in the first place...if you click on the links it takes you to the registration page for ubuntu one accounts, which i was under the impression wasn't even used any more? :)
[00:48] <arthurfiggis> (in order to get to the stage where you're asked to give your personal information and agree to this and that to get access to the automatically collected stuff i had to sign up for launchpad manually)
[00:49] <darkxst> ubuntu one provides the SSO service still
[00:49] <darkxst> its just the cloud service that was shutdown
[00:50] <darkxst> just to be clear reports to errors.ubuntu.com are anonymous, and I don't why kubuntu is directing users there, its supposed to be just "would you like to submit and error report" dialog I think
[00:51] <darkxst> and I very much doubt a random person would even be given access to errors.ubuntu.com
[00:51] <arthurfiggis> darkxst: ahh, okay! wasn't sure if it was the whole thing or just the cloud service that was given the boot, sorry for the misunderstanding...the strange thing is that the people attached to kubuntu that i've spoken with don't seem to know why kubuntu is directing users there either, so i do appreciate your thoughts on the subject...even if they are very offtopic, sorry about that :)
[00:52] <arthurfiggis> more or less i was just bringing it up as a bit of background for why i was concerned about ubuntu gnome doing the same thing, but from what you've described i don't _think_ that's the case...great! :)
[00:53] <darkxst> all flavours send error reports, no idea why kubuntu is redirecting to the website though I don't believe that is default behaviour
[00:55] <arthurfiggis> darkxst: oh you're right, it's definitely not default behaviour...kubuntu is the only flavour of the ubuntu's that i've used that does it in fact
[00:55] <arthurfiggis> (the feature was introduced in 14.04 i believe)
[01:00] <darkxst> arthurfiggis, https://lists.ubuntu.com/archives/ubuntu-devel-announce/2013-May/001039.html
[01:02] <arthurfiggis> darkxst, aha...https://forms.canonical.com/reports/, that's the one :) the link that you eventually get to if you wrangle around with account registrations enough to get there
[01:02] <arthurfiggis> (plus the non-disclosure agreement you have to sign)
[01:03] <ahoneybun> darkxst: I'm installing the 14.04.2 release now with custom partitioning.
[01:03] <darkxst> ahoneybun, great
[01:04] <arthurfiggis> ahoneybun, is 14.04.2 actually out already? i was thinking of switching back to it, the backup tool in 14.10 for ubuntu gnome causes the settings panel to crash out when you click on it :(
[01:04] <darkxst> arthurfiggis, and although anyone can apply, pretty certain the applications for access are manually screened
[01:04] <darkxst> arthurfiggis, that bug will be fixed shortly, just use the standalone deja-dup for now
[01:05] <darkxst> bug 1379446
[01:05] <ahoneybun> arthurfiggis: they are testing it right now, to be released tomorrow, right darkxst?
[01:05] <arthurfiggis> darkxst: by the sounds of it yes, it seems that it's pretty restricted as to who has access to them...and if they contain sensitive information that makes perfect sense! a shame that it's turned on by default though, as i say it may unwittingly upload something sensitive and you'd never know since, as an end user, you don't have access :( thanks for mentioning the bug incidentally, great to know that it's being looked into! i've
[01:05] <arthurfiggis> just been using another one called backintime, it's great so far
[01:07]  * ahoneybun just saves his files on a usb ext drive
[01:10] <darkxst> yes release will be tomorrow unless there are any last-minute hick-ups
[01:10] <arthurfiggis> ahoneybun, same here :) i just use backintime to do it, since (like deja-dup) it does incremental backups...i.e. checks the existing files and backs up the ones that have changed or have been added
[01:10] <darkxst> arthurfiggis, you can probably view the data on your local machine
[01:11] <arthurfiggis> the only reason i stopped using deja-dup was because of that bug mentioned above, but it looks like the ubuntu gnome team is about to bring the fly swatter down on it ;)
[01:11] <darkxst> and although its on by default, it won't automatically send the report unless you click through a dialog
[01:12] <arthurfiggis> darkxst: hmm...that's a good point actually, for the report to have any content to begin with it'd have to be generated on your PC first :) though in the case of kubuntu i never clicked on "send error report," yet when i went to that page there was about twelve links to error reports i never made...as you say i might just simply not have a good idea of how it all works :)
[01:13] <arthurfiggis> the link you posted contains some good information on why it's walled off at least, and it's from a relatively "official" source, so that's much appreciated thanks!
[01:32] <ahoneybun> arthurfiggis: I just copy and paste lol
[01:41] <arthurfiggis> ahoneybun: well hey, as long as it gets backed up, maybe it doesn't hurt to keep things simple ;) i used to do the same thing pretty much, but once i started to get to 500+gb of stuff to sort through i figured i'd let one of the backup programs do the heavy lifting for me :P
[01:42] <arthurfiggis> that's all you really need for a desktop and casual use though, a reliable usb hard drive to throw everything on to once in a while
[01:42] <ahoneybun> yea in that case for sure
[01:43] <arthurfiggis> ahoneybun: it's mostly because it just takes a hell of a long time to copy all of it, whereas the incremental backups, if nothing's changed much, only take a second or two...plus with deja-dup anyway, you can right click right in nautilus and restore or roll back to a previous version of a file :) pretty nice, but not necessary in every case for sure!
[01:47] <ahoneybun> yea
[01:47] <ahoneybun> might try it out again
[01:49] <ahoneybun> I think I just hit the bug you were talking about
[01:53] <arthurfiggis> ahoneybun: yeah, currently the backup icon that you click on normally will just bomb out and crash the settings panel...darkxst posted a link to the bug for it above and it looks like a fix for it will be out soon :) in the meantime there's another very similar program called backintime that does the exact same stuff...works great, has a gnome and a kde interface and it's available under a lot of other distro's too
[01:53] <arthurfiggis> (apt-get install backintime-gnome for the version that looks nice under gnome 3, of course :) )
[01:53] <darkxst> arthurfiggis, errors.u.c generates a hash from the error message this is used to detect dupicates, and is unique to the crash, not anything to do with your pc
[01:54] <darkxst> deja-dup-preferences also runs find and is identical to the panel, just standalone
[01:55] <arthurfiggis> darkxst: ahh, i see! overall it doesn't sound as bad as i was thinking originally, more that it's just walled off so that people other than developers don't get access at whatever was in RAM when your computer exploded ;) i think the confusion just stems from it not being adequately explained, i've learned more about the process here than from browsing around on the websites anyway!
[01:55] <arthurfiggis> it'd be nice if it were default off instead of default on in kubuntu but...eh...not using it any more so it's a bit of a moot point :)
[01:59] <darkxst> it would be useless if it defaulted to off
[02:00] <darkxst> it provides a very clear picture of how critical a crash is
[02:00] <arthurfiggis> darkxst: ...well, that's a good point, can't argue there :) at least you have the choice to turn it off anyway, if you'd really rather not have anything sent off...but yeah, if it defaulted to off they'd never get an error report in the first place
[03:06] <darkxst> arthurfiggis, seems I was slightly wrong, errors.u.c does collect a hash to identify your machine, but that is certainly not something that could be linked back to you
[03:12] <arthurfiggis> darkxst, hmm...i don't know, that doesn't sound quite as encouraging :/ if there's a unique ID _and_ the core dump happened to contain some personal or sensitive information, a person with access to the reports (intending to use them for malicious purposes) could easily identify the person attached to the machine i would think?
[03:12] <darkxst> the core dump is never publically accessible
[03:13] <darkxst> only the backtraces
[03:16] <arthurfiggis> darkxst, ahh, got it...that's a bit more reasonable, though I think it'd be a non issue if people were allowed to read their -own- error reports :) it'd be simple enough to implement if they're already uniquely identifying your system, use that and your ubuntu one/launchpad account for verification and give people access to their own error reports only
[03:17] <arthurfiggis> (on the other hand maybe there's too much of a chance of someone abusing that sort of a system for it to be practical)
[03:18] <darkxst> arthurfiggis, I wonder if that wasn't intended since there is actually a link to your own reports?
[03:18] <darkxst> in the ucc panel
[03:18] <darkxst> (and activity-log-manager)
[03:19] <darkxst> but yeh, it would be really easy to fake that sort of thing
[03:19] <darkxst> in a web request
[03:19] <arthurfiggis> darkxst, that's what i'm wondering, in the case of kubuntu as well, they give you a link to click on that goes directly to a list of reports for your system :) but you can't access them unless you're a developer and you sign up for that non disclosure/binding legal agreement that you linked to earlier...you're very right though, making them more accessible would only make them easier to hack the site and gain access to
[03:19] <arthurfiggis> potentially sensitive info
[03:20] <arthurfiggis> like jackson's law says, with a big enough hammer you can break anything :)
[03:21] <darkxst> there is no sensitive information in the reports, except on the off chance the backtraces contain something, which Ive seen a few times, but usually its a random string that without context is really useful
[03:21] <darkxst> a core dump on the other hand would quite likely provide that context
[03:24] <arthurfiggis> darkxst, the latter of those is what's worrying to me...but i guess it comes down to whether or not you trust the people who have access to the stuff and that's the developers...obviously i trust them or i wouldn't be running their stuff :) but with the right amount of effort any sufficiently complex system can be broken into, so it's good that you have the option to turn the reporting off, just in case you want to be sure that
[03:24] <arthurfiggis> you don't accidentally core dump something personal or sensitive
[03:25] <arthurfiggis> (i actually leave it on and submit reports anyway...i run ubuntu gnome, so if the bug reports help make it better, it's in my best interest :) )
[03:26] <darkxst> at which its probably not even entirely obvious how to turn it off in Ubuntu GNOME
[03:28] <arthurfiggis> darkxst: hmm...actually that's true, in kubuntu at least, you uncheck one box and that's it...no idea how you'd turn it off in ubuntu gnome :/
[03:28] <darkxst> arthurfiggis, you need to run activity-log-manager
[03:28] <darkxst> which may not even be installed by default since its mainly for interacting with zeitgeist
[03:29] <darkxst> but it just so happens to have the 'diagnostics' tab you get in ubuntu privacy panel
[03:29] <arthurfiggis> darkxst: doesn't seem to be installed by default in 14.10 anyway, got a command not found when i tried to run it :) hmm...
[03:33] <arthurfiggis> darkxst: yikes...i just installed it out of curiousity, according to the files and applications menu by default there's a _lot_ of usage info being recorded :/
[03:34] <arthurfiggis> (and of course the error reports option is checked by default, takes you to the same page with the same links as the kubuntu one...but it's not an option that's hidden away in kubuntu, so evidently they're actually more up front about it than I thought)
[03:34] <darkxst> arthurfiggis, that is completely irrelevant for Ubuntu GNOME, and for Ubuntu that is what is being logged/indexed locally that information is never sent to Canonical
[03:35] <darkxst> GNOME does similar but with tracker
[03:35] <darkxst> but again its totally local, and really if someone has access to your local account, well they can get that info either way
[03:38] <arthurfiggis> darkxst, ahh got it...sorry, i was thinking when i read it that it was recording that information and sending it off somewhere, rather than it locally tracking/indexing usage :) you still have the option to turn it off of course, which is nice, though in ubuntu gnome's case you have to install activity-log-manager and a regular user wouldn't even know about that without some serious looking around...it's the first time i've ever
[03:38] <arthurfiggis> heard of it, thanks for letting me know
[03:39] <darkxst> arthurfiggis, that tab won't do jack on Ubuntu GNOME, we don't use zeitgeist
[03:39] <darkxst> (files & applications)
[03:41] <darkxst> on GNOME indexing is controlled by tracker-preferences
[03:41] <arthurfiggis> darkxst, oh, i see! that makes sense that it wouldn't be included by default then, if it only interacts with zeitgeist it wouldn't make much sense :) the "diagnostics" part it'd be nice to have a clickable option somewhere more obvious, but it's a very minor issue really
[03:42] <lams> helo
[03:43] <darkxst> yeh, no idea where though, we are trying to get rid of all the canonical patches in gnome-control-center not add more!
[03:43] <lams> i have a problem with ubuntu gnome, can help?
[03:43] <darkxst> !as
[03:44] <darkxst> !ask
[03:45] <arthurfiggis> darkxst: true...i would personally go with the privacy menu and have an on/off switch like the other options...but i don't develop anything as complicated as gnome-control-center, so i have no idea how difficult that would be :) kubuntu just sticks it under system settings/diagnostics
[03:46] <darkxst> arthurfiggis, we are trying to get back to the upstream gnome-control-center, essentially what debian ships, so while we could patch it in, its kind of against our objectives
[03:47] <darkxst> and it is the maintainence of distro patches that is annoying, writing them is usually easy enough, then every release they need major rebases
[03:48] <arthurfiggis> darkxst: oh that certainly makes sense...you have three different groups doing distro-specific packages to the same thing and you're bound to wind up with more problems than solutions anyway :) plus i like the idea that you propose, remaining closer to what debian ships out by default
[03:49] <arthurfiggis> (essentially the less diverging from upstream, the less maintenance work falls on the heads of the ubuntu gnome developers...i would think :) )
[03:52] <darkxst> and it is possibly the sort of thing that could be included upstream, but would need to be made generic
[03:52] <darkxst> pretty sure Fedora, OpenSuse and some of the other big distro's all run similar services, but through entirely different backends
[03:56] <darkxst> arthurfiggis, and essentially the core goal of founding Ubuntu GNOME was to encourage upstream contibutions, as we slowly claw back control of the GNOME stack in Ubuntu this will become easier
[03:57] <darkxst> there obvioulsy will always be some ubuntu-isms we have to carry patches for, but that actually makes up a pretty small subset of total distro patches in Ubuntu
[04:01] <arthurfiggis> darkxst, i think that makes a lot of good sense...contributing patches upstream benefits both gnome and any distro that uses it, so long as the patches aren't distro specific :) certainly some of it has to be distro specific like you say, but perhaps as they move further along with unity there will be more opportunity to wrest back a little control of the gnome stack :)
[04:01] <arthurfiggis> (that and mir, if mir ever actually happens...kind of hoping that ubuntu gnome goes with wayland if it goes with anything, i doubt xorg will be going away any time soon in either case)
[04:02] <darkxst> we basically have control of ~50% of core stack now, but things like gtk+, network manager will continue to be problematic even after unity 8
[04:03] <darkxst> arthurfiggis, you not on ubuntu-gnome-qa list?
[04:03] <darkxst> I sent an email about wayland today!
[04:07] <arthurfiggis> darkxst, nope, admittedly i didn't even know there was one so i'm glad you brought it up :) i haven't been running ubuntu gnome for very long so every bit of information helps!
[04:12] <darkxst> https://lists.launchpad.net/ubuntugnome-qa/msg00702.html
[04:15] <arthurfiggis> darkxst: ahh, thanks very much...might have to play around with it one of these days :) not on my desktop presently though, since I play a lot of steam games I kind of need the nvidia official drivers, and from what was said there neither nvidia nor amd support wayland yet...still, good to see that it's making progress!
[04:15] <darkxst> NVIDIA are working on wayland support
[04:17] <arthurfiggis> darkxst: ahh well that's great news! hopefully intel as well, as they seemed to be quite hostile to the idea of Mir on any level when they publically addressed it a while back...i don't tend to use amd's stuff, their official drivers are...rough around the edges to say the least
[04:17] <darkxst> intel and the the other OSS drivers already support wayland
[04:18] <darkxst> no clue what AMD are doing, but their propriety driver is useless anyway
[04:19] <arthurfiggis> darkxst: not sure amd have a clue what they're doing either to be honest, but yeah, that's about on par with my opinion of their official drivers the last time i tried them :P
[04:19] <darkxst> if your really interested see http://www.x.org/wiki/Events/XDC2014/XDC2014RitgerEGLNonMesa/
[04:19] <arthurfiggis> darkxst, thanks, i'll check that one out too! it's all a bit above my head technically, but it's nice to read up and see what's coming down the pike with respect to big changes :)
[04:19] <darkxst> ^ that is about NVIDIA's work on wayland support
[04:28] <arthurfiggis> darkxst, got that one bookmarked as well, i'll have plenty to read up on tomorrow :) ought to call it a night for now before i fall asleep at the wheel, but thanks for all the answers and information, very helpful!
[04:34] <darkxst> hi amjjawad
[04:36] <amjjawad> Hi darkxst
[04:37] <amjjawad> I'm trying to figure out how to add a milestone but the headache I have now is making me weak and slow
[04:38] <darkxst> goto ubuntu-gnome project home page
[04:38] <darkxst> click "stable" series link
[04:38] <darkxst> then "Add milestone" down the page a bit
[04:39] <amjjawad> is it a link or a button? it seems I can't find any of those :(
[04:39] <darkxst> see the graph in the middle of the page?
[04:40] <amjjawad> yep
[04:40] <darkxst> where it shows all the milestones
[04:40] <darkxst> click on 'stable' there
[04:40] <amjjawad> already done
[04:40] <amjjawad> I'm on the stable page
[04:40] <amjjawad> https://launchpad.net/ubuntu-gnome/stable
[04:40] <darkxst> yes
[04:40] <darkxst> then scrolldown
[04:40] <amjjawad> I can't see any "add" thing :(
[04:40] <darkxst> maybe it is create?
[04:41] <darkxst> its a + button link
[04:41] <amjjawad> nothing at all
[04:41] <amjjawad> I don't think I have access yet
[04:41] <darkxst> yeh "Create milestone"
[04:41] <amjjawad> I don't have that at all
[04:41] <darkxst> Just below the list of existing milestones?
[04:42] <amjjawad> will try to send you a screenshot
[04:43] <darkxst> hmm probably a permissions problem
[04:44] <amjjawad> sent
[04:44] <darkxst> its down further below "Milestones and release" but I can't see that in your screenshot
[04:45] <darkxst> can you set milestones in bug reports?
[04:46] <amjjawad> sent you the rest of the screen
[04:46] <darkxst> no permission
[04:47] <amjjawad> I can set milestones yes but I can't create one :(
[04:50] <darkxst> hmm not sure what to do there, lp is very limited when it comes to permissions on projects!
[04:51] <darkxst> maybe just ping me if you need a new one
[04:55] <amjjawad> sure, no worries
[04:56] <amjjawad> even if you create a team/project, you will have limited options and only Launchpad admins have more. Not sure why?! seems non-sense to me. For example: I can't delete a blueprint I created by mistake but only admins can.
[04:56] <amjjawad> Now, I can't create a milestone
[05:14] <darkxst> amjjawad, I think only the 'driver' can create milestones
[05:15] <darkxst> ubuntu-gnome-packaging is to open, to set as driver there
[05:15] <darkxst> and gnome3-team is strictly for upload rights
[05:41] <darkxst> amjjawad, or maybe its better to just use a generic milestone for trusty? still a bunch of unresolved issues from 14.04.1 milestone ;(
[05:41] <darkxst> ^we really need someone dedicated to working on those!
[05:57] <amjjawad> 3rd test failed: https://bugs.launchpad.net/ubuntu-gnome/+bug/1418268
[05:57] <amjjawad> how can I access /var/log/installer while the installation is still running? I can't access the file manager ...
[05:58] <darkxst> amjjawad, switch to a VT
[05:59] <darkxst> ctl+alt+F1
[05:59] <darkxst> then you will need to ssh the files out, use a usb stick or something
[06:00] <amjjawad> VT?
[06:00] <darkxst> Virtual Terminal/TTY whatever they are called
[06:00] <darkxst> just hit <darkxst> ctl+alt+F1
[06:00] <amjjawad> yes yes tty
[06:01] <amjjawad> sigh
[06:01] <amjjawad> it is working on the host only, not the guest system :(
[06:01] <darkxst> maybe /var/log/partman is useful if the partitioning is failing for some reason
[06:01] <amjjawad> I think Oracle VB is not helping much!
[06:02] <darkxst> amjjawad, oh, vbox needs another key added, maybe shift as well
[06:02] <darkxst> or super
[06:02] <darkxst> I steer well clear of that rubbish these days
[06:02] <darkxst> vmware is all I use for desktop testing
[06:03] <darkxst> qemu/kvm, for server-ish stuff
[06:04] <amjjawad> No, didn't work either :(
[06:05] <amjjawad> Sigh, I have enough headache already
[06:05] <darkxst> amjjawad, I don't remember what the key is, but there is some other key you have to use (or some wierd crap to switch to a tty in Vbox
[06:08] <amjjawad> without going to tty, I am on terminal now and there are 3 directories
[06:08] <amjjawad> dm, version and debug
[06:09] <darkxst> amjjawad, I'll say pick debug
[06:10] <amjjawad> Not folders, sorry, these should be files
[06:15] <darkxst> then just grab all 3
[06:15] <darkxst> but debug will likely have the interesting stuff
[06:15] <darkxst> I think
[07:33] <mgedmin> do you still need testers?
[07:36] <darkxst> mgedmin, always
[07:36] <darkxst> but 14.04.2 is slipping a week
[07:36]  * mgedmin did this once but forgot everything, of course
[07:38] <mgedmin> what?  iso.qa.ubuntu.com won't let me log in!
[07:38] <mgedmin> "The name mgedmin is already taken"
[07:39] <mgedmin> hm, did I not use my launchpad openid when I signed up last time?
[07:39] <darkxst> mgedmin, its uses the SSO service, so probably yes
[07:40] <mgedmin> I have a saved password for qa.ubuntu.com in my pwsafe, but it's not accepted by iso.qa.ubuntu.com :(
[07:41] <darkxst> because it uses ubuntu one SSO for atleast as long as I can remember
[07:42] <mgedmin> the "have you forgotten your password" link 404s!
[07:42]  * mgedmin is a great tester, finds bugs before he even starts testing the thing he was supposed to be testing
[07:43] <darkxst> lol, yes I found a bug in infinity also, he forgot to mention that release was delayed!
[07:44] <darkxst> I always though he was a person, but just perhaps he is a bot!
[14:29] <LinDol> hello all :)
[16:56] <FunnyLookinHat> Anyone else having a problem in 15.04 with a lock screen that you can't type into?
[16:57] <FunnyLookinHat> I solved it by installing gnome-screensaver... but that was just a lucky guess I think
[16:58] <FunnyLookinHat> Wait - no it's still broken... :-P
[18:20] <Chris___> Hey how's going here?
[18:24] <Chris___> Currently I'm switching my sister-in-law's laptop from Fedora to Ubuntu GNOME; there are just too many easy ready made solutions for Ubuntu based distributions.
[20:38] <ahoneybun> darkxst: is there a delay in the release of the second point release for 14.04?
[21:00] <darkxst> ahoneybun, yes
[21:00] <darkxst> its been delayed by a week
[21:07] <ahoneybun> oh what needs to be done, testing?
[21:09] <Noskcaj> ahoneybun, ali found an install bug yesterday, plus some other flavour are having issues with gnome and kde components appearing on their images
[21:10] <ahoneybun> Noskcaj: I saw that, but I could not reproduce it
[21:48] <ahoneybun> is there a reason my printer service is not available? right now?