[09:11] <huats> good morning !
[09:18] <seb128> lut huats
[09:19] <huats> hello seb128
[09:19] <huats> thanks for the sponsoring and the sync :)
[09:19] <seb128> huats: you're welcome
[11:06] <james_w> seb128, pitti: I came across bug 276134, any thoughts?
[11:07] <seb128> james_w: upstream bug
[11:07] <james_w> ah, sorry I hadn't refreshed
[11:08] <james_w> of course you are already on it :-)
[11:08] <seb128> james_w: I don't think it's a real issue, only gedit seemed to display such dialogs on session closing and I doubt people use gedit for serious work and don't save and close their session often
[11:14] <pitti> actually, that's related to yet another bug
[11:15] <pitti> james_w, seb128: the problem right now is that using "shut down", the entire session is just killall'ed
[11:15] <pitti> since it just calls consolekit's reboot/shutdown method without ending the session properly
[11:16] <pitti> if only I could remember that related bug (we spoke about it when discussing the "shutdown/reboot doesn't work" bug
[12:49] <seb128> hate hate xulrunner
[12:50] <seb128> when the thing will stop crashing when closing epiphany-browser
[12:50] <seb128> ok, let's get some coffee while apport works on the crash, can't restart a webbrowser now
[13:32] <lool> Hmm is the bug about USB keys not automounting tracked for release?
[13:33] <seb128> no, that's not a known bug
[13:33] <lool> I think pochu was seeing the bug as well like a week ago
[13:33] <lool> seb128: If you plug an USB key, does it get mounted?
[13:34] <lool> Mine doesn't get mounted, and right-clicking to select "Mount" in nautilus doesn't work either
[13:34] <lool> (nothing in .xsession-errors)
[13:34] <seb128> I've no usbkey to try on right now but when I did it was working
[13:34] <seb128> lool: could you try to gnome-mount -v -b -d /dev/device?
[13:35] <lool> It's weird, I see two entries in nautilus, one is Média 2,1 Go and another one is Lecteur USB
[13:35] <lool> I unplugged and replugged, now I get two Lecteur USB entries
[13:36] <seb128> what partitions do you have on the key?
[13:36] <lool> seb128: Permissiondeniedbypolicy
[13:37] <lool> org.freedesktop.Hal.Device.PermissionDeniedByPolicy : org.freedesktop.hal.storage.mount-removable no <-- (action, result)
[13:37] <lool> ** (gnome-mount:3730): DEBUG: pk_action='org.freedesktop.hal.storage.mount-removable' pk_result='no'
[13:37] <seb128> lool: I guess consolekit crashed and you have no ck-session now
[13:37] <seb128> that was the issue for pochu now that you mention it
[13:37] <lool> seb128: Ah right, I heard about many CK crashes
[13:37] <seb128> I helped it to track it
[13:37] <seb128> s/it/him rather
[13:38] <lool> seb128: Are these resolved? cause my intrepid is up-to-date and my session isn't that old
[13:38] <seb128> lool: ck-list-sessions
[13:38] <lool> Session8: uid = '0' realname = 'root' seat = 'Seat4'
[13:38] <lool> ...
[13:38] <lool> Session4: uid = '1000' realname = 'Loic Minier,,,' seat = 'Seat3'
[13:38] <seb128> lool: no, pitti gave a try to consolekit 0.3 and it's in his ppa but he had issue using it
[13:38] <lool> ...
[13:38] <lool> The second is a ssh one
[13:38] <lool> /dev/ssh blah
[13:39] <seb128> lool: is there an active one?
[13:39] <pitti> lool: if you need 0.3, it and the accompanying hal change are in my PPA; but it totally breaks ACL management
[13:39] <seb128> don't bother replying
[13:39] <seb128> there is none
[13:39] <lool> no
[13:39] <seb128> your consolekit daemon probably crashed
[13:39] <seb128> pitti: what do you call ACL management exactly?
[13:39] <crevette> hello
[13:39] <seb128> lut crevette
[13:40] <crevette> salut seb128
[13:40] <crevette> did you see my wonderful son?
[13:40] <crevette> :)
[13:40] <pitti> seb128: for devices (/dev/bus/usb, etc.)
[13:40] <seb128> pitti: do you have example of things which are not working?
[13:41] <pitti> I have to try again, but it was pretty obvious (network-manager, or digicams, etc.)
[13:42] <seb128> I'll give it a try later
[13:42] <seb128> we have to do something about those consolekit crashes
[13:43] <seb128> https://edge.launchpad.net/ubuntu/+source/consolekit/+bugs urg
[13:43] <crevette> huuu
[13:47] <lool> scary for security sensitive software
[13:47] <seb128> lool: right, that's why I would like to update to the current upstream version
[14:19] <mvo> asac: do you know about http://paste.ubuntu.com/52463/ ?
[14:24] <asac> mvo: hmm
[14:25] <asac> mvo: i fixed something similar for abrowser ... either i didnt upload that fix or i missed firefox-3.0
[14:29] <mvo> asac: dunno, but I think I have the latest ff3 (unless its sitting in the queue)
[15:07] <gnomefreak> asac: mvo that was fixed thursday/friday IIRC
[15:08] <gnomefreak> mvo: can you run firefox from term?
[15:14] <mvo> gnomefreak: firefox (without -3.0) work fine, firefox-3.0 does not for me
[15:15] <gnomefreak> mvo: you have abrowser?
[15:16] <gnomefreak> abrowser conflicts with firefox-3.0 but leaves firefox installed
[15:17] <mvo> gnomefreak: no awbrowser, firefox and firefox-3.0
[15:17] <mvo> so ff does the right thing for you if you run "firefox-3.0" ?
[15:17] <gnomefreak> it was fixed in abrowser maybe he didnt apply it to ff-3.0?
[15:18] <gnomefreak> mvo: i use abrowser
[15:18] <gnomefreak> give me a minute let me test
[15:19] <mvo> thanks
[15:19] <gnomefreak> ah it conflicts with firefox not firefox-3.0 lets see if i can
[15:20] <gnomefreak> i get same error with firefox-3.0 but firefox still runs it
[15:22] <gnomefreak> asac: did you not apply the fixed link to firefox-3.0 when you fixed it in abrowser?
[15:26] <gnomefreak> he did from what changelog say
[15:26] <gnomefreak> s
[15:27] <gnomefreak> mvo: bug 273907 is the bug you are seeing but with *-3.0
[15:27] <asac> gnomefreak: most likely abrowser-3.0 is broken too right?
[15:27] <gnomefreak> asac: it is
[15:28] <gnomefreak> no
[15:28] <gnomefreak> its not
[15:28] <gnomefreak> orry
[15:28] <asac> gnomefreak: so running abrowser-3.0 from command line works?
[15:28] <gnomefreak> oh with -3.0 yes
[15:28] <asac> yeah
[15:28] <asac> ok
[15:28] <asac> gnomefreak: you have 3.1 installed by any chance?
[15:29] <gnomefreak> not atm is it in fta's PPA with abrowser branding?
[15:31] <asac> gnomefreak: not sure if he synched the latest fixes to 3.1 branch yet :) ... thats why i ask ;)
[15:31] <asac> gnomefreak: but in general there should be the abrowser branding ... yes.
[15:31] <gnomefreak> firefox-3.1 - 3.1~b1~hg20080926r19788+nobinonly-0ubuntu1~fta1
[15:31] <gnomefreak> and no he doesnt have abrowser yet
[15:32] <gnomefreak> never mind he did
[15:32] <gnomefreak> give me a few minutes and ill let you know
[15:35] <gnomefreak> smoke than test
[15:54] <seb128> I'm away for bit, bbl
[16:00] <Keybuk> seb128: still having evolution bug where my inbox is in a basically random order
[16:00] <gnomefreak> asac: it seems to work fine when using ff3 profile
[16:13] <soren> Isn't rhythmbox supposed to update id3 tags when you change a song's metadata in the UI?
[16:30] <soren> Ah, not without --enable-tag-writing.
[16:30]  * soren recompiles
[18:07] <fta> asac, gnomefreak, my 3.1 branch is in sync, it has abrowser-3.1. both ff-3.1 and ab-3.1 work fine here.
[18:07] <fta> asac, but ff-3.0 is indeed broken
[18:08] <fta> i see the problem, gasp, more branch work in perspective
[18:20] <asac> fta: i have the fix for that already
[18:20] <asac> so wait till thats pushed
[18:20] <asac> just wanted to get a confirm that its indeed ok on 3.1
[18:26] <fta> so it probably means more tweaks in my 3.1 branch, i'll see
[18:49] <asac> fta: did you need to tweak something on top of what we did in 3.0.head?
[18:50] <asac> otherwise I think the solution should work on 3.1 too
[20:40] <espacious> damn i the newest version ubuntu-desktop and now my wifi card dont work
[20:40] <asac> espacious: intrepid?
[20:41] <espacious> its a TEW424UB wirless usb adapter
[20:41] <espacious> i got it working on 8.4 NP
[20:41] <espacious> i used ndiswrapper and drivers for xp
[20:41] <asac> espacious: so its a regression in 8.10?
[20:41] <asac> espacious: what driver is it ... ah ndiswrapper
[20:41] <espacious> was working great
[20:42] <espacious> yes
[20:42] <asac> espacious: can you try to blacklist that and see if something else takes over?
[20:42] <espacious> can anybody help?
[20:42] <espacious> what is intrepid?
[20:42] <asac> 8.10
[20:43] <asac> (codename)
[20:43] <espacious> btw the adapter is working but only when i click to connect to my ruter and enter the WPA key the whole pc freezesssss.
[20:46] <asac> espacious: do what i say and blacklist ndiswrapper ... if that doesnt work, wade through the bugs of "linux" package in launchpad to find your duplicate. if there is no duplicate (unlikely), file a new bug.
[20:46] <espacious> so in /etc/modprobe.d/blacklist i added ........
[20:46] <espacious> ok so u want me to disable ndis?
[20:47] <asac> espacious: yes
[20:47] <espacious> coz i used ndis all the time in the previsious instalation and i never got the card workin without ndiswrapper
[20:47] <espacious> ok let's try
[20:47] <espacious> blacklist ndiswrapper
[20:47] <espacious> done, now?
[20:48] <asac> espacious: ndiswrapper is something that has to die .. so as long as there is another alternative that supports your chipset you should try that
[20:48] <espacious> i agree
[20:48] <espacious> so how can i get the car go now?
[20:49] <asac> espacious: depends on what you did to setup ndiswrapper ... did you do anything?
[20:49] <espacious> it's a fresh install
[20:49] <espacious> just added ndiswrapper from cd
[20:49] <espacious> repo
[20:49] <asac> espacious: so you tried without ndiswrapper?
[20:50] <espacious> and in previsious installs i only added the drivers for xp
[20:50] <espacious> i will now.
[20:50] <espacious> but i ned a bit of help
[20:50] <espacious> dont know where to start
[20:50] <asac> espacious: well. usually it should just work in a fresh install afaict
[20:51] <espacious> nope
[20:51] <espacious> it detects no wireless
[20:51] <asac> espacious: if the fresh install didnt show your card in NM then oyu probably were out of luckm
[20:51] <espacious> hmm
[20:51] <seb128> asac: is there a bug about nm 0.7 refusing to autoconnect to stock essid network names? that's starting to annoy me on intrepid
[20:51] <espacious> now it seems to use ndiswrapper
[20:51] <espacious> i must reboot or stop him
[20:52] <asac> seb128: can you commit http://bugzilla.gnome.org/show_bug.cgi?id=554485 for me? :-P
[20:52] <asac> that annoyed me for a few month ;)
[20:52] <asac> hehe
[20:52] <asac> let me check for a bug
[20:52] <asac> you are the only one complaining about it in person to me
[20:53] <seb128> asac: just add a commit on the bug saying you don't have svn access, they will commit for you and after some times you will get svn access ;-)
[20:53] <espacious> asac no luck ist's not working
[20:53] <espacious> so is there a way to get it working with ndis?
[20:53] <seb128> asac: I must be the only one to be too lazy to change the router configuration ;-)
[20:53] <espacious> i cannot find anything usefull on google
[20:54] <asac> seb128: or maybe there is something unique for your setup :(
[20:54] <seb128> asac: it's happening on several networks, one using linksys and one NETGEAR
[20:54] <asac> seb128: the expected behaviour is that it doesnt autoconnect if you never connected to a factory AP before ... but once thats done it should work :/
[20:55] <seb128> asac: it asks me for the password of somebody else in my building at every login because I clicked on the wrong entry once by mistake rather than picking my netgear essid
[20:56] <asac> seb128: remove the connection from connection-editor ... that should make that go away
[20:56] <seb128> asac: I add to delete the network in the configuration dialog and now it doesn't connect at all
[20:56] <seb128> asac: right, it just stays offline now
[20:56] <asac> seb128: if you have such a connection there then it might as well be the case that NM just likes that AP more than the other
[20:56] <asac> ok :-P
[20:56] <asac> would have been too easy
[20:57] <seb128> I workarounded it during the holidays by setting to the one I use usually to autoconnect
[20:57] <seb128> but I'm having the same issue on an another network I use sometime
[20:57] <seb128> and I can't see both to autoconnect
[20:57] <asac> seb128: does it work if you try to make a "system connection" out of it?
[20:58] <seb128> let me try
[20:58] <asac> seb128: both are open networks right?
[21:03] <seb128> asac: yes that makes it autoconnect
[21:05] <espacious> asac any other ideas except going to previsious version of ubuntu?
[21:17] <seb128> re, got disconnected
[21:18] <seb128> asac: it does autoconnect after doing this change
[21:24] <espacious> asac amazing also the new 8.10 beta
[21:25] <espacious> i tryed and it works
[21:25] <espacious> damn nobody yet had a similar usb wireless device ?
[21:26] <espacious> on 8.4
[21:29] <asac> espacious: huh?
[21:29] <asac> so it works?
[21:30] <espacious> yes on beta but beta 8.10
[21:30] <espacious> but it was making some strange issues
[21:30] <espacious> one time boot ok one time no.
[21:31] <espacious> so i wanted to install 8.4
[21:31] <espacious> but there we go no wirless drivers
[21:31] <asac> espacious: didnt you say before that ndiswrapper worked for you on 8.4?
[21:31] <espacious> no sorry it was on beta
[21:31] <asac> espacious: so without ndiswrapper it doesnt work on 8.4 but with 8.10?
[21:31] <asac> espacious: well. thats normal then. drivers for wireless improve. so wait for final
[21:32] <asac> good that it works at least
[21:32] <espacious> so. it works only with ndiswrapper, on all versions only 8.4 no
[21:32] <espacious> without ndiswrapper nothing
[21:33] <asac> seb128: ok. at best try to get back to the state where it doesnt work, then reproduce on your system and report a short bug with apport (which will append a bunch of values from your gconf - no keys!!)
[21:33] <asac> or just append syslog and i will show that to the NM maintainer
[21:52] <seb128> asac: should I open that directly on bugzilla upstream rather?
[21:57] <asac> seb128: upstream i think.
[21:57] <seb128> asac: ok will do
[21:58] <seb128> I guess that's one case where upstream think to be clever and prevent user to virtually shoot themself in the foot or something
[21:58] <asac> seb128: cool
[21:58] <asac> seb128: did you ever try to completely unset your /system/networking recursively?
[21:59] <seb128> I think I did when nm0.7 landed and we had this discussion
[21:59] <asac> seb128: ok
[21:59] <seb128> I enable the autoconnect for my usual network which workaround the issue and didn't bother since
[21:59] <seb128> but it's doing the same on this other network now
[22:00] <asac> seb128: enable the autoconnect?
[22:00] <seb128> the connection editor, the is an "autoconnect" box you can use
[22:00] <seb128> just under the connection name
[22:00] <asac> seb128: oh. so the bug is that thats not enabled by default
[22:01] <seb128> dunno if that should or if the option is to force the connection
[22:01] <asac> didnt remember that
[22:01] <asac> seb128: no. without that checkbox on its not supposed to auto connect
[22:01] <seb128> the bug is that it prefers to not connect to anything that to connect to linksys or netgear
[22:02] <asac> seb128: let me try if it automatically checks that if i unset my connection
[22:02] <asac> wait a minute
[22:05] <seb128> ok
[22:06] <asac> seb128: ok. so after unsetting everything and starting NM it doesnt connect anywhere
[22:06] <asac> but
[22:06] <asac> until i click any connection, there is no connectino configuration in connection-editor
[22:06] <asac> as soon as i click on any connection and the connect succeeds, the connection configuration becomes available
[22:06] <asac> and autoconnect is enabled
[22:07] <seb128> autoconnect is not enabled in my case
[22:07] <asac> so next time it will happen automatically
[22:07] <seb128> try setting your essid to netgear
[22:07] <seb128> NETGEAR to be exact rather
[22:07] <asac> i believe you ;)
[22:07] <seb128> it autoconnect to some other network I never connected to in my building only because I clicked on that by mistake
[22:07] <asac> you said that you removed the connection from connection editor and end up in that state
[22:07] <seb128> I think it doesn't like stock vendor essid names
[22:08] <asac> let me test if removing and then connecting again makes a differrnce
[22:08] <asac> nope autoconnect is enabled too
[22:09] <asac> so go ahead and file upstream
[22:09] <asac> vendor essids are certainly handled different ... thats a bug imo
[22:11] <asac> seb128: yeah. i found the code :) ... it indeed doesnt set it to autoconnect by default
[22:11] <asac> s_con->autoconnect = !is_manufacturer_default_ssid (ap_ssid);
[22:12] <asac> i think i also understand why its not that easy now :/
[22:12] <asac> but its still a missing feature
[22:13] <seb128> asac: why not?
[22:13] <asac> seb128: well. first step: when a scan gives you a result they create a nm-connection. that one has the autoconnect flag.
[22:13] <asac> (false)
[22:14] <asac> you cannot create that with "true", because if a nm-connection has "true" it will autoconnect ... which is not what we want for manufacturer essids (until you have connected once)
[22:15] <asac> you would have to flip the autoconnect flag to true once you have seen a bssid
[22:15] <seb128> why are manufacturer essids differents?
[22:15] <asac> but at that time you dont know if the autoconnect flag was unset by user, or just because it was default
[22:16] <asac> seb128: the chance that a neighbour has that essid is high. so lots of people would run autoconnect there and from then on would have the issue you experience ;)
[22:16] <asac> e.g. even if their home connection is autoconnect=true they randomly would connect to neighbour
[22:16] <asac> but i think there is a fix
[22:16] <asac> so file that bug for now :)
[22:17] <seb128> launchpad or bugzilla?
[22:18] <asac> seb128: bugzilla ... thats definitly something upstream has to think about
[22:18] <seb128> ok
[22:18] <asac> or at least reach consent :)
[22:19] <seb128> I don't care if it display a dialog on the first connection to explain the issue about not using a custom essid but it should just not silently not autoconnect it looks like it's broken
[22:19] <seb128> I'll open the bug and give you the number
[22:37] <seb128> lool: what do you think about bug #208729?
[22:38] <seb128> should libglib2.0-0 recommends shared-mime-info?
[23:00] <espacious> heh ndiswrapper is useless in 8.4 as it crashes..
[23:00] <espacious> damn
[23:00] <espacious> frezes the whole pc
[23:04] <Ng> seb128: if a machine isn't automounting USB media, where should I be looking to track down what's going on?
[23:04] <seb128> Ng: that starts being a classic one
[23:04] <seb128> Ng: did you get a consolekit crasher?
[23:05] <Ng> seb128: not afaik. I'm almost certain it'll be a config error, or I have some old package installed. it's a machine with a very messy install that's been upgraded for quite a few releases
[23:05] <seb128> Ng: try to run gnome-mount -v -b -d /dev/device
[23:06] <Ng> that mounted it
[23:06] <Ng> (fwiw, it's an 80gb ipod)
[23:06] <seb128> ok so I don't know
[23:06] <seb128> hum
[23:06] <seb128> unmount it
[23:06] <seb128> run lshal --monitor
[23:06] <seb128> plug the ipod again
[23:06] <seb128> and copy the log somewhere
[23:08] <Ng> http://paste2.org/p/80534
[23:12] <seb128> Ng: what is the info.capabilities in lshal for it?
[23:13] <Ng> storage, block, portable_audio_player, access_control
[23:19] <seb128> Ng: is it listed in the computer place?
[23:20] <Ng> yeah
[23:20] <seb128> what action is configure in the nautilus properties?
[23:22] <Ng> seb128: browse folder
[23:22] <seb128> for audio players?
[23:25] <Ng> yeah
[23:25] <seb128> I've just looked quickly at the code but don't see anything obvious
[23:25] <Ng> I am testing out some banshee stuff, so I don;t really want it to launch a media player automagically
[23:25] <seb128> I don't have my ipod there but I'll give it a try tomorrow
[23:25] <Ng> it works fine on my laptop, fwiw
[23:26] <Ng> I guess I'll poke around some more
[23:26] <seb128> weird
[23:26] <seb128> did you try to change the action to start rhythmbox just to see if that's working?
[23:37] <Ng> seb128: no, but I did just have a thought that takes us back to the first thing you mentioned - consolekit. the user in question is an autologin
[23:37] <seb128> that's not the issue there
[23:38] <seb128> autologin has a session too
[23:38] <Ng> ah ok, I thought maybe that means they get different permissions
[23:38] <seb128> and gnome-mount wouldn't work if there was no session
[23:38]  * Ng nods, fair enough
[23:40] <Ng> well, I need to get it copying music and get some sleep, but I'll come back to this at some point - my aim is to be able to plug the ipod into the media PC and have it autosync my library, so this will need to be beaten into shape sooner or later ;)
[23:40] <Ng> thanks for the help
[23:40] <Ng> lshal --monitor is a nugget of great value :)
[23:40] <seb128> you're welcome
[23:41] <seb128> I'll give a try to my ipod tomorrow
[23:41] <Ng> I expect it will work :)
[23:41] <seb128> I just tried using a mpt device which didn't work but I guess that's a different issue since this one is not listed at all by gvfs or nautilus