[00:00] I would report it, but apport doesn't like it :( [00:01] BUGabundo: what do you mean by "two times on every boot"? [00:01] well [00:01] I start it [00:01] it crashes [00:01] I start agait [00:01] it crashes [00:01] the 3rd it works [00:02] BUGabundo: with an Xid error? [00:02] BUGabundo: do you see the UI at all? [00:02] or does it crashes right away? [00:02] some times I have to use --sync to be able to make it start [00:02] no UI [00:02] i see [00:02] Gdk-ERROR **: The program 'firefox-3.6' received an X Window System error. [00:02] $ pastebinit .xsession-errors [00:02] http://paste.ubuntu.com/210044/ [00:02] This probably reflects a bug in the program. [00:02] in .xsession-errors [00:02] The error was 'BadWindow (invalid Window parameter)'. [00:03] seesmt to be not it [00:03] can you stop ffox and start it from consoel? [00:03] to see what it spits out there if it crashes? [00:03] (maybe start multiple times, if it doesnt crash the first time) [00:04] didn't crash this time [00:04] trying agin [00:04] got one now [00:05] http://paste.ubuntu.com/210046/ [00:10] asac: another *very* anoying bug I have on 3.6 but haven't tested on a new profile: [00:10] awesome bar will not store new entries [00:10] so it doesn't memorize new urls [00:12] (firefox-3.6:21449): Gdk-WARNING **: XID collision, trouble ahead [00:12] Removing DOMNodeRemoved listener [00:23] asac: I want to file a bug: 3.6 doesn't allow triple click to select a single word from URL [00:23] :(((( [00:24] confirmed a NEW profile [00:31] doenst work with 3.5 either here [00:32] asac: thanks for your blog post on firefox 3.5 [00:35] Grantbow: thx [00:35] asac: enabling proposed updates will work too? [00:36] for Jaunty [00:36] Grantbow: yes. just posted a comment to confirm that its in jaunty-proposed [00:36] cool, thanks [00:37] asac: you gonna get soooo many users testing packages from -proposed, without they understanting ITS TESTING PACKAGES [00:38] asac: is it? I don't remember it not working on 3.5 [00:39] I do remember soemthing on about:config for that [00:39] crazy mozilla guys who always think they know best [00:40] Grantbow: also added a "Updated:" line to the blog entry now [00:41] 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] I'll email him too [00:42] thx [00:44] asac: so bug or feature? [00:44] * BUGabundo tries to find old addon that allowed to select anything [00:44] BUGabundo: i would think its a feature ... to be sure search in bugzilla for duplicates [00:44] there probably are dupes there already [00:49] asac: Q: is it worth to file a bug to suspend OSD buble when typing in FF search?? [00:49] its *the* most stupid UX bug ever [00:54] asac: feature; http://overooped.com/post/30932542/re-firefox-3-vs-safari-3 [00:54] browser.urlbar.doubleClickSelectsAll;false [00:54] fixed [00:54] asac: typo in blog post [00:55] xulrunner, not xulrunnner [00:55] (pkix_CacheCert_Add: PKIX_PL_HashTable_Add for Certs skipped: entry existed [00:55] hey reed_ [00:56] hiya, BUGabundo [00:56] * reed_ upgrades one of his older laptops from 8.10 to 9.04 [00:56] except my dual screen support will probably be broken [00:56] due to no fglrx driver [00:56] *sigh* [00:57] reed_: ehehe [00:57] try karmic then [00:57] won't be even worse ahah [00:57] no thanks ;) [00:57] there isnt a single GPU in good state right now [00:57] asac: so the way you recommend right now for end users is checking the jaunty-proposed box? [00:57] :(( [00:58] 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] Grantbow: or install it manually from firefox.com [00:58] ;) [00:58] reed_: noooooooooooooooooo [00:58] yesssssssssssss [00:58] don't go tell that.... [00:58] I run it manually ;) [00:58] reed_: the LUGs I'm talking to are impatient [00:58] there are at least 3 PPAs with it [00:58] using official mozilla builds [00:59] hehe [00:59] reed_: and I want to give them the easiest possible solution to get it now [00:59] Grantbow: my opinion counts nothing, but, go with PPA and then remove it when it hits the archive [00:59] the jaunty-proposed sounds best [01:00] humm the prob with PPA is adding the damn key [01:00] Grantbow: but that will bring many packages that are there for testing [01:00] jaunty-proposed could easily break something else, though [01:00] if it's not turned off later [01:00] BUGabundo: which PPA do you recommend? security doesn't have it yet [01:00] and MOST users won't even have the slicest idea what bug they are testing [01:00] sure it does [01:01] Grantbow: i outlined what jaunty users should do in the blog [01:01] * BUGabundo re-checks [01:01] thats still valid [01:01] kk [01:01] Grantbow: use -security PPA [01:01] * Grantbow reads [01:01] and all is good [01:01] you can even keep its [01:02] reed_: do you build with --enable-system-cairo? [01:02] asac: no [01:02] i mean the local build you are running ;) [01:02] hmm. wonder that you never noticed font problems ;) [01:02] ) [01:02] ;) [01:03] there is quite severe problem afaict if you dont use --enable-system-cairo [01:03] well relatively severe ;) [01:03] seems to work ok for me... [01:03] as severe as font problems can be at all [01:03] reed_: you can change the hint style in gnome appearence dialog and firefox will use that? [01:04] otherwise the fonts probably look different than in other gnome apps [01:04] dunno, haven't tried that [01:04] heh [01:04] reed_: do the fonts look the same as the rest of the desktop at all? [01:04] I think I have them set differently [01:04] on purpose [01:04] asac: PPAs for LUG users is kind of messy, needing to add the key and all, but I'll teach them. [01:04] reed_: the chrome fonts? [01:04] whatever the preferences allows me to set! [01:05] Grantbow: the PPA is the right thing to do ... its also much safer than running -proposed [01:06] its only mozilla security updates that get staged there [01:06] with low risk of regressions ;) [01:06] the idea was to push that directly to jaunty-security on friday [01:07] but security team complained and even though i tried, we eneded up giving this a short break in -proposed [01:07] complained == too many packaging changes i introducde [01:07] interesting - lots of users are clamoring for FF 3.5 [01:08] thats normal [01:08] we provide various optoins [01:08] and we had - looking ahead - firefox-3.5 in the jaunty archive universe [01:09] once the packages are there they wont complain anymore and this slight delay will be forgotten ;) [01:09] Grantbow: sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com KEYID [01:10] BUGabundo: yup, thanks [01:10] Grantbow: thank fta. its his code LOL [01:11] asac: the prob is *they* are expecting 3.5 to be default _after_ upgrade [01:11] :D [01:11] they will notice soon enough ;) [01:11] I'm so tired replying to the same questions over and over [01:11] and I bet you too [01:12] not yet;) [01:12] i usually dont answer :) [01:12] btw karmic already has 3.5 as default? [01:12] asac: ahahaha [01:12] except here ;) [01:12] now you can just point them to your blog [01:12] yes thats the idea [01:13] btw karmic already has 3.5 as default? [01:13] no [01:14] https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-karmic-firefox-3.5 [01:14] https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-karmic-browsers [01:17] those are pleanty TODOs [01:17] subbed [01:19] asac: so firefox does not use update-alternatives? [01:21] it does [01:22] but it won't change 3.5 to default [01:22] it will remain as 3.0 [01:23] 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] bug 380196 [01:23] Launchpad bug 380196 in firefox-3.5 "add an alternative to /usr/bin/firefox" [Undecided,Won't fix] https://launchpad.net/bugs/380196 [01:23] wont fix [01:24] Grantbow: changing the default is a matter of moving the link to the right position, yes. [01:24] very important for users to know, thanks for that. I'll read up on it too. [01:26] read my last comment now [01:36] * Grantbow nods [01:42] Grantbow: yes [01:42] oops [01:42] ;) [01:42] * asac confused by scrollback [01:42] its getting late [01:43] asac: true [01:43] I'm about to go to bed [01:44] just trying to find a nice geek part message [01:44] lol [01:45] * BUGabundo $off ; $echo You can't off me; $sudo off; $echo ahaha you trieeeddddddzzzzzzzz [03:19] http://linuxologist.com/linuxhumor/ubuntu-is-a-microsoft-product-now/ === rzr is now known as rZr === asac_ is now known as asac [10:55] ola [11:00] ola [11:00] * BUGabundo to be cordial, I should have replied in german [11:00] _Guntag_ [11:04] BUGabundo: hey [11:04] that was fast [11:04] heheh [11:04] asac: eagles0513875 here has a broken card [11:04] viva 10mbps cable connection lol [11:05] not a broken card it works fine on nm on jaunty [11:05] wicd not as user friendly as NM [11:05] i know [11:05] he wants to test NM 0.8 [11:05] will it help his case? [11:05] but i think this is the regression that jaunty had where it couldnt connect to wpa [11:05] my wifi connection is wpa2 mixed connection [11:05] eagles0513875: this kind of broakage is usually driver (aka kernel), not much that NM can do/fix [11:05] oh right [11:06] your prob is encription [11:06] dont think that 0.8 would reall yhelp [11:06] not actual device suport [11:06] if NM doesnt work it means that the driver sucks ;) [11:06] would wicd help [11:06] especially if wicd is working [11:06] asac: it works fine in jaunty [11:06] then its a regression ;) [11:06] eagles0513875: what driver is it? [11:06] its the oss reversed engineered b43-fwcutter [11:06] for me the proprietary one doesnt work for me [11:07] asac: what does wicd really do, to work in so many cases where NM doesn't ? [11:07] yeah. those proprietary broadcom drivers are doomed to decay over time [11:07] b43-fwcutter isnt propritary though [11:07] !b43-fwcutter [11:07] Sorry, I don't know anything about b43-fwcutter [11:07] e.g. they worked well in old kernels, but they dont get better ;) [11:07] !info b43-fwcutter [11:07] b43-fwcutter (source: b43-fwcutter): Utility for extracting Broadcom 43xx firmware. In component main, is optional. Version 1:011-5 (jaunty), package size 16 kB, installed size 108 kB [11:07] thats what i use right there [11:07] no. but it wrapps the binary [11:07] meaning [11:08] so that works? [11:08] on jaunty but not on karmic [11:08] ok [11:08] maybe you accidentically cut out a newer firmware from broadcom= [11:08] ? [11:08] or are you 100% sure that you have the same firmware used on karmic vs. jaunty [11:09] its saying its installed which seems to be 1:012-1 from main repo [11:09] eagles0513875: thats not the firmware [11:09] ohhhhh wait [11:09] jaunty is a slightly older one then karmic [11:09] eagles0513875: fwcutter is a tool ... it downloads a firmware from broadcom website [11:09] and cuts out the ugly blob bits [11:09] jaunty 1:011-5 and karmic has 012-1 [11:10] so it could be that fwcutter is broken or that the firmware downloaded changed [11:10] could you please check that? [11:11] so basically uninstall reinstall [11:11] no [11:12] figure out the version you downloaded from broadcom (not the ubuntu package) [11:12] or download the firmware and install it on jaunty and karmic to check [11:12] if that all doesnt help, also check whether you actually use the same driver [11:12] asac: who is supporting BT in karmic? [11:12] there are multiple b4xxx drivers in the kernel [11:12] its even more broken then in jaunty [11:13] so it might be that you now use a different [11:13] BUGabundo: BT? [11:13] can't even connect to devices, doesn't accept password [11:13] bittorrent? bluetooth? [11:13] asac: BlueTooth [11:13] ahah right too many meaning [11:13] BUGabundo: are you using bluez-gnome? [11:13] applet freeses [11:13] asac: I _think_ I'm using what ever karmic brings [11:13] let me check [11:13] BUGabundo: ok. remove bluez-gnome and install blueman [11:14] restart system [11:14] check that all works still [11:14] then also remove blueman and install gnome-bluetooth [11:14] ahah [11:14] check that it works and compare to blueman [11:14] come on... all 3? [11:14] tell me what works better [11:14] broadcom is pita [11:14] ack [11:14] too many reboots for me [11:14] asac: seems like alot of linux wifi drivers are done and supported by http://linuxwireless.org/ [11:14] eagles0513875: if you can find your wifi card easily in your laptop, just buy a iwl4965 from ebay for 5 bucks ;) [11:14] bluez: Installed: 4.41-0ubuntu2 [11:15] and replace it [11:15] ;) [11:15] that saves you lots of issues [11:15] i can i know the model and everything [11:15] blueman: Installed: (none) Candidate: 1.10-2 [11:15] thing is this is an hp tablet so no pcmcia no nothing [11:15] gnome-bluetooth: Installed: 2.27.5-1ubuntu1 [11:15] eagles0513875: thats what i said. if you can find the wifi card inside [11:15] asac: so I better remove all and just install ONE ? [11:15] ahhhh my bad [11:15] BUGabundo: yes [11:16] i have one place i can ask is the linux-wireless irc channel [11:16] eagles0513875: to find the card inside your chassis? [11:16] eagles0513875: just open your laptop ... usually its obvious ;) [11:16] 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] asac: lspci also works its a bcm4311 reb2 wifi card [11:16] eagles0513875: like i said. first check that you reall yuse the same firmware [11:16] thats not the vresion you see in ubuntu [11:17] its the version you find on broadcom website [11:17] which they dont even have linux drivers for [11:17] linuxwireless.org im guessing is in charge of any linux drivers for broadcom [11:17] eagles0513875: do you understand what i am saying? [11:17] eagles0513875: no they are not [11:17] eagles0513875: broadcom is unsupported by linuxwireless [11:17] im not able to find anything on the broadcom site [11:18] eagles0513875: fwcutter downloads a file from broadcom site [11:18] that one you need to compare [11:18] with the one you installed in jaunty [11:18] * eagles0513875 wishes vmware server worked right now [11:19] I used the wl driver on the last broadcom laptop I had [11:19] asac: libbluetooth3 pulls evolution, gnome-do etc! should I keep it? [11:19] micahg: yeah. but wl doesnt work for all [11:19] I had to use ndiswrapper and the windows driver before that [11:20] BUGabundo: i dont knwo [11:20] BUGabundo: i had no problems eliminating blue-gnome [11:20] fwcutter never worked for me [11:20] your the opposite of me micahg [11:20] the proprietary doesnt work for me but fwcutter does [11:20] micahg: if wl works, fwcutter is not supposed to work afaik [11:21] I don't have broadcom anymore [11:21] now I have atheros [11:23] asac: ok all 3 meta packages removed [11:23] eagles0513875: you said that wicd worked on karmic still? [11:24] brb [11:24] rebooting to test bluetooth [11:24] someone else was able to successfully use wicd not me [11:25] ok [11:25] 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] b) if you are sure about that, check whether you actually use the same driver in januty vs. karmic [11:26] there are a bunch of b4xxxx drivers [11:26] ok will try that [11:26] 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] c) if all is the same, check the committs that happened on the driver you are usin gin the upstrema kernel tree [11:26] there probably shouldnt be that many [11:26] so with some luck you can identify what caused this regression [11:26] :) [11:26] d) complain on linux-wireless [11:27] i will :) [11:27] but i think that they wont help you [11:27] broadcom is a mess [11:27] lol tell me bout it [11:27] when i first started with edgy it was a nightmare [11:27] e) open up your computer ... rip out this broadcom shit [11:27] lol [11:27] buy a good card on ebay [11:27] for 5EUR [11:27] and put that in [11:27] (seriously [11:27] ) [11:27] this laptop is still under warrenty though so i dont wanna void the warrenty [11:28] i dont thin kit would void th warrenty ;) [11:28] its hp they are a mess as well [11:28] its just changing a component :) [11:28] i couldnt use the manufacturers warrenty on a machine i bought in the states [11:28] often you can just open the back panel and there is the card .. similar to a card in a desktop PC [11:28] f you are out of luck its behind the laptop screen [11:28] then youar elost ;) [11:29] eagles0513875: send machine back and claim warrenty; say the broadcom card is broken :) [11:30] seriously, everybody should cause work on the OEM side if they ship broadcom stuff [11:30] even if its just complaining that its "broken" and they have to check it etc [11:30] ya they replaced it with another broadcom [11:30] OEMs buy into broadcom because they are so cheap ... so raise maintenance cost and they will pick atheros ;) [11:31] eagles0513875: always cause work on their side explicitly mentioning broadcom :) ... maybe that helps at some point ;) [11:31] i hear atheros is a nightmare though as well [11:31] if they replace with broadcom say that its stil lbroekn [11:31] asac: back [11:31] eagles0513875: atheros is at least on their way tobecome one of the good guys [11:31] asac: what the 1st metapack you want me to test? [11:31] thats good to hear [11:31] at least they work together with linux folks on real linux drivers [11:32] in the mainline tree [11:32] and dont hide behind: "its illegal to ship open source drivers in the US" [11:32] asac: what does it mean when wlan0: ap denied association code=13 [11:32] can mean anything [11:32] is that driver message or wpa_supplicant? [11:33] did you try to connect to a open AP? (e.g. no WPA?) [11:33] no i havent [11:33] the message is showing up in dmesg [11:33] there is another one in dmesg disassociating by local choice reason 3 [11:33] asac: what the 1st bluetooth metapack you want me to test? [11:35] BUGabundo: blueman or gnome-bluetooth [11:35] you can choose [11:35] aah [11:35] blueman it is [11:36] asac: found a shell installation script that seems to get wifi driver from openwrt.org [11:36] blueman pools bluez? [11:36] BUGabundo: yes. thats ok [11:36] just not bluez-gnome [11:37] asac: $ dpkg -l | grep blue | pastebinit http://paste.ubuntu.com/210282/ [11:37] asac: is that enough/ok ? [11:37] reboot again ? [11:38] BUGabundo: maybe .... usually you dont need to reboot [11:39] restart bluetooth ... and re-login [11:39] ok [11:39] restart bt and nothing [11:39] trying session now [11:44] asac: back [11:44] ok I see the applet [11:44] I can go to settings [11:44] but it hasn't any other options enabled [11:44] they are greyed out [11:45] device, adaptors, send, receive, nothing [11:46] asac: should I try the next on the list, or am I missing a package? [11:47] 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] ok no reply moving on. gnome-bluetooth [11:53] im here BUGabundo [11:54] did get some coffee [11:54] ahh [11:54] I was about to ask eagles0513875 if you said that [11:54] BUGabundo: settings? couldnt you open the dialog where you can scan etc? [11:54] ok gnome-bluetooth installed [11:54] asac: err too late?! [11:55] only to button available on the applet [11:55] turn on/off and preferences [11:55] BUGabundo: yes. you have to turn on [11:55] all other were greyd out [11:55] ;) [11:55] duh [11:55] it was ON [11:55] I'm blond, not stupid [11:55] BUGabundo: but you right clicked [11:55] BUGabundo: have you tried to left clikc? [11:55]