[00:00] <BUGabundo> I would report it, but apport doesn't like it :(
[00:01] <asac> BUGabundo: what do you mean by "two times on every boot"?
[00:01] <BUGabundo> well
[00:01] <BUGabundo> I start it
[00:01] <BUGabundo> it crashes
[00:01] <BUGabundo> I start agait
[00:01] <BUGabundo> it crashes
[00:01] <BUGabundo> the 3rd it works
[00:02] <asac> BUGabundo: with an Xid error?
[00:02] <asac> BUGabundo: do you see the UI at all?
[00:02] <asac> or does it crashes right away?
[00:02] <BUGabundo> some times I have to use --sync to be able to make it start
[00:02] <BUGabundo> no UI
[00:02] <asac> i see
[00:02] <asac> Gdk-ERROR **: The program 'firefox-3.6' received an X Window System error.
[00:02] <BUGabundo> $ pastebinit .xsession-errors
[00:02] <BUGabundo> http://paste.ubuntu.com/210044/
[00:02] <asac> This probably reflects a bug in the program.
[00:02] <asac> in .xsession-errors
[00:02] <asac> The error was 'BadWindow (invalid Window parameter)'.
[00:03] <asac> seesmt to be not it
[00:03] <asac> can you stop ffox and start it from consoel?
[00:03] <asac> to see what it spits out there if it crashes?
[00:03] <asac> (maybe start multiple times, if it doesnt crash the first time)
[00:04] <BUGabundo> didn't crash this time
[00:04] <BUGabundo> trying agin
[00:04] <BUGabundo> got one now
[00:05] <BUGabundo> http://paste.ubuntu.com/210046/
[00:10] <BUGabundo> asac: another *very* anoying bug I have on 3.6 but haven't tested on a new profile:
[00:10] <BUGabundo> awesome bar will not store new entries
[00:10] <BUGabundo> so it doesn't memorize new urls
[00:12] <BUGabundo> (firefox-3.6:21449): Gdk-WARNING **: XID collision, trouble ahead
[00:12] <BUGabundo> Removing DOMNodeRemoved listener
[00:23] <BUGabundo> asac: I want to file a bug: 3.6 doesn't allow triple click to select a single word from URL
[00:23] <BUGabundo> :((((
[00:24] <BUGabundo> confirmed a NEW profile
[00:31] <asac> doenst work with 3.5 either here
[00:32] <Grantbow> asac: thanks for your blog post on firefox 3.5
[00:35] <asac> Grantbow: thx
[00:35] <Grantbow> asac: enabling proposed updates will work too?
[00:36] <Grantbow> for Jaunty
[00:36] <asac> Grantbow: yes. just posted a comment to confirm that its in jaunty-proposed
[00:36] <Grantbow> cool, thanks
[00:37] <BUGabundo> asac: you gonna get soooo many users testing packages from -proposed, without they understanting ITS TESTING PACKAGES
[00:38] <BUGabundo> asac: is it? I don't remember it not working on 3.5
[00:39] <BUGabundo> I do remember soemthing on about:config for that
[00:39] <BUGabundo> crazy mozilla guys who always think they know best
[00:40] <asac> Grantbow: also added a "Updated:" line to the blog entry now
[00:41] <Grantbow> asac: great, that will help as people continue to google for this.  I found your site from a link from http://www.ubuntusolutions.org/2009/07/installing-firefox-3-5-the-right-way-on-ubuntu-jaunty.html
[00:41] <Grantbow> I'll email him too
[00:42] <asac> thx
[00:44] <BUGabundo> asac: so bug or feature?
[00:44]  * BUGabundo tries to find old addon that allowed to select anything
[00:44] <asac> BUGabundo: i would think its a feature ... to be sure search in bugzilla for duplicates
[00:44] <asac> there probably are dupes there already
[00:49] <BUGabundo> asac: Q: is it worth to file a bug to suspend OSD buble when typing in FF search??
[00:49] <BUGabundo> its *the* most stupid UX bug ever
[00:54] <BUGabundo> asac: feature; http://overooped.com/post/30932542/re-firefox-3-vs-safari-3
[00:54] <BUGabundo> browser.urlbar.doubleClickSelectsAll;false
[00:54] <BUGabundo> fixed
[00:54] <reed_> asac: typo in blog post
[00:55] <reed_> xulrunner, not xulrunnner
[00:55] <BUGabundo> (pkix_CacheCert_Add: PKIX_PL_HashTable_Add for Certs skipped: entry existed
[00:55] <BUGabundo> hey reed_
[00:56] <reed_> hiya, BUGabundo
[00:56]  * reed_ upgrades one of his older laptops from 8.10 to 9.04
[00:56] <reed_> except my dual screen support will probably be broken
[00:56] <reed_> due to no fglrx driver
[00:56] <reed_> *sigh*
[00:57] <BUGabundo> reed_: ehehe
[00:57] <BUGabundo> try karmic then
[00:57] <BUGabundo> won't be even worse ahah
[00:57] <reed_> no thanks ;)
[00:57] <BUGabundo> there isnt a single GPU in good state right now
[00:57] <Grantbow> asac: so the way you recommend right now for end users is checking the jaunty-proposed box?
[00:57] <BUGabundo> :((
[00:58] <reed_> Grantbow: or you can just wait a week or so
[00:58]  * BUGabundo would rather have users using mozilla-security PPA to -proposed
[00:58] <reed_> Grantbow: or install it manually from firefox.com
[00:58] <reed_> ;)
[00:58] <BUGabundo> reed_: noooooooooooooooooo
[00:58] <reed_> yesssssssssssss
[00:58] <BUGabundo> don't go tell that....
[00:58] <reed_> I run it manually ;)
[00:58] <Grantbow> reed_: the LUGs I'm talking to are impatient
[00:58] <BUGabundo> there are at least 3 PPAs with it
[00:58] <reed_> using official mozilla builds
[00:59] <reed_> hehe
[00:59] <Grantbow> reed_: and I want to give them the easiest possible solution to get it now
[00:59] <BUGabundo> Grantbow: my opinion counts nothing, but, go with PPA and then remove it when it hits the archive
[00:59] <Grantbow> the jaunty-proposed sounds best
[01:00] <BUGabundo> humm the prob with PPA is adding the damn key
[01:00] <BUGabundo> Grantbow: but that will bring many packages that are there for testing
[01:00] <reed_> jaunty-proposed could easily break something else, though
[01:00] <reed_> if it's not turned off later
[01:00] <Grantbow> BUGabundo: which PPA do you recommend?  security doesn't have it yet
[01:00] <BUGabundo> and MOST users won't even have the slicest idea what bug they are testing
[01:00] <BUGabundo> sure it does
[01:01] <asac> Grantbow: i outlined what jaunty users should do in the blog
[01:01]  * BUGabundo re-checks
[01:01] <asac> thats still valid
[01:01] <Grantbow> kk
[01:01] <asac> Grantbow: use -security PPA
[01:01]  * Grantbow reads
[01:01] <asac> and all is good
[01:01] <asac> you can even keep its
[01:02] <asac> reed_: do you build with --enable-system-cairo?
[01:02] <reed_> asac: no
[01:02] <asac> i mean the local build you are running ;)
[01:02] <asac> hmm. wonder that you never noticed font problems ;)
[01:02] <reed_> )
[01:02] <reed_> ;)
[01:03] <asac> there is quite  severe problem afaict if you dont use --enable-system-cairo
[01:03] <asac> well relatively severe ;)
[01:03] <reed_> seems to work ok for me...
[01:03] <asac> as severe as font problems can be at all
[01:03] <asac> reed_: you can change the hint style in gnome appearence dialog and firefox will use that?
[01:04] <asac> otherwise the fonts probably look different than in other gnome apps
[01:04] <reed_> dunno, haven't tried that
[01:04] <asac> heh
[01:04] <asac> reed_: do the fonts look the same as the rest of the desktop at all?
[01:04] <reed_> I think I have them set differently
[01:04] <reed_> on purpose
[01:04] <Grantbow> asac: PPAs for LUG users is kind of messy, needing to add the key and all, but I'll teach them.
[01:04] <asac> reed_: the chrome fonts?
[01:04] <reed_> whatever the preferences allows me to set!
[01:05] <asac> Grantbow: the PPA is the right thing to do ... its also much safer than running -proposed
[01:06] <asac> its only mozilla security updates that get staged there
[01:06] <asac> with low risk of regressions ;)
[01:06] <asac> the idea was to push that directly to jaunty-security on friday
[01:07] <asac> but security team complained and even though i tried, we eneded up giving this a short break in -proposed
[01:07] <asac> complained == too many packaging changes i introducde
[01:07] <Grantbow> interesting - lots of users are clamoring for FF 3.5
[01:08] <asac> thats normal
[01:08] <asac> we provide various optoins
[01:08] <asac> and we had - looking ahead - firefox-3.5 in the jaunty archive universe
[01:09] <asac> once the packages are there they wont complain anymore and this slight delay will be forgotten ;)
[01:09] <BUGabundo> Grantbow: sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com KEYID
[01:10] <Grantbow> BUGabundo: yup, thanks
[01:10] <BUGabundo> Grantbow: thank fta. its his code LOL
[01:11] <BUGabundo> asac: the prob is *they* are expecting 3.5 to be default _after_ upgrade
[01:11] <BUGabundo> :D
[01:11] <asac> they will notice soon enough ;)
[01:11] <BUGabundo> I'm so tired replying to the same questions over and over
[01:11] <BUGabundo> and I bet you too
[01:12] <asac> not yet;)
[01:12] <asac> i usually dont answer :)
[01:12] <BUGabundo> btw karmic already has 3.5 as default?
[01:12] <BUGabundo> asac: ahahaha
[01:12] <asac> except here ;)
[01:12] <BUGabundo> now you can just point them to your blog
[01:12] <asac> yes thats the idea
[01:13] <BUGabundo> btw karmic already has 3.5 as default?
[01:13] <asac> no
[01:14] <asac> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-karmic-firefox-3.5
[01:14] <asac> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-karmic-browsers
[01:17] <BUGabundo> those are pleanty TODOs
[01:17] <BUGabundo> subbed
[01:19] <Grantbow> asac: so firefox does not use update-alternatives?
[01:21] <BUGabundo> it does
[01:22] <BUGabundo> but it won't change 3.5 to default
[01:22] <BUGabundo> it will remain as 3.0
[01:23] <Grantbow> hmm, I see it's used for other commands but not "firefox", so changing the default is still a matter of the sym link in /usr/bin?
[01:23] <asac> bug 380196
[01:23] <asac> wont fix
[01:24] <asac> Grantbow: changing the default is a matter of moving the link to the right position, yes.
[01:24] <Grantbow> very important for users to know, thanks for that.  I'll read up on it too.
[01:26] <asac> read my last comment now
[01:36]  * Grantbow nods
[01:42] <asac> Grantbow: yes
[01:42] <asac> oops
[01:42] <asac> ;)
[01:42]  * asac confused by scrollback
[01:42] <asac> its getting late
[01:43] <BUGabundo> asac: true
[01:43] <BUGabundo> I'm about to go to bed
[01:44] <BUGabundo> just trying to find a nice geek part message
[01:44] <BUGabundo> lol
[01:45]  * BUGabundo $off ; $echo You can't off me; $sudo off; $echo ahaha you trieeeddddddzzzzzzzz
[03:19] <rzr> http://linuxologist.com/linuxhumor/ubuntu-is-a-microsoft-product-now/
[10:55] <asac> ola
[11:00] <BUGabundo> ola
[11:00]  * BUGabundo to be cordial, I should have replied in german
[11:00] <BUGabundo> _Guntag_
[11:04] <eagles0513875> BUGabundo: hey
[11:04] <BUGabundo> that was fast
[11:04] <eagles0513875> heheh
[11:04] <BUGabundo> asac: eagles0513875 here has a broken card
[11:04] <eagles0513875> viva 10mbps cable connection lol
[11:05] <eagles0513875> not a broken card it works fine on nm on jaunty
[11:05] <BUGabundo> wicd not as user friendly as NM
[11:05] <eagles0513875> i know
[11:05] <BUGabundo> he wants to test NM 0.8
[11:05] <BUGabundo> will it help his case?
[11:05] <eagles0513875> but i think this is the regression that jaunty had where it couldnt connect to wpa
[11:05] <eagles0513875> my wifi connection is wpa2 mixed connection
[11:05] <BUGabundo> eagles0513875: this kind of broakage is usually driver (aka kernel), not much that NM can do/fix
[11:05] <BUGabundo> oh right
[11:06] <BUGabundo> your prob is encription
[11:06] <asac> dont think that 0.8 would reall yhelp
[11:06] <BUGabundo> not actual device suport
[11:06] <asac> if NM doesnt work it means that the driver sucks ;)
[11:06] <eagles0513875> would wicd help
[11:06] <asac> especially if wicd is working
[11:06] <eagles0513875> asac: it works fine in jaunty
[11:06] <asac> then its a regression ;)
[11:06] <asac> eagles0513875: what driver is it?
[11:06] <eagles0513875> its the oss reversed engineered b43-fwcutter
[11:06] <eagles0513875> for me the proprietary one doesnt work for me
[11:07] <BUGabundo> asac: what does wicd really do, to work in so many cases where NM doesn't ?
[11:07] <asac> yeah. those proprietary broadcom drivers are doomed to decay over time
[11:07] <eagles0513875> b43-fwcutter isnt propritary though
[11:07] <eagles0513875> !b43-fwcutter
[11:07] <asac> e.g. they worked well in old kernels, but they dont get better ;)
[11:07] <eagles0513875> !info b43-fwcutter
[11:07] <eagles0513875> thats what i use right there
[11:07] <asac> no. but it wrapps the binary
[11:07] <eagles0513875> meaning
[11:08] <asac> so that works?
[11:08] <eagles0513875> on jaunty but not on karmic
[11:08] <asac> ok
[11:08] <asac> maybe you accidentically cut out a newer firmware from broadcom=
[11:08] <asac> ?
[11:08] <asac> or are you 100% sure that you have the same firmware used on karmic vs. jaunty
[11:09] <eagles0513875> its saying its installed which seems to be 1:012-1 from main repo
[11:09] <asac> eagles0513875: thats not the firmware
[11:09] <eagles0513875> ohhhhh wait
[11:09] <eagles0513875> jaunty is a slightly older one then karmic
[11:09] <asac> eagles0513875: fwcutter is a tool ... it downloads a firmware from broadcom website
[11:09] <asac> and cuts out the ugly blob bits
[11:09] <eagles0513875> jaunty 1:011-5 and karmic has 012-1
[11:10] <asac> so it could be that fwcutter is broken or that the firmware downloaded changed
[11:10] <asac> could you please check that?
[11:11] <eagles0513875> so basically uninstall reinstall
[11:11] <asac> no
[11:12] <asac> figure out the version you downloaded from broadcom (not the ubuntu package)
[11:12] <asac> or download the firmware and install it on jaunty and karmic to check
[11:12] <asac> if that all doesnt help, also check whether you actually use the same driver
[11:12] <BUGabundo> asac: who is supporting BT in karmic?
[11:12] <asac> there are multiple b4xxx drivers in the kernel
[11:12] <BUGabundo> its even more broken then in jaunty
[11:13] <asac> so it might be that you now use a different
[11:13] <asac> BUGabundo: BT?
[11:13] <BUGabundo> can't even connect to devices, doesn't accept password
[11:13] <asac> bittorrent? bluetooth?
[11:13] <BUGabundo> asac: BlueTooth
[11:13] <BUGabundo> ahah right too many meaning
[11:13] <asac> BUGabundo: are you using bluez-gnome?
[11:13] <BUGabundo> applet freeses
[11:13] <BUGabundo> asac: I _think_ I'm using what ever karmic brings
[11:13] <BUGabundo> let me check
[11:13] <asac> BUGabundo: ok. remove bluez-gnome and install blueman
[11:14] <asac> restart system
[11:14] <asac> check that all works still
[11:14] <asac> then also remove blueman and install gnome-bluetooth
[11:14] <BUGabundo> ahah
[11:14] <asac> check that it works and compare to blueman
[11:14] <BUGabundo> come on... all 3?
[11:14] <asac> tell me what works better
[11:14] <eagles0513875> broadcom is pita
[11:14] <asac> ack
[11:14] <BUGabundo> too many reboots for me
[11:14] <eagles0513875> asac: seems like alot of linux wifi drivers are done and supported by http://linuxwireless.org/
[11:14] <asac> eagles0513875: if you can find your wifi card easily in your laptop, just buy a iwl4965 from ebay for 5 bucks ;)
[11:14] <BUGabundo> bluez:  Installed: 4.41-0ubuntu2
[11:15] <asac> and replace it
[11:15] <asac> ;)
[11:15] <asac> that saves you lots of issues
[11:15] <eagles0513875> i can i know the model and everything
[11:15] <BUGabundo> blueman:  Installed: (none)  Candidate: 1.10-2
[11:15] <eagles0513875> thing is this is an hp tablet so no pcmcia no nothing
[11:15] <BUGabundo> gnome-bluetooth:  Installed: 2.27.5-1ubuntu1
[11:15] <asac> eagles0513875: thats what i said. if you can find the wifi card inside
[11:15] <BUGabundo> asac: so I better remove all and just install ONE ?
[11:15] <eagles0513875> ahhhh my bad
[11:15] <asac> BUGabundo: yes
[11:16] <eagles0513875> i have one place i can ask is the linux-wireless irc channel
[11:16] <asac> eagles0513875: to find the card inside your chassis?
[11:16] <asac> eagles0513875: just open your laptop  ... usually its obvious ;)
[11:16] <eagles0513875> no to see if there are any patches or anything that is needed for the wifi to work
[11:16]  * asac does not encourage anyone to break his system ;)
[11:16]  * BUGabundo fires up synaptic
[11:16] <eagles0513875> asac: lspci also works its a bcm4311 reb2 wifi card
[11:16] <asac> eagles0513875: like i said. first check that you reall yuse the same firmware
[11:16] <asac> thats not the vresion you see in ubuntu
[11:17] <asac> its the version you find on broadcom website
[11:17] <eagles0513875> which they dont even have linux drivers for
[11:17] <eagles0513875> linuxwireless.org im guessing is in charge of any linux drivers for broadcom
[11:17] <asac> eagles0513875: do you understand what i am saying?
[11:17] <asac> eagles0513875: no they are not
[11:17] <asac> eagles0513875: broadcom is unsupported by linuxwireless
[11:17] <eagles0513875> im not able to find anything on the broadcom site
[11:18] <asac> eagles0513875: fwcutter downloads a file from broadcom site
[11:18] <asac> that one you need to compare
[11:18] <asac> with the one you installed in jaunty
[11:18]  * eagles0513875 wishes vmware server worked right now
[11:19] <micahg> I used the wl driver on the last broadcom laptop I had
[11:19] <BUGabundo> asac: libbluetooth3 pulls evolution, gnome-do etc! should I keep it?
[11:19] <asac> micahg: yeah. but wl doesnt work for all
[11:19] <micahg> I had to use ndiswrapper and the windows driver before that
[11:20] <asac> BUGabundo: i dont knwo
[11:20] <asac> BUGabundo: i had no problems eliminating blue-gnome
[11:20] <micahg> fwcutter never worked for me
[11:20] <eagles0513875> your the opposite of me micahg
[11:20] <eagles0513875> the proprietary doesnt work for me but fwcutter does
[11:20] <asac> micahg: if wl works, fwcutter is not supposed to work afaik
[11:21] <micahg> I don't have broadcom anymore
[11:21] <micahg> now I have atheros
[11:23] <BUGabundo> asac: ok all 3 meta packages removed
[11:23] <asac> eagles0513875: you said that wicd worked on karmic still?
[11:24] <BUGabundo> brb
[11:24] <BUGabundo> rebooting to test  bluetooth
[11:24] <eagles0513875> someone else was able to successfully use wicd not me
[11:25] <asac> ok
[11:25] <asac> i really think do this: a) check that the firmware downloaded is identical to the one you used in jaunty (thats downloaded from broadcom)
[11:25] <asac> b) if you are sure about that, check whether you actually use the same driver in januty vs. karmic
[11:26] <asac> there are a bunch of b4xxxx drivers
[11:26] <eagles0513875> ok will try that
[11:26] <eagles0513875> i need to restart my computer ill be back in a few cuz i need to get on vmware and that isnt working now
[11:26] <asac> c) if all is the same, check the committs that happened on the driver you are usin gin the upstrema kernel tree
[11:26] <asac> there probably shouldnt be that many
[11:26] <asac> so with some luck you can identify what caused this regression
[11:26] <eagles0513875> :)
[11:26] <asac> d) complain on linux-wireless
[11:27] <eagles0513875> i will :)
[11:27] <asac> but i think that they wont help you
[11:27] <asac> broadcom is a mess
[11:27] <eagles0513875> lol tell me bout it
[11:27] <eagles0513875> when i first started with edgy it was a nightmare
[11:27] <asac> e) open up your computer ... rip out this broadcom shit
[11:27] <eagles0513875> lol
[11:27] <asac> buy a good card on ebay
[11:27] <asac> for 5EUR
[11:27] <asac> and put that in
[11:27] <asac> (seriously
[11:27] <asac> )
[11:27] <eagles0513875> this laptop is still under warrenty though so i dont wanna void the warrenty
[11:28] <asac> i dont thin kit would void th warrenty ;)
[11:28] <eagles0513875> its hp they are a mess as well
[11:28] <asac> its just changing a component :)
[11:28] <eagles0513875> i couldnt use the manufacturers warrenty on a machine i bought in the states
[11:28] <asac> often you can just open the back panel and there is the card .. similar to a card in a desktop PC
[11:28] <asac> f you are out of luck its behind the laptop screen
[11:28] <asac> then youar elost ;)
[11:29] <asac> eagles0513875: send machine back and claim warrenty; say the broadcom card is broken :)
[11:30] <asac> seriously, everybody should cause work on the OEM side if they ship broadcom stuff
[11:30] <asac> even if its just complaining that its "broken" and they have to check it etc
[11:30] <eagles0513875> ya they replaced it with another broadcom
[11:30] <asac> OEMs buy into broadcom because they are so cheap ... so raise maintenance cost and they will pick atheros ;)
[11:31] <asac> eagles0513875: always cause work on their side explicitly mentioning broadcom :) ... maybe that helps at some point ;)
[11:31] <eagles0513875> i hear atheros is a nightmare though as well
[11:31] <asac> if they replace with broadcom say that its stil lbroekn
[11:31] <BUGabundo> asac: back
[11:31] <asac> eagles0513875: atheros is at least on their way tobecome one of the good guys
[11:31] <BUGabundo> asac: what the 1st metapack you want me to test?
[11:31] <eagles0513875> thats good to hear
[11:31] <asac> at least they work together with linux folks on real linux drivers
[11:32] <asac> in the mainline tree
[11:32] <asac> and dont hide behind: "its illegal to ship open source drivers in the US"
[11:32] <eagles0513875> asac: what does it mean when wlan0: ap denied association code=13
[11:32] <asac> can mean anything
[11:32] <asac> is that driver message or wpa_supplicant?
[11:33] <asac> did you try to connect to a open AP? (e.g. no WPA?)
[11:33] <eagles0513875> no i havent
[11:33] <eagles0513875> the message is showing up in dmesg
[11:33] <eagles0513875> there is another one in dmesg disassociating by local choice reason 3
[11:33] <BUGabundo> asac: what the 1st bluetooth metapack you want me to test?
[11:35] <asac> BUGabundo: blueman or gnome-bluetooth
[11:35] <asac> you can choose
[11:35] <BUGabundo> aah
[11:35] <BUGabundo> blueman it is
[11:36] <eagles0513875> asac: found a shell installation script that seems to get wifi driver from openwrt.org
[11:36] <BUGabundo> blueman pools bluez?
[11:36] <asac> BUGabundo: yes. thats ok
[11:36] <asac> just not bluez-gnome
[11:37] <BUGabundo> asac: $ dpkg -l | grep blue | pastebinit  http://paste.ubuntu.com/210282/
[11:37] <BUGabundo> asac: is that enough/ok ?
[11:37] <BUGabundo> reboot again ?
[11:38] <asac> BUGabundo: maybe .... usually you dont need to reboot
[11:39] <asac> restart bluetooth ... and re-login
[11:39] <BUGabundo> ok
[11:39] <BUGabundo> restart bt and nothing
[11:39] <BUGabundo> trying session now
[11:44] <BUGabundo> asac: back
[11:44] <BUGabundo> ok I see the applet
[11:44] <BUGabundo> I can go to settings
[11:44] <BUGabundo> but it hasn't any other options enabled
[11:44] <BUGabundo> they are greyed out
[11:45] <BUGabundo> device, adaptors, send, receive, nothing
[11:46] <BUGabundo> asac: should I try the next on the list, or am I missing a package?
[11:47] <BUGabundo> OT, asac NM 0.8 autoconnect is stupid! won't set proper DNSs or something, so I always have to disconnect and manually connect for it to work
[11:49]  * BUGabundo feels ignored
[11:51] <BUGabundo> ok no reply moving on. gnome-bluetooth
[11:53] <eagles0513875> im here BUGabundo
[11:54] <asac> did get some coffee
[11:54] <BUGabundo> ahh
[11:54] <BUGabundo> I was about to ask eagles0513875 if you said that
[11:54] <asac> BUGabundo: settings? couldnt you open the dialog where you can scan etc?
[11:54] <BUGabundo> ok gnome-bluetooth installed
[11:54] <BUGabundo> asac: err too late?!
[11:55] <BUGabundo> only to button available on the applet
[11:55] <BUGabundo> turn on/off and preferences
[11:55] <asac> BUGabundo: yes. you have to turn on
[11:55] <BUGabundo> all other were greyd out
[11:55] <asac> ;)
[11:55] <BUGabundo> duh
[11:55] <BUGabundo> it was ON
[11:55] <BUGabundo> I'm blond, not stupid
[11:55] <asac> BUGabundo: but you right clicked
[11:55] <asac> BUGabundo: have you tried to left clikc?
[11:55] <BUGabundo> yes yes
[11:55] <asac> BUGabundo: you have to left click
[11:55] <BUGabundo> both
[11:56] <asac> and there you get the dialog
[11:56] <asac> did you see that?
[11:56] <BUGabundo> no dialgog here
[11:56] <BUGabundo> let me revert the instal
[11:56] <asac> well
[11:56] <asac> that happens
[11:56] <BUGabundo> darn you and your coffe
[11:56] <asac> it open dialog called "bluetooth devices"
[11:56] <asac> there you first have to setup/bond devices
[11:56] <asac> before you get options available via right click
[11:57] <BUGabundo> reverted to blueman
[11:57] <BUGabundo> restart BT
[11:57] <BUGabundo> no applet
[11:57] <BUGabundo> reboot?
[11:57] <asac> BUGabundo: http://people.ubuntu.com/~asac/tmp/Screenshot-Bluetooth%20Devices.png
[11:57] <BUGabundo> or manually start it?
[11:57] <asac> let me check
[11:57] <asac> yes. start blueman-applet from a command line
[11:57] <BUGabundo> Bluez daemon is not running, blueman-manager cannot continue
[11:57] <BUGabundo> lolol
[11:58] <asac> BUGabundo: sudo /etc/init.d/bluetooth restart
[11:58] <BUGabundo> $ blueman-applet
[11:58] <BUGabundo> Loading configuration plugins
[11:58] <BUGabundo> there is an instance already running
[11:58] <asac> ps -eaf | grep bluetoothd
[11:58] <asac> root      3488     1  0 Jul04 ?        00:00:00 /usr/sbin/bluetoothd
[11:58] <BUGabundo> ahh there it is
[11:58] <BUGabundo> I already restart it, but took a 2nd try
[11:58] <BUGabundo> ok left click now opens somehting
[11:58] <asac> yeah. bluetoothd is sometimes not deterministic
[11:58]  * BUGabundo checks phone bt is on
[11:59] <asac> BUGabundo: so do you get the dialog?
[11:59] <BUGabundo> yep
[11:59] <asac> and there you have to setup your device first
[11:59] <asac> good
[11:59] <BUGabundo> and the right click also as more options now
[11:59] <BUGabundo> trying to browse the phone
[12:00] <BUGabundo> err
[12:00] <BUGabundo> nautilus opens and closes
[12:00] <BUGabundo> no success
[12:00] <asac> ps -eaf | grep obex
[12:00] <asac> asac      4398     1  0 Jul04 ?        00:00:00 /usr/bin/obex-data-server --no-daemon
[12:00] <asac> do you have that running at all?
[12:00] <BUGabundo> $ ps -eaf | grep obex
[12:00] <BUGabundo> 1000     21792     1  0 11:59 ?        00:00:00 /usr/lib/gvfs/gvfsd-obexftp --spawner :1.5 /org/gtk/gvfs/exec_spaw/3
[12:00] <BUGabundo> 1000     26344     1  0 11:41 ?        00:00:02 /usr/bin/obex-data-server --no-daemon
[12:00] <asac> k
[12:00] <BUGabundo> I have the mount icon with the phone
[12:00] <BUGabundo> I just can't open nautilus on it
[12:01] <asac> what do you mean by "mount symbol" ?
[12:01] <BUGabundo> I have this mount applet
[12:01] <asac> BUGabundo: so in the dialog do you see that you are currently connected to the phne?
[12:01] <BUGabundo> same thing as desktop icons
[12:01] <BUGabundo> but easier to reach
[12:01] <BUGabundo> yep
[12:01] <asac> ok
[12:01] <BUGabundo> its connected and *mounted*
[12:01] <asac> BUGabundo: ok. you can also try to use 3g ;)?
[12:01] <BUGabundo> trying dolphin file explorer
[12:02] <asac> -> serial ports -> dial up service
[12:02] <BUGabundo> 3G? like what?
[12:02] <BUGabundo> access from phone or share from phone?
[12:02] <asac> that will only work with 0.7.1 though
[12:02] <asac> BUGabundo: right click on phone in dialog
[12:02] <asac> first menu entry is
[12:02] <asac> serial ports for me
[12:02] <asac> there is dialup service
[12:02] <BUGabundo> I see both
[12:02] <asac> if i click on that i get a 3g device in network-manager 0.7.1 (not 0.8 i would think, but havent tried)
[12:03] <asac> otoh, i think the latest mm is now using udev
[12:03] <asac> so maybe 0.8 works
[12:03] <BUGabundo> so now what?
[12:03] <BUGabundo> dialog or serial?
[12:03] <BUGabundo> and what exactly do you want?
[12:03] <_eagles0513875_> humm
[12:04] <BUGabundo> me to access web from the phone via my laptop (on 3g already)
[12:04] <asac> BUGabundo: in the dialog if you right click on your phone
[12:04] <eagles0513875> wtf
[12:04] <BUGabundo> or access net using phone as modem
[12:04] <eagles0513875> brb
[12:04] <asac> i can select "serial ports" -> "dial up"
[12:04] <asac> does that work for you?
[12:04] <BUGabundo> "Success"
[12:04] <BUGabundo> that's what it shows
[12:04] <BUGabundo> no idea what it did
[12:04] <asac> BUGabundo: it creates the rfcomm device
[12:05] <BUGabundo> I see a rfccomm
[12:05] <asac> check ls /dev/rfcomm
[12:05] <BUGabundo> yep
[12:05] <BUGabundo> $  ls /dev/rfcomm
[12:05] <BUGabundo> ls: cannot access /dev/rfcomm: No such file or directory
[12:05] <asac> BUGabundo: did it show up in NM=?
[12:05] <asac> BUGabundo: yeah its rfcomm1
[12:05] <asac> or something
[12:05] <BUGabundo> not in NM
[12:05] <asac> BUGabundo: but you run 0.8, right?
[12:05] <BUGabundo> $ ls /dev/rfcomm0
[12:05] <BUGabundo> crw-rw---- 1 root dialout 216, 0 2009-07-05 12:04 /dev/rfcomm0
[12:05] <asac> yeah
[12:05] <asac> looks good
[12:05] <asac> usulaly it would now just work in NM
[12:05] <asac> which is a great plus of blueman
[12:06] <BUGabundo> network-manager:  Installed: 0.8~a~git.20090702t164632.9c8e600-0ubuntu1~nmt1
[12:06] <asac> right
[12:06] <asac> BUGabundo: if you like 3g over bluetooth you can try later again
[12:06] <asac> now check gnome-bluetooth
[12:06] <BUGabundo> ahah naaaa
[12:06] <BUGabundo> over priced here
[12:06] <asac> i doubt that the nautilus experience will be better
[12:06] <asac> BUGabundo: you can put your 3g card in your phone ;)=
[12:06] <BUGabundo> I can't see the mount point any where
[12:06] <BUGabundo> its not on Mount, not on .gfvs
[12:06] <BUGabundo> :(
[12:06] <BUGabundo> can't browse it
[12:06] <asac> BUGabundo: well. maybe it got disconnected
[12:07] <BUGabundo> let me remount it
[12:07] <asac> works for me ;)
[12:07] <asac> i just click on "browse for file ..."
[12:07] <BUGabundo> same thing
[12:07] <asac> and it open nautilus on phone
[12:07] <BUGabundo> nautilus opens then closes
[12:07] <asac> BUGabundo: did you properly bond your device?
[12:08] <asac> let me remove the phone from blueman and see what happens on fresh setup
[12:08] <asac> so now i an empty blueman dialog
[12:08] <asac> i hit "search ..."
[12:08] <BUGabundo> is there a wrong way to do it ? :)
[12:08] <asac> BUGabundo: not sure. if you didnt create it through search it might still have old config struff from bluez-gnome maybe
[12:09] <BUGabundo> removing device from bt , and pc from phone
[12:09] <BUGabundo> making new ones now
[12:10] <asac> BUGabundo: i think you only need to remove from bt
[12:10] <BUGabundo> new bond with 55555 pin works
[12:10] <BUGabundo> tried to browse, got asked on phone, accepted, and nautilus closed again
[12:10] <asac> when connected it looks like this: http://people.ubuntu.com/~asac/tmp/Screenshot-Bluetooth%20Devices-1.png
[12:11] <asac> BUGabundo: hmm
[12:11] <asac> BUGabundo: mount |pastebinit ;)
[12:12] <asac>  back in 3 minutes
[12:13] <BUGabundo> asac: http://files.getdropbox.com/u/112892/screenshot_001.png
[12:13] <BUGabundo> $ mount | pastebinit http://paste.ubuntu.com/210298/
[12:14] <e-jat> both of u use NM 0.8?
[12:14] <BUGabundo> I do
[12:14] <BUGabundo> not sure about asac
[12:14] <BUGabundo> why e-jat ?
[12:15] <e-jat> just asking :)
[12:15] <BUGabundo> e-jat: just pre-testing *before* asac puts it in the repo and breaks it to everyone
[12:15] <e-jat> i manage to use bluetooth with my Wmobile .. but using cli ..
[12:15] <e-jat> BUGabundo: ic ..
[12:16] <BUGabundo> cli?
[12:16] <e-jat> cmd line
[12:16] <BUGabundo> this is for Human Beings!
[12:16] <BUGabundo> I no what cli is LOL
[12:16] <e-jat> BUGabundo: yeap ..
[12:16] <BUGabundo> so _unfortunately_ we need click and forget
[12:16]  * BUGabundo hates mice. not the furry ones 
[12:16] <e-jat> :)
[12:17] <e-jat> im in kubuntu nowdays .. maybe can login to my gnome n test it :)
[12:17] <BUGabundo> so feris runing karmic?
[12:17] <e-jat> yeap
[12:18] <asac> i use 0.8 too atm
[12:18] <asac> works good
[12:18] <asac> 0.8 pre-alpha ;)
[12:19] <asac> with modemmanager :)
[12:19] <asac> BUGabundo: so accessing devices still doesnt work for you?
[12:19] <asac> browsing files i mean
[12:19] <asac> sounds like its really more a gvfs problem
[12:19] <asac> than bluetooth
[12:19] <e-jat> modemmanager? cool ..
[12:20] <asac> e-jat: https://edge.launchpad.net/~modemmanager/+archive/ppa
[12:20] <asac> -> NM 0.7.1 + Modemmanager
[12:20] <BUGabundo> eheh pre-alpha LOL
[12:20] <asac> https://edge.launchpad.net/~network-manager/+archive/trunk
[12:20] <e-jat> hope to get pand manager too
[12:20] <asac> -> NM 0.8 + modemmanager
[12:20] <asac> e-jat: what do you use pan for?
[12:20] <BUGabundo> pand?
[12:20] <asac> e-jat: its supported in trunk
[12:20] <asac> afaik
[12:20] <asac> at least we have general bluetooth support there now
[12:21] <BUGabundo> pand?
[12:21] <e-jat> pand with my mobile
[12:21] <BUGabundo> asac: ill talk to seb tomorrow about gfvs then
[12:21] <asac> e-jat: tell me what use case you are going to
[12:21] <BUGabundo> shall I try gnome-bt now ?
[12:21] <asac> BUGabundo: yeah. please check gnome-bluetooth just to be sure
[12:21] <e-jat> BUGabundo: The pand PAN daemon allows your computer to connect to ethernet networks using Bluetooth.
[12:21] <asac> BUGabundo: also be sure you upgraded everything
[12:22] <asac> e-jat: i just wonder why you want to do that
[12:22] <e-jat> asac: ? can understand it ..
[12:22] <asac> whats the use case you are filling
[12:22] <e-jat> cant
[12:22] <asac> understood my question now?
[12:23] <e-jat> owh ..
[12:23] <e-jat> asac: i using it with my ISC in windows mobile
[12:23] <BUGabundo> http://valid.tjp.hu/tjpzoom/ OMFG
[12:23] <BUGabundo> JS zoom LOL
[12:23] <e-jat> is there any better way to get connected with it ..
[12:23] <e-jat> love to hear that
[12:24] <BUGabundo> asac: entire system update (behing gdm and rpm)
[12:25] <BUGabundo> installed gnome-bt
[12:25] <e-jat> asac: any other way to make it work with windows Internet Connection Sharing (ICS) ?
[12:25] <BUGabundo> e-jat: well blueman seems to do it!
[12:25] <BUGabundo> I has intergration with NM or standalone
[12:26] <BUGabundo> asac: $ sudo /etc/init.d/bluetooth restart \n sudo: /etc/init.d/bluetooth: command not found
[12:26] <asac> e-jat: ok. so your computer gets an ip from your buetooth device?
[12:26] <e-jat> BUGabundo: will try the bleuman
[12:26] <asac> and your bluetooth device goes online for you?
[12:26] <asac> BUGabundo: you removed bluez?
[12:26] <e-jat> get ip
[12:26] <BUGabundo> asac: yep
[12:27] <asac> BUGabundo: thats worng ;)
[12:27] <asac> without bluez nothing will work
[12:27] <BUGabundo> asac: LOL
[12:27] <asac> bluez has kind of a monopoly
[12:27] <e-jat> why is blueman removing gnome-bluetooth ?
[12:27] <asac> so we always will have bluez
[12:27] <BUGabundo> then gnome-bt *should* depend on it
[12:27] <asac> what is interchangableis the applet
[12:27] <asac> and the obexd
[12:27] <asac> BUGabundo: you are right
[12:27] <asac> BUGabundo: thats a packaging bug for sure
[12:27] <BUGabundo> wanna me to file ?
[12:27] <asac> e-jat: its a drop in replacement
[12:28] <asac> e-jat: using same file names
[12:28] <BUGabundo> I'm quite low on my bug quota this cycle
[12:28] <e-jat> ic
[12:28] <asac> e-jat: also there is not much sense havin both running
[12:28] <BUGabundo> asac: wanna me to file it, or will I take care of it??
[12:28] <asac> BUGabundo: yes. please file. and assign to me
[12:28] <e-jat> which one better ? gnome-bluetooth or blueman?
[12:29] <asac> e-jat: thats still open
[12:29] <asac> e-jat: we will decide soon what we will use in karmic
[12:29] <asac> e-jat: your input cn influence this
[12:30] <asac> e.g. i have to decide soonish ... now i am getting first impressions ;)
[12:30] <asac> bleuman is python ... gnome-bt is C
[12:30] <asac> also blueman seems to be a bit ahead feature wise
[12:30] <asac> but gnome-bt is a gnome project which gives regular releases and good translations
[12:30] <BUGabundo> asac: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/395725
[12:30] <asac> and also its a pretty new fork of gnome-bluez so there is hope they catch up
[12:30] <asac> BUGabundo: thanks
[12:31] <BUGabundo> asac: bluez installed
[12:31] <e-jat> owh really ..
[12:31] <BUGabundo> bt restarted
[12:32] <BUGabundo> applet there
[12:32] <asac> also i try to find out which upstream is more responsive
[12:32] <BUGabundo> left click is hanging a bit
[12:32] <e-jat> hmm will try the blueman when i got a time
[12:32] <asac> so far both are in state "unresponsive" ;)
[12:32] <asac> e-jat: the ui is better imo ;)
[12:32] <asac> http://people.ubuntu.com/~asac/tmp/Screenshot-Bluetooth%20Devices-1.png
[12:33] <BUGabundo> asac: hummm I smell reboot
[12:33] <asac> BUGabundo: thats usually not a solution
[12:33] <asac> ;)
[12:33] <asac> let me try gnome-bluetooth
[12:33] <asac> to see whats up ;)
[12:33] <e-jat> but i prefer to use usb cable (rndis) with my phone
[12:33] <BUGabundo> then gnome.bt is toast on my side
[12:33] <e-jat> the blueman UI ?
[12:33] <BUGabundo> e-jat: I prefer no wires
[12:34] <e-jat> BUGabundo: but sometime i use bt
[12:34] <e-jat> for stability
[12:34] <e-jat> asac: owh .. the screenshot is blueman ?
[12:34] <BUGabundo> errr
[12:34] <e-jat> ic
[12:34] <BUGabundo> wth
[12:35] <BUGabundo> bluetooth-applet
[12:35] <BUGabundo> is another applet
[12:35]  * BUGabundo is confused
[12:35] <BUGabundo> now have *two* applets
[12:35] <asac> BUGabundo: thats what you need to start
[12:35] <asac> BUGabundo: what was the first you started?
[12:35] <BUGabundo> one does nothing the other does very little
[12:36] <asac> ps -eaf | grep blue.*applet
[12:36] <asac> BUGabundo: ?
[12:36] <BUGabundo> asac: no. I had the blueman applet, that appeard on it self after gnome.bt install
[12:36] <BUGabundo> $ ps -eaf | grep blue.*applet
[12:36] <BUGabundo> 1000     19962 14549  0 12:34 pts/1    00:00:00 bluetooth-applet
[12:36] <BUGabundo> 1000     26181 25998  0 11:41 ?        00:00:11 /usr/bin/python /usr/bin/blueman-applet
[12:36] <asac> kill 26181
[12:36] <BUGabundo> need to kill that sucker
[12:36] <asac> kill 19962
[12:36] <asac> then start bluetooth-applet again
[12:36] <asac> having two applets fighting over bluetoothd isnt good ,)
[12:37] <BUGabundo> ahhh much better
[12:37] <BUGabundo> should it have been removed when uninstled?
[12:37] <BUGabundo> or was it stuck in memory running?
[12:38]  * BUGabundo is getting a bunch of new followers on identica... poor things! don't know where they are entering!!
[12:38] <asac> BUGabundo: you didnt stop it after uninstalling
[12:38] <asac> thats ok
[12:39] <e-jat> BUGabundo: for u .. which one better ? gnome-bt or blueman ?
[12:39] <asac> i dont want to kill stuff in postrm scripts of packages
[12:39] <BUGabundo> trying to connect to phone
[12:39] <asac> BUGabundo: usually user should be asked to re-login (reboot)
[12:39] <BUGabundo> e-jat: so far blueman is prettier
[12:39] <BUGabundo> asac: it failsto connect, and shows "disconecting"
[12:39] <asac> yeah
[12:39] <asac> so its not much better ;)
[12:40] <BUGabundo> let me bond again
[12:40] <e-jat> prettier ?
[12:40] <asac> yeah
[12:40] <e-jat> cool .
[12:40] <BUGabundo> ahh right... I remember there's a bug here
[12:40] <asac> more beautiful ;)
[12:40] <BUGabundo> I set it to use MANUAL pin
[12:40] <BUGabundo> and it generates one
[12:40] <e-jat> let me relogin into gnome .. then i can try it ..
[12:40] <e-jat> brb
[12:41] <BUGabundo> humm asac Seatch is not finding anyting now!
[12:42] <BUGabundo> ok enough of this
[12:42] <asac> BUGabundo: in gnome-bluetooth?
[12:42] <asac> haha
[12:42] <BUGabundo> asac: yeah
[12:42] <BUGabundo> hey ikonia
[12:42] <ikonia> hello there
[12:42] <BUGabundo> asac: purging and testing next one
[12:42] <BUGabundo> ikonia: what brings you by?
[12:42] <asac> BUGabundo: thought you already try gnome-bluetooth
[12:42] <asac> what is next?
[12:42] <BUGabundo> bluez?
[12:42] <ikonia> BUGabundo: information seeking
[12:43] <BUGabundo> ikonia: 42!
[12:43] <ikonia> thank you
[12:43] <ikonia> problem solved
[12:43] <BUGabundo> ahahh
[12:44] <BUGabundo> asac: humm have to go
[12:44] <BUGabundo> time to feed the grampa
[12:44] <BUGabundo> ping me latter to test bluez
[12:44] <e-jat> BUGabundo: k ..
[12:44] <e-jat> trying the blueman now ..
[12:44] <e-jat> installing it .. wish me luck :)
[12:44] <BUGabundo> e-jat: remove all others before
[12:45] <asac> e-jat: you need to re-login again after install
[12:45] <BUGabundo> and you may need to reboot
[12:45] <BUGabundo> I'm off
[12:45] <e-jat> which one ?
[12:45] <BUGabundo> ALL
[12:45] <e-jat> reboot too ?
[12:45] <e-jat> cannot relogin ?
[12:46] <e-jat> asac: or i shall remove gnome-bluetooth only ?
[12:51] <asac> huh?
[12:55] <asac> e-jat: huh?
[12:55] <asac> ;)
[12:55] <asac> whats the problem?
[12:55] <e-jat> just reconnect :)
[12:55] <e-jat> still dloading the blueman dependecies ..
[12:56] <e-jat> i mean .. what should i remove ..
[12:56] <e-jat> is it enough just removing gnome-bluetooth ?
[12:56] <e-jat> then relogin ?
[12:57] <asac> e-jat: gnome-bluetooth gets automatically removed if you install blueman. so install blueman and then re-login
[12:57] <asac> thats enough usually
[12:57] <e-jat> yeah .. it remove auto
[13:01] <e-jat> im wondering kbluetooth4 can do like blueman can do :)
[13:01] <eagles0513875> asac
[13:02] <eagles0513875> drivers for b43-fwcutter they pulling the same version on jaunty and karmic the regression is in the network manager
[13:02] <eagles0513875> will continue working to fix this later
[13:08] <e-jat> asac: blueman r0x
[13:08] <e-jat> sure i will vote for blueman :)
[13:09] <e-jat> work flawlessly with wm6.1
[13:16] <asac> ejat: wm6.1?
[13:16] <asac> windows mobile?
[13:35] <BUGabundo> back
[13:35] <BUGabundo> asac: retested gnome-bt after a reboot
[13:35] <BUGabundo> seems there where some popunders blocking it
[13:36] <BUGabundo> popunder are as evil as popups (that steal your focus)
[13:36] <BUGabundo> but I sill fail to get it to conect to my phone
[13:36] <BUGabundo> there's 'bluetooth' package, but it doesn't bundle an applet
[13:37] <BUGabundo> asac: http://paste.ubuntu.com/210331/
[13:37] <BUGabundo> traces from gnome-bt
[13:41] <asac> yeah
[13:41] <asac> thanks
[13:42] <asac> i have to talk to gnome-bluetooth folks really
[13:42] <asac> blueman is for now the better
[13:43] <BUGabundo> asac: so its up to one of those too?
[13:44] <BUGabundo> so whats 'bluetooth' package
[13:45] <BUGabundo> s/too/two/
[13:56] <eagles0513875> asac: is there newere plasma widget for nm floating around in a ppa
[13:58] <asac> eagles0513875: i dont care much about kde
[13:58] <asac> (unfortunately dont have the time)
[13:58] <eagles0513875> ok
[13:58] <asac> they usually lack behind
[13:58] <asac> best is to run nm-applet i would think
[13:59] <asac> eagles0513875: you can see ppas that provide builds of a package on the main page now
[13:59] <eagles0513875> didnt know that :)
[13:59] <eagles0513875> thanks for the heads up
[13:59] <asac> https://edge.launchpad.net/ubuntu/+source/network-manager
[13:59] <asac> Other versions of 'network-manager' in untrusted archives.
[14:00] <asac> https://edge.launchpad.net/ubuntu/+source/plasma-widget-network-manager
[14:00] <asac> but doesnt look like
[14:00] <asac> karmic seems to be pretty fresh
[14:00] <eagles0513875> hummm ok
[14:01] <eagles0513875> might have to pull from svn trunk the nm
[14:01] <asac> eagles0513875: try that
[14:01] <eagles0513875> ill wry about  that later
[14:01] <asac> if its better let me know
[14:01] <eagles0513875> ok
[14:01] <asac> i can poke some people to update it then
[14:03]  * BUGabundo means kubuntu ninjas :)
[14:05] <e-jat> BUGabundo: blueman r0x :)
[14:05] <e-jat> no more cli needed
[14:05] <e-jat> huhu
[14:05] <BUGabundo> LOLOL
[14:06] <BUGabundo> I'm still waiting for asac to enlainthmen me
[14:06] <asac> e-jat: so pan works?
[14:06] <BUGabundo> so whats 'bluetooth' package
[14:06] <asac> sorry i have to run .... enjoying sunday afternoon
[14:06] <asac> bb in the evening
[14:06] <e-jat> asac: yeah
[14:06] <e-jat> ok asac me too gtg ..
[14:06] <asac> e-jat: what did you push? does it work through NM?
[14:06] <asac> or directly from blueman?
[14:06] <BUGabundo> leaving me alone ? : (
[14:06] <asac> yeah ;)
[14:07] <asac> BUGabundo: you could do some bug triage ;)
[14:07] <e-jat> asac: direct from blueman
[14:07] <BUGabundo> :)
[14:07] <asac> e-jat: ok. can you make screenshots of how you did it?
[14:07] <e-jat> network access point
[14:07] <asac> i am trying to get some kind of post up on what you can do with blueman
[14:07] <asac> like screenshots for a few use cases
[14:10] <e-jat> im uploading it ..
[14:13] <e-jat> asac: http://imagebin.ca/view/3i6T4Pol.html
[14:14] <BUGabundo> asac: gnome-phone-manager depends on gnome-bt huauahauahauhauahauaahauh
[14:14] <BUGabundo> I miss it to send sms's (when ever it works)
[14:15] <e-jat> then .. from ICS use bluetooth pan
[14:23] <e-jat> sorry .. change back to my default session :)
[14:24] <e-jat> asac: u got the screenshot right ?
[14:24] <BUGabundo> e-jat: he is no longer here
[14:24] <e-jat> :( k ..
[14:26] <BUGabundo> e-jat: He _will be back_
[14:26] <e-jat> im also gtg ..
[14:27] <e-jat> BUGabundo: u receive the screenshot url right?
[14:27]  * BUGabundo checking
[14:27] <BUGabundo> yep
[14:27] <BUGabundo> its there
[14:27] <e-jat> [Sun Jul 5 2009] [21:13:57] <e-jat> asac: http://imagebin.ca/view/3i6T4Pol.html
[14:27] <e-jat> c00l .. now no more cli for me @ n00b
[18:49] <fta> asac, https://edge.launchpad.net/~huangjiahua/+archive/hiweed-pkg ?
[18:49] <BUGabundo> lol
[18:50] <BUGabundo> more copies?
[18:50] <BUGabundo> or ppl complying from mozilla source?
[18:58] <fta> it's obviously a fork from our packages
[21:37] <asac> already saw the pango build
[21:37] <asac> not sure whats that about
[21:39] <fta> tb3 still broken, you really need to receive the logs again
[21:39] <asac> yeah
[21:53] <fta> firefox-3.5                      10425   0.91%      1458    2770    6185      12
[21:53] <fta> chromium-browser                  6973   0.61%       503    2784    3685       1
[21:54] <BUGabundo> hey fta
[21:54] <BUGabundo> is there a way for me to keep 3.6 from daily but 3.5 from archive?
[21:57] <fta> BUGabundo, http://www.debian.org/doc/manuals/apt-howto/ch-apt-get.en.html#s-pin
[21:58] <BUGabundo> right I know about pining
[21:58] <BUGabundo> but that won't allow it to be upgraded either
[22:04] <fta> it will, pin on origin
[22:04] <BUGabundo> ahhhh
[22:04] <BUGabundo> that's what I want then
[23:15] <fta> BUGabundo, did it work?
[23:15] <BUGabundo> still reading
[23:15] <BUGabundo> too much for me
[23:16] <BUGabundo> :)
[23:16] <BUGabundo>    An example:        Package: *      Pin: release v=2.2*,a=stable,c=main,o=Debian,l=Debian      Pin-Priority: 1001
[23:16] <fta> Package: *
[23:16] <fta> Pin: release o=LP-PPA-ubuntu-mozilla-daily
[23:16] <fta> Pin-Priority: 101
[23:16] <fta> you'll need to downgrade 1st
[23:18] <BUGabundo> in this case package: firefox-3.5
[23:18] <BUGabundo> and release o=universe
[23:18] <fta> didn't work for me, try
[23:31] <asac> libnl cache manager is really buggy. enough for today on that ;)
[23:36] <fta> asac, could you retry o3d please?
[23:41] <asac> fta: on 64-bit?
[23:42] <fta> both, if you can
[23:43] <asac> insalling on 64-bit
[23:44] <asac> wil check in 10 minutes or so when movin back inside
[23:44] <fta> what video card/chipset do you have?
[23:47] <asac> We are terribly sorry but it appears your graphics card is not able to run o3d. We are working on a solution.
[23:47] <asac> Click Here to go the O3D website
[23:47] <fta> intel?
[23:47] <asac>     File name: npwrapper.libnpo3dautoplugin.so
[23:47] <asac>     O3D Plugin version:0.1.40.0
[23:47] <asac> no thats ati
[23:47] <asac> intel would probabl ywork;)
[23:48] <asac> 05:00.0 VGA compatible controller: ATI Technologies Inc R580 [Radeon X1900
[23:48] <asac> hmm. no registered suffixes
[23:48] <asac> for the plugin
[23:48] <fta> doesn't work on my GM965
[23:49] <fta> registered suffixes? what is that?
[23:49] <asac> fta: check about:plugins
[23:49] <asac> there is an empty field
[23:49] <asac> suffixes means: "file extensions"
[23:49] <asac> like you want to handle .o3d files
[23:49] <fta> doesn't matter
[23:49] <asac> of course it doesnt matter
[23:49] <asac> if mime type is sent ;)
[23:50] <asac> i just wanted to point out that there is no suffix ;)=
[23:50] <asac> but besides from my graphics card suckin badly
[23:50] <asac> it seems to cause no problems
[23:50] <asac> ;)
[23:50] <micahg> asac: can you look at bug 395167
[23:52] <fta> i thing the o3d files are served as <object>s wrapped in javascript, or something like that
[23:53] <asac> micahg: i will think about what to best answer ;)
[23:53] <asac> ill reply tomorrow (so kick me if i forget ;))
[23:53] <micahg> ok, I was thinking to move to hardy-backports before bdmurray added the tag
[23:54] <asac> yeah. needs-packaging sounds wrong
[23:54] <asac> if you wanted to discuss the tag, then yeah. its backports rather
[23:54] <micahg> maybe I should ask him
[23:54] <asac> otoh, it seems the user wants it in hardy-updates or something
[23:54] <asac> which is definitly won't fix
[23:55] <asac> however, i want to provide hardy users with a good location besides from -backports which some users find too risky
[23:55] <micahg> well, the problem is that it's a new package for hardy
[23:55] <micahg> but couldn't the security ppa do it?
[23:56] <asac> the security ppa is not a place to put something you dont no where to put
[23:56] <asac> its a strict staging area for what will go in the releases
[23:56] <micahg> well, everyone else is getting updates there
[23:56] <asac> (usually into -security)
[23:56] <asac> micahg: they get it there because we stage firefox-3.5 there
[23:56] <micahg> can we have a generic ppa for mozilla?
[23:56] <asac> we have firefox-3.5 in jaunty
[23:56] <micahg> tue
[23:56] <micahg> true
[23:56] <asac> now we want to roll and update... so we put it into security ppa
[23:57] <asac> micahg: we can. but we alreawd have a bunch and we are currently undergoing some thinking about how to best organize all the PPAs we require ;)
[23:57] <micahg> see if backports provides the initial package, then the security ppa can provide updates, no?
[23:57] <asac> no
[23:57] <asac> -backports is not part of the release
[23:57] <asac> -security ppa is strictly for updates that will eventually end up in -security
[23:58] <asac> this time its a bit of an exception, because security team said we should push the build through -proposed
[23:58] <asac> but it was intended for -security ;)
[23:58] <micahg> ok
[23:58] <asac> micahg: we have -daily currently. we wanted to add -milestones ... and maybe -backports/-releases
[23:58] <asac> ppa
[23:59] <micahg> maybe it would be better to just have them all under the ~ubuntu-mozilla team?
[23:59] <micahg> instead of a separate team for eacg
[23:59] <micahg> each
[23:59] <asac> yeah thats one of the points
[23:59] <asac> the separte team approach was started when there was no ability to setup more than one ppa
[23:59] <asac> for a team