Summary: | please stabilize =net-wireless/gnome-bluetooth-0.12 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marcello Magaldi <magowiz> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | amd64, blazej.86, denilsonsa, ppc, x86 |
Priority: | High | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 284661 | ||
Bug Blocks: |
Description
Marcello Magaldi
2009-10-12 11:52:11 UTC
From bug 284661: Me: To me the question is, what needs gnome-bluetooth-0.*? Denilson: It has a bluetooth file transfer applet, that works as an obex server allows receiving files via obex push. I use that to transfer text notes from mobile phone to PC. Unless there is something else that works that way, then the users still need gnome-bluetooth. Me: If I understand it correctly, that functionality is available with bluez-gnome-1.8 applet, which has a "Browse files on device..." under right click that lets you make an obex connection and then show and transfer files with nautilus or other things that use GIO and gvfs. Additionally I should note that gnome-bluetooth-0.12 doesn't install gnome-obex-server anymore, on the premise that gnome-user-share does now. No idea about its stability keyword status right now. Anyhow, I don't see any hurt in stabilizing gnome-bluetooth-0.12, as earlier can't work anymore anyhow due to bluez-libs-3 ebuild dependencies. Arches, please proceed after bluez-4 stabilization is done (In reply to comment #1) > If I understand it correctly, that functionality is available with > bluez-gnome-1.8 applet, which has a "Browse files on device..." under right > click that lets you make an obex connection and then show and transfer files > with nautilus or other things that use GIO and gvfs. What you describe is OBEX File Transfer client. What I was talking about is an OBEX Object Push server. It allows the computer to receive OBEX push objects. That means that I can get my phone and select a text message (which is not a file, and is not browseable from OBEX file transfer) and send it to a nearby device (in this case, my computer). > Additionally I should note that gnome-bluetooth-0.12 doesn't install > gnome-obex-server anymore, on the premise that gnome-user-share does now. No > idea about its stability keyword status right now. Huh... What I've described above was exactly gnome-obex-server. So that means I need to find another OBEX server, or where is the old (or an updated) gnome-obex-server. BTW, if gnome-obex-server is not available anymore in that package, then the official documentation must be updated. (yes, I know, this should be a separate bug, I'm just posting here to not forget to open another bug later, after these things get stabilized) http://www.gentoo.org/doc/en/bluetooth-guide.xml (In reply to comment #2) > What you describe is OBEX File Transfer client. > > What I was talking about is an OBEX Object Push server. It allows the computer > to receive OBEX push objects. > That means that I can get my phone and select a text message (which is not a > file, and is not browseable from OBEX file transfer) and send it to a nearby > device (in this case, my computer). Very good information, I didn't actually know that before, I only recently got a bluetooth phone to use to test some basic things while having to take care of this stabilization only for the purpose of being able to stabilize GNOME-2.26 > > Additionally I should note that gnome-bluetooth-0.12 doesn't install > > gnome-obex-server anymore, on the premise that gnome-user-share does now. No > > idea about its stability keyword status right now. > > Huh... What I've described above was exactly gnome-obex-server. > So that means I need to find another OBEX server, or where is the old (or an > updated) gnome-obex-server. I understood gnome-user-share carries one, can you check it out? And I didn't know we have a bluetooth documentation. Should have known better, I'll try to read it soon :) I tried both bluez-gnome and blueman, blueman is the only one that provides both push client and push server. The only way in bluez-gnome to transfer a file from a device to the linux box is to browse the device and use nautilus to transfer it. gnome-bluetooth-0.12 doesn't seem to provide any of theese functionalities. (In reply to comment #5) > I tried both bluez-gnome and blueman, blueman is the only one that provides > both push client and push server. The only way in bluez-gnome to transfer a > file from a device to the linux box is to browse the device and use nautilus to > transfer it. > gnome-bluetooth-0.12 doesn't seem to provide any of theese functionalities. > So I opened a bug to ask blueman stabilization : http://bugs.gentoo.org/show_bug.cgi?id=288847 *** Bug 291874 has been marked as a duplicate of this bug. *** sparc keyword dropped gnome-bluetooth-0.12 is a dead end since it is not supported at all by upstream. Closing this as WONTFIX since we will go for gnome-bluetooth-2.28 (that I am currently using and works great ;-)) Please go to bug 315275 |