[00:23] still waiting === CEnnis91_ is now known as CEnnis91 [08:25] Is cdimage.ubuntu.com the only official place to get the daily iso images? Just wondering if there's an EU mirror where I can download 13.10 faster than what I'm getting from the main one. [08:26] SuperLag, Have you tried the torrents? [08:27] wilee-nilee: I don't see any torent links on cdimage.ubuntu.com/daily-live/current/ [08:27] torrent links, that is [08:27] otherwise, I would [08:28] SuperLag, I use zsync then you only get what is new. http://cdimage.ubuntu.com/daily-live/current/ [08:30] No reason to download the whole iso [08:32] Oh? [08:32] I've never used that before, so I'm not familiar with it [08:32] it only gets the new bits? [09:14] so how, exactly, does that work? does it just add the new stuff to the existing iso? === steveire_ is now known as steveire [10:22] Is the the correct channel for information about sausy? [10:54] hi [10:54] I want to install boot-repair in ubuntu 13.10, but the package is not found. I did sudo add-apt-repository ppa:yannubuntu/boot-repair [11:10] Hi ActionParsnip [11:10] esing: yes its the same. You will more than likely have a LOT of issues withh the release [11:10] esing: it is NOT ready and NOT stable [11:11] The package is not found, though I did sudo add-apt-repository ppa:yannubuntu/boot-repair [11:11] esing: so if you cannot do basic stuff like add PPAs etc without having to ask then you will struggle. There may be a day when an update gets pushed out that needs users to use root recovery mode to edit afile to get a deskto psession [11:11] esing: that stuff can and does happen [11:11] esing: or you may lose web access, needing files and so forth to be transferred from other systems [11:12] esing: and pretty much any other dumb thing going wrong you can think ok [11:12] esing: does Precise not work> [11:12] Hm, I see, maybe there's a workaround to still get boot-repair running [11:12] Oh, I didn't try Precise yet. Just tried 13.4 [11:12] *04 [11:13] esing: Precise is LTS and supported til April 2017. Raring is only supported to January 2014 [11:13] I use Haswell's igpu, and therefor I thought 13.04 would rather support the new haswell igpu than Precise does [11:13] esing: Saucy is also only 9 months supported and dies in July 2014 [11:14] esing: why did you not try the LTS first?? [11:14] I thought since 13.04 is newer, it has rather support for haswell's igpu [11:15] Do you recommend me to try LTS, and do you know if it supports haswells igpu? [11:15] esing: its worth trying the LTS theyare designed for stability, if there are things in the newer drivers and kernel then you may be forced to use pre-release but expect a bumpy ride [11:17] Is there a workaround for installing boot-repair? Like can I copy its package with usb? [11:17] esing: you can chroot using liveCD and reinstate Grub that way [11:18] esing: easy peasy [11:18] Oh, didn't thought about that [11:18] esing: omgubuntu has a guide called: sticking it to grub [11:18] I use uefi dualboot with windows, should still work your way? [11:19] esing: not used UEFI, sorry === Rallias is now known as NotRallias === cmagina_ is now known as cmagina [13:37] Hi folks [16:19] hi folks, I installed Mir, found it made my system unusable, had to boot into text mode, did a ppa-purge and a apt-get dist-upgrade & apt-get update --fix-missing and it was still broken. I had to edit /etc/lightdm/lightdm.conf.d/10-unity-system-compositor.conf and comment out the line for type=unity and then reboot. [16:20] In case anyone else runs into problems with Mir... that solution got me back to "normal" [16:20] although dmesg has some interesting output now :) === ritz__ is now known as ritz|dead === shadeslayer_ is now known as shadeslayer === sam113101 is now known as sam113101_afk === sam113101_afk is now known as sam113101 [22:25] no more alt+tab in ubuntu? [22:32] sam113101: still wfm [22:32] FernandoMiguel: wfm? [22:33] works for me [22:33] actually it works much better than on 13.04 [22:34] doesn't work for me [22:35] maybe last update? [22:35] haven't rebooted yet [22:36] can you try it please? [22:41] sam113101: not planning on rebooting till I go to bed, sorry [22:41] too much stuff open [22:41] exposé doesn't work either [22:42] still working here too [22:43] The following packages will be upgraded: [22:43] android-tools-adb android-tools-fastboot dmsetup evince evince-common firefox firefox-globalmenu firefox-locale-en firefox-locale-pt google-chrome-unstable libdevmapper-event1.02.1 [22:43] libdevmapper1.02.1 libevdocument3-4 libevview3-3 libgsettings-qt1 liblightdm-gobject-1-0 liblvm2app2.2 libsystemsettings1 lightdm qtdeclarative5-gsettings1.0 system-image-common [22:43] system-image-dbus ubuntu-system-settings [22:43] noting out of the ordinary here [22:43] ;( === sam113101 is now known as sam113101_afk === sam113101_afk is now known as sam113101 [22:51] got it to work for a moment [22:51] ok it works again [22:51] but there are even stranger bugs now [22:54] is there a special place to report them? [22:57] sam113101: launchpad ofc [22:57] $ ubuntu-bug unity [22:57] but what differentiate ubuntu from ubuntu+1 on launchpad? [22:58] those bugs weren't there on 13.04 [22:58] don't want to comfuse anyone [22:58] sam113101: the bug tracker will know you are on 13.10 [23:00] sam113101: ubuntu-bug tells launchpad which version you are using, along with a bunch of other system info [23:01] didn't know about it [23:01] so that's on ubuntu+1 that most of the development of ubuntu happens, right? === sam113101 is now known as sam113101_afk === sam113101_afk is now known as sam113101 [23:03] this is really buggy [23:03] I don't even know where to begin [23:04] and how am I supposed to know which packages the bug involves? [23:07] sam113101: force of habit [23:07] you can ask here or on #ubuntu-bugs [23:07] is the bar (where the wifi, sound, etc., icons are) part of unity? [23:08] yes [23:10] how is it call? [23:10] called* [23:10] nity nite [23:14] "top menu bar" === sam113101 is now known as sam113101_afk === sam113101_afk is now known as sam113101