[03:17] <calamari> anyone successfully using nvidia glx drivers in wily?
[03:18] <calamari> I'm getting "failed to initialize glamor at ScreenInit() time"
[03:43] <calamari> it's weird too, because in recovery mode I can do startx and that works without error, but in normal mode the above error
[08:11] <lordievader> Good morning.
[08:17] <calamari> mornin
[08:18] <lordievader> Hey calamari
[08:18] <calamari> I actually made some progress
[08:19] <calamari> I decided to ditch nvidia for the moment and focus on intel
[08:19] <calamari> and it gets as far as the lightdm screen
[08:20] <calamari> never gets to the desktop, but if I run startx my x apps load .. I can't see them tho, completely black screen
[08:21] <calamari> pretty sure I'm just going to have to give up and reinstall vivid
[08:22] <calamari> not sure why I'm having so much trouble.. xorg hasn't changed for years
[08:29] <lordievader> One of those hybrid things?
[08:37] <ikamusume> lordievader: hybrid? not sure I follow
[08:38] <ikamusume> it's ubuntu mate, if that's what you were asking
[08:40] <lordievader> Two graphics cards, one integrated one dedicated.
[08:40] <calamari> oh, yeah
[08:42] <calamari> it had been working fine that way under 15.04, I just disabled the intel card in the bios.
[08:45] <calamari> can't stay awake any longer.. bummed that I'll be spending my day tomorrow reinstalling. guess I've learned my lesson tho!
[08:45] <calamari> no more +1 for this squid!
[09:16] <EriC^^> can someone running wily type lsb_release -sd and paste here please?
[09:16] <Faux> Ubuntu Wily Werewolf (development branch)
[09:16] <EriC^^> thank you
[10:21] <lordievader> !schedule
[11:08] <BluesKaj> Hiyas all
[12:22] <skyjumper> anyone able to scroll gnome-terminal with screen running?
[12:23] <skyjumper> somehow shift-pgup and shift-mousewheel become escape codes when screen is running
[12:42] <sjoshi> Hello, where i can check the status of ubuntu15.10 e.g. how many bugs open and all that?
[12:42] <sjoshi> and what are those bugs
[12:45] <OerHeks> sjoshi, https://bugs.launchpad.net/ubuntu/wily
[12:45] <sjoshi> thanks OerHeks, let me check that out
[12:45] <OerHeks> sjoshi, and this, total stats https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue437?action=show&redirect=UbuntuWeeklyNewsletter%2FCurrent#Ubuntu_Stats
[13:01] <freeroute> sup, anyone testing the beta of Kubuntu 15.10? What's your opinion? Stable?
[13:02] <lordievader> Last time I ran it, it was rather stable... But it is still a beta and in development. It could be broken tommorow.
[13:03] <fhf> willy is quite stable using mir and unity 8
[13:03] <fhf> already, not tested normal version tvbh
[13:03] <fhf> tbh*
[13:27] <freeroute> lordievader: do you think it will get stable until finalrelease?
[13:28] <lordievader> Do I think it will stay stable? Likely, but I cannot look into the future.
[13:29] <freeroute> unfortunately me neither :(
[16:54] <techrx> Ubuntu 15.10 releases on the 22nd of October, correct? Are there any major differences compared to 14.04 LTS?
[20:23] <ckocagil> Hello all. What's the easiest way to use a kernel older than 4.2?
[20:23] <mcphail> ckocagil: install 14.04 :)
[20:24] <ckocagil> Argh.
[20:24] <ckocagil> I guess everything is too tied to 4.2 at this point?
[20:24] <k1l> ckocagil: what is the issue?
[20:24] <mcphail> ckocagil: not sure. You could try compiling and installing an older kernel. You can always roll "back" to 4.2
[20:26] <ckocagil> k1l: I need the vmhgfs module from vmware tools
[20:26] <ckocagil> I patched it to build for 4.2, but I get kernel panic and rather not try to debug that
[20:27] <mcphail> ckocagil: vmware usually catch up very quickly after a new Ubuntu release, but I've never seen them support _prior_ to official release date. Can you be patient for a couple of weeks?
[20:28]  * mcphail has had this problem before
[20:28] <ckocagil> I can try being patient, but I'll also look for other solutions for now
[20:29] <mcphail> ckocagil: Compiling an older kernel is very easy, so you could try that if you have some time
[20:29] <ckocagil> mcphail: sounds good to me
[20:30] <lordievader> ckocagil: You can stick with 15.04 until the end of it's support period. And periodically check if the vmware module works in 4.2.
[20:30] <ckocagil> lordievader: but where's the fun in that? :p
[20:31] <mcphail> ckocagil: the kernel makefiles are smart enough to do a "make install" in a debian/ubuntu-friendly way these days
[20:32] <ckocagil> mcphail: wow, that's actually pretty neat
[20:33] <mcphail> ckocagil: just remember to turn off all the debug stuff before compiling, if you use the Ubuntu kernel config. Otherwise you'll be compiling for weeks and the kernel/module sizes will be monstrous
[20:34] <mcphail> No idea if a pre-4.2 kernel will work, though
[20:34] <ckocagil> yeah. maybe I should debug the module.
[20:35] <lordievader> The other way around is usually easier, my 14.04 installs run 4.2 kernels.
[20:36] <mcphail> ckocagil: there are 4.1 kernels still lurking in the !mainline repo, if you want to try those
[20:36] <mcphail> !mainline
[20:39] <mcphail> Are the proprietary nvidia drivers (from the default repos) working in wily just now? Just want to check before I break my install... :)
[21:05] <ckocagil> aaaand nope. wily's open-vm-tools-dkms crashes kernel 4.0.9 too.
[21:05]  * ckocagil sighs and looks up a kernel debugging guide
[21:06] <fhf> gl hf
[21:08]  * ckocagil runs out of a cave, 20 years later, with a glorious white beard and shouts "at last I figured it out! where do I submit the patch?"
[21:09] <mcphail> ckocagil: I think you're on a hiding-to-nothing. I'm sure there will be a binary-blob at the end of the rainbow
[21:11] <mcphail> ckocagil: best stick with 14.04, or wait for vmware to sort out their drivers
[21:11] <ckocagil> mcphail: the kernel modules are open source though
[21:12] <mcphail> OK. I thought they were shims for binary blobs. You might be in luck, then