[00:01] time to call it a night. Bye! :) === steemed is now known as st33med [00:29] steemed, will unity work inside virtualbox? [00:31] I assume so... [00:31] If you are talking about 11.04 maybe [00:33] steemed trying out a beta of it right now [00:40] Okay, after detecting the keyboard, i am staring at a pink screen [00:40] is this normal? [00:40] oh there it goes [00:40] nvm [01:47] steemed are you there? [01:47] yes but I'm busy [01:47] well I need help :( [02:44] mmiller235, what do you need? [02:53] steemed to get unity to work in vbox [02:53] which apparently can't be done [02:54] I wouldn't know: I don't run 11.04 [10:32] Hello. [18:09] I will be back later. [18:55] I need help: I tried installing kde with kde-full on ubuntu (not kubuntu) i realize now that this is a mistake, but i need some way to restore gnome locally (net doesn't work on recovery console) [18:56] falco_: you're better off asking in #ubuntu, this isn't exactly a support channel. [18:56] Pici: they didn't know [18:57] falco_: No, one person didn't know. You can ask again and see if someone else can help you. [18:57] falco_: you shoult be able to bring your net up from the console with ifconfig [18:57] Pici: okay [18:57] oh [18:57] and either way, you shouldn't need it [18:57] what do i do without it to restore? [18:58] wezll, it would depend what exactly the problem is [18:58] i (partially) installed kde and i need to restore gnome [18:59] yes [19:00] by "the problem" I mean "why X doe"sn't( start" since you say you're stuck in the console [19:00] doesn't* [19:00] you don't really need to "restore Gnome", gnome is still here [19:01] ah. the error message is: 'Warning: Cannot open ConsoleKit session: Unable to open session: Launch helper exited with unknown return code 127' and after that it takes me back to the login screen. i can get into recovery console tho [19:01] it just doesn't start for some reason which is not obvious [19:01] ok [19:01] hmm [19:01] are you ytrying to log in a KDE or Gnome session? [19:02] KDE, Gnome isn't an option for some reason. [19:02] hm [19:02] hasq the login screen changed? [19:03] yes. [19:03] formerly yoou had GDM, maube the KDE installation changed it to KDM [19:03] ok [19:03] try to go back to GDM [19:03] how? [19:03] sudo dpkg-reconfigure gdm [19:03] k [19:04] alrite. [19:04] lemme try again now that i did that [19:05] booting... [19:06] it's taking a REALLY long time to boot [19:07] I think you cna press ESC to see the boot messages [19:08] it might just be fsck'ing your disks [19:09] okay, the last message it gave me was 'Starting TiMidity** midi emulation...' but it says ok, so it's doing something else. ur right tho, it may just be fsck'ing my discs. [19:10] sry, thats ALSA midi emulation [19:11] I think fscl happens before [19:11] hmm... so what's happening? [19:11] hmm you cna alwyas hard-reboot and boot without quiet splash [19:11] no idea [19:11] 'boot without quiet splash'? [19:12] boot without passing the "quiet" ans "splash" parameters to the kernel, so you can see what's going on [19:12] you can edit the boot command line in GRUB [19:12] how? [19:14] you cna press a key to edit a GRUB entry, I think it's 'e', but it's described on the GRUB menu [19:15] when do i press e? [19:16] hughlight the entry you want to modify and press 'e' [19:16] then edit the kernel line, remove "quiet splash" and boot [19:18] i can't do anything like that. trying to highlight anything only switches from the graphical (four dots) boot to the non-graphical one. [19:18] before that, when you're in the GRUB menu [19:18] if you don't have it, press shift at boot [19:18] k [19:19] pressing shift doesn't work [19:19] it should [19:19] you're probably doing it too late [19:20] do i do it right when it starts rebooting? [19:20] you have to do it right when the computer boots [19:20] after the BIOS screens, before it qtarts the OS [19:21] huh. i tried it at every possible place before my machine booted. nothing happened. [19:21] no, before it loaded ubuntu [19:21] sorry, [19:21] wording error. [19:21] or tried to load ubuntu [19:23] it definitely should work [19:23] unless you are running GRUB 1, but that's unlikely [19:25] strange... because it isn't working. but hypothetically, if i had grub 1, what would i do? [19:25] you would know it [19:25] there would be a "Press ESC to enter GRUB menu" at the top left corner of your screen [19:27] ah. that's very odd. do you have any ideas about why i cant open the grub menu? [19:27] no :( [19:27] :/ dang [19:28] you cn alaways edity the grub config from the recovery console, though [19:28] to change the boot settings [19:28] but it's still weird that you can't just enter the menu [19:28] how do i get into the recovery console if ubuntu doesn't load? [19:28] ... [19:28] good point [19:28] hmm [19:29] well the next step is boot a live CD and tinker with your system from there [19:30] though at that point, if you didn't have anything important, you might as well reinstall [19:30] well... i do have some stuff. but anyways, i'll go get the live cd [19:31] then yeah, you can access your installed system from the live cd and hopefully fix it [19:42] okay... i'm having trouble finding it, but i started dloading it, and i'll look for it in the meantime. [21:22] Bachstelze: i've booted the live cd. what do i do now? [21:27] falco_: you mount the root partition of your installed system and do whatever you want to do [21:27] either get your data back and reinstall, or try to fix it [21:28] how do i mount the root partition of the existing installation? [21:29] using the mount command, like you mount any other filesystem [21:30] ah. sorry. i wasn't thinking. [21:33] how do i navigate to my actual drive? [21:34] like you navigate to any other location, using Nautilus or the terminal [21:34] it's only showing a file system for the live cd [21:34] did you mount your drive ? [21:35] how do you mount your drive? sry, n00bish question [21:36] falco_: Is it listed on the places menu? [21:36] oh! i found it. thanks! [21:42] now is there a way to install ubuntu onto my drive without interfering with any of my personal files, or do i have to back everything up? [21:50] nnot easily, and I wouldn't recommend it [21:50] (this is why you should always have a separate /home partition)