[00:30] <Wug> I don't suppose anyone would have an insight into why the unity "search your computer and online sources" panel never shows any results? it just stays blank forever.
[00:36] <Daekdroom> Wug, it takes awhile to load, for me.
[00:42] <dpb1> Wug, that's happening for me right now after an upgrae to saucy.  I'm thinking it's dbus related, but I'm not sure yet.
[00:42] <dpb1> Maybe the lenses are not loading.  I'm not sure yet.
[00:43] <Wug> dpb1: what makes you think it's dbus
[00:43] <Wug> I don't know enough about unity to come to any conclusion
[00:43] <Wug> Daekdroom: how long is "a while"
[00:44] <Daekdroom> 10 seconds, tops.
[00:44] <Wug> yeah mine's definitely broken then
[00:44] <Daekdroom> But once it loads, it works fine and quick until I restart my session / reboot
[00:44] <Wug> does yours start with some things, and refine the search like it used to?
[00:45] <Wug> mine is basically blank forever.
[00:45] <Wug> it starts with nothing in it, and it never loads programs, files, web history, or anything else that it's probably supposed to have, even if I give it some text to chew on
[00:48] <Apteryx> Hello, using 13.10, I installed latest updates, now Unity won't start. Anyone has debugging tips?
[00:53] <wilee-nilee> Apteryx, kernel update perchance and a proprietary graphic driver?
[00:55] <Apteryx> wilee-nilee: no proprietary. Using intel HD
[00:55] <Apteryx> but kernel update, probably yes.
[00:56] <wilee-nilee> Apteryx, any customizing of compiz?
[00:56] <Apteryx> In dmesg I saw some problem about compiz segfaulting, but I not sure if this was during boot or during my attempt in a linux VT at starting manually unity
[00:56] <Apteryx> wilee-nilee: nope
[00:57] <Apteryx> Is there a special log file for Unity
[00:57] <wilee-nilee> Apteryx, There are restarts for compiz might be worth it. http://ubuntuhandbook.org/index.php/2013/08/reset-unity-and-compiz-in-ubuntu-13-10/
[01:04] <Apteryx> wilee-nilee: I think dconf reset -f /org/compiz/ && setsid unity did the trick!
[01:04] <Apteryx> Thanks for helping out!
[01:04] <Apteryx> Will now try a complete reboot
[01:05] <wilee-nilee> Apteryx, cool
[02:59] <zeep> is there any way to manage tray icons from wine applications?
[03:17] <prototrout> Hi. I'm running a 13.10 daily build off an encrypted flash drive (USB 2.0, port is USB 3.0) and getting awfully slow transfer speeds: 2.3MB/sec writes, 0.3MB/sec reads. dmesg calls it a "high-speed USB device". Anyone have ideas about why it's running so slow, or other places I could ask for help if this is a bad place? (I haven't tried using a previous release as it'd be painfully slow to set back up if it keeps transferring at this spe
[08:18] <rwsq1> how safe is it to jump from 12.04 to 13.10 in one hit (dist-upgrade)?
[08:18] <bazhang> not at all
[08:18] <bazhang> and thats not what dist-upgrade does even
[08:19] <bazhang> just use the installer to preserve /home and install fresh
[08:21] <rwsq1> bazhang, so if I change my sources to saucy and apt-get dist-upgrade it won't try to upgrade me to saucy?
[08:22] <bazhang> !dist-upgrade
[08:22] <rwsq1> !upgrade
[08:22] <bazhang> thats not the way to do it.
[08:22] <rwsq1> ok - I've only been doing it that way for 8 years :)
[08:22] <bazhang> one hit is LTS TO LTS
[08:23] <bazhang> since 5.10?
[08:23] <rwsq1> well since debian potato to be exact
[08:23] <bazhang> so two times
[08:24] <bazhang> do whatever you wish, your method is not supported at all
[08:24] <rwsq1> oh I'd like to be supported, but I'm not sure why apt-get dist-upgrade doesn't work
[08:25] <bazhang> the new installer makes a sane upgrade really easy, it's rather astounding
[08:25] <rwsq1> you mean do-release-upgrade ?
[08:25] <rwsq1> oh install off cd/
[08:25] <bazhang> the term dist-upgrade is confusing, thats all
[08:25] <rwsq1> I just hate messing around with burning media
[08:25] <rwsq1> and I like to work while it upgrades
[08:25] <bazhang> use a usb stick
[08:26] <bazhang> even the unsafest method requires some user input, to ok certain packages, keep maintainers or old (eg grub), and so on
[08:27] <rwsq1> yep, I normally run it in a console and flick back to it every so often to check it's not asking me something
[08:28] <bazhang> especially , very late in the install, the whole "these packages will be removed as they do not exist"
[08:29] <rwsq1> as long as it leaves me with a working kernel and package manager I'm normally ok
[08:30] <bazhang> that one caught me the last upgrade, expected to have a fresh install and it was hung on that screen
[08:31] <rwsq1> ok well I think I'll just run do-release-upgrade a few times
[08:33] <bazhang> the new installer is *really* impressive, and I've been on Ubuntu since nearly the start
[08:34] <bazhang> but if you want to jump through the 3 upgrades to get there, thats great too
[08:34] <bazhang> I did that for 5 plus release cycles
[08:35] <rwsq1> I'll probably get to use the new installer on another box, but I need to also be productive today
[08:37] <rwsq1> back in the day, it used to be easier to install stormix, change sources and dist-upgrade to get debian than it was to use the debian installer, so things must have got better :)
[08:39] <bazhang> hehe
[08:41] <rwsq1> at the time debian had a t-shirt that said "Debian: what your Mom would use if it was 10 times easier"
[08:42] <rwsq1> in actual fact it was pretty straightforward to use, but not to install
[08:42] <rwsq1> but then along came ubuntu and even that part was plain sailing
[08:42]  * rwsq1 will stop talking about the good old days now
[11:08] <pvh_sa> bazhang, thanks for that. I've been doing my upgrades like rwsq1 did - edit sources and dist-upgrade.
[11:09] <pvh_sa> i notice that somehow key packages on my 13.10 have gone missing (e.g. gnome-control-center) so i think when 13.10 is released i'll use the installer to "upgrade" to the final release, just to make sure everything is in place
[11:23] <bazhang> :)
[12:09] <BluesKaj> in Kubuntu, what's the setting in muon that upgrades the OS to the next release?
[12:16] <Captain_Proton> I did and upgrade from efi 64bit 13.04 to 13.10 now when I start my computer i receive a message like "serious errors while checking the disk drives for /boot" press I - S - M
[12:17] <Captain_Proton> I have done fsdk -Aa and a few other I found online but none have fix the problem
[12:17] <Captain_Proton> Is there a way to repair /boot
[12:34] <BluesKaj> Captain_Proton. not many ppl use /boot anymore , it's more common to have / and /home and grub installed to the mbr
[12:38] <alankila> Yay for the era of disposable OSes.
[12:38] <alankila> The data is important -- I'm waiting for debian to realize that I don't want any data at all under /var, but would prefer /home/postgresql, etc.
[12:39] <alankila> Every service I enable, I must evaluate to determine if it has data I want to keep and if so, into /home it goes, along with necessary changes to apparmor profiles
[13:29] <thebishop> is it normal to have 5 compiz processes running simultaneously?
[13:46] <thebishop> 5 compiz processes, frequently gobbling 80% usage across 4 cpu threads.  seeing backbuffer articles on some apps when scrolling text.  Intel graphics.  13.10 not looking good here.
[14:27] <SonikkuAmerica> elfy: (If you're around) What am I supposed to zsync my B2 image to?
[14:33] <hobarey> hey
[14:33] <hobarey> why no more partying and countdown and fireworks?
[14:34] <hobarey> does the community frown upon such behavior now?
[14:41] <k1l> !party
[14:42] <BluesKaj> usually, upgrading to the new release is an anticlimax for me , since I've been running it for 5mos :)
[14:46] <philinux> The loco's will be active
[14:48] <BluesKaj> personally i don't see the point of a release party chat, one gets tired of the incessant  'Is it out yet ?"
[14:49] <BluesKaj> :)
[14:50] <philinux> Bluefoxicy: indeed. it's out already on this lappy
[14:51] <philinux> dang tab complete
[14:51] <philinux> BluesKaj:  indeed. it's out already on this lappy
[15:59] <thebishop> possibly related to my terrible compiz performance: the dash is opaque when opened
[15:59] <thebishop> actually, even the launcher is opaque
[16:07] <wastrel> isn't that a setting
[16:07] <wastrel> my dash is always opaque
[16:08] <wastrel> launcher was until i did a setting
[16:08] <wastrel> oh panel
[16:08] <wastrel> i was thinking panel not dash
[16:08] <pip__> If anyone's interested the lubuntu 32 bit daily from 15th installs well - no freezes
[16:09] <CrackerJack> os[Linux 3.11.0-12-generic x86_64] distro[Ubuntu "saucy" 13.10] cpu[2 x AMD Athlon(tm) 7750 Dual-Core Processor (AuthenticAMD) @ 2.70GHz] mem[Physical: 3.6GB, 75.3% free] disk[Total: 33.9GB, 15.7% free] video[NVIDIA Corporation C77 [GeForce 8100 / nForce 720a]] ether[NVIDIA Corporation MCP77 Ethernet] sound[HDA-Intel - HDA NVidia]
[16:10] <CrackerJack> final date to realise is
[17:58] <BluesKaj> not very impressed with flash on FF , chromium does a much better job of playing video on youtube
[17:59] <wastrel> youtube ♥
[20:12] <sam113101> when will ubuntu 13.10 be out?
[20:12] <xarses> read the topic
[20:12] <sam113101> TOPIC TOPIC
[20:12] <sam113101> WHERE ART THOU
[20:12] <Pici> the topic says that 13.04 has been released...
[20:12] <Pici> oops
[20:13] <sam113101> tomorrow?
[20:13] <sam113101> the page says October 17th
[20:13] <Pici> sometime on the 17th
[20:14] <sam113101> which timezone
[20:14] <Pici> GMT
[20:14] <Pici> but, at any time during the day
[20:14] <k1l> !party | sam113101
[20:16] <sam113101> where can I get a list of new features/improvements in saucy?
[20:16] <IdleOne> !releasenotes
[20:18] <IdleOne> https://wiki.ubuntu.com/SaucySalamander/ReleaseNotes
[20:20] <xarses> wow, todays updates are even worse from fridays
[20:20] <xarses> my usb nic is resetting every 30s - 4 min now
[20:20] <xarses> and i haven't had wifi for days
[20:26] <sam113101> IdleOne: nothing human-friendy to read
[20:28] <IdleOne> Did you mean like a murder mystery? They info you asked for is technical in nature. I think the wiki format is very readable.
[20:29] <IdleOne> s/They/The/
[20:40] <xarses> yep, 13.10 horrible
[20:41] <xarses> s/horrible/is horrible/
[20:55] <johnjohn101> last day here for a while, thanks for the support
[20:59] <sam113101> xarses: how is it horrible?
[20:59] <sam113101> IdleOne: is it?
[21:00] <xarses> in the last 8 days i've had 4 major failed regressions
[21:01] <sam113101> maybe they will soon be fixed
[21:01] <xarses> well they weren't broken before
[21:02] <johnjohn101> what is broken?
[21:03] <xarses> 1 missing backlight driver fix that was present in the kernel in 3.9 and 3.10. 1 missing wifi driver in 3.11 and 3.12. Network Manager is nigh useless in 3.11 and 3.12. Network manager won't act on 3.12 kernels..  3.11 has some serious issues with my usb3 NIC that forced me to load the 3.12 kernel
[21:04] <xarses> the last one with the usb3 nic, just appeared with todays update of network-manager-gnome
[21:06] <johnjohn101> xarses: that's not good for that to happen one day before release.
[21:06] <xarses> none of that is acceptable to happen 1 week before a release
[21:07] <xarses> As soon as my work project is done, I'm probably jumping to debian unstable
[21:09] <johnjohn101> wow, sorry to hear that.
[21:09] <xarses> I'm not even sure how to file bug reports for this
[21:15] <johnjohn101> xarses: is that a usb3 to ethernet?
[21:17] <xarses> yes
[21:17] <xarses> i found https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1155139
[21:18] <xarses> which appears to be one of the issues im having with nm
[21:18] <xarses> I'm wondering why something from the 3rd thats marked critical hasn't been merged.
[21:19] <johnjohn101> doesn't make sense
[21:22] <xarses> any one know how to get network manager to "manage" my wifi device again?
[21:23] <ChogyDan> xarses: did you create settings for it in /etc/networking?
[21:25] <xarses> ChogyDan: other than it was working before last firday, no
[21:26] <xarses> blah, the 3.12 kernel is missing the cypress muti-touch patch again
[21:28] <ChogyDan> xarses: shrug, I dunno, that's the only thing I know.  It is surprising that the release is tomorrow.  I have a few bugs I've been sitting on that are kinda annoying...  I figured that they hadn't been fixed because the release is at the end of the month, but little did I know
[21:30] <xarses> are there supposed to be config files in /etc/network/?
[21:32] <ChogyDan> xarses: no, if you did configure via /etc/networking (that's the file there, not a folder) then I think nm would unmanage thee device
[21:33] <xarses> there is no /etc/networking file
[21:33] <xarses> and nm attempts to manage eth0 fine
[21:33] <ChogyDan> yeah, that's why I don't know. :/
[21:41] <lenzeor> Hey there! I heard 13.10 drops tomorrow. Is upgrading still as unsafe as it used to be? Im on 13.04...
[21:44] <ChogyDan> lenzeor: I think the upgrade process is pretty safe.  You should be fine in that regard
[21:46] <lenzeor> OK, that sounds good.
[21:47] <lenzeor> I currently use a PPA to get a proprietary driver for my graphics card. (AMD Legacy) Any way to port that over to 13.10?
[21:48] <ChogyDan> lenzeor: check the ppa, see if it is ported already
[21:50] <lenzeor> https://launchpad.net/~makson96/+archive/fglrx Does not seem so
[21:51] <lenzeor> Do I have to wait until the maintainer updates it for 13.10?
[21:52] <ChogyDan> lenzeor: pretty much.  I'm not sure though.  The ppa maintainer would be the one to ask.  And if the answer were simple, I imagine it would already be updated in the ppa.  A bit of a circular logic there
[21:54] <lenzeor> Phew..
[21:55] <lenzeor> I would have to sign up on launchpad to email him...
[21:55] <lenzeor> Hmmm... I guess I'll stay on 13.04 then. I wouldn't mind using the opensource drivers, but the performance just isn't even close.
[21:56] <ChogyDan> lenzeor: oh, it says on the ppa page, no 13.10 support, use the open source drivers
[21:58] <lenzeor> Aww nooo
[21:58] <ChogyDan> mhm
[21:59] <lenzeor> No more games. :/
[22:02] <lenzeor> And those dckheads at AMD only support up to kernel 3.4 -.-
[22:03] <ChogyDan> lenzeor: and phoronix confirms the performance will suck, sorry: http://www.phoronix.com/scan.php?page=article&item=amd_windows8_legacy&num=1
[22:06] <lenzeor> That's hard... I was only wondering: If that guy could patch it to work under 3.8, why can't he do the same with 3.10?
[22:06] <lenzeor> ...
[22:08] <ChogyDan> lenzeor: he just mods AMDs patch for ubuntu.  He doesn't do the patch himself
[22:10] <lenzeor> Oh I see. That's quite a downer. I'm not used to things getting WORSE in the open-source world.
[22:10] <lenzeor> Also... I can't be the only one having that problen, can I?
[22:24] <brainwash> the only one still complaining about this.. simply use something that works, like 12.04 with kernel 3.2
[22:24] <lenzeor> Yup, that's what I will do, brainwash.
[22:25] <lenzeor> Sorry for complaining.
[22:25] <brainwash> don't worry :)
[22:25] <lenzeor> I'll have to downgrade to 12.04 though. :/
[22:26] <lenzeor> okok thanks for the help ChogyDan and brainwash
[22:26] <brainwash> did you already test the new version of the source driver?
[22:26] <lenzeor> You mean open-source driver?
[22:27] <brainwash> uhm, yes
[22:27] <lenzeor> Yeah, I tested the one that came with 13.04
[22:27] <lenzeor> It works fine
[22:27] <lenzeor> but it's not nearly as fast as the one from the PPA
[22:28] <brainwash> it should be worth doing some tests with the latest version and kernel 3.12
[22:28] <lenzeor> Yeah, that's right.
[22:28] <lenzeor> What kernel does 13.10 come with?
[22:29] <brainwash> 3.11
[22:29] <brainwash> the current stable kernel version
[22:30] <lenzeor> I'll definitely test.
[22:31] <brainwash> well, you can enjoy ubuntu 13.04 3 more months before they force you to upgrade
[22:31] <lenzeor> or downgrade to 12.04 LTS
[22:31] <brainwash> :)
[22:32] <xarses> or upgrade to the sable debian-unstale
[22:32] <xarses> s/sable/stable/
[22:32] <xarses> typo's a plenty
[22:32] <lenzeor> I like to be on ubuntu actually
[22:32] <lenzeor> nothing else has ever worked for me
[22:32] <xarses> i would to, but 13.10 just got horrible
[22:33] <lenzeor> how so?
[22:36] <xarses> since thursday I've seen a number of regression bugs crop out of nowhere for things that a) wheren't issues or b) already fixed
[22:36] <snadge> i know what the solution to that is xarses .. install fedora 19, it's awesome and perfect.. and there's no issues at all
[22:36]  * snadge rolls on the floor crying with laughter
[22:37] <xarses> you sound like my co worker
[22:37] <snadge> seriously .. once you've gone fedora.. ubuntu seems like this wonderful fairyland, where everything just works perfectly
[22:38] <xarses> I've been using 13.10 since june, and the updates in the last 5 days have been the most un-stable and highest impacting
[22:38] <snadge> even the stuff that doesnt work.. you can at least find a fix for it.. or install a previously working package etc
[22:38] <snadge> well.. im running it on my home and work pc
[22:38] <xarses> ya, i'm not using a redhat based distro
[22:38] <xarses> I'll use debian-unstable or go back to gentoo
[22:39] <snadge> dude, thats harsh
[22:39] <snadge> at least in gentoo's case :p
[22:39] <snadge> thats like chopping your foot off, because you have an ingrown toenail
[22:40] <snadge> what regressions have you noticed?
[22:40] <snadge> mir related?
[22:40] <xarses> the Dell XPS backlight issue is back, was fixed in 3.9, 3.10
[22:41] <snadge> ok so presumably thats kernel related
[22:41] <snadge> the kernel guys are actually pretty good about that
[22:41] <xarses> the trackpad multi-touch bug is back in 3.12
[22:41] <xarses> was fixed in 3.10 and 3.11
[22:41] <snadge> another kernel issue
[22:41] <snadge> or xorg input?
[22:41] <xarses> kernel
[22:42] <snadge> have you tried a mainline kernel?
[22:42] <xarses> im on 3.12 rc5
[22:42] <xarses> which still have both
[22:42] <snadge> oh that blows.. thats a mainline kernel regression
[22:42] <xarses> network manager wont manage my wifi now
[22:42] <xarses> since thursday
[22:43] <xarses> nm wont start correctly since tuesday
[22:43] <snadge> try a less new mainline ?
[22:43] <xarses> 3.11 has same issue
[22:43] <snadge> downgrade the ubuntu kernel to the previous one that works.. note its exact version.. reboot into the latest affected kernel
[22:43] <snadge> and run ubuntu-bug linux
[22:43] <snadge> hmm.. when did it break then?
[22:43] <xarses> 3.11 randomly and frequently drops my usb3 to ethernet
[22:44] <xarses> which is why im on 3.12 rc5
[22:44] <xarses> which also appears to have a gpu lockup bug
[22:44] <xarses> nm has a core-dump issue that had a patch since 10-3
[22:45] <xarses> and hasn't been merged
[22:45] <xarses> which may or may not be related to the nm wont start and nm wont manage wifi issue
[22:45] <snadge> ok so is there a kernel where everything works?
[22:45] <snadge> it's a regression.. so it shouldn't be overly difficult to track which update(s) broke it
[22:47] <xarses> 3.10 was working for me, but some updates on thursday caused me to need to use a newer kernal, in that NM stopped being able to aquire a lease, but not because dhclient couldn't get a lease
[22:50] <snadge> that's disappointing
[22:51] <xarses> hence feeling like going back to gentoo is warranted
[22:51] <snadge> well.. at least when that breaks, its expected.. as opposed to an unfortunate inconvenience, that's likely to be fixed
[22:52] <snadge> :P
[22:52] <snadge> the effort you spend just installing gentoo.. is probably 5 times the amount of effort than it is to find those bugs AND resolve them
[22:52] <xarses> at least when gentoo breaks, I know how to fix it, all this ubuntu crap hides everything from me
[22:54] <snadge> sort of.. ubuntu is no giant mystery.. its basically debian.. all sources are published, and revision history etc.. launchpad
[22:55] <snadge> i wonder if you can find a newer 3.10 kernel with backported fixes for nm
[22:56] <xarses> no clue
[22:56] <xarses> ahh, figured out how to get my wifi driver back
[22:56] <xarses> thats a start
[22:57] <xarses> that was way not obvious
[22:57] <snadge> yeah.. you should be able to at least work around those issues for now
[22:58] <xarses> nm is cranky poop
[22:58] <snadge> but definitely file bugs for things that arn't working.. like the touchpad
[22:58] <snadge> and the backlight
[22:58] <xarses> the bug i can find for the backlight is a bunch of finger pointing
[22:59] <xarses> and the touchpad bug is supposed to be resolved
[22:59] <snadge> thats standard for a bug where the devs have absolutely no idea what the actual problem is
[22:59] <snadge> got the bug number?
[23:00] <xarses> Bug 1048258
[23:00] <snadge> the good news is.. its not closed
[23:00] <snadge> whut.. fix released?
[23:01] <xarses> regression fail
[23:03] <snadge> lol.. it seems they need to include this patch every release
[23:03] <snadge> then fail to
[23:03] <snadge> ahh well, theres a test kernel that fixes it
[23:03] <snadge> its got a heat rating of 60, and affects 10 people.. not bad
[23:03] <snadge> i'll click on it just because i can
[23:04] <xarses> bug 1169376
[23:06] <snadge> ive subscribed to both
[23:06] <snadge> lol 31 people for the backlight
[23:07] <snadge> 3.8.0-30-44 this version apparently fixes the backlight.. if you can find the exact patch that does it, i can maybe take a look at the current sources and see what the go is
[23:08] <xarses> 3.10 has it
[23:08] <xarses> 3.11+ is missing it
[23:08] <xarses> the issue only occurs IF you have uefi boot with out legacy module
[23:09] <snadge> ergh :P
[23:09] <snadge> SpewEFI
[23:10] <snadge> ironically i have a mac mini at work, that fedora 19 wouldn't install on.. at all.. the errata noted the issue
[23:10] <snadge> the workaround mentioned in the errata failed
[23:10] <snadge> the latest respin for fedora 19.. also failed in the same manner.. but bug is marked "wontfix" for f19.. and still remains open in rawhide (f20 dev)
[23:11] <snadge> ubuntu 13.10 installed without issue, and everything works.. except the 2nd display wasn't detected, which was worked around by installing a mainline kernel
[23:19] <xarses> lucky ducky
[23:19] <xarses> :P