[00:18] <tuedel> hi! every time i log into gnome, i get that "your last session lasted less than 10 seconds" message, and as soon as i click ok, my xserver crashes (along with some display errors). i can't find anything helpful in all those logfiles... here is my ~/.xsession-errors, if it makes sense to anyone: http://pastebin.ca/1096273 . i've already tried disabling compiz, deleting ~/.config/autostart and ~/.gnome2/session, but none of these helped. the 
[00:54] <Skiessi> anyone watching any olympic streams?
[00:54] <Skiessi> or is there anything on atm?
[00:55] <Skiessi> nvm
[00:55] <Skiessi> I'll ask in #ubuntu
[01:03] <doggymenz> anyone updated compiz in last few hours, and have problem with it no longer working?
[01:04] <mbrigdan> where are the configuration files for the screen saver kept?
[01:04] <JontheEchidna> mbrigdan: in kde or gnome?
[01:04] <mbrigdan> gnome
[01:04] <JontheEchidna> dunno
[01:06] <mbrigdan> :(
[01:06] <mbrigdan> where are they kept in KDE?
[01:07] <mbrigdan> gnome might be similar
[01:07] <JontheEchidna> ~/.kde/share/config/kscreensaverrc
[01:10] <mbrigdan> nope, not there
[01:10] <mbrigdan> oh well
[01:45] <DaskReecH> Hey can I tell from an ISO what version it is?
[01:46] <DaskReecH> Is there something I can grep for? or a file that would say hardy vs Gutsy vs Intreprid
[01:46] <DaskReecH> or the numerical designation
[01:48] <DaskReecH> ah dists ok
[02:15] <LaserJock> anybody know offhand the proper way to fix pcspeaker + PA problem?
[02:17] <Pici> LaserJock: With the screeching audio?
[02:17] <LaserJock> yeah
[02:18] <LaserJock> I mean, I've read several bugs, etc.
[02:18] <Pici> blacklist snd_pcsp worked for me.
[02:19] <biggahed> so... any reports about broken kb layouts?
[02:19] <Pici> Yes
[02:20] <biggahed> any pointers on how to fix it?
[02:20] <Pici> bug 255008
[02:20] <biggahed> thanks
[02:20] <Pici> Sure
[02:20] <biggahed> (but in my case its not only that... but first let me read it)
[02:21] <Pici> Its a whole slew of remapped keys
[02:27] <cycom> ok, I'm going nuts.  No matter what I do, I cannot get my mighty mouse to have it's horizontal scroll in the correct direction
[02:27] <cycom> unless, of course, I change xmodmap and swap 6 7 to 7 6, at which point my touch pad horizontal scroll is reversed.
[02:27] <cycom> no matter what I set in my Xorg.conf, the mouse is autodetected and ignores all my config changes.
[02:30] <cycom> any hints as to how to invert my horizontal scroll on my mighty mouse without trashing the horizontal scroll on my touchpad?  Or at the very least, invert the horizontal scroll on my synaptics touchpad so xmodmap doesn't break it?
[02:30] <biggahed> then you probably have some error on your conf
[02:30] <biggahed> or it wouldnt ignore your xorg.conf
[02:30] <biggahed> i think
[02:33] <tanath> cycom: you can use xev to check what the numbers are to know for sure what they should be in your xorg.conf
[02:34] <cycom> ok, with NOTHING set in my Xorg.conf for my mighty mouse, it defaults to left being 7 and right being 6. It's supposed to be the other way.
[02:35] <cycom> and with a section opening that device (/xev/input/by-path/(mouse path), I get an error: (EE) Grab failed. Device already configured?
[02:38] <cycom> part of me just wants to invert my synaptics touchpad driver's horizontal scroll, since it is the only device permanantly attached and in the config
[02:39] <cycom> I mean, I just disable my synaptic touchpad section, and it autodetected back in.  how can I disable autodetection in Xorg?
[03:22] <virtualroadside> cycom: its probably evdev's fault
[03:23] <virtualroadside> try adding the following ServerFlags
[03:23] <virtualroadside> Option "AllowEmptyInput" "true"
[03:25] <cycom> virtualroadside: allowemptyinput?
[03:25] <virtualroadside> yeah
[03:26] <virtualroadside> for disabling autodetection
[03:27] <virtualroadside> you also need to be sure that you're not using /dev/input/mice too
[03:30] <cycom> virtualroadside: huh. nope, didn't change anything
[03:30] <virtualroadside> hm
[03:30] <cycom> still getting 'Grab failed. Device already configured?'
[03:31] <virtualroadside> try shutting down hal and restarting X
[03:31] <virtualroadside> /etc/init.d/hal stop
[03:32] <cycom> virtualroadside: hehe, I think that may have helped, but it killed my keyboard in X, so I can't login. hang on a sec
[03:34] <virtualroadside> so i think theres some X directive to fix your button issue... what you can do is put the information into an FDI file that hal reads
[03:34] <virtualroadside> and config your touchpad from that instead of from xorg.conf
[03:35] <cycom> well, it's the mighty mouse I'm worried about really
[03:35] <cycom> it's a bluetooth mouse, and even if I manually configure it...
[03:36] <cycom> it doesn't seem to be using the config
[03:36] <virtualroadside> yeah
[03:36] <virtualroadside> which is because of the config isn't used after you start X
[03:36] <virtualroadside> so you use an FDI file to load a config for it
[03:36] <virtualroadside> via HAL
[03:37] <virtualroadside> i had this problem with my touchscreen, where it wouldn't work if i unplugged it
[03:37] <virtualroadside> because it wouldn't work with autodetect, and there wasn't a way to specify a config that would always be used for that device
[03:37] <virtualroadside> so i patched it :)
[03:37] <virtualroadside> so use an FDI file
[03:37] <virtualroadside> its documented nicely.. one sec
[03:38] <cycom> cool!
[03:40] <virtualroadside> heh
[03:40] <virtualroadside> oh
[03:40] <cycom> yeah, buttons 6 and 7 are still reversed without hal enabled, no matter what I do with the config :p
[03:40] <cycom> getting a bit annoyed with that.
[03:40] <virtualroadside> /usr/share/hal/fdi/policy/10osvendor/10-x11-keymap.fdi
[03:41] <virtualroadside> no
[03:41] <virtualroadside> heh
[03:41] <virtualroadside> its not there
[03:41] <virtualroadside> odd
[03:41] <virtualroadside> silly lack of docs
[03:41] <virtualroadside> /usr/share/hal/fdi/policy/10osvendor/10-x11-input.fdi
[03:41] <virtualroadside> no
[03:42] <virtualroadside> damnit
[03:42] <virtualroadside> the documented one isn't there
[03:42] <cycom> I found the policy that makes it evdev
[03:43] <virtualroadside> http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=blob;h=9c3f9fb725c4c6ae5c955fe0b2fe714c3f349dcb;hb=4212599c922373a224d2235c74672a3a3aa8e0b1;f=config/x11-input.fdi
[03:43] <virtualroadside> that one is nicely documented
[03:47] <virtualroadside> heh, none of that stuff ever made it onto the X wiki
[03:47] <virtualroadside> go figure
[03:48] <cycom> virtualroadside: I still don't understand what I'm supposed to change...
[03:48] <virtualroadside> well if you setup an FDI file that matches your device
[03:48] <cycom> I mean, what can I do about the horizontal scrolling? I have seen NO options for that so far
[03:48] <virtualroadside> then it will load that config
[03:49] <virtualroadside> oh
[03:49] <virtualroadside> ok
[03:49] <virtualroadside> so, im useless for that part :)
[03:50] <virtualroadside> why not just fix the driver?
[03:50] <virtualroadside> add an option to switch them around
[03:51] <cycom> heh. was hoping I wouldn't have to. besides, who says that it won't break other mise?
[03:51] <cycom> mice*
[03:51] <virtualroadside> have you tried ZAxisMapping?
[03:51] <virtualroadside> well thats why you make it an option
[04:13] <IdleOne> looks like my actual upgrade to Intrepid went well :) sound and network is working fine
[04:38] <cycom> virtualroadside: SUCCESS.  I editited the source and changed mouse_wheel_left=7 and mouse_wheel_right=6 and it worked. not sure what it'll do to other mice, but I don't have any other mise.
[04:38] <virtualroadside> lol
[04:38] <cycom> mice* jesus, how do I keep typoing that.
[04:39] <virtualroadside> you should add an option for it, and submit a patch :)
[04:39] <cycom> god, with my C coding skills? I imagine I would make people cry.
[04:39] <virtualroadside> just need to copy the other part of the driver -- I would imagine that its got *other* settings you can mimic
[04:39] <cycom> 'WHY?! WHY DOES IT LOOK SO TERRIBLE?!  Did he vomit on his keyboard? XD'
[04:40] <cycom> yeah, I kinda figured. We'll see what I can do.
[04:40] <virtualroadside> awesome though :)
[04:42] <cycom> hehe. yeah, you have no idea how stoked I am.
[04:43] <virtualroadside> indeed
[08:24] <zniavre> good morning
[08:25] <cycom> mornin'
[09:31] <tuedel> good morning. every time i log into gnome, i get that "your last session lasted less than 10 seconds" message, and as soon as i click ok, my xserver crashes (along with some display errors). i can't find anything helpful in all those logfiles... here is my ~/.xsession-errors, if it makes sense to anyone: http://pastebin.ca/1096273 . i've already tried disabling compiz, deleting ~/.config/autostart and ~/.gnome2/session, but none of these he
[10:06] <Finnish> Hmm, I get this error: W: Failed to fetch http://fi.archive.ubuntu.com/ubuntu/dists/intrepid/Release
[10:06] <Finnish> W: Some index files failed to download, they have been ignored, or old ones used instead.
[10:23] <gnomefreak> Finnish:  change the fi to uk or gb and see if that helps run update after you change all fi to any country code but since uk and gb are main mirrors thats why i suggest them
[10:23] <gnomefreak> gb works for me on intrepid
[10:40] <tuedel> every time i log into gnome, i get that "your last session lasted less than 10 seconds" message, and as soon as i click ok, my xserver crashes (along with some display errors). i can't find anything helpful in all those logfiles... here is my ~/.xsession-errors, if it makes sense to anyone: http://pastebin.ca/1096273 . i've already tried disabling compiz, deleting ~/.config/autostart and ~/.gnome2/session, but none of these helped. the fail
[10:40] <tuedel> this is really getting me mad :(
[10:43] <Ayabara> is there a nice site with an overview of what's new in Intrpid Ibex?
[10:44] <gnomefreak> tuedel: file a bug and attach the Xorg.0.log and Xorg.0.log.old and  .xsession-errors
[10:44] <gnomefreak> Ayabara: see /topic
[10:44] <tuedel> gnomefreak: bug for gnome-session?
[10:45] <gnomefreak> i would file it against xorg or you can use gnome-session and it will be redirected if its not right
[10:46] <tuedel> ok, will do that. thanks!
[10:47] <gnomefreak> np
[10:47] <gnomefreak> be back reboot
[10:47] <Ayabara> gnomefreak: I tried that link, but haven't found any nice overview yet :)
[11:39] <Finnish> gnomefreak: Thanks! Setting the source to Main server helped me out
[11:39] <gnomefreak> np glad you got it
[11:47] <k0p> hi all.
[11:48] <k0p> I have a package on repositorys added yesterday. But it's not compiled yet. Is need requirement a compile to the package?
[11:50] <gnomefreak> k0p: see #ubuntu-motu and you might want to explain it better
[11:51] <k0p> gnomefreak, ok thanks
[11:51] <gnomefreak> np
[11:52] <s0ullight> does nvidia support 2.6.26 allreadY?
[11:56] <gnomefreak> yes
[11:57] <s0ullight> so X should be working now i mean high resolutions
[11:57] <gnomefreak> you may need to screw with xorg.conf
[11:57] <gnomefreak> depending ont he card you have nvidia-glx-numbers
[11:58] <gnomefreak> replace numbers with your cards drivers
[11:58] <s0ullight> 8600
[11:59] <s0ullight> and what compat wireless tree is intrepid using?
[12:00] <gnomefreak> nvidia-glx-177
[12:00] <gnomefreak> s0ullight: ^^
[12:01] <s0ullight> lemme just look up some things :d ill ask you again if i have questions tnx
[12:01] <gnomefreak> remember xorg.conf hasnt been fixed for many yet
[12:03] <s0ullight> gnomefreak: atm i have a custom compiled 2.6.26 :D i need that kernel till intrepid is stable enough im going to play with the custom kernel
[12:04] <gnomefreak> s0ullight: the above drivers may not work with it but might
[12:05] <s0ullight> gnomefreak: X isnt the most important thing for me
[12:06] <s0ullight> iwl4965 that driver and its compability with 2.6.26 and some additional patches :d
[12:06] <s0ullight> last time compat wireless tree was totally broken and i had kernel panic microcode errors and so o
[12:07] <s0ullight> n
[14:13] <tormod> ssam: want to try gdb?
[14:15] <tormod> ssam: how much RAM do you have?
[14:26] <tormod> ssam: if you have a lot, try booting with mem=1024M for instance
[14:48] <ssam> tomsku, hi
[14:48] <ssam> tormod, hi
[14:48] <ssam> i have 2GB
[14:48] <ssam> i'll give it a go
[15:00] <ssam> mem=512M did not help :-(
[15:09] <tormod> ssam: did you try gdb? can be tricky. anyway, maybe they know upstream. can you file a bug?
[15:10] <ssam> just uploading my gdb log to LP. thank you for helping me
[15:10] <ssam> there are some similar bugs upstream. and ones with the blank screen. but no hard lock
[15:11] <ssam> if i open a new bug i guess they can figure out if they are dupes
[15:13] <tormod> ssam: sure.
[15:15] <ssam> tormod, also just to note, my lspci is attached higher up the bug
[15:18] <tormod> oh yes, I got confused by that Intel hijacker
[15:19] <tormod> I am not sure about that gdb, the SIGUSR1 should better be ignored. wait...
[15:20] <tormod> handle SIGUSR1 nostop
[15:21] <tormod> once you're at the first breakpoint, make a second: break xf86MapPciMem
[15:21] <tormod> then "cont" should take you to the second
[15:21] <tormod> type "where" and "list" to see where you are
[15:24] <ssam> i'll give that a try
[15:27] <ssam> i dont get a prompt back after doing 'cont' after adding the second break
[15:27] <ssam> there was a "Function "xf86MapPciMem" not defined. "message
[15:28] <ssam> is there an earlier point i can break at
[15:30] <tormod> aha it's not compiled with XSERVER_LIBPCIACCESS
[15:30] <tormod> break pci_device_map_range
[15:36] <ssam> that worked
[15:37] <ssam> http://pastebin.ubuntu.com/35861/
[15:37] <ssam> the machine is still alive
[15:38] <tormod> ahem it is compiled with XSERVER_LIBPCIACCESS, I just can't read ifndefs.
[15:38] <tormod> can you do a "bt full" there?
[15:39] <ssam> http://pastebin.ubuntu.com/35864/
[15:43] <tormod> hmm all values are "optimized" away
[15:43] <ssam> by the compiler?
[15:45] <tormod> yes the code is so optimized that there are no values around for gdb
[15:45] <tormod> can you install the libpciaccess dbg package?
[15:46] <tormod> libpciaccess0-dbgsym
[15:46] <ssam> ok. then shall i make my way back to where we are in gdb
[15:46] <tormod> maybe it works while it's running
[15:48] <tormod> type "frame 1" to be in RADOEONMapMMIO and then "print *info"
[15:50] <ssam> gives http://pastebin.ubuntu.com/35867/
[15:51] <tormod> that's a lot of zeroes. do you read the code so you see what I want to check?
[15:52] <tormod> I want to see the arguments to pci_device_map_range
[15:52] <ssam> i have not looked at the source yet
[15:53] <tormod> you can do "list" and "list -" to look at the code around where you are
[15:53] <tormod> but maybe that doesn't work with dbgsym packages btw
[15:54] <ssam> they just show me "in ../../src/radeon_driver.c"
[15:54] <ssam> i dont have the source installed
[15:54] <ssam> they show a number aswell. line number?
[15:55] <tormod> MMIOAddr = 3491758080, MMIOSize = 65536,
[15:55] <tormod> http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/tree/src/radeon_driver.c line 357
[15:55] <ssam> thanks, i was just googling for the source :-)
[15:56] <tormod> I have no clue if these parameters make sense
[15:56] <tormod> once you have the libpciaccess0-dbgsym you can "step" into that function and see how far you get
[15:57] <ssam> so you want to know whats being passed to pci_device_map_range when it crashes
[15:57] <tormod> exactly
[15:57] <ssam> if i do step, and then 'bt full' will it tell the arguments?
[15:58] <tormod> yes that should work if it has the symbols
[15:58] <tormod> you can always try without also
[15:58] <ssam> did the 'frame 1' command move me somewhere else, do i need to move back?
[16:00] <tormod> yes you're now in frame 1 = RADEONMapMMIO
[16:00] <tormod> but you're already inside pci_device_map_range this time.
[16:01] <tormod> not you, but the program counter :)
[16:01] <tormod> well you already did bt full, it won't list argument unless it has debug symbols
[16:02] <ssam> step killed it :-( "Single stepping until exit from function pci_device_map_range, which has no line number information."
[16:02] <tormod> ok get that dbgsym
[16:03] <ssam> done
[16:04] <tormod> now "next" your way through pci_device_map_range()
[16:05] <ssam> ok
[16:06] <tormod> do a bt full to start with
[16:06] <tormod> then while next'ing, try "info locals" to see the variables
[16:07] <ssam> is "Breakpoint 2, pci_device_map_range (dev=0x123f8b8, base=3491758080, size=65536, map_flags=1, addr=0x1257788)" what you are after?
[16:08] <tormod> good, that's the arguments. from here on I don't know much, maybe these parameters are fine or obviously wrong.
[16:08] <tormod> where
[16:08] <tuedel> from .xsession-errors: "Unable to create /home/tuedel/.dbus/session-bus" <-- could this be a reason for my xserver/gnome-session crashing? (for a description of my problem see https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/256332 )
[16:10] <tormod> can you walk through pci_device_map_range. caution
[16:10] <tormod> if you in RADEONMapMMIO and do next it will do the whole pci_device_map_range in one.
[16:10] <tormod> make sure you're in pci_device_map_range (where and frame) and then do "next" here
[16:11] <ssam> http://pastebin.ubuntu.com/35868/   the info locals dont seem to be that interesting
[16:12] <ssam> shall i keep nexting
[16:19] <tormod> ssam, I wonder why it jumps between  215 and 226
[16:19] <tormod> http://cgit.freedesktop.org/xorg/lib/libpciaccess/tree/src/common_interface.c
[16:19] <tormod> (but the line numbers might be a little off from the Ubuntu code)
[16:20] <tormod> yes do a few more nexts
[16:21] <tormod> the fun starts at line 260
[16:22] <tormod> or more at line 273
[16:22] <ssam> the line numbers are jumping around strangly, but now in locals i have region=0 and err=14
[16:22] <ssam> now region=1
[16:23] <tormod> ok we must be in 281 then
[16:23] <ssam> now 2. ah, i see loop from 0 to 6
[16:24] <ssam> i am at 260
[16:24] <tormod> pastebin?
[16:25] <tormod> we should have a "live" pastebin :) I guess it's called vnc :)
[16:25] <ssam> http://pastebin.ubuntu.com/35870/
[16:26] <ssam> i was think that. a hacked up tee command that fed to a website
[16:26] <ssam> more nexts?
[16:27] <tormod> yeah let's see if eventually hangs here, on a given region
[16:29] <ssam> it died. whole session at http://pastebin.ubuntu.com/35874/
[16:30] <ssam> shall i upload it to LP
[16:30] <tormod> to make it easier you could apt-get source the libpciaccess0, export DEB_BUILD_OPTIONS="nodebug nostrip noopt", and debuild -b -us -uc
[16:30] <tormod> then you would have all symbols and source code with numbers you can trust
[16:30] <ssam> ok
[16:31] <tormod> pastebin at crash?
[16:31] <tormod> at least you're a gdb professional by now :)
[16:31] <ssam> that last link is has all the way to the crash
[16:32] <tormod> oh yeah I missed that
[16:34] <tormod> yes please attach it to LP
[16:37] <ssam> done. do i need to remove the dbsym  package, now that libpciaccess has it all built in?
[16:38] <tormod> you don't need but I think it does no harm.
[16:38] <tormod> your new binary will not look there anyway
[16:43] <ssam> ok, so am back in pci_device_map_range
[16:43] <ssam> do you want a paste
[16:43] <tormod> yes and do a list so I see what the line numbers mean
[16:44] <ssam> http://pastebin.ubuntu.com/35878/
[16:44] <ssam> line numbers seem to match
[16:45] <tormod> yes they do, go on next'ing
[16:45] <tormod> and do another "list" because the code could have changed further down
[16:46] <tormod> info locals should make more sense now
[16:46] <ssam> oo, its showing me the source as i go :-)
[16:47] <tormod> yes even
[16:48] <tormod> you can do cool things like "display region" and it will print its current value all the time
[16:49] <ssam> upto line 252, numbers still agree
[16:50] <ssam> shall i next until it dies
[16:51] <tormod> well if you could stop just before :)
[16:51] <tormod> last time it died on region=2
[16:52] <ssam> ok i am on line 273, with region=2
[16:53] <ssam> i think the next 'next' would kill it
[16:54] <ssam> http://pastebin.ubuntu.com/35880/
[16:55] <tormod> can you do print *mappings
[16:55] <pen> how's intrepid now?
[16:55] <pen> good?
[16:55] <ssam> $1 = {base = 3491758080, size = 65536, region = 2, flags = 1, memory = 0x0}
[16:56] <tormod> print devp->num_mappings
[16:56] <ssam> $2 = 0
[16:58] <tormod> print pci_sys->methods->map_range
[16:58] <ssam> $3 = (int (*)(struct pci_device *, struct pci_device_mapping
[16:58] <ssam>      *)) 0x7fd17abd10db <pci_device_linux_sysfs_map_range>
[16:59] <tormod> we should have enough information now (I have no clue about this)
[17:00] <ssam> thanks. i'll upload that log
[17:00] <tormod> you could do "step" now, instead of "next", and we'll be inside pci_sys->methods->map_range
[17:01] <ssam> pci_device_linux_sysfs_map_range (dev=0x16728b8, map=0x168b300) at ../../src/linux_sysfs.c:507
[17:02] <tormod> list corresponds to http://cgit.freedesktop.org/xorg/lib/libpciaccess/tree/src/linux_sysfs.c ?
[17:02] <ssam> http://pastebin.ubuntu.com/35882/
[17:03] <tormod> can you "next" thru the snprintf
[17:03] <ssam> no
[17:04] <tormod> it died?
[17:04] <ssam> done, still alive
[17:04] <tormod> print name
[17:05] <ssam> http://pastebin.ubuntu.com/35884/
[17:06] <tormod> that looks fine. next
[17:08] <ssam> how far shall i go
[17:09] <tormod> are you done with "fd = open"
[17:09] <ssam> up to map->memory = mmap(NULL, map->size, prot, MAP_SHARED, fd, offset);
[17:09] <zbrahead91> Hello?
[17:10] <tormod> print *map
[17:10] <tormod> info locals
[17:11] <tormod> then next until you're out of this function again.
[17:11] <ssam> it died on the next
[17:12] <tormod> it died on mmap? interesting.
[17:12] <zbrahead91> In intrepid, the new netwrok-manager (and the old one) refused to let me use a GUI to manually configure my IP address on my LAN. The old one allowed me to edit /etc/network/interfaces and it worked. However, the new network-manager does not seem to use this file. How can I fix this?
[17:12] <ssam> http://pastebin.ubuntu.com/35887/
[17:12] <tormod> now we're in libc and almost kernel, so it should be enough :)
[17:12] <ssam> cool, i'll upload it
[17:13] <tormod> thanks for the handwork
[17:13] <ssam> lol, linux is not happy booting with mem=1024 (missing them M)
[17:13] <ssam> thanks for the gdb power
[17:14] <tormod> does it need more than a whopping kilobyte nowadays?
[17:14] <zbrahead91> Anyone going to give me any help :s?
[17:27] <tormod> zbrahead91: ask asac or look for / file a bug
[17:29] <tormod> zbrahead91: or ask in http://ubuntuforums.org/showthread.php?t=676992&page=19
[17:29] <zbrahead91> kk
[17:35] <tuedel> from .xsession-errors: "Unable to create /home/tuedel/.dbus/session-bus" <-- could this be a reason for my xserver/gnome-session crashing? (for a description of my problem see https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/256332 )
[17:50] <theunixgeek> Is there finally a new Human theme?
[17:57] <theunixgeek> yes there is! :D
[17:58] <theunixgeek> yayyy
[18:19] <tormod> ssam: you never used fglrx on that setup, right?
[18:23] <ssam> no, i am just check for sure
[18:25] <ssam> could it be something in the linux-resticted-modules-* packages
[18:27] <zbrahead91> By the way, whenever I use the file-roller application, it resukts in a catastrophic system crash based on permissions. I cant rport bugs very well, however, just thought I would mention it.
[18:30] <ssam> tormod, i removed all the resticted modules. i never had fglrx installed. still no joy
[18:33] <tormod> ssam: that's what I thought :) upstream asked.
[18:34] <ssam> i am replying on the bug
[18:34] <tormod> good
[18:35] <tormod> he's probably on #radeon as well
[18:36] <ssam> i have to go sorry, thanks for the help. bye
[20:02] <tanath> hrm, the login splash screen doesn't go away after logging in now :-/
[20:09] <tanath> and every new app i run is appearing in the loading at the bottom of the splash
[20:09] <tanath> weird
[22:17] <DanaG> ARgh... NetworkManager is a pain.
[22:17] <DanaG> I use rfkill to disable my onboard wifi card.... and NetworkManager disables ALLLLLL wireless cards.
[22:17] <DanaG> That's stupid.
[22:17] <DanaG> I could understand if it were a software rfkill like on Toshiba, but it's not -- it's the Intel card's own rfkill.
[22:19] <DanaG> Great, and now I disable rfkill... and NetworkManager still won't let me use any wireless devices.
[22:19] <DanaG> ... so now I have to kill NetworkManager.
[22:27] <DanaG> ARgh.
[22:27] <DanaG> http://lists.opensuse.org/opensuse-bugs/2008-05/msg06729.html
[22:36] <DanaG> "Remember: HAL rfkill button objects are _not_ tied to a specific hardware device; some just happen to be, but that was never the intention becuase it's just not possible."
[22:36] <DanaG> oh, if it's not possible...... then how can they be?
[22:36] <DanaG> =þ
[22:53] <Marco> Is anyone else's network connection going off/on all the time?
[22:54] <nemo> Marco: you using Comcast? :)
[22:54] <Marco> nah, AT&T DSL
[22:54] <nemo> oh. bellsouth
[22:55] <nemo> Marco: meh. maybe they have noisy unreliable connections too
[22:55] <nemo> although last service call did wonders for mine.
[22:55] <Marco> well, I just went over to my router and some cables weren't fully pushed in
[22:55] <Marco> hopefully that was it
[22:56] <Marco> nemo, I always wonder how service calls end up fixing issues like that
[22:56] <nemo> Marco: heh.
[22:57] <nemo> in my case they just have crappy cables
[22:57] <nemo> was main reason my connection problems seemed related to temperature I think
[23:57] <jacob> anyone running compiz seeing something similar to this when running some OpenGL apps/games? http://launchpadlibrarian.net/16680426/neverball-corrupt2.png