=== darkxst_ is now known as darkxst
[03:34] <aeoril> darkxst sarnold thinking what to do next - probably build vim.tiny, but not sure which way to do it
[03:35] <aeoril> darkxst sarnold probably take the easy way first and build with --with-features=tiny (or small)
[03:36] <aeoril> darkxst did you read the backlog about the vim.tiny and vim.gtk (or vim.gui or whatever)
[03:36] <darkxst> aeoril, no
[03:36] <darkxst> and I have no idea what tiny is
[03:41] <aeoril> darkxst the version of vim that ships with ubuntu is vim.tiny (found via a chain of 2 symbolic links) - it is a stripped down version of vim, I assume.  The one I tested turned out to be configured as "Normal GTK2 GUI"  --version shows this information.  --version shows "Small version without GUI" for the ones that ship with Ubuntu, and /debian/rules in the vim package downloaded from lp
[03:41] <aeoril> verifies this
[03:41] <darkxst> aeoril, I doubt that is something you could change via an SRU
[03:42] <darkxst> and why GTK?
[03:43] <aeoril> darkxst I am not sure I would want to change that, but was thinking of doing some more testing somehow using a build more like what is on Ubuntu.  Why GTK?  I have no idea - should I be able to answer that?  Because there is a GUI version and it uses GTK because the designers chose to???
[03:44] <darkxst> aeoril, rerun you bisect using the same build options as ubuntu uses
[03:45] <darkxst> aeoril, actually I have seen that gtk interface I think, but only on windows!
[03:45] <aeoril> darkxst yes, that is what I was thinking - that was my original question, at least what I was trying to convey - should that be my next step ...
[03:45] <darkxst> certainly worth a try, shouldnt take long, know you know how to git bisect ;)
[03:45] <aeoril> darkxst yes, the gtk gui version was not any different on Ubuntu than the small no-GTK/GuI version, from what I could see
[03:46] <aeoril> darkxst yes, I think I can pull out the proper config rules from /debian/rules - I found the main ones but need to hunt around for any others - another good thing to learn, how to read /debian/rules ...
[03:47] <darkxst> aeoril, heh enjoy that
[03:48] <darkxst> no  idea what vim uses but basically there are two competing standards, debhelper and cdbs
[03:49] <aeoril> darkxst my question was based on something you do not know, though.  There may be a shortcut to try before figuring out all the options from /debian/rules - I asked on #vim and they said I could create vim.tiny with a simple command line option to ./configure - ./configure --with-features=tiny.  Not exactly the same, but if it fails, it might show me the place anyway using bisect
[03:50] <aeoril> darkxst debhelper and cdbs - ok - can you explain further, or should I google those?
[03:50] <aeoril> darkxst I remember using debhelper, but not all the details ...
[03:53] <aeoril> darkxst maybe I should take a detour to a tutorial on the Ubuntu or Debian wikis to learn packaging better?
[03:57] <aeoril> darkxst I remember that debhelper or whatever built the desired build environment using rules I specified in some kind of config file.  You have to run it and fix problems until all errors and warnings were gone, IIRC
[04:00] <darkxst> aeoril, its just two different systems really dh is simple, cdbs more complicated but mor powerful
[04:00] <darkxst> (technically they both use debhelper just in different ways)
[04:05] <darkxst> aeoril, gtg, but try build trusty version 7.4.052 (or whatever it was) and see if it fails
[04:05] <darkxst> if so go ahead with a bisect
[04:05] <darkxst> with you =tiny thing
[04:06] <aeoril> darkxst yes, will do - already found out it works fine without -tiny, so need to do that.  Thanks
[04:06] <aeoril> darkxst will you be back?
[04:06] <aeoril> darkxst actually, I need to go too so never mind
[04:06] <aeoril> darkxst will bisect tomorrow, if I can (busy day)
[04:07] <darkxst> aeoril, ok
[04:08] <aeoril> darkxst unfortunately, my wife is sick so I have not had the normal amount of time to spend on this past couple of days ...
[04:08] <aeoril> (she has the flu)
[04:09] <darkxst> soft ;)
[04:10] <aeoril> darkxst soft?
[04:13] <aeoril> Society of Forensic Toxicologists? darkxst?
[04:13] <aeoril> oh, you meant my excuse was soft - I thought you were throwning an internet acronym at me!
[04:14] <darkxst> hah no your wife is soft taking up all your time for the flu ;)
[04:14] <aeoril> darkxst yes, she is a princess for sure - with a capital P!
[04:14] <aeoril> darkxst but, I am still very fortunate to have her ...
[04:15] <darkxst> heh I kinda had one once, it was very much a one way street
[04:15] <aeoril> darkxst actually, it is just the opposite - I am having to do all the stuff she normally does, so I appreciate all the more what she accomplishes in a given day in addition to full time work!
[04:16] <darkxst> ok, really gtg now
[04:16] <aeoril> darkxst ~bye!
[04:16] <aeoril> darkxst and thanks!  Will get to it tomorrow hopefully!
[04:17] <darkxst> aeoril, if you want easier bugs to work on come join Ubuntu GNOME team ;)
[04:18] <aeoril> darkxst maybe so ... :)
[04:18] <aeoril> darkxst so far, I still like this one ... :)
[04:19] <aeoril> darkxst I think the hard part is having to work with upstream repo for bisect?
[04:19] <darkxst> aeoril, that is the usual way
[04:19] <aeoril> darkxst I figured ... :)
[04:20] <darkxst> I do all my dev work on upstream git repos (for GNOME)
[04:20] <aeoril> darkxst I hope I am doing ok with all this ... not being a burden on you guys
[04:20] <darkxst> and then backport patches to suit ubuntu packaging
[04:20] <aeoril> darkxst I see
[04:20] <darkxst> and mostly because I prefer git over bzr
[04:21] <darkxst> and jhbuild makes it nice and quick to test builds
[04:21] <aeoril> darkxst yes, I was not really as fond of bzr as I am of git now
[04:21] <aeoril> darkxst yes, that sounds interesting, and git is a plus for me I think
[04:22] <darkxst> aeoril, bzr is dead really (in maintenance mode atleast)
[04:22] <aeoril> darkxst I kind of saw the writing on the wall for it a long time ago with the advent of git and github, and some of the problems with big projects people reported with it
[04:23] <darkxst> aeoril, git pre-dated bzr
[04:24] <aeoril> darkxst maybe the advent of git's popularity or my own familiarity with it?  Anyway, git seemed like a bzr killer at some oint to me
[04:24] <aeoril> point
[04:25] <aeoril> darkxst the thing that really concerned me several years ago about bzr is when I heard people on IRC or whatever mentioning it was unstable with large projects
[04:25] <darkxst> not sure about that
[04:26] <aeoril> darkxst there was a particular project they mentioned that was really huge, maybe the biggest on bzr at the time, and people said it was unstable
[04:26] <darkxst> my issues with it are that I learnt git first
[04:27] <darkxst> and bzr really has nothing on git, for local branches where you hammer the history
[04:27] <darkxst> rebases and what not
[04:27] <aeoril> darkxst My biggest issue with my line of chatting at the moment is I really never learned either very well so I need to stop talking about what I don't know about ... :P
[04:28] <aeoril> darkxst But i am happy to listen to you! :)
[04:28] <darkxst> well I was going remember!
[04:28] <aeoril> darkxst now I just don't believe you at all! ;)
[04:29] <aeoril> darkxst Have an Ubuntu day!
[04:29] <aeoril> (or night or morning or evening or whatever)
[04:29] <darkxst> aeoril, U-GNOME day ;)
[04:29] <aeoril> lol ok!
[04:29] <darkxst> and its about mid afternoon now
[04:30] <aeoril> where in the world are you?
[04:30] <darkxst> in your future ;)
[04:30] <darkxst> Aus
[04:30] <aeoril> Cool!
[04:30] <aeoril> You are about 18 or so hours ahead of me then!
[04:31] <aeoril> And hot!
[04:31] <aeoril> (probably)
[04:31] <darkxst> aeoril, yes hot, I want to move to Europe to fix that
[04:31]  * darkxst gone now though
[04:31] <aeoril> toodles~
=== mfisch is now known as Guest90369
[10:15] <svetlana> 1) patch pilots URL in topic got cut off. 2) http://emacs-app.sourceforge.net/ is in gnu/emacs now, built by supplying --with-ns option to configure. how do I request that it is packaged -- with debian first, or not?
=== _salem is now known as salem_
=== salem_ is now known as _salem
[17:54] <Bluefoxicy> 9.9 Wonderful.  upgrade Chromium, and AGAIN youtube stops working with the html5 player.
[17:56] <Bluefoxicy> My video driver still hangs a lot
[17:56] <Bluefoxicy> like I can't use rhythmbox because it nearly kills my PC; if I hit the Gnome 3 activities view, trying to composite causes a 2-5 second hang.
[17:56] <Bluefoxicy> It was snappy on 14.04 LTS
[17:56] <Bluefoxicy> Do you know what they told me when I filed the bug?
[17:56] <Bluefoxicy> "Upgrade your bios."
[17:57] <Bluefoxicy> Yes, it worked on the previous version, but this version the problem must be my bios.
[17:57] <Bluefoxicy> Well I did that, and it's still broken.  Good job:  the Intel HD2000 chipset is useless in Ubuntu 14.10, and five-star in 14.04.
[17:58]  * ejat jom makan 
[17:59] <Bluefoxicy> I'm upgrading to 15.04 as soon as the first beta is out, because I can't imagine it being worse than 14.10.  Every distro occasionally has its sunken ship release, the one that should be blotted out of history; 14.10 is it for Ubuntu.
[17:59] <Bluefoxicy> Upgrading from 14.04 to 14.10 is as advisable as upgrading from 98SE to Windows ME
[17:59] <bekks> Why dont you stick with 14.04 if that worked fine?
[18:00] <Bluefoxicy> Because I'd have to downgrade backwards, somehow, and I can't do-release-downgrade
[18:00] <Bluefoxicy> Hopefully someone took down some lessons learned from this release and came up with a list of things to not do again, and things to do in the future before releasing a production OS
[18:00] <bekks> Because there is no do-release-downgrade at all and downgrading releases isnt supported at all.
[18:01] <bekks> Did you file bugs for every single item of your "list", so these "things" will get noticed?
[18:01] <Bluefoxicy> No, because some of them are things like the Google Calender plug-in ceasing to function at all in Thunderbird, which I'm not sure is supported anyway, or why it's broken.
[18:02] <Bluefoxicy> I filed a bug on the video driver and was told that if it worked in 14.04 and ceased functioning on upgrade to 14.10, it was obviously my bios
[18:03] <bekks> Bluefoxicy: So if it was you bios, ubuntu cant do anything about it.
[18:03] <bekks> And shipping an old graphics driver is no viable solution.
[18:03] <Bluefoxicy> bekks:  It was a regression.
[18:03] <Bluefoxicy> My hardware is Intel HD2000 in modern Core i5 CPUs
[18:04] <Bluefoxicy> If a newer graphics driver fails where an old one worked, the new driver has a regression.  That's a bug.
[18:04] <bekks> If it fails because of a bios issue, the driver cant do anything about it.
[18:04] <Bluefoxicy> When I finally did get my bios updated--a difficult task, as there's no floppy drive and it's difficult to boot DOS (last time I tried a memdisk boot, it refused to patch the bios)--it didn't fix anything.
[18:04] <Bluefoxicy> bekks: it didn't fail because of a bios update; the response was "oh your bios is a version behind, so we're not looking at this"
[18:04] <Bluefoxicy> bringing the bios up to date didn't fix it.
[18:05] <Bluefoxicy> Apparently the proper response to a report of stuff suddenly not working on upgrade is "well that's somehow someone else's problem"
[18:06] <Bluefoxicy> when I figure out how Chromium broke AGAIN on upgrade, I'll file a bug on that.  If I ever do.  For some reason, it could play HTML5 youtube videos an hour ago; I ran apt-get upgrade and it upgraded Chromium; I restarted Chromium and now I can't make Youtube videos play at all.
[18:06] <bekks> Besides some rare facts I can see a lot of ranting in your posts. Did you continue on providing information on your bug report which you created?
[18:07] <Bluefoxicy> I ran some commands I was asked for and provided a bunch of files
[18:07] <bekks> And meanwhile you can add several additional bug reports for the other items on your "list" :)
[18:10] <Bluefoxicy> Most of everything came down to the graphics driver; there's also some kind of system issue with running out of memory (the OOM killer doesn't kick in when you're low on pagecache, so you just grind the system to a halt--this is being looked into on linux-mm), which is secondary to Chromium going out-of-control and allocating tons of RAM; and Chromium randomly breaks for Youtube HTML5 videos when it's updated
[18:11] <Bluefoxicy> Of course, the graphics driver in question is a majority driver:  it's Intel HD graphics
[18:11] <Bluefoxicy> and I have nfc what's actually wrong with Chromium
[18:18] <bekks> And can you confirm that issue using other browsers?
[18:22] <Bluefoxicy> https://www.youtube.com/watch?feature=player_detailpage&v=eRxOcdLm2_8 plays with HTML5 in Firefox.  In Chromium, it just shows a spinning circle, and downloads the whole video; if I seek through the video, it shows me the frame I seek to (as if paused), while the player acts as if it is perpetually waiting to buffer.
[18:30] <Bluefoxicy> oh ffs.
[18:34] <Bluefoxicy> I can't unload the sound card driver module.  I bet my sound card driver is AFU and it's causing video to not play in Chromium (only on Youtube:  video plays without sound on Twitch and in Firefox; I have nfc why)
[18:35] <Bluefoxicy> I need about 5 minutes to do some maneuvering to cover my identity in some other places before I can reboot.
[18:56] <Bluefoxicy> sound core failure.  Complete sound core failure.  Now I have to track down why >:|