[02:31] <tracker1> Hi! 
[02:32] <tracker1> i have a question about xubuntu! someone can help me?
[07:05] -SwissBot:#xubuntu-devel- ::xubuntu-docs:: [yakkety] r627 Launchpad automatic translations update. (by Launchpad Translations on behalf of ubuntu-core-doc)
[09:05] <flocculant> bluesabre: feels like I just finding more stuff for someone else :( but - are we going to revert to (and get that fixed) tosystem user units 
[10:41] <sorinello> Hello. I might have found an issue regarding Xubuntu and VMWare workstation. This might not be related to xubuntu, but related to Ubuntu. Upgrading or making a clean install of 16.10 on a WmWare Workstation doesn't work. After upgrade, the system hands. At the clean install,  the system hangs also
[10:41] <sorinello> any Idea if I am missing something ?
[10:42] <sorinello> I remember I had some issues when I upgraded to 16.04 6 months ago, and it was a reported bug
[10:42] <flocculant> sorinello: not really seen any specific vmware bugs during the cycle - but I don't actively look either
[10:43] <flocculant> if you had issues with 16.04 it's entirely possible you will again
[10:43] <flocculant> we don't specifically test against virtual hosts 
[10:43] <flocculant> maybe try #ubuntu 
[10:44] <sorinello> flocculant,  yes, but now I also get stuck when installing 16.10 from scratch. so this not my old vm which is bad. I asked here just to see if you guys know something about this, as I really don't think this is xubuntu related
[10:44] <flocculant> the time to be seeing if a new dev version works with *your* vm host isn't the week after it's released - but the months before it is release
[10:44] <flocculant> d
[10:44] <flocculant> much more chance of getting something fixed :)
[10:45] <flocculant> yea - this is more likely to be a *buntu issue for sure
[10:45] <sorinello> I'll investigate it, but when starting in debug mode, I saw a kernel panic  there, but I can't figure out from which module
[10:45] <sorinello> it might be the drivers for vmware
[11:52] <bluesabre> flocculant, no hurry to, I don't know how to fix it once we do, so I'll wait for pitti to poke us with i
[11:52] <bluesabre> t
[11:54] <flocculant> cool - wasn't in any hurry - was just wondering :)
[11:54] <flocculant> have a good day :D
[12:45] <sorinello> flocculant, ok, mystery solved. It seems I had to edit the vmx file of the VM, and add a line to make it work.
[12:45] <sorinello> Error Message: "The CPU has been disabled by the guest operating system. Power off or reset the virtual machine."
[12:45] <sorinello> found t he oclution on a youtube video
[12:45] <sorinello> *solution
[12:53] <flocculant> sorinello: oh right - well yea - I saw that fix too, but didn't know your error :)
[12:55] <sorinello> seems to be on VmWare's side, no related to *ubuntu
[12:55] <flocculant> mmm
[23:32] -SwissBot:#xubuntu-devel- ::xubuntu-artwork:: [greybird] r480 Get rid of more single-color gradients (issue #155)... (by Simon Steinbeiß)
[23:32] -SwissBot:#xubuntu-devel- ::xubuntu-artwork:: [greybird] r481 Get rid of the remaining single-stop gradients (issue #155)... (by Simon Steinbeiß)