[00:53] <johnjohn101> 3 weeks 3 days. i can't wait
[00:55] <snadge> for what?
[00:55] <johnjohn101> release of 13.10 and hopefully ubuntu on my nexus 7
[00:58] <snadge> oh im already running 13.10
[00:58] <snadge> but you mean.. from a getting excited perspective that its actually released? :p
[00:59] <snadge> theres at least one bug that needs to be fixed
[01:00] <johnjohn101> bug for which? desktop or tablet?
[01:10] <snadge> desktop
[01:10] <snadge> its not a show stopper because nobody uses gnome fallback (no effects)
[01:10] <snadge> clearly ;)
[01:14] <johnjohn101> i didn't even know that existed, lol.  I am using it on a vmware machine at work and it's pretty good.
[05:55] <SuperLag> Is there any known issue that would cause $LAUNCHER_ICON to not retain its position?
[08:55] <snadge> so where do i start looking for this ctrl-alt-t gnome fallback session bug ?
[08:56] <snadge> figuring out which change broke it is half the fun
[09:23] <Smedles> hi all - annoying change in recent days to Unity - clicking the icon of an already running app, makes that app active, but does not change the virtual desktop like it used to
[09:23] <Smedles> any way to change this behaviour?
=== jje is now known as Guest58761
[09:44] <Smedles> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1229540 describes my issue
[09:44] <ubottu> Ubuntu bug 1229540 in unity (Ubuntu) "[regression] Clicking launcher icon does not switch to application with multiple workspaces" [Undecided,Confirmed]
[12:24] <boneslash> Hi guys is here anybody to help me with some delicius problem? :))
[12:24] <boneslash> *delicious
[12:26] <Dark_light> How are scopes in 13.10? last time I checked there was no way to disable them selectively, I liked some but don't care/want amazon ads when I'm searching for something
[12:27] <boneslash> It was bad idea to install Ubuntu 13.10 still errors :D
[12:35] <BluesKaj> Hiyas all
[12:39] <boneslash> HOYAAHAAHAHAHA MAN
[12:42] <BluesKaj> boneslash, ??
[12:42] <boneslash> wassup man I am just saying hallo in an original way :D
[12:43] <BluesKaj> well, that's original alright , boneslash :)
[12:43] <boneslash> Hey man are you on of the "helpers" or one of the "askers" do you know what I mean? :)
[12:44] <boneslash> *one
[12:45] <boneslash> BluesKaj
[12:47] <BluesKaj> boneslash, got a question , just ask ,if we can help we will
[12:48] <boneslash> alright Is there any possibility of installing other programs similar to Wine?
[12:49] <boneslash> I have pretty big lags in every game, It is pretty annyoing I tried to connect myself to other wifi sites but It didnt help me :(
[12:49] <boneslash> I mean in multiplayer of course
[12:49] <BluesKaj> steam games ?
[12:50] <boneslash> well not really :D
[12:50] <boneslash> Zdaemon - for running Doom 1, Doom2, hexen, Heretic etc..
[12:51] <boneslash> oh and I had also this problem in Ubuntu 13.04 so I tried to upgrade it to 13.10 but It doesnt help :(
[12:52] <BluesKaj> dunno much about games , boneslash , doubr running them in Windoiwsw VB environment would make them much faster
[12:52] <BluesKaj> doubt
[12:52] <boneslash> Ok thanks for help I hope It will help me
[12:53] <BluesKaj> what will help you ?  I don't think virtuals will help
[12:53] <boneslash> I'll see
[12:54] <boneslash> oh and I didnt say the whole story I am running it on Acer Aspire one - Netbook
[12:54] <BluesKaj> which ubuntu are you running ?
[12:54] <boneslash> but I dont use Unity - using Xfce :)
[12:54] <boneslash> 13.10
[12:54] <BluesKaj> ok
[12:54] <boneslash> there are everyday updates for it
[12:54] <boneslash> beta version of course
[12:55] <BluesKaj> right
[12:57] <boneslash> I had OS windows on this netbook
[12:58] <boneslash> but now Ubuntu I am newbie - trying new OS :)
[13:03] <BluesKaj> boneslash, being a new user it's usually best to run a stable OS like 13.04
[13:03] <boneslash> no problem I was experimentator always :D
[13:04] <boneslash> same with my mobile phone - but that is out of the topic :D
[14:28] <SuperLag> Nice. I didn't know about the Ctrl-Alt-t thing.
[15:32] <taneli> after dist-upgrade and reboot, i get only grub prompt
[15:32] <taneli> giving linux /vmlinuz and initrd /initrd.img it dies of kernel panic
[15:32] <taneli> unable to mount root fs
[15:32] <taneli> is this to be expected?
[15:34] <taneli> upgraded pretty much every day, rebooted every couple of weeks or so
[15:37] <taneli> was xfs support dropped?
[15:54] <taneli> xfs seems to be there in /lib/modules ... but it only tries ext3 ext4 vfat fuseblk
[16:09] <taneli> do i have to provide some new init= parameter to make it boot?
[16:21] <taneli> aha, had to provide root=/dev/sda1, now i get also "VFS: Cannot open root deice "sda1" or unknown-block(0,0): error -6"
[16:21] <taneli> any ideas what that might be?
[16:30] <MoPac> Hi all. I'm getting a "could not calculate upgrade" error when trying to upgrade in place, and I'm wondering if there is a common reason for that and/or a way to access details of the error
[16:39] <BluesKaj> MoPac:  what command are you using ?
[16:41] <MoPac> update-manager -d
[16:41] <MoPac> Sorry, BluesKaj: update-manager -d , following the gui
[16:43] <BluesKaj> MoPac:  so you're upgrading to 13.10 ?
[16:43] <MoPac> BluesKaj: Right
[16:48] <BluesKaj> what about sudo do-release-upgrade -d
[16:48] <BluesKaj> MoPac: ^
[16:49] <MoPac> BluesKaj: I could try that; is there any practical difference in what that does?
[16:50] <BluesKaj> no gui , unles you have a setting that prevents release upgrades
[16:52] <MoPac> BluesKaj: Don't mind a lack of GUI; just want to make sure that doing it that way isn't me working around something that I shouldn't work around because update-manager has seen that something is going to break
[16:55] <BluesKaj> MoPac: the package managers and apt all use the dpkg system to install /upgrade , if there's a problem dpkg will detect it
[16:55] <MoPac> awesome; thanks
[16:56] <johnjohn101> i know of no setting that prevents the update of releases, is there one?
[16:59] <BluesKaj> johnjohn101:   just the LTS only upgrade
[17:00] <BluesKaj> only one that comes to mind , but I don't know for sure
[17:00] <johnjohn101> it's ok.  just curious.
[17:02] <johnjohn101> hard to believe it's almost october and we're 3 weeks away. will 13.10 only have nine months of support?
[17:03] <MoPac> BluesKaj: Bah, do-release-upgrade also couldn't calculate but didn't give more details. Is there a way to run it verbose?
[17:04] <BluesKaj> ok, make sure you've updated, upgraded and distupgraded before trying to release upgrade , MoPac
[17:05] <MoPac> so it's safe to do dist-upgrade before release-upgrade?
[17:05] <BluesKaj> yes
[17:06] <BluesKaj> it also removes unecessary packages and dependenies etc
[17:08] <BluesKaj> MoPac:  also run autoremove and autoclean
[17:18] <BluesKaj> I have to reboot , testing beta 2 atm
[17:25] <ubuntu76> has anyone came across a glitch on 13.10 beta 1 when renaming a file it blanks out
[17:26] <ubuntu76> i was trying to report it but there is no option
[17:27] <TJ-> what blanks out? a GUI application's window ?
[17:28] <MoPac> BluesKaj: Sorry to keep bothering. Got the same result - unable to calculate - after all the preparatory steps
[17:30] <MoPac> BluesKaj: is there a way to get a verbose log for do-release-upgrade -d?
[17:30] <BluesKaj> look in /var/log/syslog
[17:32] <BluesKaj> did you reboot after running those clean commands etc , MoPac
[17:32] <MoPac> BluesKaj: I didn't although there wasn't really much for them to do
[17:32] <MoPac> I'll give that a try
[17:32] <BluesKaj> nop have tyou checked your partitions with gparted ?
[17:33] <BluesKaj> err MoPac^
[17:58] <ubuntu76> @Tj sorry i was called away the renaming of a folder the name just dissapears until you hit enter and you can't see what your typing
[17:59] <ubuntu76> also will we be able to upgrade to final beta when it comes out or do we have to do a clean install
[18:00] <BluesKaj> ubuntu76:  yes and no , but a clean install with data backup is always best
[18:05] <Anonynimity> I am running ubuntu 13.10. I have some lag issues with gaming.
[18:05] <Anonynimity> could anyone help me diagnose this?
[18:46] <MoPac> BluesKaj: unfortunately, still no joy on release upgrade after reboot. No obvious hints in the syslog - would it help to do a pastebin of the apt log?
[18:47] <BluesKaj> MoPac:  have you checked you partitions , there could be something there that will give us a hint
[18:47] <BluesKaj> your partitions
[18:47] <MoPac> what information about them should I check?
[18:49] <BluesKaj> make sure they show a definite size for one
[18:49] <TJ-> MoPac: Have you looked at the logs in /var/log/dist-upgrade/ ?
[18:51] <MoPac> Yes; the apt.log in there shows a number of breaks and fixes, and the main log shows various debug entries and then failure/abort
[18:51] <MoPac> 2013-09-24 12:40:53,219 ERROR Dist-upgrade failed: 'E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.'
[18:52] <MoPac> the last thing in the apt.log is Broken gnome-control-center:amd64 Depends on libcheese-gtk23 [ amd64 ] < 3.6.2-0ubuntu3 -> 3.8.3-0ubuntu1 > ( libs ) (>= 3.4.0)
[18:52] <MoPac>   Considering libcheese-gtk23:amd64 50 as a solution to gnome-control-center:amd64 32
[18:52] <MoPac>   Holding Back gnome-control-center:amd64 rather than change libcheese-gtk23:amd64
[18:52] <MoPac> (sorry for the bad paste)
[18:56] <TJ-> MoPac: has the /etc/apt/sources.list already been edited by do-release-upgrade to refer to saucy, not raring? If not, will "apt-get -f install" fix it? It sounds like the kind of problem you get when you've used a PPA package at some point and then removed mention of the PPA from the sources lists
[18:58] <MoPac> TJ-: it's all showing raring at the moment
[18:59] <MoPac> TJ-: apt-get install -f finds nothing to do
[18:59] <TJ-> MoPac: No, it wouldn't. Let me check on a 13.10 install here
[19:00] <MoPac> TJ-: thanks
[19:04] <FernandoMiguel> I'm having a weird keyboard issue
[19:04] <TJ-> OK, I believe I have an explanation for you. You probably need to check for, and if not found, file a bug.
[19:05] <FernandoMiguel> it's missing @ and ] from many apps
[19:05] <FernandoMiguel> it doesn't detect alt+gr
[19:06] <TJ-> MoPac: The version of libcheese-gtk23 in raring is 3.6.2-0ubuntu3, in saucy it is 3.8.3-0ubuntu1. gnome-control-center says it needs libcheese-gtk23 > 3.4.0 ... so the raring package satisfies the version.
[19:07] <TJ-> MoPac: Not sure if the solution is in gnome-control-center's Depends versioning or in ensuring libcheese-gtk23 is updated prior to gnome-control-center
[19:08] <TJ-> MoPac: But, you could try specifically "sudo apt-get install libcheese-gtk23" first, to get you out this bind.
[19:08] <MoPac> TJ-: libcheese actually shows up a number of times regarding breaks in the debug section of the apt.log http://pastebin.com/aTNjstTV
[19:10] <MoPac> Broken libcheese-gtk23:amd64 Depends on libclutter-1.0-0 [ amd64 ] < 1.12.2-0ubuntu3.1 -> 1.14.4-3 > ( libs ) (>= 1.13.0)
[19:10] <MoPac>   Considering libclutter-1.0-0:amd64 50 as a solution to libcheese-gtk23:amd64 20
[19:10] <MoPac>   Removing libcheese-gtk23:amd64 rather than change libclutter-1.0-0:amd64
[19:11] <TJ-> MoPac: too many breaks on many packages there
[19:12] <MoPac> TJ-: could there be a common source for the problems?
[19:13] <TJ-> MoPac: I suspect you need to return /etc/apt/sources.list to its Raring state: "sudo sed -i 's/saucy/raring/g' /etc/apt/sources.list" then "sudo apt-get update" which should return to a 'good' Raring state, then try again
[19:15] <MoPac> TJ-: My sources.list doesn't have any saucy in it, though
[19:17] <TJ-> MoPac: Hmmm, have you previously changed it then? because do-release-upgrade performs by, in part, changing the release codename to the dev release to figure out the upgraded packages. Which is where those log messages originated
[19:17] <MoPac> TJ-: when it aborts, it reverts to the original state, which I assume includes rewriting the sources.list?
[19:18] <TJ-> MoPac... hmmm, never seen it do that for me when upgrades have barfed!
[19:18] <MoPac> TJ-: Well, it's either very broken (not changing the codename in the first place), or it's working very well (changing and then reverting back)
[19:19] <MoPac> I guess I could manually s/raring/saucy ... ?
[19:20] <TJ-> MoPac: not a good idea! You'd get into a worse mess
[19:21] <BluesKaj> MoPac: perhaps backing up your data , then doing a clean installl is best in your case.
[19:22] <TJ-> MoPac: Here's a matching bug #1229491
[19:22] <ubottu> bug 1229491 in ubuntu-release-upgrader (Ubuntu) "Can't upgrade to Ubuntu 13.10 from Ubuntu 13.04" [Undecided,New] https://launchpad.net/bugs/1229491
[19:25] <MoPac> TJ-: BluesKaj: thanks for the advice -- since my setup is a bit complex (dual boot), I wouldn't really have time to mess with a clean install right now
[19:25] <MoPac> I'll check out the bug -- have to go away for a bit now
[19:27] <BluesKaj> dual boots are easliy handled by a cleran install , MoPac , they aren't difficult
[19:59] <wilee-nilee> kerloi, I have to take off in a minute or so, but we want to be on the correct channel is all, here is some additional uefi info. http://ubuntuforums.org/showthread.php?t=2147295
[20:00] <wilee-nilee> !uefi this as well is used
[20:00] <wilee-nilee> !uefi
[20:00] <ubottu> UEFI is a specification that defines a software interface between an operating system and platform firmware, it is meant as a replacement for the BIOS. For information on how to set up and install Ubuntu and its derivatives on UEFI machines please read https://help.ubuntu.com/community/UEFI
[20:01] <wilee-nilee> kerloi, Besides the IRC that author of the thread is excellent help, and visits and uefi thread on the forums to help, might be worth having a thread there if you do not get answers here.
[20:02] <wilee-nilee> and=any
[20:02] <kerloi> wilee-nilee, Well I followed the instructions and many other tuto. My problem is that I have a BIOS motherboard
[20:03] <wilee-nilee> kerloi, Yeah, they all are, so it is just a matter of getting the setup to work is all
[20:03] <wilee-nilee> I believe they all are if it is a oem uefi setup anyway
[20:03] <BluesKaj> kerloi:  that should not be a preoblem , no uefi is easier to use installtion -wise than uefi is
[20:03] <kerloi> AN other problem is that I am unable to see any problem during the installation ... Even when I re-run the grub commands from the live usb everything seems fine.
[20:04] <wilee-nilee> I have to catch a bus now is all, so just wanted to get you some info.
[20:04] <kerloi> wilee-nilee, ok thx
[20:04] <wilee-nilee> no problem, best of luck. ;)
[20:08] <ker_loi> Hi all. I bought a new laptop few weeks ago and I was unable to install ubuntu 13.04 on it (many hardware problems ...) I've decided to test ubuntu 13.10. The installation went fine but then when I start my laptop I have the grub 2 command line ... I tried to re-install without success or to live boot and re-run grub update and install without any success
[20:09] <BluesKaj> ker_loi: grub rescue ?
[20:11] <Version1> ker_loi:  can you boot using live CD?
[20:12] <ker_loi> Version1, yes I have a live usb
[20:12] <ker_loi> working
[20:14] <Version1> ker_loi: have you deleted the ubuntu partition
[20:18] <kerloi> Sorry my connection is not good tonight
[20:20] <loiker> >< Fed up with these disconnections
[20:21] <loiker> I see "GNU GRUB version 2.00-19ubuntu1" at the top, a line of informations about grub and then the "grub>"
=== loiker is now known as kerloi
[20:24] <Version1> kerloi: you can use Grub2Win if you have windows installed
[20:24] <kerloi> Version1, I don't
[20:34] <Version1> kerloi: i think you need to type commands and boot the kernel
[20:39] <ker_loi> Well it's working. Maybe it will be enought for now. I'll wait 13.10 to be released to fix that problem
[20:39] <ker_loi> Thx Version1