[00:00] No! Super+num doesn't work! That's a total dealbreaker. Guess it'll be fixed by release. :) [00:01] I just installed today's image, the upgrade was working really oddly. [00:02] what does that mean? [00:02] how do I re-attach to the oldest Screen session? [00:03] BUGabundo: assuming the oldest one is the one screen considers "first", screen -d -RR would do it. [00:03] jo-erlend: it means that I had upgraded to 11.10, but it was acting strangely, so I formated / and installed it there. [00:03] nope [00:03] that's actually the newest rww [00:03] fun [00:04] screen -ls [00:04] Pici: I know how to list them [00:04] I'm just being lazy.... [00:04] BUGabundo: Clearly :P [00:04] this is so powerful, must allow me that [00:14] this new release cycle of Mozillas bother me a little bit. I haven't been able to use moonlight a single time since that started. [00:16] jo-erlend: flash should work from multiverse [00:16] micahg, hmm? [00:17] jo-erlend: ubufox should attempt to install flash from multiverse or install gnash [00:17] I've never seen that. [00:17] it always tells me that no suitable plugin was found, then it presents me with a button to install manually. If I do, I'm sent to Adobes homepage. [00:18] jo-erlend: the plugin finder service isn't usually updated until close to release [00:18] ah, ok. [00:19] and there's an FTBFS bug blocking a moon update to work with Firefox 4+ [00:19] ftbfs? [00:19] fails to build from source [00:20] ah. [00:21] MADNESS [00:21] 24 0.02s 2.03s 20.3G 2.3G 0K 180K ? ? 71% chromium-brows [00:32] screen -r `screen -list | grep '.*\..*(.*)' | sort | head -n 1 | awk '{ print $1 }'` [00:32] rww: Pici ^^^ [00:34] eww [00:36] agreed [00:38] rww: LOL [00:38] it works! [00:39] can you do better? [01:12] nite [01:17] from what I've seen so far, I think I want to upgrade. [01:19] I want to upgrade. bbl [01:23] I've noticed the bottom little bit of my java windows is not displaying. Is that a known issue? [01:33] I can't remember the last time I upgraded at such an early stage. Must have been feisty or dapper or something. Hope this works well :) [01:34] jo-erlend, it's actually working well so far except for the grey banner at the bottom of java windows. [01:35] yes, because I care much about java windows :> [01:44] uh... I get an error 403 forbidden when downloading packages. How come? [02:06] switched to another archive and that worked. === __mikem is now known as mmiller235 [06:45] Hi, is "list columns" view supported by nautilus in oneiric? I can't find it... [10:56] Why does python-dbus break python-qt4-dbus :( [11:15] anyone know of workrave alternatives that work on oneiric? [11:15] (workrave is not installable right now) [11:37] is a bug filed? [11:39] installs fine in my chroot [11:52] damn, I forgot to uninstall the catalyst driver before upgrading, which causes the system to freeze at boot. What's the easiest way of fixing that? I booted in recovery mode, but I could no longer find an option to fix X. [11:55] jtaylor: installing libpanel-applet2-0 (of which workrave depends) causes gnome-panel to be uninstalled [11:55] how do I start the failsafe x? [11:57] did you install lightdm-gtk-greeter? [11:57] jo-erlend: ^ [11:57] jtaylor, I've just upgraded from 11.04 [11:57] but I'm fairly certain it's the catalyst driver for my hd5850. It always does this when I upgrade the kernel. [11:58] there was a problem with lightdm casing hanging boot [11:58] and since the radeon driver now is much better, I just want to remove the proprietary driver. [11:58] anyhow you get into a failsafe by choosing the recovery kernel in grub [11:58] its possible that installing the greeter will solve your problem [11:58] how? I couldn't find any such options anymore. There used to be an option in that menu you get, but ... [11:59] there should be a more options option now where its hidden [11:59] you could also try booting from your previous kernel [11:59] well, until proven otherwise, I will assume it's the catalyst driver that causes these issues, since it's consistently caused exactly this problem each time I've upgraded the kernel. [12:00] booting works fine on my machine, I just get glichtes after login ^^ [12:00] listen. I just want to remove the proprietary driver. I've never wanted it and now I no longer need it. [12:00] also cataclyist [12:00] yes, but on my system, on many clean installs, every single time I've upgraded the kernel, I cannot boot afterwards. 100%. [12:00] I just want to say it may not be the driver causing the problem [12:00] this time [12:01] yes, but until I know that for an absolute certainty, I will still assume that it's the driver causing the issue. But in any case, I want to remove the driver. I really, really don't want to use it. [12:02] it's insanely slow compared to the open driver and as I've said, I know from experience that it's also very unstable. And after all, I do prefer open drivers. [12:02] I'm not arguing that the prop drivers are good [12:02] so what I'm asking, is "how do I run failsafex?" [12:03] choose the grub boot entry for recovery or edit the line (pressing e I think) [12:03] well, that was the first thing I did, because in earlier versions, there was an option to "Fix X" or something. There no longer is. [12:04] you just need a root shell, from there you can remove the drivers [12:06] I wish I could remember the name and location of the uninstall script. :/ [12:06] its not installed via the package? [12:06] no, as I said, after any kernel upgrade, I've had to manually install the newest driver, otherwise I haven't been able to boot. [12:07] hiyas all [12:07] then no wonder it does not work on upgrade, you have to rebuild the kernel modules each time by placing something in /etc/kernel/postinst.d [12:07] btw; I forget which button to push to show the grub menu. [12:07] shift [12:08] jtaylor, yes, I know this. As I said, I expected to be unable to reboot so I had intended to uninstall the proprietary driver first, but I forgot. [12:09] but really... It has to be possible to run failesafex without using a menu option? [12:10] probably, but maybe you don't get so far due to the lightdm problem [12:10] but the first thing I need to know, is how to display the grub menu. I don't understand why it's been hidden completely. [12:11] holding shift during boot I think, it shows for me because I have ~6 operating systems installed ^^ [12:11] jtaylor, maybe I'll have a look at that once I've confirmed that it is _not_ the catalyst driver that's causing the issue. [12:12] oh, ok. That helps. I'll give it a go. [12:12] fixing lightdem is a simple apt-get install lightdm-gtk-greeter [12:12] if its already installed its not the problem [12:29] in case someone else should ask, you can run failsafe X by running failesafeXServer. [12:31] and it seems that for some reason, the uninstall script was removed when I upgraded. So I'm downloading the driver installer so I can install it so I can remove it. There should be an easy way to drop all proprietary drivers. [12:36] ok. It's gone. Hope that really was the problem :) [12:56] alright, so removing the proprietary driver stopped my system from halting at boot, but I'm still not able to run X. [12:59] if I login and run startx, then I just get a black screen. If I start lightdm manually, then I get a mouse pointer, but nothing else. But what's extremely annoying is that I'm only able to display the grub menu once in a while. I had to cold boot about ten times before I was able to display it. [13:00] Does running sudo lightdm -d give you any information? (once you've stopped lightdm of course) ?> [13:03] yes. It's a little bit difficult to copy the messages though. [13:04] Well, anything obviously in-error? [13:05] yes. It exits with 127. Then I get some exceptions. GLib-GObject-CRITICAL: g_object_ref assertion 'G_IS_OBJECT (object)' failed [13:08] but if I log in first and then run startx unprivileged, shouldn't that bypass the display manager? [13:13] but... One thing at a time. How do I make the grub menu always appear? It's really annoying having to reboot so many times just to display it. When I press shift at boot, it's only being displayed about every tenth time or something. [13:16] it seems zeitgeist-daemon is still crashing on startup [13:16] I don't understand why the default is to not display the only thing that can help you fix problems when something goes wrong. [13:19] gnomefreak: I get that too [13:27] guess someone in #grub will know how to display the menu at boot. [13:27] Ian_Corne: the other day they uploaded a fix but it seems to only fix 1 type of the crash from what i can tell [13:28] jo-erlend: i dont understand what you are looking for [13:28] if i dont answer right away its because im engrossed in a blueprint that makes no sense :( [13:30] gnomefreak: well. I would like to be able to display the grub menu at boot so that I can run the failsafe x. Right now I don't have X at all. [13:31] in any case, being able to get to a root shell is useful, so I would like to get that possibility. Currently, I have to reboot lots of times before I'm able to get to the menu. Holding down shift only works about one time in ten. [13:32] jo-erlend: you can get to root shell by using the recovery mode kernel [13:32] it will give you 4 or 5 options to choose from [13:32] that is not possible because I cannot access the grub menu. [13:32] oh [13:33] well. If I reboot 10-15 times, then I might get lucky. [13:33] thats not good [13:33] in the old days, I could edit the grub menu to show itself for x seconds before booting the default option, but I no longer know how to do that. [13:33] * gnomefreak not a great grub person but it should like the partition is corupt [13:34] no, not at all. Everything works quite nicely, except it doesn't accept shift. Perhaps because it's a usb keyboard, I don't know. [13:34] wait a min. they were talking about hiding it at one time during natty dev cycle but i never saw that instead they hid the extra kernels [13:35] i wouldnt think USB keyboard would giv eyou issues [13:35] at least not for grub unless it is not being recognized [13:35] until plymouth at least [13:36] well, it seems it doesn't catch the keystrokes. And the keyboard is being turned off and on again, so that might be it. In any case, if I keep rebooting and holding shift, then the menu is sometimes shown. [13:36] jo-erlend: do you have a ps2 keyboard to try [13:36] I'd say out of 20 reboots when I hold shift, the menu is displayed 3-4 times perhaps. [13:37] that is really bad [13:37] I obviously don't. But that's not the point either. I want to display the grub menu at boot. [13:37] * gnomefreak wonders if you can reset the partition without wiping everything [13:37] what is bad is to default to hiding the only tool that can help you when something goes really bad. [13:38] gnomefreak: hmm? What do you mean reset partition? [13:38] reset the partition? [13:38] overwrite format [13:38] should have a / in there [13:38] that would wipe out the file system's mft [13:38] thats what i thought it would do [13:38] the files would exist but they wouldn't be listed or named [13:39] so you'd need a file recovery tool [13:39] you have to copy the files to another partition and then format and copy them back [13:39] is there anyway to test the partition to see if it is that or something else? [13:39] ah [13:40] gnomefreak, to see if it is that what? [13:40] its quiker and easier to reinstall :) [13:40] gnomefreak: if what is what? I don't think you've actually described the problem? [13:40] if the partition is corrupt in some way [13:40] what makes you think it is? [13:40] just do a fsck [13:40] * gnomefreak really dont htink its the keyboard [13:41] gnomefreak: oh, are you talking about me? I can tell you with absolute certainty that it has nothing to do with partitioning. [13:41] im just getting the thought that its someone with the partition(wish i could remember the name) [13:41] jo-erlend: yes you [13:42] ok [13:42] just downloaded the alpha image , but it was empty ...? [13:42] as I've told you, everything works. It boots the default. It's just that I want to get a root shell and that means I have to display the menu. I want it to be displayed by default. [13:43] pressing shift sometimes displays the menu, but very rarely and it's exceedingly annoying to have to reboot so many times just hoping that the menu will be displayed. [13:43] i remember talk about hiding it but i dont recall much after that. i have always had it show, other than hiding the older kernels [13:43] why does the grub menu have to be displayed? [13:43] bjsnider: I need a root shell. More precisely, I need to run failsafex. [13:43] bjsnider: it shandy to have a choice to boot into recovery or edit [13:44] ok, so change the settings so that it is showed [13:44] very shandy indeed :) [13:44] brb smoke [13:44] bjsnider: ... I've been asking how to do that for quite some time. I used to know how that was done, but I don't know how to do it with grub2. [13:45] edit the file /etc/default/grub [13:45] then run update-grub [13:46] that's it? I thought there was something else I needed to do. [13:46] which, by the way, is in the ubuntu wiki page for grub2 [13:46] that is all there is to it [13:47] https://help.ubuntu.com/community/Grub2 [13:47] !grub2 [13:47] GRUB2 is the default Ubuntu boot manager since 9.10 (Karmic). Lost GRUB after installing Windows? See https://help.ubuntu.com/community/RestoreGrub - For more information and troubleshooting for GRUB2 please refer to https://help.ubuntu.com/community/Grub2 - See !grub1 for releases before Karmic (9.10) [13:47] yes, I've never gotten comfortable using w3m. [13:48] bjsnider: grub_timeout is set to 10, but grub_hidden_timeout is set to 0. What's the difference between them? [13:48] read the docs [13:48] before you change anything you should probably know what you're changing [13:49] hmm. The live session takes forever to boot. And then I need to reboot twenty times in order to get a shell so I can edit the menu. If it was easy to look up, then I would have. [13:50] but I guess maybe I can use w3m for this. [13:50] bjsnider: have you heard anything about fglrx being fixed? [13:51] * gnomefreak using links [13:51] gnomefreak: the main reason for my upgrade is that I no longer have to use fglrx :) [13:51] uses [13:51] links. I had forgotten about that one. [13:51] it's been a while since I run linux without x :) [13:52] well, for desktop use that is. I have a few headless servers, but I rarely need to surf on them :) [13:52] gnomefreak, no i haven't, but there was a new release yesterday i think [13:52] bjsnider: thanks [13:53] gnomefreak: is links supposed to only display a black screen? [13:54] jo-erlend: no [13:54] jo-erlend: Maybe try hit g for "go to URL" then type in some address.... [13:55] it should give you a screen pretty much empty except for a choice or 2 but i dont have it installed atm [13:55] anyone feel like trying reproduce a bug in untiy for me [13:55] i would love a confirmed on this bug [13:56] bug 816106 [13:56] Launchpad bug 816106 in unity (Ubuntu) "Cant add anything to launcher panel" [Undecided,New] https://launchpad.net/bugs/816106 [13:57] still think it's a little strange to make the system recovery option unavailable by default though. [14:20] if I want to boot directly into the live session and skip the installer... Is it sufficient to just uninstall ubiquity? [14:20] let me rephrase that. If I want to boot a live session and skip the installer. What is the best way of doing that? [14:21] heh? isn't that the default? [14:22] no, when you boot from a cd or memory stick, then you go into the installer, asking if you want to try or install Ubuntu. If you click try, then you get into a live session. But that adds several minutes to the boot time, so I'd rather just go directly into the live session. [14:24] I think it's a little strange btw.. I can boot yesterdays live image without any problems. It takes forever to boot, but when it's up, it's much faster than 11.04 was installed on the same machine. But when I install from the same image, then I can get x up. I was able to get failsafex up earlier today, but I'm no longer able to. [14:25] oh dunno, I only install from the test images [14:25] what does that mean? You mean the alpha releases? [14:25] ya, aphla, beta, rc's [14:26] oh, right. And then you wait until the next test release before you install any upgrades? === thade_w is now known as Alexia_Death_ [14:26] no [14:26] but I don't install from a cd [14:26] upgrades aren't via cdrom [14:26] what does that matter? [14:26] you are complaining about the cdrom [14:27] I am not. Not in any way. Quite the contrary. I'm saying that the upgraded system does not work, but running from a cd image works perfectly. [14:27] and I think that is a little strange, since it's supposed to be the same software. [14:29] this is why I upgraded in the first place. Running 11.10 from a CD is _much_ faster than running my installed 11.04 ever was. I suspect that's mostly because of the VGA drivers. [14:30] jo-erlend: if you press a key when the cd is just starting, before the language selection shows, you get an additional menu. There you can choose "try Ubuntu without installing" [14:31] albert23, oh, I thought that had been removed. But how do I make that the default option? Is it in the grub menu? [14:31] No, there is no grub with a live cd [14:32] I don't think you can change that [14:32] well. I seem to remember being able to do it in lucid. But I don't remember exactly what I did, thought perhaps I just uninstalled uniquity? [14:33] indeed, older versions showed that menu by default [14:34] no, I mean I was able to make my memory stick OS load the live session automatically. But I tried to just uninstall it, so I can reboot and see. [14:34] brb [14:37] is it just me or can everyone not add a shortcut on the desktop? [14:39] yup. That worked. Heh... So I guess I'll be running from a memory stick for a while. :) [14:41] does anyone know why there is a limit of 4GB persistence when you make a bootable memory stick, btw? That seems a little strange. [14:47] k3b won't burn the alpha image to a dvdrw or cdrw , gotta use dd [14:49] BluesKaj, permissions issue? [14:50] BluesKaj, the only reason I say that is that I did have permissions issue with k3b at one point [14:53] coz it doesn't recognize the empty cdrw or dvdrw ,it acts like there's data on it [14:53] they're blankd [15:00] BluesKaj, ooo ok that is a different issue ,, sorry [15:11] coz_, some of these dvd/cdrws are old and have been written too many times , so the substrate is probly cooked ...found on e that works after 4 tries :) [15:12] BluesKaj, ah oh ,, phew,, at least it was not software related :) [15:13] wah. My head is tired. I can't even figure out how to mount my partitions. mdadm --assemble --scan gives med /dev/md0 and md1, but I can't find the partitions on the lvm. [15:14] ok gonna try the image ...couldn't rescue nvidia/X on the try ..blacklisting nouveau and reinstalling nvidia current made no difference [15:14] last try [15:51] is there an kubuntu oneiric alpha image available ?...searching , but not finding much [15:51] alpha2 [15:56] ok, no kubuntu alpha 2 images available [16:09] BluesKaj, you're having trouble with nvidia? [16:13] bjsnider, yes i tried the nouveau blacklist and it worked for a day or 2 then X broke again ..I had tty access but nomodeset and noacpi didn't help [16:13] ok, first of all i doubt reimaging is going to fix it [16:14] it's probably a packaging issue related to multiarch [16:14] tried unblacklisting nouveau and removing nvidia current [16:14] assuming nvidia-current is properly installed [16:14] nvidia-current already blacklists nouveau [16:16] not in my case, the nouveau driver was in use after I installed nvidia-current, so blacklisting nouveau and reinstalling nvidia current did work for a while [16:16] you can't use nouveau instead of nvidia for the moment? [16:17] I tried that , but X still wouldn't load [16:17] I reinstalled natty...again [16:17] look, i'm fairly certain i can troubleshoot this into working again [16:18] run this command: sudo jockey-text -e xorg: nvidia-current [16:19] yofel suggested the blacklist and it did work , but I don't know what broke X ...checked the logs but all i got was the noscrns message [16:22] bjsnider, I'm on natty again ...it's not a big deal to reinstall due to separate / and /home partitions , but this nvidia/X problem is becoming a pita , so I'm leery on upgrading again ...running kde btw [16:26] bjsnider, sudo jockey-text -e xorg: nvidia-current ... looks for the additional drivers ? [16:36] no, it installs and activates nvidia-current [16:36] is there no reboot option now? [16:37] (from the gui_ [16:37] ) [16:38] ok , bjsnider , upgrading ... probly take an hr or so.. we'll see what happens then :) [16:39] gay [17:40] those issues with lightdm is well known, yes? [17:42] jo-erlend_: which issues? [17:43] well, you know.. "the issues" :) It wouldn't run when I upgraded from 11.04. Running from a live memory stick was perfect. [17:44] and I got the feeling that it was some well known issue. [17:44] jo-erlend_: which desktop are you using? [17:44] ubuntu. 64bit is that matters. [17:44] s/is/if/. [17:46] Anyone noticed an issue where the cursor is moved to the right 3 spaces on the console? [17:46] makes it a little hard to use vi :) [17:50] greetings.. [17:52] so.. [17:53] if I wanted to downgrade back to 11.01 how would I do that? [17:53] possible? [17:53] I accidentally upgraded a macahine to oneiric [17:53] !downgrade [17:53] Attempting to downgrade to an older Ubuntu version is explicitly not supported and may break your system. [17:53] thinking it was my own box.. [17:53] ok [17:53] fresh install of 11.04 [17:53] ugh. [17:53] 11.01 doesn't really exist [17:54] sorry I meant 11.04 [17:58] sri, a fresh install is much faster if you don't have to consider mdadm or lvm and that stuff. [17:59] that is to say; as long as you don't need to use the alternate installer, it's much faster to install fresh than it is to install via the package system. [18:39] where is stored the desktop image? Where i can find it in the distribution [18:41] Hmm, KDE is broken entirely with latest upgrade [18:41] broken dependencies I guess, some packages need processing by an archive admin [18:42] *never* run dist-upgrade without checking what it does first ;) [18:42] Me either. [18:42] yofel: Indeed, but it seemingly replaced some stuff, evidently not enough. [18:43] well, here it wants to remove workspace stuff too [18:43] there's a new wallpaper package worspace now depends on, and that's stuck in BINARY NEW [18:44] How do I install stuff from binary new? [18:44] or is that insanity [18:44] I wonder if its due to the accidental package sync. [18:44] Pici: What is that? [18:45] let me grab a link from the mailing list. [18:45] antihero: see https://lists.ubuntu.com/archives/ubuntu-devel-announce/2011-July/000877.html [18:45] Pici: Don't have a browser right now. [18:45] I'm sitting in the console. [18:46] I suppose I could load up e17 though [18:46] antihero: Basically a javascript bug caused us to sync everything from debian. [18:46] w3m should be enough for this, it's 99% text. [18:46] Pici: Eek. I'm guessing that's bad? [18:47] antihero: yes. [18:47] Pici: ballback idea on when I'll be able to install KDE again? [18:47] *ballbark (lol?) [18:47] PARK [18:47] heh [18:48] I'm not sure, I haven't investigated the list of packges thoroughly, nor have I tried to do a (dist-)upgrade on my 11.10 install lately. [18:48] tomorrow I guess? [18:48] here a dist-upgrade wants to remove kde-workspace as well, not much to do except to wait [18:48] Likely soon though, I'd guess that the more important packages will get fixed sooner. [18:49] for build the package yourself [18:49] *or [18:49] This must have happened in the last 4-5 hours, I did a dist-upgrade then without issues [18:49] No way to simply ignore a couple deps? [18:50] genii-around: Its possible that the packages didn't build until more recently. [18:50] antihero: Then they wouldn't be dependencies. [18:51] Hm [18:51] essentially all I need is kde-workspace-data 4.7.0-0ubuntu2 [18:52] whereas all I can get is kde-workspace-data-4.7.0-0ubuntu1 [18:52] aargh [18:54] uh, no ubuntu2 depends on kde-wallpapers-default which is uninstallable currently [18:54] antihero: Looks like that just finished building. [18:54] so ubuntu1 is your only chance currently [18:54] Pici: Excellent! Can I get the deb? [18:54] Pici: Where did you find out that that had just finished building? [18:54] antihero: https://edge.launchpad.net/ubuntu/+source/kde-workspace [18:56] hmm, that doesn't depend on kde-workspace data it seems [18:56] oh wait, it does. [18:56] Its the source package for kde-workspace-data [18:57] ah true, it's fine now [18:58] Essentially the problem is that kde-workspace-bin ubuntu1 depends on kde-workspace-data ubuntu2 [18:58] ffs [18:58] there's no versions in the dependencies, it's just that those versions were available at that moment [18:59] yofel: Ubuntu -- Package Se [18:59] oops [18:59] antihero: You could take your chances and dpkg -i --force-depends on the workspace-bin file in your cache [19:00] " kde-workspace-bin : Depends: kde-workspace-data (= 4:4.7.0-0ubuntu2) but 4:4.7.0-0ubuntu1 is to be installed " [19:00] antihero: refresh your cache again [19:00] here (de.archive.ubuntu.com amd64) the deps are OK now [19:00] yofel: apt-get update? [19:00] I'm on gb, is that slow? [19:00] except python-dbus which has been stuck for a while here [19:00] antihero: no idea, but update is right [19:01] yofel: yeah the python-qt4-dbus thing seems weird [19:01] Hmm, deps not fixed on GB. How do I know when that's updated? [19:03] aaaargh [19:03] sorry [19:03] not fixed, I got it from another source -.- [19:03] so is it that whoever's maintining it has accidentally put ubuntu2 instead of ubuntu1? [19:03] yofel: Could I get that source? [19:04] antihero: that's private, but different way: [19:04] got to https://edge.launchpad.net/ubuntu/+source/kde-wallpapers/4:4.7.0-0ubuntu1/+build/2653513 [19:04] download the debs and dpkg -i them [19:05] goddamn uxterm let me copy paste [19:06] yofel: But I thought the issue was with kde-workspace-data? [19:06] and the fact that the available version is ubuntu1 but kde-workspace-bin needs ubuntu2 [19:07] fwiw kubuntu-desktop is still broken ;) [19:07] yes, kde-workspace-data depends on kde-wallpapers-default which doesn't exist yet [19:07] -> problem [19:07] yofel: I see. [19:07] install wallpapers by hand and apt should be happy [19:07] yofel. The package should really have wallpapers as optional >_< [19:08] I mean crikey, taking down a system for *wallpapers* [19:08] no, the depends is right, this is just what happens in +1 sometimes [19:10] yofel: Wallpapres thing did not fix. [19:10] what happens now? [19:10] same thing [19:10] which packages did you install? [19:10] kde-wallpapers and kde-wallpapers-default [19:11] antihero: you know you don't have to install every update as soon as it shows up, right? ;-) [19:11] had to remove kde-workspace-data (ub1) to do it too [19:11] jbicha: I know I know now [19:11] k, then run apt-get update again [19:11] if it's still broken you do have a bit outdated mirror I guess [19:11] yofel: Which mirror are you using? DE? [19:11] yep [19:11] which mirror is the most up to date usually? [19:11] archive.ubuntu.com [19:12] the main one? :P [19:12] antihero: here's a bit of an explanation: http://ubuntuforums.org/showthread.php?t=1751299 [19:12] Is there a way to see if I am on Unity 3D or 2d? I logged into 'Unity' but none of my ccsm settings are applying and all of my old desktop settings are gone. [19:12] btw is anyone here running O on the new Macbook Pro? [19:14] jbicha: I will bear this in mind [19:15] yofel: Hmm, now I've used the DE mirror a bunch of stuff about things being too new :( [19:15] "too new" o.O? [19:15] because kde-workspace-bin=4:4.7.0-0-ubuntu2 is not existing [19:15] kde-workspace-bin : Depends: libkephal4abi1 (= 4:4.7.0-0ubuntu1) but 4:4.7.0-0ubuntu2 is to be installed [19:17] yofel: Perhaps they're finishing off the 4:4.7.0-0ubuntu2 builds as we speak? [19:18] antihero: no problem, it takes practice & experience to know when to update but usually avoid partial or dist-upgrades [19:18] argh no, ubuntu2 is on LP [19:18] LP? [19:18] but I forgot that kde-workspace-data-extras is stuck in new too -.- [19:18] Launchpad [19:18] LaunchPad [19:18] ah [19:18] I'll try US mirror, perhaps it is more up to date? [19:19] Nope. [19:19] or you could install unity or gnome-shell or something :-) [19:19]