[00:00] <jo-erlend> No! Super+num doesn't work! That's a total dealbreaker. Guess it'll be fixed by release. :)
[00:01] <Pici> I just installed today's image, the upgrade was working really oddly.
[00:02] <jo-erlend> what does that mean?
[00:02] <BUGabundo> how do I re-attach to the oldest Screen session?
[00:03] <rww> BUGabundo: assuming the oldest one is the one screen considers "first", screen -d -RR would do it.
[00:03] <Pici> 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] <BUGabundo> nope
[00:03] <BUGabundo> that's actually the newest rww
[00:03] <rww> fun
[00:04] <Pici> screen -ls
[00:04] <BUGabundo> Pici: I know how to list them
[00:04] <BUGabundo> I'm just being lazy....
[00:04] <Pici> BUGabundo: Clearly :P
[00:04] <BUGabundo> this is so powerful, must allow me that
[00:14] <jo-erlend> 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] <micahg> jo-erlend: flash should work from multiverse
[00:16] <jo-erlend> micahg, hmm?
[00:17] <micahg> jo-erlend: ubufox should attempt to install flash from multiverse or install gnash
[00:17] <jo-erlend> I've never seen that.
[00:17] <jo-erlend> 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] <micahg> jo-erlend: the plugin finder service isn't usually updated until close to release
[00:18] <jo-erlend> ah, ok.
[00:19] <micahg> and there's an FTBFS bug blocking a moon update to work with Firefox 4+
[00:19] <jo-erlend> ftbfs?
[00:19] <micahg> fails to build from source
[00:20] <jo-erlend> ah.
[00:21] <BUGabundo> MADNESS
[00:21] <BUGabundo>     24         0.02s         2.03s        20.3G         2.3G           0K         180K          ?          ?        71%       chromium-brows
[00:32] <BUGabundo> screen -r `screen -list | grep '.*\..*(.*)' | sort | head -n 1 | awk '{ print $1 }'`
[00:32] <BUGabundo> rww: Pici ^^^
[00:34] <rww> eww
[00:36] <Pici> agreed
[00:38] <BUGabundo> rww: LOL
[00:38] <BUGabundo> it works!
[00:39] <BUGabundo> can you do better?
[01:12] <BUGabundo> nite
[01:17] <jo-erlend> from what I've seen so far, I think I want to upgrade.
[01:19] <jo-erlend> I want to upgrade. bbl
[01:23] <jhouse5266534> I've noticed the bottom little bit of my java windows is not displaying.  Is that a known issue?
[01:33] <jo-erlend> 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] <jhouse5266534> jo-erlend, it's actually working well so far except for the grey banner at the bottom of java windows.
[01:35] <jo-erlend> yes, because I care much about java windows :>
[01:44] <jo-erlend> uh... I get an error 403 forbidden when downloading packages. How come?
[02:06] <jo-erlend>  switched to another archive and that worked.
[06:45] <alkisg> Hi, is "list columns" view supported by nautilus in oneiric? I can't find it...
[10:56] <antihero> Why does python-dbus break python-qt4-dbus :(
[11:15] <ior3k> anyone know of workrave alternatives that work on oneiric?
[11:15] <ior3k> (workrave is not installable right now)
[11:37] <jtaylor> is a bug filed?
[11:39] <jtaylor> installs fine in my chroot
[11:52] <jo-erlend> 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] <ior3k> jtaylor: installing libpanel-applet2-0 (of which workrave depends) causes gnome-panel to be uninstalled
[11:55] <jo-erlend> how do I start the failsafe x?
[11:57] <jtaylor> did you install lightdm-gtk-greeter?
[11:57] <jtaylor> jo-erlend: ^
[11:57] <jo-erlend> jtaylor, I've just upgraded from 11.04
[11:57] <jo-erlend> but I'm fairly certain it's the catalyst driver for my hd5850. It always does this when I upgrade the kernel.
[11:58] <jtaylor> there was a problem with lightdm casing hanging boot
[11:58] <jo-erlend> and since the radeon driver now is much better, I just want to remove the proprietary driver.
[11:58] <jtaylor> anyhow you get into a failsafe by choosing the recovery kernel in grub
[11:58] <jtaylor> its possible that installing the greeter will solve your problem
[11:58] <jo-erlend> how? I couldn't find any such options anymore. There used to be an option in that menu you get, but ...
[11:59] <jtaylor> there should be a more options option now where its hidden
[11:59] <jbicha> you could also try booting from your previous kernel
[11:59] <jo-erlend> 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] <jtaylor> booting works fine on my machine, I just get glichtes after login ^^
[12:00] <jo-erlend> listen. I just want to remove the proprietary driver. I've never wanted it and now I no longer need it.
[12:00] <jtaylor> also cataclyist
[12:00] <jo-erlend> yes, but on my system, on many clean installs, every single time I've upgraded the kernel, I cannot boot afterwards. 100%.
[12:00] <jtaylor> I just want to say it may not be the driver causing the problem
[12:00] <jtaylor> this time
[12:01] <jo-erlend> 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] <jo-erlend> 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] <jtaylor> I'm not arguing that the prop drivers are good
[12:02] <jo-erlend> so what I'm asking, is "how do I run failsafex?"
[12:03] <jtaylor> choose the grub boot entry for recovery or edit the line (pressing e I think)
[12:03] <jo-erlend> 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] <jtaylor> you just need a root shell, from there you can remove the drivers
[12:06] <jo-erlend> I wish I could remember the name and location of the uninstall script. :/
[12:06] <jtaylor> its not installed via the package?
[12:06] <jo-erlend> 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] <BluesKaj> hiyas all
[12:07] <jtaylor> 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] <jo-erlend> btw; I forget which button to push to show the grub menu.
[12:07] <jtaylor> shift
[12:08] <jo-erlend> 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] <jo-erlend> but really... It has to be possible to run failesafex without using a menu option?
[12:10] <jtaylor> probably, but maybe you don't get so far due to the lightdm problem
[12:10] <jo-erlend> 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] <jtaylor> holding shift during boot I think, it shows for me because I have ~6 operating systems installed ^^
[12:11] <jo-erlend> 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] <jo-erlend> oh, ok. That helps. I'll give it a go.
[12:12] <jtaylor> fixing lightdem is a simple apt-get install lightdm-gtk-greeter
[12:12] <jtaylor> if its already installed its not the problem
[12:29] <jo-erlend> in case someone else should ask, you can run failsafe X by running failesafeXServer.
[12:31] <jo-erlend> 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] <jo-erlend> ok. It's gone. Hope that really was the problem :)
[12:56] <jo-erlend> alright, so removing the proprietary driver stopped my system from halting at boot, but I'm still not able to run X.
[12:59] <jo-erlend> 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] <Pici> Does running sudo lightdm -d give you any information? (once you've stopped lightdm of course) ?>
[13:03] <jo-erlend> yes. It's a little bit difficult to copy the messages though.
[13:04] <Pici> Well, anything obviously in-error?
[13:05] <jo-erlend> yes. It exits with 127. Then I get some exceptions. GLib-GObject-CRITICAL: g_object_ref assertion 'G_IS_OBJECT (object)' failed
[13:08] <jo-erlend> but if I log in first and then run startx unprivileged, shouldn't that bypass the display manager?
[13:13] <jo-erlend> 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] <gnomefreak> it seems zeitgeist-daemon is still crashing on startup
[13:16] <jo-erlend> 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] <Ian_Corne> gnomefreak: I get that too
[13:27] <jo-erlend> guess someone in #grub will know how to display the menu at boot.
[13:27] <gnomefreak> 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] <gnomefreak> jo-erlend: i dont understand what you are looking for
[13:28] <gnomefreak> if i dont answer right away its because im engrossed in a blueprint that makes no sense :(
[13:30] <jo-erlend> 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] <jo-erlend> 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] <gnomefreak> jo-erlend: you can get to root shell by using the recovery mode kernel
[13:32] <gnomefreak> it will give you 4 or 5 options to choose from
[13:32] <jo-erlend> that is not possible because I cannot access the grub menu.
[13:32] <gnomefreak> oh
[13:33] <jo-erlend> well. If I reboot 10-15 times, then I might get lucky.
[13:33] <gnomefreak> thats not good
[13:33] <jo-erlend> 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] <jo-erlend> 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] <gnomefreak> 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] <gnomefreak> i wouldnt think USB keyboard would giv eyou issues
[13:35] <gnomefreak> at least not for grub unless it is not being recognized
[13:35] <gnomefreak> until plymouth at least
[13:36] <jo-erlend> 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] <gnomefreak> jo-erlend: do you have a ps2 keyboard to try
[13:36] <jo-erlend> I'd say out of 20 reboots when I hold shift, the menu is displayed 3-4 times perhaps.
[13:37] <gnomefreak> that is really bad
[13:37] <jo-erlend> 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] <jo-erlend> what is bad is to default to hiding the only tool that can help you when something goes really bad.
[13:38] <jo-erlend> gnomefreak: hmm? What do you mean reset partition?
[13:38] <bjsnider> reset the partition?
[13:38] <gnomefreak> overwrite format
[13:38] <gnomefreak> should have a / in there
[13:38] <bjsnider> that would wipe out the file system's mft
[13:38] <gnomefreak> thats what i thought it would do
[13:38] <bjsnider> the files would exist but they wouldn't be listed or named
[13:39] <bjsnider> so you'd need a file recovery tool
[13:39] <bjsnider> you have to copy the files to another partition and then format and copy them back
[13:39] <gnomefreak> is there anyway to test the partition to see if it is that or something else?
[13:39] <gnomefreak> ah
[13:40] <bjsnider> gnomefreak, to see if it is that what?
[13:40] <gnomefreak> its quiker and easier to reinstall :)
[13:40] <jo-erlend> gnomefreak: if what is what? I don't think you've actually described the problem?
[13:40] <gnomefreak> if the partition is corrupt in some way
[13:40] <jo-erlend> what makes you think it is?
[13:40] <bjsnider> just do a fsck
[13:40]  * gnomefreak really dont htink its the keyboard
[13:41] <jo-erlend> gnomefreak: oh, are you talking about me? I can tell you with absolute certainty that it has nothing to do with partitioning.
[13:41] <gnomefreak> im just getting the thought that its someone with the partition(wish i could remember the name)
[13:41] <gnomefreak> jo-erlend: yes you
[13:42] <gnomefreak> ok
[13:42] <BluesKaj> just downloaded the alpha image , but it was empty ...?
[13:42] <jo-erlend> 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] <jo-erlend> 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] <gnomefreak> 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] <bjsnider> why does the grub menu have to be displayed?
[13:43] <jo-erlend> bjsnider: I need a root shell. More precisely, I need to run failsafex.
[13:43] <gnomefreak> bjsnider: it shandy to have a choice to boot into recovery or edit
[13:44] <bjsnider> ok, so change the settings so that it is showed
[13:44] <jo-erlend> very shandy indeed :)
[13:44] <gnomefreak> brb smoke
[13:44] <jo-erlend> 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] <bjsnider> edit the file /etc/default/grub
[13:45] <bjsnider> then run update-grub
[13:46] <jo-erlend> that's it? I thought there was something else I needed to do.
[13:46] <bjsnider> which, by the way, is in the ubuntu wiki page for grub2
[13:46] <bjsnider> that is all there is to it
[13:47] <bjsnider> https://help.ubuntu.com/community/Grub2
[13:47] <bjsnider> !grub2
[13:47] <jo-erlend> yes, I've never gotten comfortable using w3m.
[13:48] <jo-erlend> bjsnider: grub_timeout is set to 10, but grub_hidden_timeout is set to 0. What's the difference between them?
[13:48] <bjsnider> read the docs
[13:48] <bjsnider> before you change anything you should probably know what you're changing
[13:49] <jo-erlend> 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] <jo-erlend> but I guess maybe I can use w3m for this.
[13:50] <gnomefreak> bjsnider: have you heard anything about fglrx being fixed?
[13:51]  * gnomefreak using links
[13:51] <jo-erlend> gnomefreak: the main reason for my upgrade is that I no longer have to use fglrx :)
[13:51] <gnomefreak> uses
[13:51] <jo-erlend> links. I had forgotten about that one.
[13:51] <jo-erlend> it's been a while since I run linux without x :)
[13:52] <jo-erlend> well, for desktop use that is. I have a few headless servers, but I rarely need to surf on them :)
[13:52] <bjsnider> gnomefreak, no i haven't, but there was a new release yesterday i think
[13:52] <gnomefreak> bjsnider: thanks
[13:53] <jo-erlend> gnomefreak: is links supposed to only display a black screen?
[13:54] <gnomefreak> jo-erlend: no
[13:54] <genii-around> jo-erlend: Maybe try hit g for "go to URL" then type in some address....
[13:55] <gnomefreak> it should give you a screen pretty much empty except for a choice or 2 but i dont have it installed atm
[13:55] <gnomefreak> anyone feel like trying reproduce a bug in untiy for me
[13:55] <gnomefreak> i would love a confirmed on this bug
[13:56] <gnomefreak> bug 816106
[13:57] <jo-erlend> still think it's a little strange to make the system recovery option unavailable by default though.
[14:20] <jo-erlend> if  I want to boot directly into the live session and skip the installer... Is it sufficient to just uninstall ubiquity?
[14:20] <jo-erlend> 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] <patdk-wk> heh? isn't that the default?
[14:22] <jo-erlend> 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] <jo-erlend> 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] <patdk-wk> oh dunno, I only install from the test images
[14:25] <jo-erlend> what does that mean? You mean the alpha releases?
[14:25] <patdk-wk> ya, aphla, beta, rc's
[14:26] <jo-erlend> oh, right. And then you wait until the next test release before you install any upgrades?
[14:26] <patdk-wk> no
[14:26] <patdk-wk> but I don't install from a cd
[14:26] <patdk-wk> upgrades aren't via cdrom
[14:26] <jo-erlend> what does that matter?
[14:26] <patdk-wk> you are complaining about the cdrom
[14:27] <jo-erlend> 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] <jo-erlend> and I think that is a little strange, since it's supposed to be the same software.
[14:29] <jo-erlend> 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] <albert23> 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] <jo-erlend> 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] <albert23> No, there is no grub with a live cd
[14:32] <albert23> I don't think you can change that
[14:32] <jo-erlend> 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] <albert23> indeed, older versions showed that menu by default
[14:34] <jo-erlend> 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] <jo-erlend> brb
[14:37] <gnomefreak> is it just me or can everyone not add a shortcut on the desktop?
[14:39] <jo-erlend> yup. That worked. Heh... So I guess I'll be running from a memory stick for a while. :)
[14:41] <jo-erlend> 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] <BluesKaj> k3b won't burn the alpha image to a dvdrw  or cdrw , gotta use dd
[14:49] <coz_> BluesKaj,   permissions  issue?
[14:50] <coz_> BluesKaj,  the only reason I say that is that I did have permissions issue with k3b  at one point
[14:53] <BluesKaj> coz it doesn't recognize the empty cdrw or dvdrw ,it acts like there's data on it
[14:53] <BluesKaj> they're blankd
[15:00] <coz_> BluesKaj,  ooo  ok that is a different issue ,, sorry
[15:11] <BluesKaj> 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] <coz_> BluesKaj,  ah oh ,, phew,, at least it was not software related :)
[15:13] <jo-erlend> 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] <BluesKaj> ok gonna try the image ...couldn't rescue nvidia/X on the try ..blacklisting nouveau and reinstalling nvidia current made no difference
[15:14] <BluesKaj> last try
[15:51] <BluesKaj> is there an kubuntu oneiric alpha image available ?...searching , but not finding much
[15:51] <BluesKaj> alpha2
[15:56] <BluesKaj> ok, no kubuntu alpha 2 images available
[16:09] <bjsnider> BluesKaj, you're having trouble with nvidia?
[16:13] <BluesKaj> 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] <bjsnider> ok, first of all i doubt reimaging is going to fix it
[16:14] <bjsnider> it's probably a packaging issue related to multiarch
[16:14] <BluesKaj> tried unblacklisting nouveau and removing nvidia current
[16:14] <bjsnider> assuming nvidia-current is properly installed
[16:14] <bjsnider> nvidia-current already blacklists nouveau
[16:16] <BluesKaj> 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] <bjsnider> you can't use nouveau instead of nvidia for the moment?
[16:17] <BluesKaj> I tried that , but X still wouldn't load
[16:17] <BluesKaj> I reinstalled natty...again
[16:17] <bjsnider> look, i'm fairly certain i can troubleshoot this into working again
[16:18] <bjsnider> run this command: sudo jockey-text -e xorg: nvidia-current
[16:19] <BluesKaj> 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] <BluesKaj> 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] <BluesKaj> bjsnider, sudo jockey-text -e xorg: nvidia-current ... looks for the additional drivers ?
[16:36] <bjsnider> no, it installs and activates nvidia-current
[16:36] <carl0s-> is there no reboot option now?
[16:37] <carl0s-> (from the gui_
[16:37] <carl0s-> )
[16:38] <BluesKaj> ok , bjsnider , upgrading ... probly take an hr or so.. we'll see what happens then :)
[16:39] <carl0s-> gay
[17:40] <jo-erlend_> those issues with lightdm is well known, yes?
[17:42] <micahg> jo-erlend_: which issues?
[17:43] <jo-erlend_> 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] <jo-erlend_> and I got the feeling that it was some well known issue.
[17:44] <micahg> jo-erlend_: which desktop are you using?
[17:44] <jo-erlend_> ubuntu. 64bit is that matters.
[17:44] <jo-erlend_> s/is/if/.
[17:46] <dr_willis> Anyone noticed an issue where the cursor is moved to the right 3 spaces on the console?
[17:46] <dr_willis> makes it a little hard to use vi :)
[17:50] <sri> greetings..
[17:52] <sri> so..
[17:53] <sri> if I wanted to downgrade back to 11.01 how would I do that?
[17:53] <sri> possible?
[17:53] <sri> I accidentally upgraded a macahine to oneiric
[17:53] <yofel> !downgrade
[17:53] <sri> thinking it was my own box..
[17:53] <sri> ok
[17:53] <charlie-tca> fresh install of 11.04
[17:53] <sri> ugh.
[17:53] <charlie-tca> 11.01 doesn't really exist
[17:54] <sri> sorry I meant 11.04
[17:58] <jo-erlend_> sri, a fresh install is much faster if you don't have to consider mdadm or lvm and that stuff.
[17:59] <jo-erlend_> 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] <mauri_> where is stored the desktop image? Where i can find it in the distribution
[18:41] <antihero> Hmm, KDE is broken entirely with latest upgrade
[18:41] <yofel> broken dependencies I guess, some packages need processing by an archive admin
[18:42] <yofel> *never* run dist-upgrade without checking what it does first ;)
[18:42] <Pici> Me either.
[18:42] <antihero> yofel: Indeed, but it seemingly replaced some stuff, evidently not enough.
[18:43] <yofel> well, here it wants to remove workspace stuff too
[18:43] <yofel> there's a new wallpaper package worspace now depends on, and that's stuck in BINARY NEW
[18:44] <antihero> How do I install stuff from binary new?
[18:44] <antihero> or is that insanity
[18:44] <Pici> I wonder if its due to the accidental package sync.
[18:44] <antihero> Pici: What is that?
[18:45] <Pici> let me grab a link from the mailing list.
[18:45] <Pici> antihero: see https://lists.ubuntu.com/archives/ubuntu-devel-announce/2011-July/000877.html
[18:45] <antihero> Pici: Don't have a browser right now.
[18:45] <antihero> I'm sitting in the console.
[18:46] <antihero> I suppose I could load up e17 though
[18:46] <Pici> antihero: Basically a javascript bug caused us to sync everything from debian.
[18:46] <Pici> w3m should be enough for this, it's 99% text.
[18:46] <antihero> Pici: Eek. I'm guessing that's bad?
[18:47] <Pici> antihero: yes.
[18:47] <antihero> Pici: ballback idea on when I'll be able to install KDE again?
[18:47] <antihero> *ballbark (lol?)
[18:47] <antihero> PARK
[18:47] <Pici> heh
[18:48] <Pici> 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] <yofel> tomorrow I guess?
[18:48] <yofel> here a dist-upgrade wants to remove kde-workspace as well, not much to do except to wait
[18:48] <Pici> Likely soon though, I'd guess that the more important packages will get fixed sooner.
[18:49] <yofel> for build the package yourself
[18:49] <yofel> *or
[18:49] <genii-around> This must have happened in the last 4-5 hours, I did a dist-upgrade then without issues
[18:49] <antihero> No way to simply ignore a couple deps?
[18:50] <Pici> genii-around: Its possible that the packages didn't build until more recently.
[18:50] <Pici> antihero: Then they wouldn't be dependencies.
[18:51] <genii-around> Hm
[18:51] <antihero> essentially all I need is kde-workspace-data 4.7.0-0ubuntu2
[18:52] <antihero> whereas all I can get is kde-workspace-data-4.7.0-0ubuntu1
[18:52] <antihero> aargh
[18:54] <yofel> uh, no ubuntu2 depends on kde-wallpapers-default which is uninstallable currently
[18:54] <Pici> antihero: Looks like that just finished building.
[18:54] <yofel> so ubuntu1 is your only chance currently
[18:54] <antihero> Pici: Excellent! Can I get the deb?
[18:54] <antihero> Pici: Where did you find out that that had just finished building?
[18:54] <Pici> antihero: https://edge.launchpad.net/ubuntu/+source/kde-workspace
[18:56] <antihero> hmm, that doesn't depend on kde-workspace data it seems
[18:56] <antihero> oh wait, it does.
[18:56] <Pici> Its the source package for kde-workspace-data
[18:57] <yofel> ah true, it's fine now
[18:58] <antihero> Essentially the problem is that kde-workspace-bin ubuntu1 depends on kde-workspace-data ubuntu2
[18:58] <antihero> ffs
[18:58] <yofel> there's no versions in the dependencies, it's just that those versions were available at that moment
[18:59] <antihero> yofel: Ubuntu -- Package Se
[18:59] <antihero> oops
[18:59] <genii-around> antihero: You could take your chances and dpkg -i --force-depends      on the workspace-bin file in your cache
[19:00] <antihero> " kde-workspace-bin : Depends: kde-workspace-data (= 4:4.7.0-0ubuntu2) but 4:4.7.0-0ubuntu1 is to be installed "
[19:00] <yofel> antihero: refresh your cache again
[19:00] <yofel> here (de.archive.ubuntu.com amd64) the deps are OK now
[19:00] <antihero> yofel: apt-get update?
[19:00] <antihero> I'm on gb, is that slow?
[19:00] <yofel> except python-dbus which has been stuck for a while here
[19:00] <yofel> antihero: no idea, but update is right
[19:01] <antihero> yofel: yeah the python-qt4-dbus thing seems weird
[19:01] <antihero> Hmm, deps not fixed on GB. How do I know when that's updated?
[19:03] <yofel> aaaargh
[19:03] <yofel> sorry
[19:03] <yofel> not fixed, I got it from another source -.-
[19:03] <antihero> so is it that whoever's maintining it has accidentally put ubuntu2 instead of ubuntu1?
[19:03] <antihero> yofel: Could I get that source?
[19:04] <yofel> antihero: that's private, but different way:
[19:04] <yofel> got to https://edge.launchpad.net/ubuntu/+source/kde-wallpapers/4:4.7.0-0ubuntu1/+build/2653513
[19:04] <yofel> download the debs and dpkg -i them
[19:05] <antihero> goddamn uxterm let me copy paste
[19:06] <antihero> yofel: But I thought the issue was with kde-workspace-data?
[19:06] <antihero> and the fact that the available version is ubuntu1 but kde-workspace-bin needs ubuntu2
[19:07] <shadeslayer> fwiw kubuntu-desktop is still broken ;)
[19:07] <yofel> yes, kde-workspace-data depends on kde-wallpapers-default which doesn't exist yet
[19:07] <yofel> -> problem
[19:07] <antihero> yofel: I see.
[19:07] <yofel> install wallpapers by hand and apt should be happy
[19:07] <antihero> yofel. The package should really have wallpapers as optional >_<
[19:08] <antihero> I mean crikey, taking down a system for *wallpapers*
[19:08] <yofel> no, the depends is right, this is just what happens in +1 sometimes
[19:10] <antihero> yofel: Wallpapres thing did not fix.
[19:10] <yofel> what happens now?
[19:10] <antihero> same thing
[19:10] <yofel> which packages did you install?
[19:10] <antihero> kde-wallpapers and kde-wallpapers-default
[19:11] <jbicha> antihero: you know you don't have to install every update as soon as it shows up, right? ;-)
[19:11] <antihero> had to remove kde-workspace-data (ub1) to do it too
[19:11] <antihero> jbicha: I know I know now
[19:11] <yofel> k, then run apt-get update again
[19:11] <yofel> if it's still broken you do have a bit outdated mirror I guess
[19:11] <antihero> yofel: Which mirror are you using? DE?
[19:11] <yofel> yep
[19:11] <antihero> which mirror is the most up to date usually?
[19:11] <Pici> archive.ubuntu.com
[19:12] <shadeslayer> the main one? :P
[19:12] <jbicha> antihero: here's a bit of an explanation: http://ubuntuforums.org/showthread.php?t=1751299
[19:12] <jakemp> 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] <shadeslayer> btw is anyone here running O on the new Macbook Pro?
[19:14] <antihero> jbicha: I will bear this in mind
[19:15] <antihero> yofel: Hmm, now I've used the DE mirror a bunch of stuff about things being too new :(
[19:15] <yofel> "too new" o.O?
[19:15] <antihero> because kde-workspace-bin=4:4.7.0-0-ubuntu2 is not existing
[19:15] <antihero>  kde-workspace-bin : Depends: libkephal4abi1 (= 4:4.7.0-0ubuntu1) but 4:4.7.0-0ubuntu2 is to be installed
[19:17] <antihero> yofel: Perhaps they're finishing off the 4:4.7.0-0ubuntu2 builds as we speak?
[19:18] <jbicha> antihero: no problem, it takes practice & experience to know when to update but usually avoid partial or dist-upgrades
[19:18] <yofel> argh no, ubuntu2 is on LP
[19:18] <antihero> LP?
[19:18] <yofel> but I forgot that kde-workspace-data-extras is stuck in new too -.-
[19:18] <yofel> Launchpad
[19:18] <Pici> LaunchPad
[19:18] <antihero> ah
[19:18] <antihero> I'll try US mirror, perhaps it is more up to date?
[19:19] <antihero> Nope.
[19:19] <jbicha> or you could install unity or gnome-shell or something :-)
[19:19] <antihero> No.
[19:19] <antihero> I'm using flux atm, it's ok
[19:20] <antihero> I didn't mind unity too much, but just got irritating and I hate gnome 3's attitude towards customisation etc
[19:20] <yofel> antihero: if you want to try it, go on https://edge.launchpad.net/ubuntu/+source/kde-workspace/4:4.7.0-0ubuntu2/ - click on the architecture you need, and take -data from i386
[19:21] <yofel> maybe it'll help
[19:21] <yofel> or wait till we get it out of NEW
[19:21] <antihero> yofel: What exactly is NEW
[19:21] <antihero> currently I'm looking at http://packages.ubuntu.com/hu/oneiric/kde-workspace-data and that tells me it's still ubuntu1
[19:22] <jakemp> Is there a way to see if I am on Unity 3D or just 2d?
[19:22] <yofel> if you build a new binary package from a known source, that package will get stuck in the Binary New moderation queue until an Archive Admin accepts the package
[19:22] <antihero> Hum
[19:22] <yofel> that's why it's nowhere to be found yet. Built: YES, Published: NO
[19:23] <antihero> grr
[19:23] <yofel> you could download the ubuntu2 debs from the architecture pages if you want
[19:23] <yofel> they're up
[19:24] <antihero> yofel: Not kde-workspace-data asfaics
[19:24] <antihero> just -bin
[19:24] <yofel> antihero: -data is Arch ALL, thus only built on i386
[19:24] <yofel> you'll see it there
[19:24] <antihero> a
[19:24] <antihero> ahhh
[19:27] <jakemp> I am logging into Unity, but it seems to be switching over to unity 2D
[19:27] <jakemp> Since this recent dist upgrade
[19:27] <antihero> jakemp: Try runnign startx from a console and see if your drivers are screwed up?
[19:28] <antihero> yofel: If I install all these dependencies, will this frack up my upgrades down the line once the repos catch up?
[19:29] <antihero> and by "install" i mean "download debs and install"
[19:29] <jakemp> antihero, how do I kill my current x session?
[19:30] <shadeslayer> jakemp: sudo service gdm stop
[19:30] <yofel> antihero: those are the exact same packages that will end up in the repos, so no
[19:30] <jakemp> I thought gdm was removed
[19:30] <antihero> yofel: Unless they get moderated and rejected
[19:31] <antihero> right?
[19:31] <antihero> I'm basically being a human version of apt right now
[19:32] <antihero> wooo after installing about 15 deps I seem to have made progress
[19:32] <antihero> A fitting punishment for the naiive dist-upgrader
[19:33] <antihero> Thee only reason I accepted the dist-upgrade is that sometimes "necessary" sounding packages are replaced with different named ones
[19:33] <yofel> no reason for them to get rejected, we just don't have an admin around right now to accept them
[19:33] <antihero> yofel: Can I be an admin?
[19:33] <yofel> nope, and I don't know how to become one (not easy though)
[19:34] <jakemp> startx did not run, something about a missing protocol
[19:34] <antihero> yofel: What about if we set up a repo that essentially hosted brand new package hot from launchpad, with our own moderation?
[19:34] <antihero> jakemp: what error message dude?
[19:34] <jakemp> (I'm running on HD3000) graphics
[19:34] <antihero> Hmm.
[19:34] <yofel> antihero: have fun at proposing that to the LP devs
[19:35] <antihero> yofel: screenscraping :)
[19:35] <jakemp> "No protocol specified" just repeated
[19:35] <jakemp> I had to switch to another term and kill -9 it.
[19:35] <antihero> jakemp: Aye, that's sucky. I'm not too knwledgable about the HD3000, though NV was having probs
[19:36] <jakemp> Is there a way to see if I am in 2D or 3D?
[19:36] <antihero> yofel: It's great when aptitude's "solution" is to leave everything uninstalled and suck it up, and then if you reject that "solution" it just repeats it.
[19:37] <yofel> it doesn't repeat it, it gives you one where it removes one other package :P
[19:37] <antihero> yofel: Hoo ray.
[19:38] <jamesbond2> Hi I'm trying to run apport-retrace but I get the follow error http://pastebin.ubuntu.com/653963/
[19:38] <antihero> how do I turn noises off in kde
[19:39] <antihero> I keep getting these weird /opt/google/chome/chrome processes that take up absurd amounts of CPU.
[19:39] <yofel> blame chrome
[19:40] <antihero> Indeed, but I like chome. This one has been active for like, 4 hours ?!
[19:40] <antihero> sigkill and my system responds like modern computer again
[19:41] <jamesbond2> I have added the key but it still gives that error
[19:55] <antihero> yofel: Here's a colour scheme I made as a thanks for help https://github.com/radiosilence/Dogs-ColourScheme
[19:56] <yofel> heh, thanks :)
[19:58] <jakemp> This recent dist upgrade has two problems: now maximized winsows go behind the left bar, and when I prest the win key and start typing, I have to then get the mouse and click on the icon to run it; enter no longer works.
[20:06] <antihero> How would I enable stuff for my (nvidia) gfx card like triple buffering?
[20:11] <yofel> antihero: nvidia-settings I think
[20:17] <Daekdroom> indicator-me is still a unity-2d dependency, it seems
[20:51] <henke> anybody else having problems with Flash hanging X with nvidia drivers in oneiric?
[20:54] <nit-wit> henke, you might try using the FF add on flash aid to get the lateest adobe and cleaned up
[21:11] <henke> nit-wit, that's a useful add-on, however, it was of no help as I still get the X freeze at most flash animations
[21:12] <henke> although oddly enough youtube works well
[21:13] <nit-wit> henke, bummer, I'm about to reinstall oneiric again I removed a week ago, so I'm not sure what is going on in general.
[21:13] <nit-wit> henke, did yo install the restricted extras
[21:13] <nit-wit> *you
[21:13] <henke> oneiric has been extremely unstable for me all along, I have had much better luck with previous alpha/beta phases
[21:14] <nit-wit> henke, did you install the restricted extras
[21:14] <henke> nit-wit, I used to have the xorg-edgers ppa, but downgraded all that in case that caused problems.
[21:14] <henke> not sure which extras you ask of?
[21:15] <nit-wit> henke, look for restricted extras in sysnaptic
[22:36] <BUGabundo> evening
[22:36] <BUGabundo> and no GDM or lightDM working
[22:36] <BUGabundo> YAY
[22:36] <jo-erlend_> BUGabundo, hehe.. Yes, I had to go back to natty :)
[22:36] <BUGabundo> glad startx uses my last WM
[22:37] <BUGabundo> jo-erlend_: *worse* cicle I can remember
[22:37] <BUGabundo> and I've had them all
[22:37] <jo-erlend_> circle?
[22:37] <jo-erlend_> cycle! :)
[22:38] <BUGabundo> yeah
[22:38] <jo-erlend_> yes, but you know... I think it's better in the long run.
[22:39] <BUGabundo> then we should have been warned NOT TO run this devel cycle
[22:39] <jo-erlend_> absolutely. The communication has been very poor. Canonical needs to learn from that.
[22:40] <jo-erlend_> I totally support and agree with the focus on 12.04, but people needs to know that between now and then, things are going to get rough.
[22:41] <micahg> BUGabundo: what's not working?
[22:41] <BUGabundo> micahg: can I say what's actually working? the list should be smaller :)
[22:41] <BUGabundo> broken notification
[22:42] <BUGabundo> broken Classic with composite
[22:42]  * micahg hasn't rebooted since the lightdm 0.9.2 upgrade
[22:42] <BUGabundo> broken gnome applets
[22:42] <BUGabundo> now broken lightDM
[22:42] <jo-erlend_> oh. Then you're able to run the normal desktop at all? I'm not.
[22:42] <BUGabundo> jo define "normal"
[22:42] <BUGabundo> I was running lubuntu for over one month
[22:42] <jo-erlend_> non-failsafe.
[22:42] <BUGabundo> cause no other DM would work
[22:42] <BUGabundo> I'm on a STARTX session
[22:43] <jo-erlend_> in the end, I wasn't even able to start the failsafex. :)
[22:43] <BUGabundo> with gnome classic with no 3D
[22:43]  * micahg has been running xubuntu on oneiric fine with the exception of needing to click "other" to log in with lightdm
[22:43] <BUGabundo> if at least notifications worked :\
[22:44] <BUGabundo> I tried all those new gnome3 and unity WMs
[22:44] <BUGabundo> but.... they aren't for me
[22:44] <BUGabundo> I like classic
[22:44] <jo-erlend_> micahg, yes, that's what I'm experiencing with a live session, but when it's installed, I don't get any greeter at all. I can't login first and then run startx either. FailsafeXServer worked for a little while, but then it stopped working as well.
[22:44] <BUGabundo> but.... ITS BROKEN to hell
[22:44] <jo-erlend_> yup.
[22:44] <charlie-tca> The really sad part is the Xubuntu images are broken to the point they won't let you install
[22:44] <micahg> jo-erlend_: there was a bug where the greeter didn't get installed, but that was fixed
[22:45] <jo-erlend_> when?
[22:45] <jo-erlend_> I used yesterdays image.
[22:45] <micahg> oh, idk about images, charlie-tca would know more
[22:45] <charlie-tca> heh, broken
[22:46] <charlie-tca> I don't really know about the Ubuntu images. I haven't tried them this week
[22:47] <jo-erlend_> guess I'll give it another shot at the next alpha.
[22:55] <BUGabundo> micahg: all I can see on my side is that it fails to upgrade
[22:55] <BUGabundo> I just forced it
[22:55] <BUGabundo> hope it gets okay on the next reboot
[22:55] <micahg> BUGabundo: which fails to upgrade?
[22:55] <BUGabundo> ligthdm
[22:57] <charlie-tca> Make sure lightdm-greeter-gtk is installed
[22:59] <micahg> BUGabundo: did you still have lubuntu-desktop intalled?
[23:01] <BUGabundo> I think I've removed most of it
[23:01] <micahg> k, lubuntu-desktop was just fixed
[23:06] <charlie-tca> Does lubuntu use lightdm now?
[23:07] <micahg> charlie-tca: they were, they switched back to lxdm until the conf file issue is fixed
[23:07] <charlie-tca> I see
[23:40] <antihero> \a
[23:41] <antihero> argh, my nouveau module is loading for some reason and now it's saying "nvidia" module is not found :(
[23:42] <BUGabundo> WOW