/srv/irclogs.ubuntu.com/2010/05/30/#ubuntu-desktop.txt

hallynuse gnome keyboard shortcuts to define alt-ctrl-enter to 'gnome-terminal'.  when a terminal comes up, it doesn't appear to have my environment - puts me in / instead of /home/serge, doesn't share ssh keys with terminals launched from gnome menu, etc.  worked fine in karmic, not in just-installed lucid...01:28
ccheneyhallyn, hi!03:57
ccheneyhallyn, are you the serge that was at trio on thursday? :)03:58
ccheneyhallyn, i definitely see the same issue you are reporting on my install04:06
ccheneyhallyn, you should probably file a bug04:06
ccheneyhallyn, or report it to seb128 when you see him around04:06
hallynccheney: yup, hey04:27
hallynok, i'll make a note to file on tuesday.  there was also another bug, with the installer04:28
ccheneyhallyn, ok reporting both would be good :)04:28
hallynit installed grub on /dev/sda, but /dev/sda was the usb stick.  had to look at the 'advanced' view of the summary to see what had happened04:28
ccheneyyea i am Chris I saw next to Nick who was sitting directly next to you from what I recall04:28
hallyni may come around asking where bugs get filed around here04:29
hallynthe debian dude :)04:29
ccheneyhallyn, for installer it is most likely ubiquity04:29
ccheneyyea04:29
hallynok, thanks, bbl04:30
hallynccheney: oh hey, if you're still there, i can ask you my i'm-a-dumbass question.  is there a cd image i can use to isntall 64-bit on intel?04:34
ccheneyyea04:34
ccheneyhttp://releases.ubuntu.com/10.04/04:34
ccheneythe architecture is called 'amd64' as amd made it and named it04:35
ccheneyintel has called their clone of it 3 or 4 different things over the years04:35
ccheneyamd64 is essentially the same thing as x64_64 / x86-64 that you may see elsewhere, the reason for the difference in naming was due to amd contracting SUSE to port the toolchain before they finalized the name of the arch and actually even before they had silicon04:36
hallynhm, when i made a live-usb from that one it wouldn't boot, so i assumed core i7 just wasn't supported04:36
ccheneyit should work, i installed 10.04 on my i7-860, i don't recall if it was via usb or cd though04:36
hallynhm.  guess i'll try again then04:38
ccheneyit may be that for some reason it doesn't want to boot off usb at all, you may want to verify that part does work with something else04:40
ccheneyfrom what i recall i've had problems getting booting off usb to work reliably, i can't remember if it was a computer issue or a usb key issue though04:41
hallyni was able to boot ubuntu-10.04-i386 and fedora-13-x86-64 from usb04:42
hallynmaybe i made a silly misstep04:42
ccheneyok, so it should be working then04:42
hallynbut gah where did tha tiso go04:43
azteechis there a Ubuntu specific chat room for the amd64 based OS?06:18
jo-erlendno. Why would there be?06:19
azteechwas looking to see if there was a specific irc channel the targeted the amd64 (x86-64) release of Ubuntu is all.06:22
jo-erlendyes, but why?06:22
azteechjo-erlend .. because it is what I use on my desktop as of this week, and, since Ubuntu is debian-based, and they also have a amd64 irc room, was looking to see if one was available to log on to here .. is all ... have no specific problem to resolve ...06:26
jo-erlendhmm. Wonder why they do. Seems redundant to me.06:28
azteechmy guess, and it is why I was looking, is there are problems that are specific to x86-64 that don't impact x86-32 ...06:31
ccheneyi think debian probably only has amd64 channel due to legacy reasons06:31
ccheneyit was originally started from what i recall when we were doing porting work to the amd64 arch back around 2003/200406:31
azteechccheney .. you mean the debian-amd64 channel?06:32
ccheneyazteech, yea06:32
azteechah, okay ... that sort of explains why there is little chatter these days .. in it then ... tks ...06:33
ccheneyok06:33
hallynccheney: yeah i can't even boot an amd64 cdrom.  weird.16:00
=== JanC_ is now known as JanC
ftaguys, the new python2.6 makes rhythmbox crash in maverick: bug 58758918:31
ubot2fta: Bug 587589 on http://launchpad.net/bugs/587589 is private18:31
ccheneyhallyn: do you have the most up to date bios for your system?19:05
ccheneyhallyn: also it a p55 or some other chipset?19:05
ccheneyhallyn: i7 can be 1156 or 1366 and there are several chipsets, mine that works is a p55 chipset 1156 i7-86019:06
hallynmodel: 3019:09
hallynmodel name: Intel(R) Core(TM) i7 CPU       Q 720  @ 1.60GHz19:09
ccheneyoh a i7 laptop?19:11
ccheneyyou might be able to find information about it on the ubuntuforums site, i don't know if the kernel in 10.04 is new enough for that chipset or not19:11
ccheneythough i do recall seeing people using the thinkpad x201 which i think uses the same chipset19:12
hallyn<grimace>19:12
hallynhm, well so maybe the daily maverick cd build if there is sucha thing yet might work19:13
ccheneyyea19:13
ccheneythey haven't started generating yet19:14
ccheneythey will be in http://cdimage.ubuntu.com/daily-live/current/ when they are available19:14
hallynwell i'll tell you waht i'm not doing - installing 32-bit on an 8G laptop :)19:14
hallyndo you know when they start building those?19:14
ccheneyhallyn: does the cd not even attempt to load the boot loader?19:14
hallynwell the cd must have been corrupt19:14
hallyni can't boot kvm off that either19:15
ccheneyhallyn: if i remember correctly there should be a way to get it to show you the kernel output19:15
ccheneyoh ok19:15
hallynthe usb stick starts to boot,19:15
ccheneyhopefully just corrupt cd then19:15
hallynoh no19:15
hallynhm.  no the usb stick hasn't even been trying to boot now19:15
hallynall right, maybe i'll walk to cvs and buy some new cds19:15
hallyn(i'm out of blanks :)19:15
ccheneyif you still have trouble after verifying the cd is written correctly let me know, i have some other things for you to try19:15
hallynwell it'll be awhile bf i can test that so if they seem like likely ideas...19:16
ccheneyhallyn: ok next idea if it does not work, is to if it shows the weird hieroglphics on the bottom of the screen hit a key, it shows you the regular old style screen were you can modify the kernel boot line, i think you can change it to where it will spew kernel info and hopefully show you where it hangs, you can also from that menu do a memory test and maybe an image test as well (or used to be able to)19:19
ccheneyif it doesn't even get to the point where you can select items on the boot menu you may need to try using the alternate cd if still having problems to track down the issue19:20
ccheneyif none of the above works ask someone on the austin team to look at it for you :)19:20
ccheneythey may have some more tricks to try that they could do in person19:21
hallynok - of course since fedora works and lucid doesn't, i suppose i can take a clsoer look at the file contents19:26
hallyn(what happened before was i got the initial screen, then it said it couldn't read the image.  Now It doesn't even try to boot any more)19:26
ccheneyhallyn: well i think fedora 13 has newer kernel than ubuntu, so it might be related to that, but hopefully not19:27
ccheneyit released nearly a month after ubuntu from what i recall19:28
ccheneyhallyn: if it ends up being kernel related you can probably manage to get the new maverick kernel into a lucid install but it may take a bit of work19:29

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!