[00:20] <BarkingFish> good morning :)  would someone please be kind enough to remind me how to pin a package so that apt-get dist-upgrade doesn't upgrade it please? I need it held back cause the next version up breaks things i need :)
[00:31] <BarkingFish> nvm, i've discovered i don't need to pin them :) apparently, and for someone who's been on here for almost 3 years, this is bad - i just learned synaptic can lock a version so it won't get upgraded :)
[00:32] <yofel> BarkingFish: see apt_preferences manpage, putting something like this into the preferences file would work: http://paste.kde.org/663380
[00:32]  * yofel wonders how synaptic holds them back
[00:32] <yofel> I've found anything besides apt pins to be somewhat unreliable in the past. Maybe it's better today
[00:34] <BarkingFish> yofel - i have no idea how synaptic holds back.  i just found the entry when you click a package and hit the package menu, there's an entry "Lock version"
[00:34] <BarkingFish> i just tried it, ran the dist upgrade, and it's left firefox alone
[00:35] <yofel> yeah, not sure how that works. maybe it tells dpkg to hold it back
[00:36] <BarkingFish> even so, the new kernel is still having trouble :(  ndiswrapper still won't build on it
[00:37] <BarkingFish> I'm dying to find out what's gone wrong between 3.5.0-22-generic and 3.8.0-4-generic
[00:37] <BarkingFish> or even 3.8.0-1 - which is where ndiswrapper started failing again.
[00:38] <BarkingFish> i can't properly beta test raring without all the bits work as needed, and for that I either need the 3.8.0 kernels to work, and the ar5523 driver or ndiswrapper to function/build/do something which looks promising
[00:41] <BarkingFish> i'll get the dkms log from the ndiswrapper build, paste it up and then do my system restart, catch you on the way back
[00:41] <yofel> BarkingFish: I took a quick glance on that, needs ndiswrapper fixed. Some of the API it uses was removed it seems
[00:41] <BarkingFish> http://paste.ubuntu.com/1599053 - build log from ndiswrapper 1.58~rc1
[00:42] <BarkingFish> ok, yofel - it's a shame the ar5523 driver broke so quickly on the first round of updates to 3.8.0-1, i was as happy as a pig in a turnip shed when that launched :)
[00:43] <yofel> BarkingFish: this commit breaks it: http://paste.kde.org/663386
[00:43] <yofel> hm
[00:43] <yofel> did you file a bug about ar5523?
[00:44] <BarkingFish> i can't find it on launchpad. I wonder if it's come from upstream via linux-wireless or kernel
[00:44] <yofel> what? ar5523?
[00:45] <yofel> that's part of the kernel
[00:45] <yofel> linux-image-extra-3.8.0-3-generic: /lib/modules/3.8.0-3-generic/kernel/drivers/net/wireless/ath/ar5523/ar5523.ko
[00:45] <BarkingFish> i'll paste the dmesg up from that and show you what it does too :)
[00:46] <BarkingFish> ah. so bug reports would go to...kernel.org or to launchpad?
[00:46] <yofel> first launchpad, then upstream I guess
[00:46] <BarkingFish> you'll have to excuse me if I'm extra stupid tonight, i'm tired and it's late.
[00:47] <yofel> nah, same for me, I'm off shortly
[00:47] <BarkingFish> I'll file one there - i have to boot into the new kernel and get a dmesg from it first, then come back to the current one and pastebin it
[00:47] <yofel> for kernel.org try the mailine kernel first, latest would be http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc6-raring/
[00:47] <IdleOne> report it to launchpad and if needed the ubuntu maintainer will forward upstream
[00:47] <yofel> you'll need the one all package and the ones for your arch
[00:48] <BarkingFish> upshot is, it moans about being unable to probe the device, error -110, and complains of an error -2 on RX urb
[00:48] <BarkingFish> what the hell that means, I have no idea, it doesn't work though :(
[00:48] <BarkingFish> anyhow, i'm getting bugged for a system restart from the kernel upgrade i just did, so I'll be back in a while :)
[00:48] <BarkingFish> see you soon
[01:12] <BarkingFish> morning again :)  right... yofel -this is the pastebin of my dmesg where the ar5523 module is trying to load... http://paste.ubuntu.com/1599083 :)
[01:13] <BarkingFish> the issue starts when cfg80211 goes in at [15.422489
[01:13] <yofel> file a bug, I'm clueless what's wrong there
[01:13] <yofel> and the driver code doesn't seem to have had a change since november (at least upstream)
[01:14] <BarkingFish> okies, i'll stick in launchpad.
[01:14] <yofel> use ubuntu-bug linux
[01:14] <yofel> that'll add the relevant logs
[01:14] <yofel> now I'm off to bed before I fall asleep on the keyboard
[01:14] <yofel> good night
[01:14] <BarkingFish> ok then
[01:15] <BarkingFish> okies, goodnight :)
[01:15] <BarkingFish> sleep well
[01:15] <BarkingFish> incidentally, don't i need to be in that kernel to get the right info?
[01:47] <BarkingFish> yay. whole bug now filed - i hope it helps, god knows I hope it does :)  I've made a right pig's ear of it.
[01:47] <BarkingFish> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1113048
[02:23] <smallfoot-> Why raring have Chromium 22, when Windows have Chrome 24?
[02:42] <bazhang> !find chromium
[02:42] <bazhang> !info chromium-browser
[02:43] <bazhang> smallfoot-, why is that important
[02:44] <smallfoot-> bazhang, Chromium 22 is old and contains security vulnerabilities that were fixed in Chromium 24
[02:46] <bazhang> smallfoot-, then it will be updated if these "security vulnerabilities" are serious enough to warrant it. be patient. It's a development version of Ubuntu, so bug testing and fixing is the order of the day, not version chasing
[02:47] <smallfoot-> bazhang, but 12.04 LTS and 12.10 stable also contain the old insecure version
[02:47] <smallfoot-> and its been insecure for months, since it doesn't even have Chromium 23
[02:48] <bazhang> !bugs | smallfoot- so file one
[02:48] <bazhang> smallfoot-, did you want actual change? or just to complain about it
[02:48] <smallfoot-> I don't think Ubuntu devs will care to fix it, so I mailed the Debian maintainers, I hope they fix it and Ubuntu resync
[02:48] <smallfoot-> I dont know
[02:48] <bazhang> smallfoot-, ...
[02:49] <bazhang> then FIle a bug
[02:49] <smallfoot-> oki
[02:51] <smallfoot-> How can I know which files are on the default install, but not on my system?
[02:52] <smallfoot-> I mean which packages
[02:57] <bazhang> http://google-chrome.en.uptodown.com/ubuntu  smallfoot- you seem to be misinformed about Chrome 24 not being available for Ubuntu
[02:58] <smallfoot-> oh, i just saw it wasnt in the official repo
[02:58] <bazhang> thats because Chrome is Never in the ubuntu repos
[02:58] <smallfoot-> so now i have to get it from a third-party unofficial site which might be shady and not trusty
[02:59] <bazhang> what!
[02:59] <smallfoot-> yeah, I don't know what uptodown.com is
[02:59] <smallfoot-> it surerly isnt ubuntu.com
[02:59] <smallfoot-> I believe Chrome is always in Ubuntu universe repo
[03:00] <bazhang> smallfoot-, ok. you got the wrong channel then. this is NOT the complaints/rants channel, as you have been told many many times
[03:00] <bazhang> Chromium and chrome are distinct items.
[03:01] <smallfoot-> I meant Chromium, it was you who mentioned Chrome which confused me
 Why raring have Chromium 22, when Windows have Chrome 24?
[03:01] <smallfoot-> then you linked me to a website about Chrome, when I asked about Chromium
[03:02] <bazhang> no that was YOU
[03:02] <smallfoot-> Yes, but Chromium should the same version as Chrome ,because Chrome is the stable version
[03:02] <smallfoot-> Chromium 25 and 26 exist too, but Chrome uses version 24 because that is the stable version
[03:02] <bazhang> so file a bug...
[03:02] <smallfoot-> so Ubuntu should have Chromium 24, not old 22 or new 24 beta or 25 dev
[03:03] <bjsnider> there's a manpower shortage on chromium
[03:04] <smallfoot-> bjsnider, oh I see, I thought it was a popular browser
[03:04] <bjsnider> the build scripts are very complex, and the entire chromium linux distro has to be downloaded just to build the browser. it's not easy
[03:04] <smallfoot-> wow
[03:04] <bjsnider> all of the work used to be done by one guy, and he quit
[03:04] <smallfoot-> oh :s
[03:05] <bjsnider> last i checked canonical is looking for something like 3 chromium developers
[03:05] <bjsnider> but those jobs have been up there years
[03:05] <smallfoot-> oh, I see
[03:06] <bjsnider> it's hard to get anybody away from google, because they're, you know, a good employer and whatnot
[03:06] <smallfoot-> Is it possible to get Alex Shkop to help out?
[03:06] <bjsnider> so i think a lot of chromium users have switched to chrome
[03:06] <smallfoot-> How about get a volunteer?
[03:06] <smallfoot-> http://www.webupd8.org/2012/09/new-chromium-stable-and-development.html
[03:07] <bjsnider> also i think there was a hard drive space problem at one point
[03:07] <bjsnider> maybe still is
[03:07] <smallfoot-> Chris Coulson is the guy who quit?
[03:07] <bjsnider> no
[03:14] <smallfoot-> Okay, I mailed Alex Shkop and asked him to apply to join the Chromium team
[03:14] <bjsnider> i tried to volunteer myself, but the builds were so large and resource-intensive that they wouldn't finish on my computer at the time
[03:14] <smallfoot-> and I mailed the Chromium team and asked them to invite Alex Shkop
[03:14] <bjsnider> who is that?
[03:14] <smallfoot-> Alex Shkop is the guy who maintains a Chromium PPA
[03:14] <smallfoot-> https://launchpad.net/~a-v-shkop
[03:14] <bjsnider> well, i think they'd be happy to accept help
[03:14] <smallfoot-> https://launchpad.net/~a-v-shkop/+archive/chromium
[03:15] <smallfoot-> https://launchpad.net/~a-v-shkop/+archive/chromium-dev
[03:15] <smallfoot-> I hope so
[03:15] <bjsnider> given the size of the source tarballs it would be hard for anybody to have a chromium ppa
[03:15] <smallfoot-> your computer wouldn't finish on time, does it need finish so fast?
[03:16] <smallfoot-> Cant you just wait some extra time and still be done with it?
[03:16] <bjsnider> the builds would fail for lack of resources, ie. ram
[03:16] <smallfoot-> I see
[03:16] <smallfoot-> but RAM is dead cheap, go buy some more
[03:17] <bjsnider> i'm satisfied with chrome at the moment
[03:17] <bjsnider> i have other things to do
[03:17] <smallfoot-> I see
[03:17] <bjsnider> the build scripts are the most complicated i've seen
[03:17] <smallfoot-> oh
[03:17] <smallfoot-> why aren't the PPA compiled for raring?
[03:17] <bjsnider> 70+ lines for the rules file, when they're normally around 10 or less these days
[03:18] <bjsnider> or was it 700 lines? i don't remember now
[03:20] <smallfoot-> Is there any way to find out if there is a package included on the default install, that is not installed on my system?
[03:21] <bjsnider> the default install is in the ubuntu-desktop metapackage, so you could reinstall that
[03:22] <smallfoot-> any other way to find out?
[04:29] <skp1> gwibber not refreshing
[04:29] <skp1> no feed from facebook or twitter
[06:48] <phunyguy> hey folks, was hoping I could get some advice on something, since phone support is coming, I have a Lenovo Thinkpad 2 tablet, with UEFI and Windows 8 pro.... I am just trying to get any kind of Ubuntu to boot from a liveUSB... I disabled secureboot in the bios, but there is no option to allow "legacy OS" to be installed. Am I boned?
[06:51] <phunyguy> I should add, it is an Atom-based tablet, that is only 32bit
[07:02] <phunyguy> ewps.. in case anyone was looking to answer, I had to restart to test the USB stick to make sure at least that was working on another laptop, before trying again on the tablet
[11:38] <BluesKaj> Howdy all
[15:48] <ironhalik> anyone noticed decreased performance on intel wifi cards?
[15:48] <ironhalik> intel 6205 in my case
[16:52] <phunyguy> ironhalik, how are you testing?  Fileshare transfers?
[17:16] <ironhalik> phunyguy: I was running a ISP speedtest. Over ethernet I got 12mbps, over wifi, 3mbps
[17:17] <ironhalik> but nvm,  currently disabling 802.11n fixed the issue
[17:17] <ironhalik> not the perfect solution, but it works, and I don't do much heavy lifting over wifi
[17:38] <phunyguy> ahh ok.
[18:35] <wzssyqa> anyone is using nautilus-open-terminal on raring? Can it work correctly?
[18:35] <wzssyqa> Can it set the path correctly?