[00:41] <bjsnider> longstanding nvidia-current issue is now resolved in the x-updates ppa and in natty official int he next couple of days
[00:42] <bjsnider> stand up and pollute your britches with joy
[01:05] <durt> hey folks, an update this afternoon has left me without network, NM's message upon exit during boot is 'cannot find usable dhcp client' or some such, I'll try re-installing isc-dhcp-client. Anybody have anything else to suggest?
[01:44] <jfi> durt: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/724556
[01:53] <durt> jfi, thanks just found it myself and got them, now to reboot to natty.
[01:59] <jeffwheeler> I'm trying to figure out how nm determines when to connect to a network. I often have ethernet available, but it seems like nm will try to connect to a wifi network in addition to this, which means that it drops my stream and restarts it. But since this happens pretty frequently (a few times a minute, until my wifi starts breaking), a music stream is pretty annoying.
[01:59] <jeffwheeler> It seems like once it has an ethernet connection, it shouldn't try to route any traffic over an available wifi network, even if that network is set to connect automatically.
[02:02] <nemo> wow. that last set of natty updates screwed up my system bad
[02:02] <nemo> network manager was helpless
[02:02] <nemo> had to go to a vt and manually setup eth0 after borrowing a cable
[02:04] <nemo> here's hoping the next setup fixes
[02:04] <jeffwheeler> I've had longtime wifi problems, never quite diagnosed it. It'll drop after being online for only a few seconds, without my system seeing that the network has died (i.e. it thinks it's still connected, but can't get to the internet anymore, at which point reconnecting fixes it). Other times, it just times out connecting again and again.
[02:04] <nemo> also entire desktop repeatedly crashed, causing continual error dialogs to pop up
[02:08] <nemo> whew. seems to be all better
[04:19] <lamalex> can someone please help me escape dependency hell?
[04:20] <elky> You'll need to be more specific.
[04:22] <lamalex> elky, I don't exactly know how- when I try and update it wants to remove. ... pretty much everything
[04:31] <nit-wit> this is common in this level of development, wait for a straight update/upgrade
[04:33] <elky> lamalex, update "it"?
[06:44] <cdbs> Is there some memory leak in Ubuntu?
[06:45] <cdbs> My system hogs up a lot of memory very soon
[06:45] <cdbs> even though I may not run that many apps
[06:49] <cdbs> okay, got it: bug #722972
[07:21] <leagris> Hello
[07:21] <susundberg> Good morning
[07:22] <leagris> Please could you guide me in reporting a bug. Some updates ago, the root account no longer has ENV variables set up for system wide proxy settings. What package should I report to in Launchpad?
[07:24] <leagris> I could patch /root/.bashrc and add export https_proxy=https://10.48.7.1:3128/ because the lan I'm on require this so Apport can report crash using SSL, but my guess is, root should share the system wide proxy settings verbatim
[07:26] <leagris> I reckon not looking at that before as it just used to work. Maybe Apport switched to SSL and the ENV proxy settings where never set up for root, or it ceased to be. I don't know.
[07:34] <leagris> Well, looking further, .bashrc for root is the same as for all users. It look like proxy_settings are in /etc/environment but this does not get loaded by root, so Apport does not know of the proxy for SSL
[07:40] <susundberg> Please see: https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting
[07:40] <susundberg> Finding proper package (linked from that page): https://wiki.kubuntu.org/Bugs/FindRightPackage
[07:41] <susundberg> And "f for some reason you cannot file a bug through the Apport tool you can file one via Launchpad"
[07:45] <leagris> Thanks susundberg but I could not find any clue on identifying a package related to /etc/environment loading by root. apt-file search /etc/environment return nothing.
[07:54] <leagris> Sorry, crap ! https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/207768
[07:55] <leagris> A two years old bug resurfacing, still open, still confirmed, not-fixed
[07:56]  * leagris slap the Maverick Meerkat with a rotten bug numbered 207768
[09:30] <proti> morning
[09:38] <znejk> Hi, I have one partition with 10.10 and one with natty. Today when i did an update in natty it updated grub but when i rebooted the only thing I can see from 10.10 is memtest. Is there a way to reprobe the kernels or something with grub or is all lost?
[12:27] <om26er> natty does not boot, even did a clean install and the same problem, have to manually start dbus and then gdm starts
[12:27] <om26er> anyone know of a solution?
[12:31] <robin0800> om26er, got that here too have to do sudo stop gdm   wait then sudo start gdm
[12:38]  * yofel installs nvidia driver again
[12:43] <yofel> better :)
[12:45] <susundberg> Binary from nvidia page? does it work (again) with new X?
[12:47] <yofel> no, 270.29 package from x-updates ppa, works fine
[12:47] <yofel> 270.29 was released yesterday and adds support for x server 1.10
[12:48] <yofel> http://www.nvnews.net/vbulletin/showthread.php?t=159990
[12:48] <vega->  hmm i use x-swat-updates and have not gotten 270.29
[12:48] <vega-> still on 270.18
[12:49] <vega-> or is this a different ppa?
[12:50] <yofel> hm, no, it's https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/ - the driver is only there for natty though
[12:50] <vega-> oh ok, i'm still on maverick (on this machine)
[12:51] <vega-> guess 270.29 would still work on maverick though
[12:51] <htorque> natty is still at 260.19.29-0ubuntu1, though
[12:52] <vega-> sure, officially
[12:52] <htorque> my monitor blinks every 30 seconds with nouveau - do want binary blob NOW
[12:52] <yofel> yep, it'll take a few days until it's in the archive
[13:28] <dsdale24> I'm running kubuntu natty, been keeping up to date. After upgrading yesterday or the day before "aptitude full-upgrade" and restarting, I can no longer access the network. Wireless networking isnt working, and even rebooting with a wired connection isn't working. Its a dual-boot machine, windows 7 can connect to the network. Is there a way I can check my config?
[13:30] <susundberg> the fact that wire-net is not working sounds alarming
[13:30] <susundberg> ifconfig shows your network configuration
[13:30] <susundberg> and iwconfig your wireless configuration
[13:38] <dsdale24> ifconfig just shows lo
[13:41] <dsdale24> iwconfig shows "lo no wireless extensions" "eth0 no wireless extensions" "wlan IEEE 802.11abg ESSID off/any"
[13:41] <susundberg> so you are not connected anywhere ..
[13:41] <dsdale24> right
[13:41] <susundberg> should the wired connection have dhcp? What are you usually configuring your net with? Why does that not work?
[13:42] <dsdale24> I tried rebooting with an older kernel (-4 and -5), in safe mode root with networking, but it won't connect
[13:42] <dsdale24> dhcp, yes
[13:42] <susundberg> it wont connect -- you mean its not connecting automatically as it used to?
[13:43] <susundberg> have you tried clicking the network manager icon?
[13:43] <dsdale24> I usually don't have to do anything for the wired, it just works. With wireless, I use the network manager app in kubuntu
[13:44] <susundberg> And if you click the network manager what happens -- it seems to work but nothing happens?
[13:45] <dsdale24> right, its not connecting automatically. When I use the network manager program in kubuntu, the wired connections tab is greyed out and inaccessible, and when I scan for wireless networks, the interface combo box is empty and there are no networks found
[13:45] <susundberg> ok, try open console and type there 'iwlist scan'
[13:45] <susundberg> That should scan for available wireless networks (i used to test if driver works ok)
[13:46] <dsdale24> lo and eth0: "interface doesnt support scanning", wlan0: "failed to read scan data: network is down"
[13:46] <susundberg> hmm
[13:46] <susundberg> oh you did say that ifconfig didn show anything but lo
[13:46] <dsdale24> nothing but lo, yes
[13:46] <susundberg> try "ifup wlan0"
[13:47] <susundberg> and then again ifconfig
[13:47] <susundberg> check if wlan0 appeared there
[13:47] <dsdale24> ignoring unknown interface wlan0=wlan0
[13:47] <susundberg> and ifconfig shows nothing?
[13:47] <dsdale24> ifconfig still only shows lo
[13:47] <proti> dsdale24: did you try a dhclient eth0 as root ?
[13:47] <susundberg> ok, how about eth0 then? (ifup eth0)
[13:48] <yofel> there was a dhclient bug yesterday, maybe you're hit by that
[13:48] <yofel> made DHCP essentially unusable
[13:48] <dsdale24> sudo ifup eth0: interface eth0 already configured
[13:48] <susundberg> but that should not make network manager unusable?
[13:49] <proti> dsdale24: try: ifconfig eth0 up && dhclient eth0
[13:49] <dsdale24> dhclient: command not found
[13:49] <yofel> bug 724556
[13:49] <proti> Wonderfull
[13:49] <yofel> susundberg: it will render every app that needs dhclient unable to use DHCP
[13:49] <proti> Wan kind of dhcp client do you have then ?
[13:49] <susundberg> ah ok.
[13:49] <yofel> proti: got that too, he needs to update
[13:50] <yofel> somehow...
[13:50] <proti> How ? He's got not network..
[13:50] <susundberg> (but why isnt the eth0 showing up in ifconfig)
[13:50] <proti> bo*
[13:50] <susundberg> with usb stick :)
[13:50] <dsdale24> how do I update without networking? (not meant to sound snarky)
[13:50] <popey> boot from a live cd, mount up and chroot the local install, update?
[13:50] <proti> dsdale24: You can ifconfig manualy all the relevant informations.
[13:51] <proti> You have to know all the dhcp information to connect.
[13:51] <dsdale24> booting from a live cd is a royal pain on my computer, there is a problem with the drive
[13:51] <yofel> well, one option would be to download the new isc-dhcp-client .deb and copy it over, or set your IP and gateway by hand, I did latter
[13:51] <susundberg> not all, but ip and router?
[13:51] <popey> usb?
[13:51] <dsdale24> I've never been able to boot a live cd
[13:51] <popey> pull the disk out, put it in another machine, chroot, update :)
[13:51] <proti> Make an usb boot and use it.
[13:52] <yofel> IP, hostmask and gateway and DNS should be enough
[13:52] <susundberg> !! why not copy the package to usb stick and install there
[13:52] <susundberg> well one can use 8.8.8.8 as 'fix me soon' dns ;)
[13:52] <susundberg> (that is google dns )
[13:53] <yofel> seriously, if you don't know how to set the IP by hand, just copy the .deb from another machine
[13:53] <proti> dsdale24: You need to have the previous informations from the dhcp. They lies in a dhcp lease or in your /var/log/syslog.
[13:53] <dsdale24> If I can just copy a deb to usb, and upgrade from there, that seems easiest. Where can I get it, and could you explain the command to run?
[13:53] <proti> easiest but not the fastest.
[13:54] <yofel> dsdale24: what architecture?
[13:54] <proti> browse http://archive.ubuntu.com/ubuntu/pool/main/
[13:54] <proti> the isc-dhcp-client should be in i/isc-dhcp-something
[13:54] <yofel> he can just fetch it from launchpad
[13:55] <yofel> doesn't matter though, right
[13:55] <proti> indeed
[13:55] <yofel> https://launchpad.net/ubuntu/natty/+source/isc-dhcp/4.1.1-P1-15ubuntu5 go to the build for your arch and fetch what you need, isc-dhcp-client at least
[13:56] <dsdale24> ok
[13:58] <dsdale24> yofel: amd64, sorry, hard to keep up. You guys are amazingly responsive
[13:58] <proti> He needs the isc-dhcp-common too or not ?
[13:59] <yofel> maybe, I'm not sure what he'll need to fix it, after that he can just update the others over net
[14:03] <proti> I mean he'll to dpkg --force-all to install this packages since deps won't match.
[14:03] <dsdale24> I can't remember how to install from a .deb, guess I've been spoiled by the package manager
[14:03] <yofel> oh yeah, it has an explicit version depends on -common, so he'll need it
[14:03] <proti> If I remember well, the package was just missing the /var/run/isc-... files.
[14:04] <proti> Well dpkg *will think* it needs it.
[14:04] <yofel> yeah
[14:04] <yofel> dsdale24: sudo dpkg -i <deb>
[14:05] <dsdale24> thanks
[14:05] <yofel> give both at -client and -common at the same time, then dpkg won't complain
[14:08] <dsdale24> ok, done. shall I reboot?
[14:08] <yofel> shouldn't be necessary
[14:09] <dsdale24> well, when I click on the network manager icon (which is a red button with a white X on it), I still don't have access to wired networking
[14:09] <proti> hggdh: ping
[14:10] <yofel> dsdale24: what does sudo dhclient say now?
[14:10] <hggdh> proti: bonjour
[14:11] <dsdale24> yofel: "sudo dhclient eth0" it doesn't say anything
[14:11] <yofel> oh cool, nvidia 270.29 uploaded to natty
[14:11] <yofel> that's progress over command not found, try rebooting, maybe our ifup/down messed something up
[14:11] <proti> hggdh: salut
[14:12] <dsdale24> will do
[14:12] <proti> hggdh: no news from our fellows devs ?
[14:12] <proti> The bug is picking up heat.
[14:12] <hggdh> yeah
[14:12] <hggdh> cjwatson was going to look at it
[14:13] <proti> I'll post a workaround that works for me to unblock people
[14:13] <hggdh> but I know there was yet another critical bug that had him for a while
[14:13] <proti> the dhcp one ?
[14:13] <hggdh> proti: please do it
[14:14] <hggdh> proti: no, I do not think so, although it might have been yet another
[14:14] <proti> Well, it's manual. no way to fix that for now. It's just a formal write of boot init=/bin/bash then initctl stop mountall, kill, initctl start moutall again and again until it boots.
[14:15] <proti> hggdh: He told me it was something to do with CDIMAGE of server broken.
[14:15] <proti> I remember now
[14:15] <dsdale24> thank you yofel, proti, and susundberg, I'm back in business. Just in time too, I was planning on working on python3 support for matplotlib this weekend, now that I finished migrating the project to git and github
[14:15] <hggdh> correct
[14:16] <proti> dsdale24: you're welcome.
[14:16] <yofel> :)
[14:16] <dsdale24> you guys are awesome
[14:16] <hggdh> proti: but it does not work for all. Mine is still hosed, ecryptfs down
[14:16] <proti> hggdh: Did you try to reverse the package one by one until it works ?
[14:17] <proti> We'll know then who's the culprit.
[14:18] <hggdh> proti: no, I did not. I did try to identify the sequence, but upstart still befuddles me... there is really no doc on which events are used, and the flow
[14:18] <hggdh> I did think of building a preti net for it
[14:19] <proti> a what ?
[14:20] <Ian_Corne> does the new xorg stack work with the beta nvidia drivers? (270)
[14:22] <yofel> Ian_Corne: it does with 270.29
[14:22] <hggdh> proti: a petri net, sorry. Dyslexia is having a day with me
[14:23] <yofel> Ian_Corne: fetch it from x-updates or wait a few hours
[14:23] <Ian_Corne> I will wait a few hours
[14:23] <Ian_Corne> I'm kinda lurking and leeching this +1
[14:23] <yofel> ^^
[14:23] <Ian_Corne> don't have time to work stuff out :)
[14:30] <proti> hggdh: What's a petri net ? Like a petri box ?
[14:31] <proti> hggdh: I updated the bug with the operation description.
[14:31] <proti> Mind to try if it resurrects your ecryptfs ?
[14:37] <hggdh> proti: a preti net is a tool for modelling event-based flows -- http://en.wikipedia.org/wiki/Petri_net
[14:38] <proti> ok
[14:40] <proti> May I say that the logic of the boot was not changed by the update. Something in the update changed the behaviour of the mountall.
[14:44] <hggdh> proti: what I noticed on my side is that the upstart event sequence is changing from boot to boot
[14:44] <hggdh> and I do not know what programme emits what signals
[14:45] <hggdh> this would help a LOT, since then we would have a clear picture of the boot sequence, event-based
[14:45] <hggdh> proti: I will also try your sequence (I was running it a bit different)
[14:53] <proti> hggdh: I modified it because if I kill -9 the mountall process, upstart launch the sulogin as emergency on/ or do a shutdown instead of going on.
[14:53] <proti> sulogin on the same console as an interactive shell makes the tty unusable.
[14:53] <hggdh> heh. Yes, I found it out :-)
[14:54] <proti> So I tried sleep 5 && kill -9 mountall
[14:54] <proti> and switch to vt7
[14:54] <proti> Unfortunately, this morning, this resulted only in shutdown sequence.
[14:58] <hggdh> this is why I think we are getting stuck in different points each boot
[15:03] <proti> hggdh: init -v always showed the same end of sequence
[15:03] <coz_> hey guys
[15:04] <proti> mountall and other running then mountall-net and others ends correctly but mountall which stays there stuck.
[15:04] <proti> The picture you took is coherent with what I saw.
[15:10] <hggdh> yes, but the steps before varied. I have 9 filesystems; the ones that would be mounted varied per boot; the sequence of mounting also
[15:18] <HerrBert> How can I get my system to use the downloaded and upgraded (via apt-get) kernel 2.6.38?
[15:20] <patdk-wk> apt-get dist-upgrade, reboot
[15:21] <HerrBert> I upgraded all versions of 2.6.38 (daily update and dist-upgrade) but it was never used, grub only shows the 2.6.37
[15:22] <proti> update-grub
[15:22] <proti> HerrBert: you're using natty ?
[15:23] <HerrBert> did not help... here is dpkg -l linux-image-*: http://pastebin.com/wedJYqu0
[15:23] <patdk-wk> should be, only thing with 2.6.38 in it :)
[15:23] <proti> Hum, you really should purge some of them.
[15:24] <HerrBert> can I just purge an old kernel version
[15:24] <proti> Yes
[15:24] <HerrBert> via apt-get purge?
[15:24] <patdk-wk> apt-get remove linux-image-2.6.2.*
[15:24] <proti> dpkg -P linux-image (everything from 2.6.24 -> 2.6.35)
[15:25] <hggdh> proti: yes... in my case, a 'initctl stop mountall' hangs. I have to kill -9 it
[15:25] <proti> And keep just one version of each major (2.6.38-5 2.6.37-12)
[15:25] <proti> hggdh: Then how about your ecryptfs ?
[15:26] <hggdh> oh, it is still dead
[15:26] <proti> Let me see
[15:26] <HerrBert> patdk-wk: trying to remove brings: Package linux-image-2.6.28-16-generic is not installed, so not removed (for 2.6.24 to 2.6.27)
[15:27] <patdk-wk> just ignore that message
[15:27] <patdk-wk> it attempt to remove anything, even things not installed :)
[15:29] <proti> hggdh: If I remember well, the ecryptfs is pam controled, not upstart.
[15:29] <HerrBert> uuups, I accidentally all kernels
[15:30] <proti> HerrBert: Classic. I hate aptitute for this.
[15:30] <proti> dpkg is much more picky which means more secure at usE.
[15:31] <patdk-wk> I never had an issue with apt
[15:31] <proti> aptiture happilly removes half of your system.
[15:31] <patdk-wk> me and aptiture don't get along
[15:31] <HerrBert> I just had: apt-get remove  linux-image-2.6.31* and it wanted to delete all my kernels... dunno why
[15:32] <patdk-wk> HerrBert, it takes regex input
[15:32] <patdk-wk> maybe use ' around it
[15:33] <proti> patdk-wk: Try -> aptitude remove --purge-unused
[15:33] <patdk-wk> proti that wants to remove like nothing
[15:34] <proti> Removes every packages it thinks is unused.
[15:34] <proti> Problem is it guess completely wrong.
[15:34] <HerrBert> same as autoremove?
[15:34] <patdk-wk> I only have two kernels installed
[15:34] <proti> HerrBert: That's the command.
[15:35] <proti> I've been bitten once. So I decided, no more aptitude, never and ever.
[15:35] <yofel> I usually just run aptitude interactively and remove all kernels marked as obsolete
[15:35] <yofel> that never did the wrong thing so far
[15:36]  * patdk-wk keeps deleting old kernels, and forgetting some xen systems still use them
[15:36] <patdk-wk> but xen will be completely gone soon, so won't have to worry
[15:36] <yofel> trying to put working patterns in the parameters is pretty complicated and I usually get that wrong too
[15:37] <proti> hggdh: You have to check your pam configuration for the ecryptfs thing.
[15:37] <HerrBert> I still want to know how to get from 2.6.37 to 2.6.38 =) any help?
[15:38] <soreau> Hey guys I downloaded a natty live image a couple days ago but when I try to install it, there is only a busy cursor on installation screen after clicking forward to install
[15:39] <yofel> iirc the images were pretty broken recently, try to sync the image or use the alternate disk
[15:40] <yofel> HerrBert: what's the error you get again?
[15:40] <proti> HerrBert: Once old kernel purged, you need to issue the update-grub command.
[15:40] <yofel> he shouldn't need to, removing kernels will trigger update-grub
[15:40] <proti> I would like to see the ouput of the command in a pastebin to check.
[15:41] <proti> yofel: the install too. I suspect there is too many kernel for the grub.
[15:41] <genii-around> Is: "Error org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success" anything to currently worry over?
[15:41] <yofel> yeah, he got Xen errors on update-grub yesterday, we didn't get any further at debugging that back then
[15:41] <HerrBert> the problem I have is: "apt-get install linux-image-2.6.38-generic -> linux-image-2.6.38-5-generic is already the newest version." but uname -r -> 2.6.37-8-generic
[15:42] <proti> Your problem happenned near 2.6.37-8.
[15:42] <yofel> HerrBert: we need the output of update-grub, pastebin would be best
[15:42] <proti> My last kernel 2.6.37 is -12.
[15:42] <HerrBert> gimme a sec
[15:43] <HerrBert> yofel: http://pastebin.com/MQZxTLjg
[15:43] <yofel> oh, you have old grub..
[15:44] <proti> Hum, there are obviously not xen kernels.
[15:45] <proti> HerrBert: How about installing grub-pc ?
[15:45] <yofel> still, shouldn't fail, at least file a bug
[15:45] <HerrBert> I'll try =) never heard of that although :D
[15:45] <proti> It is grub 2
[15:46] <yofel> and since grub1 is still in main it is supposed to be supported
[15:47] <proti> Indeed. The update-grub thinks for whatever reason that your kernel is a Xen kernel.
[15:47] <proti> Strange.
[15:47] <yofel> I found the lines in update-grub that fail, let's see if I get what they do...
[15:48] <yofel> http://paste.kde.org/5826/ line 1424
[15:49] <HerrBert> the grub-pc configuration asks me some stuff about chainloading, shall I do yes or no? :)
[15:50] <proti> yofel: I think the problem is rather near 1555.
[15:50] <proti> HerrBert: You have windows ?
[15:50] <HerrBert> nope
[15:51] <yofel> proti: that's the end of the file...
[15:51] <proti> yofel: Oups, sorry, 1384
[15:51] <HerrBert> but 1 line in grub showing windows, but there is no installation i think
[15:51] <yofel> proti: agreed, that's what I'm looking at currently
[15:52] <yofel> our kernels do have CONFIG_XEN_PRIVILEGED_GUEST=y set
[15:53] <HerrBert> I think grub-pc did it =)
[15:54] <proti> So they are considered as XEN kernels.
[15:55] <proti> yofel: Why are the kernel setting this options ? They are DOMU kernels ?
[15:55] <yofel> no idea, let me look at the changelog
[15:56] <yofel> nothing to be found..
[15:57] <proti> yofel: http://paste.kde.org/5829/
[15:58] <proti> XEN is on with every kernel.
[15:58] <proti> every 2.6.38.*
[15:59] <yofel> yeah, probably since 37-9 looking at his issue
[15:59] <HerrBert> grup-pc really did it
[15:59] <HerrBert> thx
[15:59] <HerrBert> but still the problem with the mountall 'n stuff
[16:02] <proti> HerrBert: Did you use the & to make the getty go background
[16:02] <HerrBert> mhm
[16:03] <HerrBert> I commented the bug in lp with more detail
[16:04] <proti> HerrBert: Oups, Sorry I misread your entry.
[16:04] <HerrBert> np =)
[16:04] <proti> So after getty tty8, you don't have a shell in the vt8 ?
[16:04] <HerrBert> nope, just my blinking underscore
[16:05] <proti> You can do a mount -a
[16:05] <proti> then : initctl start tty2
[16:05] <proti> 3, 4 and so one but not the one where you are.
[16:06] <proti> HerrBert: Ha, another thing, you have to exit twice from the chroot for the things going on.
[16:06] <proti> You did it ?
[16:07] <HerrBert> I do not have a shell, I used exactly(!) the commands of the post above mine =)
[16:07] <proti> Let sum up -> break=mount then ctrl-x to boot
[16:07] <HerrBert> i will try now, because I have different kernel and different grub now, maybe it was affected by that
[16:07] <HerrBert> y
[16:07] <proti> Then a prompt wiht (initramfs) ?
[16:07] <HerrBert> yes
[16:08] <proti> chroot /root /bin/bash
[16:08] <HerrBert> then I had the 3 mentioned errors
[16:08] <proti> gives you a prompt like (null)@root#
[16:08] <HerrBert> but i could do 2 times the exit and system was booting
[16:08] <HerrBert> yes
[16:08] <HerrBert> root@(null) i think
[16:09] <proti> When launching the getty twice, you should have the same prompt on two different tty (alt+f6 and alt+f8).
[16:09] <proti> HerrBert: correct, I swaped both
[16:11] <proti> HerrBert: Then you don't have those two prompts. I don't get it, you should have them.
[16:12] <HerrBert> I launched getty twice and exit twice and then waited for system to halt (when booting) -> then  I checked tty6 and tty8 but there was nothing
[16:12] <proti> You can check just after the start of the getty.
[16:13] <proti> Anyway you can do the initctl start/stop and the shell you get after sysreq+i.
[16:14] <proti> and/at*
[16:16] <proti> HerrBert: Is this the machine you using now that has this problem ?
[16:24] <yofel> FWIW - CONFIG_XEN_PRIVILEGED_GUEST=y seems to be set for all amd64 kernels set by Tim Gardner "UBUNTU: [Config]: updateconfigs after rebase to 2.6.37-rc1"
[16:25] <proti> not coherent.
[16:25] <proti> It happens only after 2.6.37-9 which is quite late.
[16:25] <proti> -rc1 is the first patch.
[16:25] <yofel> git does say
[16:25] <yofel> 26749bc7 (Tim Gardner               2010-10-22 14:16:25 -0600 482) CONFIG_XEN_PRIVILEGED_GUEST=y
[16:25] <yofel> though
[16:26] <proti> When was the 2.6.37-9 published ?
[16:26] <proti> One has to ask him about this.
[16:27] <proti> It seems we are running Xen kernel for quite a long time ? Or not ?
[16:28] <yofel> yeah, odd -9 is from Date: Thu, 09 Dec 2010 18:15:35 +0000
[16:28] <proti> Humm...
[16:29] <yofel> it's set for i386 virtual and generic-pae too, but not for generic
[16:29] <proti> You are talking about i386 arch.
[16:29] <proti> It's set here for amd64.
[16:30] <yofel> did he tell us what he used? it is set for amd64 generic at least
[16:30] <yofel> ah well, have to go, bbl
[16:31] <proti> bye then
[16:31] <proti> yofel: Need to file bug ?
[16:33] <Herrbert> getty -8 -n -l /bin/bash 38440 tty8& does still not bring up a shell on Alt+F8
[16:34] <yofel> I'll do that later after poking the kernel team
[16:34] <proti> yofel: it's basicaly a dummy symbol.
[16:34] <proti> Not using anywhere in the arch.
[16:35] <proti> Herrbert: it's 38400 not 38440.
[16:35] <proti> That's why.
[16:35] <Herrbert> argh :D why do all say its 38440?
[16:35] <proti> I did a Stupid typo.
[16:36] <Herrbert> mkay, retry again
[16:38] <yofel> ah, feel free to file one then
[16:38] <yofel> now I'm really gone
[16:39] <proti> Against kernel or update-grub ?
[16:44] <proti> HerrBert: Welcome back.
[16:44] <HerrBert> proti: now your workaround works =) I'll never shut down my machine until this is fixed :D
[16:44] <proti> Good
[16:45] <proti> Now you're natty again.
[16:45] <HerrBert> yay :D
[16:45] <proti> I should have done the same as you (double boot between natty/maverick).
[16:46] <proti> Unfortunately, I only have natty on this machine.
[16:46] <HerrBert> nah, i only have natty
[16:46] <proti> HerrBert: How then did you boot before ?
[16:47] <HerrBert> but with sysreq+i , startx and stard dbus start network manager i managed to get into irc on the "broken" natty
[16:47] <HerrBert> =)
[16:47] <proti> wow. You're quite resilient.
[16:48] <proti> yofel: bug already filed 586786
[16:49] <HerrBert> proti: im not good in shell commands, but if i have X i feel comfortable, because I can use many tools i cant in only shell
[16:55] <proti> hggdh: ping
[16:55] <HerrBert> btw: is unity still very buggy?
[16:56] <proti> Don't know. I'm not using it.
[17:06] <hggdh> proti: sir?
[17:07] <proti> Well, look at backlog, there is a nice bug in update-grub from grub1
[17:08] <proti> hggdh: Herrbert was not seeing newer kernels installed on his system.
[17:08] <HerrBert> should I have filed that one? i forgot...
[17:09] <proti> It's related to a bug in update-grub that ignores every kernel that has the XEN_PRIVILEGES_GUEST set in the confi.
[17:09] <proti> config*
[17:09] <hggdh> hum
[17:10] <proti> And since xen is not installed, it does not generate a xen entry for those.
[17:10] <proti> bug 586756 is related
[17:10] <proti> I added a comment, but it's undecided / unassigned.
[17:12] <HerrBert> what is this xen stuff?
[17:12] <proti> Paravirtualisation of the kernel. Search for xen domU dom0.
[17:33] <Volkodav> did nvidia get the new drivers out? looks like safe-upgrade is not holding the xorg anymore
[17:36] <Volkodav> 270.29 is OK with new X I guess ?
[18:14] <bjsnider> Volkodav, affirmative
[18:14] <Volkodav> good
[18:17] <Volkodav> so these are beta drivers right?
[18:24] <HerrBert> I think i also have probs with my nvidia drivers, sometime out of nowhere parts of my panels become black, and when mousover the symbols that are there come up again, but still black areas there where no buttons and stuff is...
[18:26] <bjsnider> Volkodav, affirmative
[19:09] <BUGabundo> hey
[19:29] <Daekdroom> Has anyone else been facing problems with transmission's indicator?
[20:46] <cjohnston> Is anyone having issues with the titlebar not showing up on windows?
[21:24] <pietro10> Hi. Why does the update-manager -d process want me to remove cmake
[21:24] <pietro10> ?
[21:24] <pietro10> it's used by several projects I help with
[21:27] <yofel> could be a dependency conflict as it's not part of the default installation - I personally have cmake installed here
[21:29] <pietro10> huh
[21:29] <pietro10> is there a way to find out from within synaptic?
[21:30] <yofel> iirc update-manager had logs somewhere, it should have the reason why it wants to remove it in there
[21:31] <pietro10> I'll check again later then, thanks
[21:32] <yofel> you can probably install it again later, as I said, it's installed fine here