[13:37] <scientes>  iinstalled the ubuntu-mobile package and it totally messed my desktop
[13:37] <scientes> xchat is stuck in full screen and is set so you cant resize it
[13:44] <ian_brasil_> scientes: what device are you using
[13:44] <scientes> a desktop
[13:44] <scientes> i though the changes would be autonomous and i could just load up another gdm and look at it, or nest a gdm
[13:45] <scientes> a restart after deinstalling what i could fixed the window manager
[13:45] <ian_brasil_> why don't you try it in kvm or qemu
[13:45] <scientes> but simply restarting the window manager didnt
[13:45] <scientes> yeah
[13:45] <ian_brasil_> there is also a gconf key you could change to exit the full screen
[13:46] <persia> No, it's not a gconf key : it's a config file value.
[13:46] <scientes> most thing you could jsut use ctrl-click (of course only in compiz), but for some reason xchat was stuck at full screen
[13:46] <ian_brasil_> gconf-editor in a termainl
[13:46] <scientes> i mean alt-click to move/resize
[14:17] <crevette> heya
[14:17] <crevette> someone from the bluetooth team here ?
[14:18] <crevette> I wanted to know what the state of bluetooth, because this is quite hectic now in intrepid, and we need to fix that.
[14:20] <persia> crevette, Well, how do you suggest we fix it?  It's certainly broken.  slytherin was testing some patches, but never found anything that both worked and seemed small enough to fit in an SRU.
[14:20] <persia> My memory is that the biggest issue was with gnome-user-share and it needing apache.
[14:21] <crevette> a lot of people complain about sending and reception issues
[14:21] <crevette> sending from computer
[14:21] <persia> Sending from the computer?  That worked last time I checked.
[14:21]  * persia tests again now
[14:21] <crevette> I think this is due to nautilus-sendto which is too restructive when checking the phone capabilities
[14:21] <crevette> persia, some phoen don't work
[14:22] <crevette> phones
[14:22] <crevette> (apparently), mine does
[14:22] <persia> Oh, so that it works for me isn't enough.  I very much dislike bugs I can't reproduce :(
[14:22] <crevette> I needed to hack the source but didn't find time
[14:23] <persia> I suspect others are in the same position.
[14:23] <crevette> https://bugs.edge.launchpad.net/nautilus-sendto/+bug/285283
[14:24] <crevette> people should try to execute dbus-send --system --print-reply --dest=org.bluez /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX org.bluez.Device.GetProperties
[14:24] <crevette> if in the properties there is no somethiong like 0x1106 in the UUID nautilus-sendto won't even go further
[14:25] <crevette> I wonder if bluetooth-sendto checks the capabilities or not 
[14:25] <crevette> but most of the time it works fine
[14:25] <crevette> so if bluetooth-sendto work but not nautilus-sendto, you can bet this is the nautilus-sednto bug
[14:25] <persia> Yeah, it certainly sounds like one.
[14:26] <crevette> so I need to remove the capabilities check from nautilius-sendto
[14:26] <crevette> or someon with REAL coding capaibilities
[14:26] <crevette> I just know copy & pasting code
[14:26] <persia> Mind you, it might be a applet bug that it does allow send, but a bug that's left there to work around devices that don't describe themselves.
[14:27] <crevette> for the file reception problem, there is an issue with obex-data-server, our snapshot isnot working fine
[14:28] <crevette> jumping to 0.4.2 would be radical, but it proved to work for me at least, and some other persons
[14:28] <persia> Right.  slytherin thought that some gconf adjustments might help.
[14:28] <crevette> gconf ? for which problem ?
[14:29] <crevette> s/\ \?//
[14:29] <persia> jumping to 0.4.2 for jaunty would be a sensible step then.  That doesn't require any approvals.  I'm less sure what to do with intrepid.
[14:29] <persia> gconf for the obex-data-server issue.
[14:29] <crevette> okay, for changing which key, (I didn't know that obex-data-server uses gconf)
[14:31] <persia> I don't actually know.  Best ask slytherin (who is rarely in this channel : more often in #ubuntu-motu).
[14:31] <crevette> okay
[14:31] <ian_brasil_> crevette? there is also the password issue in bluetooth
[14:31] <crevette> the third problem is the reporter themself, who are a little confused and mix the problems
[14:32] <crevette> ian_brasil_, the one where the notification disappear quickly ?
[14:32] <persia> crevette, I think the reporter is seeing both bugs.
[14:32] <ian_brasil_> yes..for instance on a gps device there is no way to enert a password
[14:32] <ian_brasil_> enert == enter
[14:32] <persia> ian_brasil, Or the one where the filter for which devices get assigned a password, and which have defaults is mostly broken?
[14:32] <crevette> ian_brasil, rh has some patch, where they hard-code 000
[14:32] <crevette> 0000
[14:32] <persia> Well, that needs a better device DB.
[14:32] <ian_brasil_> i saw that...the main.c hack
[14:33] <crevette> yep
[14:33] <ian_brasil_> the proper solution is to modify the UI i think
[14:34] <ian_brasil_> but much more time involved ibviously
[14:34] <ian_brasil_> damn keyboard ..ibviously == obviously
[14:35] <crevette> ian_brasil, you suggest let the user enter the pair code ihimself ?
[14:37] <crevette> persia, perhaps I wasn't clear enough, I was stating that users are confused between various bluetooth package, and which one provide which functionnality, so people add a comment on nautilus-sendto stating about reception, 
[14:37] <persia> For devices that can enter codes, I like the UI.  I'm somewhat annoyed that one of my devices on which I can enter a code defaults to 0000.  On the other hand, I know several people have devices on which they can't enter codes which default to random, which is even more annoying.
[14:37] <ian_brasil_> crevette: that was how it worked in hardy IIRC
[14:37] <ian_brasil_> and is the expected behaviour from a users POV
[14:40] <persia> Yeah, the hardy behaviour wasn't that bad either.
[14:42] <crevette> we need to see with uptream, perhaps
[14:42] <crevette> it would make sense
[14:42] <crevette> damn, if I wish I were rich to have time for that
[14:42] <crevette> :)à
[14:42] <crevette> unfortunately I'm at work now :)
[14:43] <persia> Well, the hardy implementation was a bit annoying, and very fragile.  The UI might be nice, but it would be better to do it differently.
[14:44] <crevette> persia, you're talking about bluez-properties ?
[14:44] <crevette> (I'm lost)
[14:44] <crevette> :)
[14:46] <crevette> persia, for nautilus-sendto http://svn.gnome.org/viewvc/nautilus-sendto/trunk/src/plugins/bluetooth.c?view=markup line 32 and after line 377
[14:47] <persia> crevette, Yeah.  That's the issue.
[14:47] <persia> No, I was talking about the pinentry hack, which isn't worth keeping.
[14:47] <crevette> ah I don't it
[14:48] <crevette> +know
[14:48]  * persia didn't really look at bluetooth that much between Breezy and Intrepid, so may have missed a step or two
[14:48]  * crevette didn't look at bluetooth until now
[14:48] <crevette> :)
[14:49] <persia> My memory was that there was a hook into the config file, which if it had a certain value would then call an external helper to ask the user for the PIN (or else use a default PIN in the config file).  This was more fragile than the current state, which is broken, but at least robust.
[14:50] <crevette> there was a bluez-pin yeah
[14:50] <crevette> with dbus activation eventually?
[14:51] <persia> That still sounds a little fragile to me, but it might work well, as various services could use a common tool.
[15:12] <rrittenhouse> When I try Ubuntu umpc on this new Aspire G1, is there a way to restore back to Windows in case the crap hits the fan?
[15:13] <persia> Well, first try the live image.  That lets you test the basics.
[15:13] <rrittenhouse> It is the windows model. The files look to be stored on a 5gb partition on the hd and I'm not sure how I would initiate a restore.
[15:13] <rrittenhouse> ooh ok :) Is there a Wiki entry for this?
[15:13] <persia> It's worth doing a defrag of your windows disk first, but the installer should be able to resize it so you can dual-boot.
[15:14] <persia> When you're satisfied, delete Windows.
[15:14] <rrittenhouse> Does it use that Wubi thing from windows?
[15:15] <persia> Oh, if you have a restore partition, you can probably just install over Windows, and "dual-boot" with the restore partiion.  Personally, I'd be careful, and maybe test with a triple-boot scenario first.
[15:15] <persia> No.  Ubuntu UMPC doesn't work with wubi yet.  Maybe for Jaunty.
[15:15] <rrittenhouse> hmm. Personally I don't like Windows at all but this model had better specs.
[15:15] <rrittenhouse> and it was available at Staples
[15:20] <rrittenhouse> Is the Ubuntu UMPC Edition a live-install ?
[15:21] <persia> Yep.
[15:21] <persia> dd it to USB.  Boot a live session.  If you like it, click "install".  If you don't, try a different flavour of Ubuntu :)
[15:27] <rrittenhouse> persia: I don't have a thumbdrive laying around. Would a spare usb hard drive work?
[15:27] <rrittenhouse> It seems like it would
[15:29] <persia> It might, although dd of 600MB to a hard drive is soemthing that calls for a near-future reformat :)  I'd recommend making sure your device can boot from external USB HD first : some machines balk at booting from real hard drives on USB.
[15:29] <rrittenhouse> Interesting :)
[18:31] <bizkut> os[Linux 2.6.27.2-aao i686] distro[Ubuntu "intrepid" 8.10] cpu[2 x Intel(R) Atom(TM) CPU N270   @ 1.60GHz (GenuineIntel) @ 1.60GHz] mem[Physical: 0.9GB/1.5GB free] disk[Total: 22.1GB/27.9GB free] video[Intel Corporation Mobile 945GME Express Integrated Graphics Controller] sound[HDA-Intel - HDA Intel]
[18:37] <piju> os[Linux 2.6.24-21-generic i686] distro[Debian lenny/sid] cpu[2 x Intel(R) Core(TM)2 Duo CPU     T5450  @ 1.66GHz (GenuineIntel) @ 1.67GHz] mem[Physical: 2.5GB, 75.1% free] disk[Total: 110.0GB, 65.9% free] video[Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller] sound[HDA-Intel - HDA Intel]