Re: [gentoo-user] KDE4.x installation blocks
Am Dienstag, 8. September 2009 schrieb Massimiliano Ziccardi: > Already done > > localhost ~ # emerge --search bluez | egrep "bluez|installed" | egrep -v > "Homepage|Description" > [ Results for search key : bluez ] > * dev-python/pybluez > Latest version installed: [ Not Installed ] > * net-wireless/bluez > Latest version installed: [ Not Installed ] > * net-wireless/bluez-bluefw > Latest version installed: [ Not Installed ] > * net-wireless/bluez-firmware > Latest version installed: [ Not Installed ] > * net-wireless/bluez-gnome > Latest version installed: [ Not Installed ] > * net-wireless/bluez-hcidump > Latest version installed: [ Not Installed ] > * net-wireless/bluez-hciemu > Latest version installed: [ Not Installed ] > * net-wireless/bluez-libs > Latest version installed: [ Not Installed ] > * net-wireless/bluez-utils > Latest version installed: [ Not Installed ] > * sec-policy/selinux-bluez > Latest version installed: [ Not Installed ] > * x11-plugins/gkrellm-bluez [ Masked ] > Latest version installed: [ Not Installed ] > > > So I guess I don't have bluez anymore.... > > Any other idea? You have some thing installed that needs bluez-3. So if you do --update world, both bluez versions are pulled in, and then they block each other. The solution is to remove the need for both of them, either by removing the package that needs bluez-3 or by removing its dependency on bluez by settings its use flags to bluetooth. $ equery d bluez -- Gruß | Greetings | Qapla' LOL, you said ROFL. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] KDE4.x installation blocks
Already done localhost ~ # emerge --search bluez | egrep "bluez|installed" | egrep -v "Homepage|Description" [ Results for search key : bluez ] * dev-python/pybluez Latest version installed: [ Not Installed ] * net-wireless/bluez Latest version installed: [ Not Installed ] * net-wireless/bluez-bluefw Latest version installed: [ Not Installed ] * net-wireless/bluez-firmware Latest version installed: [ Not Installed ] * net-wireless/bluez-gnome Latest version installed: [ Not Installed ] * net-wireless/bluez-hcidump Latest version installed: [ Not Installed ] * net-wireless/bluez-hciemu Latest version installed: [ Not Installed ] * net-wireless/bluez-libs Latest version installed: [ Not Installed ] * net-wireless/bluez-utils Latest version installed: [ Not Installed ] * sec-policy/selinux-bluez Latest version installed: [ Not Installed ] * x11-plugins/gkrellm-bluez [ Masked ] Latest version installed: [ Not Installed ] So I guess I don't have bluez anymore Any other idea? Thanks. Massimiliano
Re: [gentoo-user] KDE4.x installation blocks
On Friday 04 September 2009 19:32:15 Jim Cunning wrote:
> I am trying to install KDE 4.2 or 4.3 on a stable KDE 3.5.10 system,
> following the guidelines in
> http://www.gentoo.org/proj/en/desktop/kde/kde4-guide.xml, and the emerge
> fails with the following blocks:
> ---
> [blocks B ] net-wireless/bluez-libs ("net-wireless/bluez-libs" is
> blocking net-wireless/bluez-4.39)
> [blocks B ] net-wireless/bluez ("net-wireless/bluez" is blocking
> net-wireless/bluez-libs-3.36)
>
> Total: 294 packages (3 upgrades, 145 new, 141 in new slots, 5 reinstalls),
> Size of downloads: 347,708 kB
> Conflict: 2 blocks (2 unsatisfied)
>
> * Error: The above package list contains packages which cannot be
> * installed at the same time on the same system.
>
> ('installed', '/', 'net-wireless/bluez-libs-3.36', 'nomerge') pulled in
> by
>
> >=net-wireless/bluez-libs-3.12 required by
>
> ('installed', '/', 'gnome-base/gvfs-1.0.3-r2', 'nomerge')
>
> ('ebuild', '/', 'net-wireless/bluez-4.39', 'merge') pulled in by
> net-wireless/bluez required by
> ('ebuild', '/', 'kde-base/solid-4.2.4', 'merge')
> ---
>
> I don't use gnome, but it appears that gnome-base/gvfs is ultimately pulled
> in by net-im/pidgin, which I do use. Does this mean I can't continue
> using pidgin with KDE4? Are there good alternatives to pidgin, including
> OTR (the encrypted plug-in)?
>
bluez and bluez-libs are mutally blocking.
emerge -avC bluez-libs
emerge -av bluez
The message about gcfs is simply the dependency tree so you can see what
causes bluez to be installed/retained, it's not the actual blocker.
IIRC gvfs can use bluez-4. Check the gvfs ebuild to make sure.
--
alan dot mckinnon at gmail dot com
Re: [gentoo-user] KDE4.x installation blocks
Hello,
just remove any bluez 3.x , such as bluez-libs
the problem will be solved.
Best regards,
Gentoo
2009/9/8 Massimiliano Ziccardi
> I have exactly the same problem:
>
> I tried everything (well, everything I'm aware of :-) ) but I always get:
>
> [blocks B ] net-wireless/bluez ("net-wireless/bluez" is blocking
> net-wireless/bluez-libs-3.36)
> [blocks B ] net-wireless/bluez-libs ("net-wireless/bluez-libs" is
> blocking net-wireless/bluez-4.39-r1)
>
>
> Any idea?
>
> Thanks,
> Massimiliano
>
[gentoo-user] bluez
The Gentoo Linux Bluetooth Guide says to emerge net-wireless/bluez-libs and net-wireless/bluez-utils, but what is net-wireless/bluez? If bluez is installed there's blocking. bluez and bluez-utils have the same description "Bluetooth Tools and System Daemons for Linux." What is the difference and when would one be used in place of the other two? Thanks, dhk
Re: [gentoo-user] KDE4.x installation blocks
I have exactly the same problem:
I tried everything (well, everything I'm aware of :-) ) but I always get:
[blocks B ] net-wireless/bluez ("net-wireless/bluez" is blocking
net-wireless/bluez-libs-3.36)
[blocks B ] net-wireless/bluez-libs ("net-wireless/bluez-libs" is
blocking net-wireless/bluez-4.39-r1)
Any idea?
Thanks,
Massimiliano
[gentoo-user] KDE4.x installation blocks
I am trying to install KDE 4.2 or 4.3 on a stable KDE 3.5.10 system, following
the guidelines in http://www.gentoo.org/proj/en/desktop/kde/kde4-guide.xml,
and the emerge fails with the following blocks:
---
[blocks B ] net-wireless/bluez-libs ("net-wireless/bluez-libs" is blocking
net-wireless/bluez-4.39)
[blocks B ] net-wireless/bluez ("net-wireless/bluez" is blocking
net-wireless/bluez-libs-3.36)
Total: 294 packages (3 upgrades, 145 new, 141 in new slots, 5 reinstalls),
Size of downloads: 347,708 kB
Conflict: 2 blocks (2 unsatisfied)
* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
('installed', '/', 'net-wireless/bluez-libs-3.36', 'nomerge') pulled in by
>=net-wireless/bluez-libs-3.12 required by
('installed', '/', 'gnome-base/gvfs-1.0.3-r2', 'nomerge')
('ebuild', '/', 'net-wireless/bluez-4.39', 'merge') pulled in by
net-wireless/bluez required by
('ebuild', '/', 'kde-base/solid-4.2.4', 'merge')
---
I don't use gnome, but it appears that gnome-base/gvfs is ultimately pulled in
by net-im/pidgin, which I do use. Does this mean I can't continue using
pidgin with KDE4? Are there good alternatives to pidgin, including OTR (the
encrypted plug-in)?
--
Jim
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] KDE4.x installation blocks
Am Freitag, 4. September 2009 schrieb Jim Cunning:
> I am trying to install KDE 4.2 or 4.3 on a stable KDE 3.5.10 system,
> following the guidelines in
> http://www.gentoo.org/proj/en/desktop/kde/kde4-guide.xml, and the emerge
> fails with the following blocks:
> ---
> [blocks B ] net-wireless/bluez-libs ("net-wireless/bluez-libs" is
> blocking net-wireless/bluez-4.39)
> [blocks B ] net-wireless/bluez ("net-wireless/bluez" is blocking
> net-wireless/bluez-libs-3.36)
>
> Total: 294 packages (3 upgrades, 145 new, 141 in new slots, 5 reinstalls),
> Size of downloads: 347,708 kB
> Conflict: 2 blocks (2 unsatisfied)
>
> * Error: The above package list contains packages which cannot be
> * installed at the same time on the same system.
>
> ('installed', '/', 'net-wireless/bluez-libs-3.36', 'nomerge') pulled in
> by
>
> >=net-wireless/bluez-libs-3.12 required by
>
> ('installed', '/', 'gnome-base/gvfs-1.0.3-r2', 'nomerge')
>
> ('ebuild', '/', 'net-wireless/bluez-4.39', 'merge') pulled in by
> net-wireless/bluez required by
> ('ebuild', '/', 'kde-base/solid-4.2.4', 'merge')
> ---
>
> I don't use gnome, but it appears that gnome-base/gvfs is ultimately pulled
> in by net-im/pidgin, which I do use. Does this mean I can't continue using
> pidgin with KDE4? Are there good alternatives to pidgin, including OTR
> (the encrypted plug-in)?
I've had (and still have) the same problem. I solved it by removing
kdebluetooth and the current bluez files. Another possibility is to disable
bluetooth support in kde4 by setting USE flags to -bluetooth for the
responsible kde4 packages. (use -t with emerge to see which packages those
are).
--
Gruß | Greetings | Qapla'
IBM - International Bubblegum Machines
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] bluez
On Sat, 13 Mar 2010 16:15:59 -0500, dhk wrote: > The Gentoo Linux Bluetooth Guide says to emerge net-wireless/bluez-libs > and net-wireless/bluez-utils, but what is net-wireless/bluez? If bluez > is installed there's blocking. > What is the difference and when would one be used in place of the other > two? From version 4, libs and utils were combined in the one package. Only use the libs and utils packages if you want the old version. -- Neil Bothwick Top Oxymorons Number 28: Butt Head signature.asc Description: PGP signature
[gentoo-user] Re: Logitech K810 Keyboard On Gentoo?
Hello, I'v solved it. Just recompile bluez and unmerge gnome-bluetooth. Now, K810 works well with me on Gentoo:) B.R Kermit 在 2013-3-13，上午8:46，Kermit 写道： > Hello all, > >I'v bought this keyboard: > http://www.logitech.com/en-roeu/product/bluetooth-illuminated-keyboard-k810?crid=26 > >But I can't used it on Gentoo, I had installed the follow packages: > $ eix blue|grep "^\[I" > [I] net-wireless/bluez > [I] net-wireless/bluez-hcidump > [I] net-wireless/gnome-bluetooth > [I] x11-plugins/gkrellm-bluez > >And with gnome-bluetooth, Apple bluetooth keyboard works well for > me. But when I connect to Logitech K810, it(maybe gnome-bluetooth) > always told me "Setting up 'Logitech K810' failed". > >I saw some one have been used it on ubuntu 12.04: > > http://devasive.blogspot.com/2012/11/ubuntu-1204-persistent-bluetooth-pairing.html > >But I can't find the command such as: > bluez-test-input > bluez-simple-agent > hidd >and so on. > > > How can I deal with it? > > Thanks > B.R > Kermit
[gentoo-user] Logitech K810 Keyboard On Gentoo?
Hello all, I'v bought this keyboard: http://www.logitech.com/en-roeu/product/bluetooth-illuminated-keyboard-k810?crid=26 But I can't used it on Gentoo, I had installed the follow packages: $ eix blue|grep "^\[I" [I] net-wireless/bluez [I] net-wireless/bluez-hcidump [I] net-wireless/gnome-bluetooth [I] x11-plugins/gkrellm-bluez And with gnome-bluetooth, Apple bluetooth keyboard works well for me. But when I connect to Logitech K810, it(maybe gnome-bluetooth) always told me "Setting up 'Logitech K810' failed". I saw some one have been used it on ubuntu 12.04: http://devasive.blogspot.com/2012/11/ubuntu-1204-persistent-bluetooth-pairing.html But I can't find the command such as: bluez-test-input bluez-simple-agent hidd and so on. How can I deal with it? Thanks B.R Kermit
Re: [gentoo-user] KDE4.x installation blocks
equery d bluez did not return anything... localhost ~ # equery d bluez [ Searching for packages depending on bluez... ] localhost ~ # Any other idea? Thank you!!
Re: [gentoo-user] KDE4.x installation blocks
On Dienstag 08 September 2009, Massimiliano Ziccardi wrote: > equery d bluez did not return anything... > > localhost ~ # equery d bluez > [ Searching for packages depending on bluez... ] > localhost ~ # > > Any other idea? > > Thank you!! > yes, get rid of wicd and its dependencies.
Re: [gentoo-user] KDE4.x installation blocks
Am Dienstag, 8. September 2009 schrieb Frank Steinmetzger: > You have some thing installed that needs bluez-3. So if you do --update > world, both bluez versions are pulled in, and then they block each other. > The solution is to remove the need for both of them, either by removing the > package that needs bluez-3 or by removing its dependency on bluez by > settings its use flags to bluetooth. ^ I meant -bluetooth of course. -- Gruß | Greetings | Qapla' Contrariwise, if it was so, it might be; and if it were so, it would be; but as it isn’t, it ain’t. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] 'emerge --update @world -pv' keeps trying to upgrade to a masked package
On Tue, 13 Oct 2015 17:53:54 Marat BN wrote: > Hello there, > > I'm having a curious problem trying to update my system. > > I issue the command: > > emerge --update @world -pv > > > Portage comes back with the following: > > !!! Multiple package instances within a single package slot have been pulled > !!! into the dependency graph, resulting in a slot conflict: > > net-wireless/bluez:0 > >(net-wireless/bluez-4.101-r9:0/0::gentoo, installed) pulled in by >net-wireless/bluez:0/0= required by > (media-sound/pulseaudio-5.0-r7:0/0::gentoo, installed) >^ > (net-wireless/blueman-1.23-r2:0/0::maratbn, installed) >^ ^ > >(net-wireless/bluez-5.33:0/3::gentoo, ebuild scheduled for merge) > pulled in by > >>=net-wireless/bluez-5 required by > > (net-misc/networkmanager-1.0.6:0/0::gentoo, ebuild scheduled for merge) >^^ ^ > > But I have the following line in my '/etc/portage/package.mask': > > =net-misc/networkmanager-1.0.6:0/0::gentoo > > > So doesn't this tell portage not to upgrade to it? Why does it still > schedule it for merge? > > > Thanks a lot, > Marat Try adding "--autounmask-keep-masks y" to your emerge command line, to stop it suggesting that you unmask packages. -- Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/ Asking for technical help in newsgroups? Read this first: http://catb.org/~esr/faqs/smart-questions.html#intro
Re: [gentoo-user] KDE4.x installation blocks
On Dienstag 08 September 2009, Alan McKinnon wrote: > On Tuesday 08 September 2009 14:14:27 Volker Armin Hemmann wrote: > > On Dienstag 08 September 2009, Massimiliano Ziccardi wrote: > > > equery d bluez did not return anything... > > > > > > localhost ~ # equery d bluez > > > [ Searching for packages depending on bluez... ] > > > localhost ~ # > > > > > > Any other idea? > > > > > > Thank you!! > > > > yes, get rid of wicd and its dependencies. > > No, he doesn't need to do that. gksu is one of three options: > > RDEPEND=" > > || ( x11-misc/ktsuss x11-libs/gksu kde-base/kdesu ) > > So he probably wants to do this: > > emerge -av1 kdesu > emerge -avuND world > > This works. I know it works. I have wicd and I do not have gksu and emerge > doesn't feel inclined to tell me to get gksu. > the problem is that gksu is already installed. He has to remove that and all its deps or emerge will always try to pull in bluez-libs.
Re: [gentoo-user] KDE4.x installation blocks
On Dienstag 08 September 2009, Massimiliano Ziccardi wrote: > Yep, sorry. > > Same question : how did you notice the problem was gksu? I didn't notice > any dependency from bluez... > > (I'd like to be able to solve these problems without bother you) > > Thanks, > Massimiliano > from your emerge-log.txt: [nomerge ] net-misc/wicd-1.5.9-r1 [nomerge ] x11-libs/gksu-2.0.2 [nomerge ] gnome-base/nautilus-2.24.2-r3 [nomerge ]gnome-base/gnome-desktop-2.24.3-r1 [nomerge ] dev-python/libgnome-python-2.22.3 [nomerge ] gnome-base/libgnomeui-2.24.1 [nomerge ] gnome-base/libgnome-2.24.1 [nomerge ]gnome-base/gvfs-1.0.3-r2 [ebuild N] net-wireless/bluez-libs-3.36 USE="-debug" wicd is installed and needs/wants gksu. gksu is installed and needs nautilus (wtf?) nautilus is installed and needs gnome-desktop ... gnome gvfs is installed and wants bluez-libs. bluez-libs are not installed, so they are pulled in.
[gentoo-user] 'emerge --update @world -pv' keeps trying to upgrade to a masked package
Hello there, I'm having a curious problem trying to update my system. I issue the command: emerge --update @world -pv Portage comes back with the following: !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: net-wireless/bluez:0 (net-wireless/bluez-4.101-r9:0/0::gentoo, installed) pulled in by net-wireless/bluez:0/0= required by (media-sound/pulseaudio-5.0-r7:0/0::gentoo, installed) ^ =net-wireless/bluez-5 required by (net-misc/networkmanager-1.0.6:0/0::gentoo, ebuild scheduled for merge) ^^ ^ But I have the following line in my '/etc/portage/package.mask': =net-misc/networkmanager-1.0.6:0/0::gentoo So doesn't this tell portage not to upgrade to it? Why does it still schedule it for merge? Thanks a lot, Marat
Re: [gentoo-user] bluez 5 not connecting
On 04/23/14 19:59, cov...@ccs.covici.com wrote: > William Kenworthy wrote: > >> The bluez-5 stack is causing me some problems. It will pair but then >> says its not paired so wont connect. Googling shows lots of problems >> with many saying it suddenly starts working and they don't know what >> happened! >> >> The BT dongle worked fine under bluez-3 and 4. The other end is an >> arduino which needs to be connected via an rfcomm channel (for serial >> comms) and the hardware on both ends has been working for literally years. >> >> After upgrading to bluez-5 it stopped working. >> >> I used bluetoothctl to pair it and info shows it paired and trusted, but >> I cant connect to it: >> >> [bluetooth]# info 00:11:03:17:01:12 >> Device 00:11:03:17:01:12 >> Name: anubis >> Alias: anubis >> Class: 0x001f00 >> Paired: yes >> Trusted: yes >> Blocked: no >> Connected: no >> LegacyPairing: yes >> UUID: Serial Port >> (1101--1000-8000-00805f9b34fb) >> [bluetooth]# connect 00:11:03:17:01:12 >> Attempting to connect to 00:11:03:17:01:12 >> [CHG] Device 00:11:03:17:01:12 Connected: yes >> Failed to connect: org.bluez.Error.NotAvailable >> [CHG] Device 00:11:03:17:01:12 Connected: no >> [bluetooth]# >> >> >> What am I missing/misunderstanding? > > Make sure you have at least 5.14, below that mine did not work at all. > Try the connect from blutoothctl and seewhat it says. Also, you have to > put the device up before you do anything, such as hciconfig hci0 up > whereas before you did not have to do this. > Hi John, the above is bluez 5.15, and the messages above including from the connect command are using bluetoothctl ... Had a play with hcitool and and I cant get a connect with that either. Tried updating bluez to 5.17 and still nothing. BillK
Re: [gentoo-user] more bluetooth troubles with 5.14
On 03/03/14 21:21, cov...@ccs.covici.com wrote: > Mick wrote: > >> On Sunday 02 Mar 2014 13:05:10 cov...@ccs.covici.com wrote: >> >>> I don't even have any /etc/bluetooth/rfcomm.conf. >> What do you have in your /etc/conf.d/bluetooth? This is mine: >> = >> # Bluetooth configuraton file >> >> # Bind rfcomm devices (allowed values are "true" and "false") >> RFCOMM_ENABLE=true >> >> # Config file for rfcomm >> RFCOMM_CONFIG="/etc/bluetooth/rfcomm.conf" >> = >> >> Also, /etc/init.d/bluetooth has a dependency on rfcomm, so it starts it >> first. >> >> I need rfcomm for tethering, but I don't know if it is necessary for your >> needs. Is your rfcomm running? >> >> >>> I did pair, trust and >>> connect with bluetoothctl. Are you using bluetooth5 -- I never had >>> these problems till the upgrade to 5. The device is pretty close to the >>> computer and it does show up on the scan from hcitool. >> No, my bluetooth devices are rather ancient, so I don't know if my set up >> would work with blutooth 5.0 and in any case I don't seem to have >> bluetoothctl. Which program provides it now? I can't fine bluez-utils in >> portage. > I think they may have changed things, in bluetooth 4, I think there was > a separate package, now all seems to be in bluez package. Maybe hcidump > is still separate. > If you have bluez 4, the agent is simple-agent and would not work on 5 > -- they changed the apis. > > correct, bluez-utils was part of bluez 3
Re: [gentoo-user] KDE4.x installation blocks
On Tuesday 08 September 2009 14:56:35 Volker Armin Hemmann wrote: > On Dienstag 08 September 2009, Alan McKinnon wrote: > > On Tuesday 08 September 2009 14:14:27 Volker Armin Hemmann wrote: > > > On Dienstag 08 September 2009, Massimiliano Ziccardi wrote: > > > > equery d bluez did not return anything... > > > > > > > > localhost ~ # equery d bluez > > > > [ Searching for packages depending on bluez... ] > > > > localhost ~ # > > > > > > > > Any other idea? > > > > > > > > Thank you!! > > > > > > yes, get rid of wicd and its dependencies. > > > > No, he doesn't need to do that. gksu is one of three options: > > > > RDEPEND=" > > > > || ( x11-misc/ktsuss x11-libs/gksu kde-base/kdesu ) > > > > So he probably wants to do this: > > > > emerge -av1 kdesu > > emerge -avuND world > > > > This works. I know it works. I have wicd and I do not have gksu and > > emerge doesn't feel inclined to tell me to get gksu. > > the problem is that gksu is already installed. He has to remove that and > all its deps or emerge will always try to pull in bluez-libs. So why are you telling him to get rid of wicd? -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] KDE4.x installation blocks
On Tuesday 08 September 2009 17:11:33 Massimiliano Ziccardi wrote:
> Still no luck...
>
> Attached my new log...
>
> Any other idea?
From your log:
[nomerge ] www-client/mozilla-firefox-3.0.13 USE="dbus gnome startup-
notification xulrunner -bindist -custom-optimization -iceweasel -java -
mozdevelop -restrict-javascript" LINGUAS="-af -ar -be -bg -bn -bn_IN -ca -cs -
cy -da -de -el -en -en_GB -en_US -eo -es -es_AR -es_ES -et -eu -fi -fr -fy -
fy_NL -ga -ga_IE -gl -gu -gu_IN -he -hi -hi_IN -hu -id -is -it -ja -ka -kn -ko
-ku -lt -lv -mk -mn -mr -nb -nb_NO -nl -nn -nn_NO -oc -pa -pa_IN -pl -pt -
pt_BR -pt_PT -ro -ru -si -sk -sl -sq -sr -sv -sv_SE -te -th -tr -uk -zh -zh_CN
-zh_TW"
[nomerge ] gnome-base/libgnomeui-2.24.1 USE="-doc"
[nomerge ] gnome-base/libgnome-2.24.1 USE="esd -debug -doc"
[nomerge ]gnome-base/gvfs-1.0.3-r2 USE="bluetooth gnome hal -archive
-avahi -bash-completion -cdda -debug -doc -fuse -gnome-keyring -gphoto2 -
samba"
[ebuild N] net-wireless/bluez-libs-3.36 USE="-debug" 0 kB
The basic problem is that bluez version 3 and 4 are incompatible. You can have
one or the other but not both. If packages want to give you both, you have to
persuade them to not give you the undesired one.
You need to learn to read the emerge output and see what is causing bluez-
libs-3 to be emerged. In this case it is gvfs. That ebuild says this:
RDEPEND="
...
bluetooth? (
dev-libs/dbus-glib
>=net-wireless/bluez-libs-3.12
And bluez-libs is part of the version 3 package. The only way to solve this is
to stop gvfs from wanting bluez-libs. Several options:
You are installing kde-meta, do you really want all of gnome? Put -gnome in
USE.
Do you really want gnome support in Firefox? Put -gnome in package.use for
firefox
Do you use gvfs to access filesystems over bluetooth? Put -bluetooth in
package.use for gvfs
Do you actually use bluetooth at all? Put -bluetooth in USE
--
alan dot mckinnon at gmail dot com
Re: [gentoo-user] bluez 5 not connecting
William Kenworthy wrote: > On 04/23/14 19:59, cov...@ccs.covici.com wrote: > > William Kenworthy wrote: > > > >> The bluez-5 stack is causing me some problems. It will pair but then > >> says its not paired so wont connect. Googling shows lots of problems > >> with many saying it suddenly starts working and they don't know what > >> happened! > >> > >> The BT dongle worked fine under bluez-3 and 4. The other end is an > >> arduino which needs to be connected via an rfcomm channel (for serial > >> comms) and the hardware on both ends has been working for literally years. > >> > >> After upgrading to bluez-5 it stopped working. > >> > >> I used bluetoothctl to pair it and info shows it paired and trusted, but > >> I cant connect to it: > >> > >> [bluetooth]# info 00:11:03:17:01:12 > >> Device 00:11:03:17:01:12 > >> Name: anubis > >> Alias: anubis > >> Class: 0x001f00 > >> Paired: yes > >> Trusted: yes > >> Blocked: no > >> Connected: no > >> LegacyPairing: yes > >> UUID: Serial Port > >> (1101--1000-8000-00805f9b34fb) > >> [bluetooth]# connect 00:11:03:17:01:12 > >> Attempting to connect to 00:11:03:17:01:12 > >> [CHG] Device 00:11:03:17:01:12 Connected: yes > >> Failed to connect: org.bluez.Error.NotAvailable > >> [CHG] Device 00:11:03:17:01:12 Connected: no > >> [bluetooth]# > >> > >> > >> What am I missing/misunderstanding? > > > > Make sure you have at least 5.14, below that mine did not work at all. > > Try the connect from blutoothctl and seewhat it says. Also, you have to > > put the device up before you do anything, such as hciconfig hci0 up > > whereas before you did not have to do this. > > > > Hi John, the above is bluez 5.15, and the messages above including from > the connect command are using bluetoothctl ... > > Had a play with hcitool and and I cant get a connect with that either. > Tried updating bluez to 5.17 and still nothing. Can you do hcitool scan? If not, do hciconfig hci0 up or whatever your device name if you have more than one. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] KDE4.x installation blocks
On Tuesday 08 September 2009 15:14:40 Volker Armin Hemmann wrote: > On Dienstag 08 September 2009, Alan McKinnon wrote: > > On Tuesday 08 September 2009 14:56:35 Volker Armin Hemmann wrote: > > > On Dienstag 08 September 2009, Alan McKinnon wrote: > > > > On Tuesday 08 September 2009 14:14:27 Volker Armin Hemmann wrote: > > > > > On Dienstag 08 September 2009, Massimiliano Ziccardi wrote: > > > > > > equery d bluez did not return anything... > > > > > > > > > > > > localhost ~ # equery d bluez > > > > > > [ Searching for packages depending on bluez... ] > > > > > > localhost ~ # > > > > > > > > > > > > Any other idea? > > > > > > > > > > > > Thank you!! > > > > > > > > > > yes, get rid of wicd and its dependencies. > > > > > > > > No, he doesn't need to do that. gksu is one of three options: > > > > > > > > RDEPEND=" > > > > > > > > || ( x11-misc/ktsuss x11-libs/gksu kde-base/kdesu ) > > > > > > > > So he probably wants to do this: > > > > > > > > emerge -av1 kdesu > > > > emerge -avuND world > > > > > > > > This works. I know it works. I have wicd and I do not have gksu and > > > > emerge doesn't feel inclined to tell me to get gksu. > > > > > > the problem is that gksu is already installed. He has to remove that > > > and all its deps or emerge will always try to pull in bluez-libs. > > > > So why are you telling him to get rid of wicd? > > because wicd was/is pulling in gksu on his system, which is pulling in > nautilus, which is pulling in a lot of other stuff. Which conflicts with this prior statement of yours: "the problem is that gksu is already installed" If it's already installed, it will pull in bluez. It's in the dep tree not because he wants wicd, but because it is already present. wicd works just fine without gksu. It will use kdesu, which is also fine as he wants to merge kde-meta -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] more bluetooth troubles with 5.14
Samuli Suominen wrote: > > On 03/03/14 21:21, cov...@ccs.covici.com wrote: > > Mick wrote: > > > >> On Sunday 02 Mar 2014 13:05:10 cov...@ccs.covici.com wrote: > >> > >>> I don't even have any /etc/bluetooth/rfcomm.conf. > >> What do you have in your /etc/conf.d/bluetooth? This is mine: > >> = > >> # Bluetooth configuraton file > >> > >> # Bind rfcomm devices (allowed values are "true" and "false") > >> RFCOMM_ENABLE=true > >> > >> # Config file for rfcomm > >> RFCOMM_CONFIG="/etc/bluetooth/rfcomm.conf" > >> = > >> > >> Also, /etc/init.d/bluetooth has a dependency on rfcomm, so it starts it > >> first. > >> > >> I need rfcomm for tethering, but I don't know if it is necessary for your > >> needs. Is your rfcomm running? > >> > >> > >>> I did pair, trust and > >>> connect with bluetoothctl. Are you using bluetooth5 -- I never had > >>> these problems till the upgrade to 5. The device is pretty close to the > >>> computer and it does show up on the scan from hcitool. > >> No, my bluetooth devices are rather ancient, so I don't know if my set up > >> would work with blutooth 5.0 and in any case I don't seem to have > >> bluetoothctl. Which program provides it now? I can't fine bluez-utils in > >> portage. > > I think they may have changed things, in bluetooth 4, I think there was > > a separate package, now all seems to be in bluez package. Maybe hcidump > > is still separate. > > If you have bluez 4, the agent is simple-agent and would not work on 5 > > -- they changed the apis. > > > > > > correct, bluez-utils was part of bluez 3 Yep, I have the same conf.d/bluetooth and my rfcomm is running. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
[gentoo-user] bluez 5 not connecting
The bluez-5 stack is causing me some problems. It will pair but then says its not paired so wont connect. Googling shows lots of problems with many saying it suddenly starts working and they don't know what happened! The BT dongle worked fine under bluez-3 and 4. The other end is an arduino which needs to be connected via an rfcomm channel (for serial comms) and the hardware on both ends has been working for literally years. After upgrading to bluez-5 it stopped working. I used bluetoothctl to pair it and info shows it paired and trusted, but I cant connect to it: [bluetooth]# info 00:11:03:17:01:12 Device 00:11:03:17:01:12 Name: anubis Alias: anubis Class: 0x001f00 Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: yes UUID: Serial Port (1101--1000-8000-00805f9b34fb) [bluetooth]# connect 00:11:03:17:01:12 Attempting to connect to 00:11:03:17:01:12 [CHG] Device 00:11:03:17:01:12 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device 00:11:03:17:01:12 Connected: no [bluetooth]# What am I missing/misunderstanding? BillK
Re: [gentoo-user] bluetooth and headset with gentoo...
Tamer Higazi wrote, at 01/06/2012 11:14 AM:
> People!
> I am not a bluetooth expert how do I configure bluez to make a
> permanent connection with the bluez headset???
>
>
> I did:
>
> pcm.jabra {
> type bluetooth
> }
[snip]
.asoundrc is an audio part of configuration. bebore that you have to:
* configure the kernel to support audio over bluetooth (these settings are for
3.x kernel, for earlier versions these are slightly deffer from showed):
CONFIG_BT=m
CONFIG_BT_L2CAP=y
CONFIG_BT_SCO=y
* install net-wireless/bluez
* configure and pair your headset with host bluetooth adapter using desktop
applet - net-wireless/blueman in my case, or manually - hcitool etc
* enjoy the result :)
hth
victor
Re: [gentoo-user] KDE4.x installation blocks
On Tuesday 08 September 2009 14:14:27 Volker Armin Hemmann wrote: > On Dienstag 08 September 2009, Massimiliano Ziccardi wrote: > > equery d bluez did not return anything... > > > > localhost ~ # equery d bluez > > [ Searching for packages depending on bluez... ] > > localhost ~ # > > > > Any other idea? > > > > Thank you!! > > yes, get rid of wicd and its dependencies. No, he doesn't need to do that. gksu is one of three options: RDEPEND=" || ( x11-misc/ktsuss x11-libs/gksu kde-base/kdesu ) So he probably wants to do this: emerge -av1 kdesu emerge -avuND world This works. I know it works. I have wicd and I do not have gksu and emerge doesn't feel inclined to tell me to get gksu. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] KDE4.x installation blocks
On Dienstag 08 September 2009, Alan McKinnon wrote: > On Tuesday 08 September 2009 14:56:35 Volker Armin Hemmann wrote: > > On Dienstag 08 September 2009, Alan McKinnon wrote: > > > On Tuesday 08 September 2009 14:14:27 Volker Armin Hemmann wrote: > > > > On Dienstag 08 September 2009, Massimiliano Ziccardi wrote: > > > > > equery d bluez did not return anything... > > > > > > > > > > localhost ~ # equery d bluez > > > > > [ Searching for packages depending on bluez... ] > > > > > localhost ~ # > > > > > > > > > > Any other idea? > > > > > > > > > > Thank you!! > > > > > > > > yes, get rid of wicd and its dependencies. > > > > > > No, he doesn't need to do that. gksu is one of three options: > > > > > > RDEPEND=" > > > > > > || ( x11-misc/ktsuss x11-libs/gksu kde-base/kdesu ) > > > > > > So he probably wants to do this: > > > > > > emerge -av1 kdesu > > > emerge -avuND world > > > > > > This works. I know it works. I have wicd and I do not have gksu and > > > emerge doesn't feel inclined to tell me to get gksu. > > > > the problem is that gksu is already installed. He has to remove that and > > all its deps or emerge will always try to pull in bluez-libs. > > So why are you telling him to get rid of wicd? > because wicd was/is pulling in gksu on his system, which is pulling in nautilus, which is pulling in a lot of other stuff.
[gentoo-user] PAN with bluez-utils-3
Hi list! I used to have a working private area network (pan) over bluetooth. However, since the update to net-wireless/bluez-utils-3.36, it doesn't work anymore. I especially want to get rid of the old daemons (USE="-old-daemons") because, as I understand it, they are deprecated. However, I just can't find satisfying documentation on the new structure and config files. I don't want to go into detail on what exactly doesn't work at the moment because I really just guessed how I had to configure everything. So my question is: Does anyone have a working set of configuration files for newer bluez-utils? Preferably something related to the roles GN or NAP. Thanks in advance! Florian Philipp signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] KDE4.x installation blocks
On Dienstag 08 September 2009, Alan McKinnon wrote: > On Tuesday 08 September 2009 17:11:33 Massimiliano Ziccardi wrote: > > Still no luck... > > > > Attached my new log... > > > > Any other idea? > > From your log: > > [nomerge ] www-client/mozilla-firefox-3.0.13 USE="dbus gnome startup- > notification xulrunner -bindist -custom-optimization -iceweasel -java - > mozdevelop -restrict-javascript" LINGUAS="-af -ar -be -bg -bn -bn_IN -ca > -cs - cy -da -de -el -en -en_GB -en_US -eo -es -es_AR -es_ES -et -eu -fi > -fr -fy - fy_NL -ga -ga_IE -gl -gu -gu_IN -he -hi -hi_IN -hu -id -is -it > -ja -ka -kn -ko -ku -lt -lv -mk -mn -mr -nb -nb_NO -nl -nn -nn_NO -oc -pa > -pa_IN -pl -pt - pt_BR -pt_PT -ro -ru -si -sk -sl -sq -sr -sv -sv_SE -te > -th -tr -uk -zh -zh_CN -zh_TW" > [nomerge ] gnome-base/libgnomeui-2.24.1 USE="-doc" > [nomerge ] gnome-base/libgnome-2.24.1 USE="esd -debug -doc" > [nomerge ]gnome-base/gvfs-1.0.3-r2 USE="bluetooth gnome hal > -archive -avahi -bash-completion -cdda -debug -doc -fuse -gnome-keyring > -gphoto2 - samba" > [ebuild N] net-wireless/bluez-libs-3.36 USE="-debug" 0 kB > > The basic problem is that bluez version 3 and 4 are incompatible. You can > have one or the other but not both. If packages want to give you both, you > have to persuade them to not give you the undesired one. > > You need to learn to read the emerge output and see what is causing bluez- > libs-3 to be emerged. In this case it is gvfs. That ebuild says this: > > RDEPEND=" > ... > bluetooth? ( > dev-libs/dbus-glib > > >=net-wireless/bluez-libs-3.12 > > And bluez-libs is part of the version 3 package. The only way to solve this > is to stop gvfs from wanting bluez-libs. Several options: > > You are installing kde-meta, do you really want all of gnome? Put -gnome in > USE. > > Do you really want gnome support in Firefox? Put -gnome in package.use for > firefox > > Do you use gvfs to access filesystems over bluetooth? Put -bluetooth in > package.use for gvfs > > Do you actually use bluetooth at all? Put -bluetooth in USE > That covers pretty much all bases. If you don't wnat gnome - just put -gnome in make.conf (btw -alsa, are you sure about that? you have -alsa, -oss - you don't want sound? set -gnome, if you don't want gnome. Then do an emerge -a --newuse world. Then emerge -a --depclean, and then retry. As long as gvfs with bluetooth flag is around, you will have that blockers. As long as several packages of you have the gnome flag, they will pull in gvfs.
[gentoo-user] Re: 'emerge --update @world -pv' keeps trying to upgrade to a masked package
Ah, I think I figured out what was the problem. Looked down further in the Portage output, and saw this: The following mask changes are necessary to proceed: (see "package.unmask" in the portage(5) man page for more details) # required by gnome-extra/nm-applet-1.0.6::gentoo # required by net-misc/networkmanager-pptp-1.0.6::gentoo[gtk] # required by @selected # required by @world (argument) # /etc/portage/package.mask: # 2015-09-19--01 =net-misc/networkmanager-1.0.6 # required by net-misc/networkmanager-pptp-1.0.6::gentoo[gtk] # required by @selected # required by @world (argument) # /etc/portage/package.mask: # 2015-09-14--01 =gnome-extra/nm-applet-1.0.6 # required by net-misc/networkmanager-1.0.6::gentoo[bluetooth] # required by gnome-extra/nm-applet-1.0.6::gentoo # required by net-misc/networkmanager-pptp-1.0.6::gentoo[gtk] # required by @selected # required by @world (argument) # /etc/portage/package.mask: # 2015-06-22--01 =net-wireless/bluez-5.33 It appears that 'net-misc/networkmanager-1.0.6' was being pulled in by 'gnome-extra/nm-applet-1.0.6::gentoo', 'net-misc/networkmanager-pptp-1.0.6::gentoo[gtk]', and so on, and these were just being reported further down below. So I added them to '/etc/portage/package,mask' as well and the problem went away. -- Marat Original Message Subject: 'emerge --update @world -pv' keeps trying to upgrade to a masked package From: Marat BN To: gentoo-user@lists.gentoo.org Date: 10/13/2015 05:53 PM > Hello there, > > I'm having a curious problem trying to update my system. > > I issue the command: > > emerge --update @world -pv > > > Portage comes back with the following: > > !!! Multiple package instances within a single package slot have been pulled > !!! into the dependency graph, resulting in a slot conflict: > > net-wireless/bluez:0 > >(net-wireless/bluez-4.101-r9:0/0::gentoo, installed) pulled in by >net-wireless/bluez:0/0= required by > (media-sound/pulseaudio-5.0-r7:0/0::gentoo, installed) >^ > > > > (net-wireless/blueman-1.23-r2:0/0::maratbn, installed) >^ ^ > > > > >(net-wireless/bluez-5.33:0/3::gentoo, ebuild scheduled for merge) > pulled in by >>=net-wireless/bluez-5 required by > (net-misc/networkmanager-1.0.6:0/0::gentoo, ebuild scheduled for merge) >^^ ^ > > > > > > > But I have the following line in my '/etc/portage/package.mask': > > =net-misc/networkmanager-1.0.6:0/0::gentoo > > > So doesn't this tell portage not to upgrade to it? Why does it still > schedule it for merge? > > > Thanks a lot, > Marat >
Re: [gentoo-user] KDE4.x installation blocks
I hate this Now I get this error: Calculating dependencies... done! >>> Verifying ebuild manifests !!! Digest verification failed: !!! /usr/portage/dev-python/PyQt4/ChangeLog !!! Reason: Filesize does not match recorded size !!! Got: 11925 !!! Expected: 11928 Have you any idea? Thanks a lot, Massimiliano On 9/8/09, Alan McKinnon wrote: > On Tuesday 08 September 2009 15:14:40 Volker Armin Hemmann wrote: >> On Dienstag 08 September 2009, Alan McKinnon wrote: >> > On Tuesday 08 September 2009 14:56:35 Volker Armin Hemmann wrote: >> > > On Dienstag 08 September 2009, Alan McKinnon wrote: >> > > > On Tuesday 08 September 2009 14:14:27 Volker Armin Hemmann wrote: >> > > > > On Dienstag 08 September 2009, Massimiliano Ziccardi wrote: >> > > > > > equery d bluez did not return anything... >> > > > > > >> > > > > > localhost ~ # equery d bluez >> > > > > > [ Searching for packages depending on bluez... ] >> > > > > > localhost ~ # >> > > > > > >> > > > > > Any other idea? >> > > > > > >> > > > > > Thank you!! >> > > > > >> > > > > yes, get rid of wicd and its dependencies. >> > > > >> > > > No, he doesn't need to do that. gksu is one of three options: >> > > > >> > > > RDEPEND=" >> > > > >> > > > || ( x11-misc/ktsuss x11-libs/gksu kde-base/kdesu ) >> > > > >> > > > So he probably wants to do this: >> > > > >> > > > emerge -av1 kdesu >> > > > emerge -avuND world >> > > > >> > > > This works. I know it works. I have wicd and I do not have gksu and >> > > > emerge doesn't feel inclined to tell me to get gksu. >> > > >> > > the problem is that gksu is already installed. He has to remove that >> > > and all its deps or emerge will always try to pull in bluez-libs. >> > >> > So why are you telling him to get rid of wicd? >> >> because wicd was/is pulling in gksu on his system, which is pulling in >> nautilus, which is pulling in a lot of other stuff. > > Which conflicts with this prior statement of yours: > > "the problem is that gksu is already installed" > > If it's already installed, it will pull in bluez. It's in the dep tree not > because he wants wicd, but because it is already present. > > wicd works just fine without gksu. It will use kdesu, which is also fine as > he > wants to merge kde-meta > > -- > alan dot mckinnon at gmail dot com > >
Re: [gentoo-user] KDE4.x installation blocks
hmm... an emerge-webrsync seems to have solved it Thank you a lot!!! On 9/8/09, Massimiliano Ziccardi wrote: > I hate this Now I get this error: > > Calculating dependencies... done! > >>>> Verifying ebuild manifests > > !!! Digest verification failed: > !!! /usr/portage/dev-python/PyQt4/ChangeLog > !!! Reason: Filesize does not match recorded size > !!! Got: 11925 > !!! Expected: 11928 > > > Have you any idea? > > Thanks a lot, > Massimiliano > > On 9/8/09, Alan McKinnon wrote: >> On Tuesday 08 September 2009 15:14:40 Volker Armin Hemmann wrote: >>> On Dienstag 08 September 2009, Alan McKinnon wrote: >>> > On Tuesday 08 September 2009 14:56:35 Volker Armin Hemmann wrote: >>> > > On Dienstag 08 September 2009, Alan McKinnon wrote: >>> > > > On Tuesday 08 September 2009 14:14:27 Volker Armin Hemmann wrote: >>> > > > > On Dienstag 08 September 2009, Massimiliano Ziccardi wrote: >>> > > > > > equery d bluez did not return anything... >>> > > > > > >>> > > > > > localhost ~ # equery d bluez >>> > > > > > [ Searching for packages depending on bluez... ] >>> > > > > > localhost ~ # >>> > > > > > >>> > > > > > Any other idea? >>> > > > > > >>> > > > > > Thank you!! >>> > > > > >>> > > > > yes, get rid of wicd and its dependencies. >>> > > > >>> > > > No, he doesn't need to do that. gksu is one of three options: >>> > > > >>> > > > RDEPEND=" >>> > > > >>> > > > || ( x11-misc/ktsuss x11-libs/gksu kde-base/kdesu ) >>> > > > >>> > > > So he probably wants to do this: >>> > > > >>> > > > emerge -av1 kdesu >>> > > > emerge -avuND world >>> > > > >>> > > > This works. I know it works. I have wicd and I do not have gksu >>> > > > and >>> > > > emerge doesn't feel inclined to tell me to get gksu. >>> > > >>> > > the problem is that gksu is already installed. He has to remove that >>> > > and all its deps or emerge will always try to pull in bluez-libs. >>> > >>> > So why are you telling him to get rid of wicd? >>> >>> because wicd was/is pulling in gksu on his system, which is pulling in >>> nautilus, which is pulling in a lot of other stuff. >> >> Which conflicts with this prior statement of yours: >> >> "the problem is that gksu is already installed" >> >> If it's already installed, it will pull in bluez. It's in the dep tree >> not >> because he wants wicd, but because it is already present. >> >> wicd works just fine without gksu. It will use kdesu, which is also fine >> as >> he >> wants to merge kde-meta >> >> -- >> alan dot mckinnon at gmail dot com >> >> >
Re: [gentoo-user] Re: bluez 5 not connecting
On 04/24/14 01:06, James wrote: > William Kenworthy iinet.net.au> writes: > > >> The bluez-5 stack is causing me some problems. >> What am I missing/misunderstanding? > > These wireless protocols, have many versions (variants) and > nuances via the prticular hardware that is used. Some light > reading might better postion you? > > > https://www.usenix.org/legacy/event/woot07/tech/full_papers/ > spill/spill_html/index.html > > http://www.ti.com/tool/packet-sniffer > > net-wireless/bluez-hcidump (never tried this one) > > > I would think that there should be some open-source Bluetooth packet > sniffers that may help diagnose the problem. > > I was able to find : > > MAC Address PrefixManufacturer > 001103kawamura electric inc. > > > using the MAC address. Perhaps an email to their tech support > descriping your problems might help? > > I suggest you dissect the packets and hardware and look for the issue > to your problem. Can you move the BT device to a winblozs box and > see if it works? Amplifiers die all the time, particularly if they > are overheated or fed noisy power.. > > could be hardware or software related. dissect the pieces, > > HTH, > good_hunting! > James > > I was able to get it working manually - gentoo's init scripts are out of date with bluez 5, blutoothctl is broken (or probably just poorly documented which equates to the same thing if the command doesn't work) . In bluetoothctl: power on scan on agent on default-agent pair trust exit In a shell: rfcomm bind rfcomm0 do serial port stuff with /dev/rfcomm0 rfcomm unbind rfcomm0 bluetoothctl connect command does not work - connects and immediately disconnects with an error gentoo's rfcomm initscript has removed the -f flag which bluez 5 does not have, but it also looks like the bind all in the 5.17 ebuild is also not supported by late bluez5 so it immediately exits and no rfcomm device is created. Ive adapted my python script to the changes now - but the pairing does not survive restarting bluetooth so I'll need an expect script to set it up each bluetooth re-init as it looks like there are no scripting hooks in bluetoothctl. BillK
[gentoo-user] Re: bluez 5 not connecting
William Kenworthy iinet.net.au> writes: > The bluez-5 stack is causing me some problems. > What am I missing/misunderstanding? These wireless protocols, have many versions (variants) and nuances via the prticular hardware that is used. Some light reading might better postion you? https://www.usenix.org/legacy/event/woot07/tech/full_papers/ spill/spill_html/index.html http://www.ti.com/tool/packet-sniffer net-wireless/bluez-hcidump (never tried this one) I would think that there should be some open-source Bluetooth packet sniffers that may help diagnose the problem. I was able to find : MAC Address Prefix Manufacturer 001103 kawamura electric inc. using the MAC address. Perhaps an email to their tech support descriping your problems might help? I suggest you dissect the packets and hardware and look for the issue to your problem. Can you move the BT device to a winblozs box and see if it works? Amplifiers die all the time, particularly if they are overheated or fed noisy power.. could be hardware or software related. dissect the pieces, HTH, good_hunting! James
Re: [gentoo-user] Re: 'emerge --update @world -pv' keeps trying to upgrade to a masked package
Marat BN wrote: > Ah, I think I figured out what was the problem. Looked down further in > the Portage output, and saw this: > > The following mask changes are necessary to proceed: > (see "package.unmask" in the portage(5) man page for more details) > # required by gnome-extra/nm-applet-1.0.6::gentoo > # required by net-misc/networkmanager-pptp-1.0.6::gentoo[gtk] > # required by @selected > # required by @world (argument) > # /etc/portage/package.mask: > # 2015-09-19--01 > =net-misc/networkmanager-1.0.6 > # required by net-misc/networkmanager-pptp-1.0.6::gentoo[gtk] > # required by @selected > # required by @world (argument) > # /etc/portage/package.mask: > # 2015-09-14--01 > =gnome-extra/nm-applet-1.0.6 > # required by net-misc/networkmanager-1.0.6::gentoo[bluetooth] > # required by gnome-extra/nm-applet-1.0.6::gentoo > # required by net-misc/networkmanager-pptp-1.0.6::gentoo[gtk] > # required by @selected > # required by @world (argument) > # /etc/portage/package.mask: > # 2015-06-22--01 > =net-wireless/bluez-5.33 > > > It appears that 'net-misc/networkmanager-1.0.6' was being pulled in by > 'gnome-extra/nm-applet-1.0.6::gentoo', > 'net-misc/networkmanager-pptp-1.0.6::gentoo[gtk]', and so on, and these > were just being reported further down below. > > So I added them to '/etc/portage/package,mask' as well and the problem > went away. > > > -- Marat > > Original Message > Subject: 'emerge --update @world -pv' keeps trying to upgrade to a > masked package > From: Marat BN > To: gentoo-user@lists.gentoo.org > Date: 10/13/2015 05:53 PM > >> Hello there, >> >> I'm having a curious problem trying to update my system. >> >> I issue the command: >> >> emerge --update @world -pv >> >> >> Portage comes back with the following: >> >> !!! Multiple package instances within a single package slot have been pulled >> !!! into the dependency graph, resulting in a slot conflict: >> >> net-wireless/bluez:0 >> >>(net-wireless/bluez-4.101-r9:0/0::gentoo, installed) pulled in by >>net-wireless/bluez:0/0= required by >> (media-sound/pulseaudio-5.0-r7:0/0::gentoo, installed) >>^ >> >> >> >>> (net-wireless/blueman-1.23-r2:0/0::maratbn, installed) >>^ ^ >> >> >> >> >>(net-wireless/bluez-5.33:0/3::gentoo, ebuild scheduled for merge) >> pulled in by >>>=net-wireless/bluez-5 required by >> (net-misc/networkmanager-1.0.6:0/0::gentoo, ebuild scheduled for merge) >>^^ ^ >> >> >> >> >> >> >> But I have the following line in my '/etc/portage/package.mask': >> >> =net-misc/networkmanager-1.0.6:0/0::gentoo >> >> >> So doesn't this tell portage not to upgrade to it? Why does it still >> schedule it for merge? >> >> >> Thanks a lot, >> Marat >> I started to post that it looked like some other package was pulling it in but portage's output is sometimes cryptic at best. Sometimes I can figure it out but usually, I have to get Alan or Neil to pull out their magic decoder ring and uncrypt the thing. Anyway, glad you got it sorted out and all is well again. Dale :-) :-)
[gentoo-user] bluetooth keyboard on embeded device
Hi all, I have a C-BOX 134 system that I'm using as a mythtv frontend. It's running a VIA Nehemiah 1Ghz processor, which with XvMC can play dvds and ripped movies just fine, but doesn't have a whole lot of horse power for anything else. I recently received a bluetooth keyboard that I'm trying to get working with the system. I can get it working with bluez using the old-daemons use flag and manually running 'hidd --search' while the keyboard is in discoverable mode, so I know it will work, but I'm having a lot of difficulty setting it up. In order to get the keyboard into discoverable mode you have to press a button with a paperclip. Also since it's not paired yet, when the keyboard enters a "sleep" mode, it won't reattach to the pc when it wakes up. So I can't just add the hidd command to the startup scripts and have it work. I've tried to set up the /etc/init.d/hidd startup script, but it doesn't seem to want to connect to the keyboard that way. I've tried bluez-libs/bluez-utils versions 2.25 and 3.36, and bluez 4.39. The 2.x versions gave me compile errors with some undefined variables. 3.x and 4.x seem to work ok, but I can't make sense of the documentation for either one, and the examples that are provided always error out. Does anyone here have a bluetooth keyboard/mouse setup and working? Or does anyone know where a good, working walkthrough/howto/wiki on how to set one up? Thanks in advance. Chris
Re: [gentoo-user] bluez 5 not connecting
William Kenworthy wrote: > The bluez-5 stack is causing me some problems. It will pair but then > says its not paired so wont connect. Googling shows lots of problems > with many saying it suddenly starts working and they don't know what > happened! > > The BT dongle worked fine under bluez-3 and 4. The other end is an > arduino which needs to be connected via an rfcomm channel (for serial > comms) and the hardware on both ends has been working for literally years. > > After upgrading to bluez-5 it stopped working. > > I used bluetoothctl to pair it and info shows it paired and trusted, but > I cant connect to it: > > [bluetooth]# info 00:11:03:17:01:12 > Device 00:11:03:17:01:12 > Name: anubis > Alias: anubis > Class: 0x001f00 > Paired: yes > Trusted: yes > Blocked: no > Connected: no > LegacyPairing: yes > UUID: Serial Port > (1101--1000-8000-00805f9b34fb) > [bluetooth]# connect 00:11:03:17:01:12 > Attempting to connect to 00:11:03:17:01:12 > [CHG] Device 00:11:03:17:01:12 Connected: yes > Failed to connect: org.bluez.Error.NotAvailable > [CHG] Device 00:11:03:17:01:12 Connected: no > [bluetooth]# > > > What am I missing/misunderstanding? Make sure you have at least 5.14, below that mine did not work at all. Try the connect from blutoothctl and seewhat it says. Also, you have to put the device up before you do anything, such as hciconfig hci0 up whereas before you did not have to do this. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] bluetooth and headset with gentoo...
People!
I am not a bluetooth expert how do I configure bluez to make a
permanent connection with the bluez headset???
I did:
pcm.jabra {
type bluetooth
}
pcm.jabra-in {
type plug
slave {
pcm jabra
rate 48000
}
}
ctl.jabra {
type bluetooth
}
but for sure it's not all enough
Please, help me i am still a small baby in this subject
Am 06.01.2012 07:36, schrieb victor romanchuk:
> pcm.genius {
> type bluetooth
> }
> pcm.genius-in {
> type plug
> slave {
> pcm genius
> rate 48000
> }
> }
> ctl.genius {
> type bluetooth
> }
Re: [gentoo-user] How to get hid2hci command -> SOLVED
On 09/16/10 20:34, Kyle Bader wrote: > > net-wireless/bluez maybe? > > Kyle > >> On Sep 16, 2010 1:01 PM, "Hung Dang" > <mailto:hungp...@gmail.com>> wrote: >> >> Hi all, >> >> I need to use hid2hci for my bluetooth keyboad. However, I could not >> figure out how to get the hid2hci command. >> Any suggestion would be appreciate? >> >> Thanks in advance >> Hung Thanks Kyle. I have bluez-4.7.1 installed in my system and it turn out that hid2hci is located at /lib64/udev/ which does not include in system path. Thanks Hung
Re: [gentoo-user] bluetooth and headset with gentoo...
To extend this thread - because of other apps I am using pulse and the
BT headset (Jabra Halo) generally works fine - my only problem is the
microphone when using sjphone which is an oss app. I can hear audio,
pulse indicates it can hear me speaking but sjphone is silent so it
seems to be the oss mic thats the problem - any hints/ideas on what to
do?
BillK
-Original Message-
From: victor romanchuk
Reply-to: gentoo-user@lists.gentoo.org
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] bluetooth and headset with gentoo...
Date: Fri, 06 Jan 2012 11:34:26 +0400
Tamer Higazi wrote, at 01/06/2012 11:14 AM:
> People!
> I am not a bluetooth expert how do I configure bluez to make a
> permanent connection with the bluez headset???
>
>
> I did:
>
> pcm.jabra {
> type bluetooth
> }
[snip]
.asoundrc is an audio part of configuration. bebore that you have to:
* configure the kernel to support audio over bluetooth (these settings are for
3.x kernel, for earlier versions these are slightly deffer from showed):
CONFIG_BT=m
CONFIG_BT_L2CAP=y
CONFIG_BT_SCO=y
* install net-wireless/bluez
* configure and pair your headset with host bluetooth adapter using desktop
applet - net-wireless/blueman in my case, or manually - hcitool etc
* enjoy the result :)
hth
victor
Re: [gentoo-user] Re: bluez 5 not connecting
On Thursday 24 Apr 2014 02:11:57 William Kenworthy wrote: > I was able to get it working manually - gentoo's init scripts are out of > date with bluez 5, blutoothctl is broken (or probably just poorly > documented which equates to the same thing if the command doesn't work) . > > In bluetoothctl: > power on > scan on > agent on > default-agent > pair > trust > exit > > In a shell: > rfcomm bind rfcomm0 > > do serial port stuff with /dev/rfcomm0 > > rfcomm unbind rfcomm0 > > bluetoothctl connect command does not work - connects and immediately > disconnects with an error > gentoo's rfcomm initscript has removed the -f flag which bluez 5 does > not have, but it also looks like the bind all in the 5.17 ebuild is also > not supported by late bluez5 so it immediately exits and no rfcomm > device is created. > > Ive adapted my python script to the changes now - but the pairing does > not survive restarting bluetooth so I'll need an expect script to set it > up each bluetooth re-init as it looks like there are no scripting hooks > in bluetoothctl. > > BillK Thanks BillK, your suggestions above helped somewhat, because I was able to connect with my phone, but it didn't get me far enough. I was not able to connect with rfcomm to my mobile. When I ran 'pon ' pppd started, but I got errors like: Apr 26 18:15:12 dell_xps chat[29579]: -- write failed: Transport endpoint is not connected Apr 26 18:15:12 dell_xps chat[29579]: Failed This was despite the fact that I had created manually the rfcomm0 device and binded it to the bdaddr of my phone as you suggested. Googling for this error revealed that this is because the rfcomm code has changed - but there is a patch which may fix things: http://comments.gmane.org/gmane.linux.bluez.kernel/42303 I ran out of time and did not try 'rfcomm connect' instead of 'rfcomm bind' to see if it makes a difference in my case. FYI, I'm on net-wireless/bluez-5.15 and kernel 3.12.13-gentoo. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Bluetooth is impossible
>>> I have a TRENDnet TBW-105UB USB bluetooth adapter and Motorola H560
>>> bluetooth headset, and I'm trying to use them with twinkle VOIP
>>> software. I've spent at least 8 hours today following up with every
>>> single lead and I can't figure out how this is supposed to work. I
>>> think I don't have the 2 devices "pairing". The instructions here:
>>>
>>> http://www.gentoo.org/doc/en/bluetooth-guide.xml
>>>
>>> seem to be completely outdated. I installed blueman in the hopes that
>>> it would help facilitate pairing, but I only get python errors when I
>>> try to run the binaries. Is it gnome-only? I'm running xfce4.
>>
>> Dumb question, Grant, but you are using the right passkey, right?
>>
>> These headsets have it built into them, and you usually have to do something
>> like hold down the headset's power button for 4 or 6 seconds (instead of
>> just pushing it and letting go, as you would normally do to power on the
>> device) and the indicator light will flash (or flash more slowly than usual,
>> or change colour or in some other way indicate it's doing things
>> differently). This initiates pairing mode on the headset, and you have 10 or
>> 20 seconds to pair.
>>
>> The passkey of the headset is usually fixed at , but check the manual.
>> You can't change it, and you'll need to match your PC to that.
>>
>> It seems like you're a bit frustrated by all this, the way you've posted
>> without giving us any information. If you're struggling with the concept of
>> pairing, then I suggest you try pairing the headset with your phone & using
>> it, just to get the hang of it. If you don't have a bluetooth phone, maybe
>> you could borrow one? Usually headsets pair with phones pretty easily, first
>> or second time, just as soon as you've worked out which of the tiny little
>> buttons to hold in the right way for pairing. Once you've got this sussed
>> out it'll pair immediately - or even automatically - with your PC.
>>
>> The article doesn't look *that* out of date to me, as it mentions "... with
>>>=bluez-libs-3.x and >=bluez-utils-3.x, pin helpers have been replaced..."
>> and here on my systems versions 2.25 are still marked as stable. On the
>> other hand I see that 3.36 is marked as stable, too. :/
>>
>> Stroller.
>
> Thank you for taking the time to write, and I'm sorry my frustration
> shined through. I got blueman running and everything is working now.
> To get blueman running I had to use the dbus bluetooth.conf from here:
>
> http://bugs.gentoo.org/275470
>
> and run blueman-applet and then blueman-manager.
>
> That Gentoo Bluetooth page really is way out of date. I reverted back
> to original everything, and the only info I needed from that page was
> the kernel config. Absolutely nothing else necessary except for
> emerging blueman, copying the dbus bluetooth.conf from above, and
> starting /etc/init.d/bluetooth. That page refers to bluez-utils-3.*
> and bluez-libs-3.* which are both deprecated and the config is
> different. bluetooth stuff in portage depends on bluez-4.* which
> blocks the other two.
>
> Also, it was necessary to add the following to /etc/asound.conf and
> specify "bluetooth" for the alsa devices in twinkle:
>
> pcm.bluetooth {
> type bluetooth
> device 00:1F:82:14:7F:11
> }
>
> You mentioned that the headset's PIN can't be changed. Couldn't
> anybody pair with it if they enter ?
>
> - Grant
Using the blueman-1.21 ebuild is really the secret to success here:
http://bugs.gentoo.org/show_bug.cgi?id=289902
All that is required is emerge bluez, reload dbus, start bluetooth,
emerge blueman-1.21, config asound.conf as above, and restart
alsasound.
Has anyone gotten bluetooth pairing without a GUI tool such as
blueman? That's the "impossible" part.
- Grant
Re: [gentoo-user] Re: 'emerge --update @world -pv' keeps trying to upgrade to a masked package
On 14/10/2015 03:53, Dale wrote: > Marat BN wrote: >> Ah, I think I figured out what was the problem. Looked down further in >> the Portage output, and saw this: >> >> The following mask changes are necessary to proceed: >> (see "package.unmask" in the portage(5) man page for more details) >> # required by gnome-extra/nm-applet-1.0.6::gentoo >> # required by net-misc/networkmanager-pptp-1.0.6::gentoo[gtk] >> # required by @selected >> # required by @world (argument) >> # /etc/portage/package.mask: >> # 2015-09-19--01 >> =net-misc/networkmanager-1.0.6 >> # required by net-misc/networkmanager-pptp-1.0.6::gentoo[gtk] >> # required by @selected >> # required by @world (argument) >> # /etc/portage/package.mask: >> # 2015-09-14--01 >> =gnome-extra/nm-applet-1.0.6 >> # required by net-misc/networkmanager-1.0.6::gentoo[bluetooth] >> # required by gnome-extra/nm-applet-1.0.6::gentoo >> # required by net-misc/networkmanager-pptp-1.0.6::gentoo[gtk] >> # required by @selected >> # required by @world (argument) >> # /etc/portage/package.mask: >> # 2015-06-22--01 >> =net-wireless/bluez-5.33 >> >> >> It appears that 'net-misc/networkmanager-1.0.6' was being pulled in by >> 'gnome-extra/nm-applet-1.0.6::gentoo', >> 'net-misc/networkmanager-pptp-1.0.6::gentoo[gtk]', and so on, and these >> were just being reported further down below. >> >> So I added them to '/etc/portage/package,mask' as well and the problem >> went away. >> >> >> -- Marat >> >> Original Message >> Subject: 'emerge --update @world -pv' keeps trying to upgrade to a >> masked package >> From: Marat BN >> To: gentoo-user@lists.gentoo.org >> Date: 10/13/2015 05:53 PM >> >>> Hello there, >>> >>> I'm having a curious problem trying to update my system. >>> >>> I issue the command: >>> >>> emerge --update @world -pv >>> >>> >>> Portage comes back with the following: >>> >>> !!! Multiple package instances within a single package slot have been pulled >>> !!! into the dependency graph, resulting in a slot conflict: >>> >>> net-wireless/bluez:0 >>> >>>(net-wireless/bluez-4.101-r9:0/0::gentoo, installed) pulled in by >>>net-wireless/bluez:0/0= required by >>> (media-sound/pulseaudio-5.0-r7:0/0::gentoo, installed) >>>^ >>> >>> >>> >>>>> (net-wireless/blueman-1.23-r2:0/0::maratbn, installed) >>>^ ^ >>> >>> >>> >>> >>>(net-wireless/bluez-5.33:0/3::gentoo, ebuild scheduled for merge) >>> pulled in by >>>>=net-wireless/bluez-5 required by >>> (net-misc/networkmanager-1.0.6:0/0::gentoo, ebuild scheduled for merge) >>>^^ ^ >>> >>> >>> >>> >>> >>> >>> But I have the following line in my '/etc/portage/package.mask': >>> >>> =net-misc/networkmanager-1.0.6:0/0::gentoo >>> >>> >>> So doesn't this tell portage not to upgrade to it? Why does it still >>> schedule it for merge? >>> >>> >>> Thanks a lot, >>> Marat >>> > > I started to post that it looked like some other package was pulling it > in but portage's output is sometimes cryptic at best. Sometimes I can > figure it out but usually, I have to get Alan or Neil to pull out their > magic decoder ring and uncrypt the thing. > > Anyway, glad you got it sorted out and all is well again. To figure out that "required by/pulled in by/installed" listing, you have to think like a programmer. That whole listing is not so much portage telling you what it will do, it's portage telling you how it got to the point where there's a problem. Think of it like debugger output - emerge runs, there's a problem and the dev asks for a memory dump of the dep tree emerge has evaluated so far. A little bit lower you find the helpful hint the some judicious unmasking might get around it. But what's really missing is a clear message about a mask. Portage is often like a 10 year old telling you why they are upset. Lots of tears and wailing, but no real description of /why/... :-) -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] Still not feeling familiar with emerge
Dear group,
I'm using gentoo for more than three years now and using the gentoo packaging
system
in general is exactly what I expect from a packaging system. You just open a
shell
somewhere on your virtual desktop, start a process and the rest is done
automatically
(in general).
But, when it comes to packages blocking each other I simply have to guess, what
to do next
and sometimes I fail in guessing the right things I once removed the wrong
package,
which left me with a system without working packaging system - a very bad
experience. In fact
I could only solve this problem by copying a dynamic library from another linux
installation
to reanimate emerge.
So some weeks ago I was too busy to take care of some conflicts caused by the
end of support
for KDE 3.5). I stopped updating, because I didn't have the time to switch to
newer KDE
version and wanted to do that later on.
Now I want to upgrade, but I would like to better understand the messages
telling me the
conflicting packets. A current call to 'emerge --update --deep --ask world'
gives me the
following conflicts:
* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
('installed', '/', 'sys-fs/device-mapper-1.02.24-r1', 'nomerge') pulled in by
>=sys-fs/device-mapper-1.00.07-r1 required by ('installed', '/',
'sys-fs/cryptsetup-1.0.6-r2', 'nomerge')
('ebuild', '/', 'kde-base/kdebase-data-4.3.3', 'merge') pulled in by
>=kde-base/kdebase-data-4.3.3[-kdeprefix] required by ('ebuild', '/',
'kde-base/kdelibs-4.3.3-r1', 'merge')
>=kde-base/kdebase-data-4.3.3[-kdeprefix] required by ('ebuild', '/',
'kde-base/kdebase-meta-4.3.3', 'merge')
('installed', '/', 'app-arch/lzma-utils-4.32.7', 'nomerge') pulled in by
app-arch/lzma-utils required by ('ebuild', '/', 'dev-libs/mpfr-2.4.1_p5',
'merge')
app-arch/lzma-utils required by ('ebuild', '/',
'dev-texlive/texlive-basic-2008-r1', 'merge')
app-arch/lzma-utils required by ('ebuild', '/',
'dev-texlive/texlive-latex-2008-r2', 'merge')
(and 5 more)
('installed', '/', 'kde-base/akregator-3.5.10', 'nomerge') pulled in by
>=kde-base/akregator-3.5.10:3.5 required by ('installed', '/',
'kde-base/konqueror-akregator-3.5.10', 'nomerge')
('ebuild', '/', 'sys-fs/udev-146-r1', 'merge') pulled in by
virtual/dev-manager required by world
>=sys-fs/udev-103 required by ('ebuild', '/', 'media-gfx/iscan-2.21.0',
'merge')
>=sys-fs/udev-124 required by ('installed', '/',
'sys-fs/cryptsetup-1.0.6-r2', 'nomerge')
(and 3 more)
('ebuild', '/', 'net-wireless/bluez-4.39-r2', 'merge') pulled in by
net-wireless/bluez required by ('ebuild', '/', 'gnome-base/gvfs-1.2.3',
'merge')
net-wireless/bluez required by ('ebuild', '/', 'kde-base/solid-4.3.3',
'merge')
('ebuild', '/', 'kde-base/akregator-4.3.3', 'merge') pulled in by
>=kde-base/akregator-4.3.3[-kdeprefix] required by ('ebuild', '/',
'kde-base/kdepim-meta-4.3.3', 'merge')
('ebuild', '/', 'app-arch/xz-utils-4.999.9_beta', 'merge') pulled in by
app-arch/xz-utils required by ('ebuild', '/',
'app-arch/libarchive-2.7.1-r1', 'merge')
('installed', '/', 'net-wireless/bluez-libs-3.36', 'nomerge') pulled in by
net-wireless/bluez-libs required by ('installed', '/',
'net-libs/libpcap-1.0.0-r2', 'nomerge')
('installed', '/', 'kde-base/kdebase-data-3.5.10', 'nomerge') pulled in by
>=kde-base/kdebase-data-3.5.10:3.5 required by ('installed', '/',
'kde-base/kcontrol-3.5.10', 'nomerge')
>=kde-base/kdebase-data-3.5.10:3.5 required by ('installed', '/',
'kde-base/kicker-3.5.10-r1', 'nomerge')
For me some of the messages are mysterious. What is e.g. the exact meaning of
the four components in
('ebuild', '/', 'net-wireless/bluez-4.39-r2', 'merge') or
('installed', '/', 'kde-base/akregator-3.5.10', 'nomerge')
How should I resolve the conflict
net-libs/libpcap-1.0.0-r2 versus gnome-base/gvfs-1.2.3 and
kde-base/solid-4.3.3
I don't even have any bluetooth device in my computer. Should I fiddle with the
USE flags of
KDE and Gnome or libpcap to avoid they pull in net-wireless/bluez?
Which packets are causing the device-mapper conflict?
What is the most secure way to switch to KDE 4? Should I remove the packages
konqueror-akregator,
kcontrol and kicker, then update to KDE 4 and then reinstall those packets?
Maybe someone can explain how to proceed best. Are there some things I can
check using
equery or whatsoever to support my decisions? I'm feeling unsure how to handle
these
problems keeping the risk to leave my system (partially) unusable as small as
possible.
Maybe someone can give me a hint, where to find more information about how to
handle conflicts
in the packaging system.
Sorry for the long mail.
Cheers, Heinz
Re: [gentoo-user] more bluetooth troubles with 5.14
Mick wrote: > On Sunday 02 Mar 2014 13:05:10 cov...@ccs.covici.com wrote: > > > I don't even have any /etc/bluetooth/rfcomm.conf. > > What do you have in your /etc/conf.d/bluetooth? This is mine: > = > # Bluetooth configuraton file > > # Bind rfcomm devices (allowed values are "true" and "false") > RFCOMM_ENABLE=true > > # Config file for rfcomm > RFCOMM_CONFIG="/etc/bluetooth/rfcomm.conf" > = > > Also, /etc/init.d/bluetooth has a dependency on rfcomm, so it starts it first. > > I need rfcomm for tethering, but I don't know if it is necessary for your > needs. Is your rfcomm running? > > > > I did pair, trust and > > connect with bluetoothctl. Are you using bluetooth5 -- I never had > > these problems till the upgrade to 5. The device is pretty close to the > > computer and it does show up on the scan from hcitool. > > No, my bluetooth devices are rather ancient, so I don't know if my set up > would work with blutooth 5.0 and in any case I don't seem to have > bluetoothctl. Which program provides it now? I can't fine bluez-utils in > portage. I think they may have changed things, in bluetooth 4, I think there was a separate package, now all seems to be in bluez package. Maybe hcidump is still separate. If you have bluez 4, the agent is simple-agent and would not work on 5 -- they changed the apis. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] Re: bluez 5 not connecting
On 04/27/14 02:33, Mick wrote: > On Thursday 24 Apr 2014 02:11:57 William Kenworthy wrote: > >> I was able to get it working manually - gentoo's init scripts are out of >> date with bluez 5, blutoothctl is broken (or probably just poorly >> documented which equates to the same thing if the command doesn't work) . >> >> In bluetoothctl: >> power on >> scan on >> agent on >> default-agent >> pair >> trust >> exit >> >> In a shell: >> rfcomm bind rfcomm0 >> >> do serial port stuff with /dev/rfcomm0 >> >> rfcomm unbind rfcomm0 >> >> bluetoothctl connect command does not work - connects and immediately >> disconnects with an error >> gentoo's rfcomm initscript has removed the -f flag which bluez 5 does >> not have, but it also looks like the bind all in the 5.17 ebuild is also >> not supported by late bluez5 so it immediately exits and no rfcomm >> device is created. >> >> Ive adapted my python script to the changes now - but the pairing does >> not survive restarting bluetooth so I'll need an expect script to set it >> up each bluetooth re-init as it looks like there are no scripting hooks >> in bluetoothctl. >> >> BillK > > Thanks BillK, your suggestions above helped somewhat, because I was able to > connect with my phone, but it didn't get me far enough. I was not able to > connect with rfcomm to my mobile. When I ran 'pon ' pppd > started, but I got errors like: > > Apr 26 18:15:12 dell_xps chat[29579]: -- write failed: Transport endpoint is > not connected > Apr 26 18:15:12 dell_xps chat[29579]: Failed > > > This was despite the fact that I had created manually the rfcomm0 device and > binded it to the bdaddr of my phone as you suggested. > > Googling for this error revealed that this is because the rfcomm code has > changed - but there is a patch which may fix things: > > http://comments.gmane.org/gmane.linux.bluez.kernel/42303 > > > I ran out of time and did not try 'rfcomm connect' instead of 'rfcomm bind' > to > see if it makes a difference in my case. > > FYI, I'm on net-wireless/bluez-5.15 and kernel 3.12.13-gentoo. > I just upgraded to 3.12.13 and it stopped working with the same error you have. I did see some other messages saying that certain kernel versions are broken but I'll now need to look into that now. BillK
Re: [gentoo-user] Bluetooth speakers
Peter: ... > What would help is some idea of how the whole BT system works, ... There are two incompatible types of bluetooth: Bluetooth Low Energy (BLE) Bluetooth Classic see: https://www.bluetooth.com/learn-about-bluetooth/tech-overview/ You must check which generation of bluetooth your speaker uses. If your speaker uses the classic type, this might help you: https://wiki.debian.org/Bluetooth/Alsa /// More info about bluetooth: https://en.wikipedia.org/wiki/Bluetooth https://www.bluetooth.com/specifications/specs/ /// Current linux bluetooth tools (http://www.bluez.org/) doesn't handle bluetooth classic, unless you build bluez with --enable-deprecated configure option. Also, bluez has dropped direct /dev file access for users, you have to set up and go through dbus regardless wether you like it or not. Regards, /Karl Hammar
Re: [gentoo-user] Bluetooth is impossible
>> I have a TRENDnet TBW-105UB USB bluetooth adapter and Motorola H560
>> bluetooth headset, and I'm trying to use them with twinkle VOIP
>> software. I've spent at least 8 hours today following up with every
>> single lead and I can't figure out how this is supposed to work. I
>> think I don't have the 2 devices "pairing". The instructions here:
>>
>> http://www.gentoo.org/doc/en/bluetooth-guide.xml
>>
>> seem to be completely outdated. I installed blueman in the hopes that
>> it would help facilitate pairing, but I only get python errors when I
>> try to run the binaries. Is it gnome-only? I'm running xfce4.
>
> Dumb question, Grant, but you are using the right passkey, right?
>
> These headsets have it built into them, and you usually have to do something
> like hold down the headset's power button for 4 or 6 seconds (instead of
> just pushing it and letting go, as you would normally do to power on the
> device) and the indicator light will flash (or flash more slowly than usual,
> or change colour or in some other way indicate it's doing things
> differently). This initiates pairing mode on the headset, and you have 10 or
> 20 seconds to pair.
>
> The passkey of the headset is usually fixed at , but check the manual.
> You can't change it, and you'll need to match your PC to that.
>
> It seems like you're a bit frustrated by all this, the way you've posted
> without giving us any information. If you're struggling with the concept of
> pairing, then I suggest you try pairing the headset with your phone & using
> it, just to get the hang of it. If you don't have a bluetooth phone, maybe
> you could borrow one? Usually headsets pair with phones pretty easily, first
> or second time, just as soon as you've worked out which of the tiny little
> buttons to hold in the right way for pairing. Once you've got this sussed
> out it'll pair immediately - or even automatically - with your PC.
>
> The article doesn't look *that* out of date to me, as it mentions "... with
>>=bluez-libs-3.x and >=bluez-utils-3.x, pin helpers have been replaced..."
> and here on my systems versions 2.25 are still marked as stable. On the
> other hand I see that 3.36 is marked as stable, too. :/
>
> Stroller.
Thank you for taking the time to write, and I'm sorry my frustration
shined through. I got blueman running and everything is working now.
To get blueman running I had to use the dbus bluetooth.conf from here:
http://bugs.gentoo.org/275470
and run blueman-applet and then blueman-manager.
That Gentoo Bluetooth page really is way out of date. I reverted back
to original everything, and the only info I needed from that page was
the kernel config. Absolutely nothing else necessary except for
emerging blueman, copying the dbus bluetooth.conf from above, and
starting /etc/init.d/bluetooth. That page refers to bluez-utils-3.*
and bluez-libs-3.* which are both deprecated and the config is
different. bluetooth stuff in portage depends on bluez-4.* which
blocks the other two.
Also, it was necessary to add the following to /etc/asound.conf and
specify "bluetooth" for the alsa devices in twinkle:
pcm.bluetooth {
type bluetooth
device 00:1F:82:14:7F:11
}
You mentioned that the headset's PIN can't be changed. Couldn't
anybody pair with it if they enter ?
- Grant
[gentoo-user] nvidia module won't load after updates
from dmesg nvidia: version magic '2.6.14-gentoo-r4 K7 gcc-3.4' should be '2.6.14-gentoo-r42.6.14-r-4_new K7 gcc-3.3' This looks like the kernel was compiled with gcc-3.3 and nvidia-kernel was compiled with gcc-3.4. Do I need to rebuild my kernel? I know I've restarted x since updating gcc on 12/6/05 $ gcc-config -c i686-pc-linux-gnu-3.4.4 How can I find what gcc version my kernel was built with? Recent updates: pygtk-2.8.2 bluez-utils-2.22-r1 bluez-libs-2.22 gst-plugins-flac-0.8.11 gst-plugins-vorbis-0.8.11 gst-plugins-ogg-0.8.11 gst-plugins-mad-0.8.11 gtk-gnutella-0.95.4-r1 coreutils-5.2.1-r7 nvidia-kernel-1.0.6629-r5 -- Regards, Ernie -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] bluetooth headset and espeak
On Sun, May 23, 2010 at 7:20 AM, W.Kenworthy wrote:
[...]
> It looks like bluez is continually changing so most of the guides Ive
> found dont apply - I am using bluez-4.39. alsamixer etc dont list the
> bluetooth device and I cant see it in /proc/asound, but its obviously
> there if mplayer can access it!
With:
gnome-base/gnome-2.28.2
net-wireless/gnome-bluetooth-2.28.6
media-sound/pulseaudio-0.9.21.1
You only go to System->Preferences->Bluetooh, "Set new device...",
detect and connect yo your headset, and then System->Sound, in the
output tab you select your headset, and all the PulseAudio
applications will output sound through your headset.
If also you have
pcm.!default {
type pulse
}
ctl.!default {
type pulse
}
in your ~/.asoundrc, all the ALSA applications will use PulseAudio,
and then it will work for them too.
Regards.
--
Canek Peláez Valdés
Instituto de Matemáticas
Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: bluez 5 not connecting
On 04/27/14 11:14, William Kenworthy wrote: > On 04/27/14 02:33, Mick wrote: >> On Thursday 24 Apr 2014 02:11:57 William Kenworthy wrote: >> >>> I was able to get it working manually - gentoo's init scripts are out of >>> date with bluez 5, blutoothctl is broken (or probably just poorly >>> documented which equates to the same thing if the command doesn't work) . >>> >>> In bluetoothctl: >>> power on >>> scan on >>> agent on >>> default-agent >>> pair >>> trust >>> exit >>> >>> In a shell: >>> rfcomm bind rfcomm0 >>> >>> do serial port stuff with /dev/rfcomm0 >>> >>> rfcomm unbind rfcomm0 >>> >>> bluetoothctl connect command does not work - connects and immediately >>> disconnects with an error >>> gentoo's rfcomm initscript has removed the -f flag which bluez 5 does >>> not have, but it also looks like the bind all in the 5.17 ebuild is also >>> not supported by late bluez5 so it immediately exits and no rfcomm >>> device is created. >>> >>> Ive adapted my python script to the changes now - but the pairing does >>> not survive restarting bluetooth so I'll need an expect script to set it >>> up each bluetooth re-init as it looks like there are no scripting hooks >>> in bluetoothctl. >>> >>> BillK >> >> Thanks BillK, your suggestions above helped somewhat, because I was able to >> connect with my phone, but it didn't get me far enough. I was not able to >> connect with rfcomm to my mobile. When I ran 'pon ' pppd >> started, but I got errors like: >> >> Apr 26 18:15:12 dell_xps chat[29579]: -- write failed: Transport endpoint >> is >> not connected >> Apr 26 18:15:12 dell_xps chat[29579]: Failed >> >> >> This was despite the fact that I had created manually the rfcomm0 device and >> binded it to the bdaddr of my phone as you suggested. >> >> Googling for this error revealed that this is because the rfcomm code has >> changed - but there is a patch which may fix things: >> >> http://comments.gmane.org/gmane.linux.bluez.kernel/42303 >> >> >> I ran out of time and did not try 'rfcomm connect' instead of 'rfcomm bind' >> to >> see if it makes a difference in my case. >> >> FYI, I'm on net-wireless/bluez-5.15 and kernel 3.12.13-gentoo. >> > > I just upgraded to 3.12.13 and it stopped working with the same error > you have. > > I did see some other messages saying that certain kernel versions are > broken but I'll now need to look into that now. > > BillK > > > I used the patch from the reply above - worked! It did take a couple of goes but after restarting the bluetooth initscript before using bluetoothctl via expect (took 3 goes before I got a clean run from "expect" - timing might need adjusting?) BillK
Re: [gentoo-user] Re: bluez 5 not connecting
On Sunday 27 Apr 2014 08:27:31 William Kenworthy wrote: > On 04/27/14 11:14, William Kenworthy wrote: > > On 04/27/14 02:33, Mick wrote: > >> On Thursday 24 Apr 2014 02:11:57 William Kenworthy wrote: > >>> I was able to get it working manually - gentoo's init scripts are out > >>> of date with bluez 5, blutoothctl is broken (or probably just poorly > >>> documented which equates to the same thing if the command doesn't > >>> work) . > >>> > >>> In bluetoothctl: > >>> power on > >>> scan on > >>> agent on > >>> default-agent > >>> pair > >>> trust > >>> exit > >>> > >>> In a shell: > >>> rfcomm bind rfcomm0 > >>> > >>> do serial port stuff with /dev/rfcomm0 > >>> > >>> rfcomm unbind rfcomm0 > >>> > >>> bluetoothctl connect command does not work - connects and immediately > >>> disconnects with an error > >>> gentoo's rfcomm initscript has removed the -f flag which bluez 5 does > >>> not have, but it also looks like the bind all in the 5.17 ebuild is > >>> also not supported by late bluez5 so it immediately exits and no > >>> rfcomm device is created. > >>> > >>> Ive adapted my python script to the changes now - but the pairing does > >>> not survive restarting bluetooth so I'll need an expect script to set > >>> it up each bluetooth re-init as it looks like there are no scripting > >>> hooks in bluetoothctl. > >>> > >>> BillK > >> > >> Thanks BillK, your suggestions above helped somewhat, because I was able > >> to connect with my phone, but it didn't get me far enough. I was not > >> able to connect with rfcomm to my mobile. When I ran 'pon > >> ' pppd started, but I got errors like: > >> > >> Apr 26 18:15:12 dell_xps chat[29579]: -- write failed: Transport > >> endpoint is not connected > >> Apr 26 18:15:12 dell_xps chat[29579]: Failed > >> > >> > >> This was despite the fact that I had created manually the rfcomm0 device > >> and binded it to the bdaddr of my phone as you suggested. > >> > >> Googling for this error revealed that this is because the rfcomm code > >> has > >> > >> changed - but there is a patch which may fix things: > >> http://comments.gmane.org/gmane.linux.bluez.kernel/42303 > >> > >> I ran out of time and did not try 'rfcomm connect' instead of 'rfcomm > >> bind' to see if it makes a difference in my case. > >> > >> FYI, I'm on net-wireless/bluez-5.15 and kernel 3.12.13-gentoo. > > > > I just upgraded to 3.12.13 and it stopped working with the same error > > you have. > > > > I did see some other messages saying that certain kernel versions are > > broken but I'll now need to look into that now. > > > > BillK > > I used the patch from the reply above - worked! > > It did take a couple of goes but after restarting the bluetooth > initscript before using bluetoothctl via expect (took 3 goes before I > got a clean run from "expect" - timing might need adjusting?) This is getting worse! O_O I am on net-wireless/bluez-5.18 and gentoo-sources-3.12.20 without the patch. Now I have no rfcomm service at all listed under rc-update and if I try to start /etc/init.d/bluetooth I get: # /etc/init.d/bluetooth restart * ERROR: bluetooth needs service(s) rfcomm Creating /dev/rfcomm0 with: # rfcomm bind rfcomm0 hci0 does not change the error. Starting KDE's BlueDevil shows no adaptor found. Indeed, hci0 is not configured. O_o So, running: # hciconfig hci0 up allows me to list it: $ hcitool dev Devices: hci090:4C:E5:FA:F2:A8 but NOT under bluetoothctl! [bluetooth]# power on No default controller available [bluetooth]# show No default controller available [bluetooth]# list [bluetooth]# [bluetooth]# devices [bluetooth]# NOTE: using hcitool I can scan my mobile phone, but without rfcomm I can't use it. Hmm ... am I alone in this quest? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] nvidia module won't load after updates
On 1/24/06, Ernie Schroder <[EMAIL PROTECTED]> wrote: > from dmesg > > nvidia: version magic '2.6.14-gentoo-r4 K7 gcc-3.4' should be > '2.6.14-gentoo-r42.6.14-r-4_new K7 gcc-3.3' > > This looks like the kernel was compiled with gcc-3.3 and nvidia-kernel was > compiled with gcc-3.4. Do I need to rebuild my kernel? I know I've restarted > x since updating gcc on 12/6/05 > Yes, just recompile your kernel and modules, configure your bootloader to point to the new kernel, reboot, then you should be good to go. HTH- James > $ gcc-config -c > i686-pc-linux-gnu-3.4.4 > How can I find what gcc version my kernel was built with? > > > Recent updates: > pygtk-2.8.2 > bluez-utils-2.22-r1 > bluez-libs-2.22 > gst-plugins-flac-0.8.11 > gst-plugins-vorbis-0.8.11 > gst-plugins-ogg-0.8.11 > gst-plugins-mad-0.8.11 > gtk-gnutella-0.95.4-r1 > coreutils-5.2.1-r7 > nvidia-kernel-1.0.6629-r5 > -- > Regards, Ernie > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Bluetooth speakers
On Monday, 9 May 2022 14:56:42 BST k...@aspodata.se wrote: > Peter: > ... > > > What would help is some idea of how the whole BT system works, > > ... > > There are two incompatible types of bluetooth: > Bluetooth Low Energy (BLE) > Bluetooth Classic > see: > https://www.bluetooth.com/learn-about-bluetooth/tech-overview/ > > You must check which generation of bluetooth your speaker uses. > If your speaker uses the classic type, this might help you: > https://wiki.debian.org/Bluetooth/Alsa > > /// > > More info about bluetooth: > https://en.wikipedia.org/wiki/Bluetooth > https://www.bluetooth.com/specifications/specs/ > > /// > > Current linux bluetooth tools (http://www.bluez.org/) doesn't > handle bluetooth classic, unless you build bluez with > --enable-deprecated configure option. > Also, bluez has dropped direct /dev file access for users, you > have to set up and go through dbus regardless wether you like it > or not. > > Regards, > /Karl Hammar I've met some success getting BT to work and I tend to follow these basic steps: 1. Configure the kernel according to the BT chipset available on the PC. 2. Power the BT chip by using whatever hardware button is available and check dmesg identified the device and loaded whatever module and firmware is necessary. 3. Use 'rfkill list' to check the device is not blocked and unblock it if necessary. 4. Run 'rc-service -v bluetooth start'. 5. Run 'bluetoothctl' to scan, list, pair and trust any peripherals - exchange a PIN to facilitate pairing as necessary. These steps should be relatively easy to complete and GUI tools are also available to assist with the above. Any problems thereafter are userspace related, i.e. whether the applications I use will be able to work with the BT peripherals. Audio has been problematic on a particular use case, where neither alsa (bluez-alsa), nor pulseaudio allowed me to output audio via BT. Eventually I tried blueman which after a couple of restarts helped pulseaudio to recognise the device and output audio through it. In all cases I prefer cables to temperamental radio connectivity and where quality matters, like it can be in some audio applications, I would seek to connect with a cable. HTH signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] after last update hciconfig disappeared
On Monday 27 Mar 2017 13:45:08 Raffaele Belardi wrote: > John Covici wrote: > > Hi. After the last update of net-wireless/bluez hciconfig has > > disappeared. Even downgrading did not bring it back, although it was > > there in the previous release. How do I do hciconfig, scan and > > friends now, or is there a way to get them back. > > > > As a workaround I put an old one back just copying the binary, so I > > could proceed, but there has got to be a better way. > > > > Thanks in advance for any suggestions. > > https://wiki.archlinux.org/index.php/bluetooth#Deprecated_method_using_hcico > nfig > > The ebuild lets you specify an extra-tools USE flag, maybe that one gets > them back. > > raffaele I'm on net-wireless/bluez-5.43-r1 with these USE flags: Installed versions: 5.43-r1(09:55:34 02/05/17)(cups obex readline udev - debug -deprecated -doc -experimental -extra-tools -selinux -systemd -test - test-programs -user-session ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32" PYTHON_TARGETS="python2_7") I still have hciconfig, hcitools, et al. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: bluez 5 not connecting
On 29/05/14 06:28, Mick wrote: > On Wednesday 28 May 2014 20:02:29 Samuli Suominen wrote: >> On 28/05/14 21:42, Mick wrote: >>> Hmm ... am I alone in this quest? >> >> See here, http://bugs.gentoo.org/show_bug.cgi?id=505362 > > Thanks! I missed this bug when I glanced earlier. However, it does not > mention rfcomm is now missing, or the fact that the gentoo rc script fails to > initialise bluethooth and complains about rfcomm service not having > started/exist, or that bluetoothctl now does not work at all. Is all this > down to a missing udev rule? > No its the fact that bluez 5 has been redesigned to fit in more with the systemd world. it works if: remove rfcomm using rc-update /etc/init.d/bluetoothctl restart (get rid of any existing config) bluetoothctl power on scan on agent on default-agent trust [MAC ADDRESS OF CLIENT] pair [MAC ADDRESS OF CLIENT] enter PIN when requested wait for "Connected: no" exit After this you should have an rfcomm channel available to the client. I have the above in an expect script as bluetoothctl has no inate remote controllability capabilities. No separate pairing app or rfcomm init script needed. BillK
[gentoo-user] Bluetooth and KDE Connect
Evening all, I've plugged in a new USB Bluetooth adapter, following the instructions in the wiki: https://wiki.gentoo.org/wiki/Bluetooth . The idea is to connect to my Android phone, but I'm only getting part way. After installing bluez and broadcom-bt-firmware, then booting with the new kernel, Bluetooth discovery and pairing work fine, but KDE Connect on each device can't see the other: they both report "No Devices". That nice Mr Google doesn't help, nor do the fine manuals and KDE web pages. Has anyone succeeded with this? $ hciconfig -a hci0: Type: Primary Bus: USB BD Address: 5C:F3:70:9C:BB:9F ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:5628 acl:45 sco:0 events:557 errors:0 TX bytes:41821 acl:47 sco:0 commands:487 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'BlueZ 5.55' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 4.1 (0x7) Revision: 0x16e4 LMP Version: 4.1 (0x7) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) -- Regards, Peter.
Re: [gentoo-user] Re: bluez 5 not connecting
On 28/05/14 21:42, Mick wrote: > Hmm ... am I alone in this quest? See here, http://bugs.gentoo.org/show_bug.cgi?id=505362
Re: [gentoo-user] Bluetooth and hciconfig
On Tue, Mar 28, 2017 at 07:59:02AM -0700, Mick wrote: > Mar 28 15:50:20 dell_xps bluetoothd[10619]: Unknown key AutoEnable in > main.conf Did you use the 'AutoEnable' option in the '[Policy]' section of main.conf? > So, what's the solution if hciconfig et al are not installed with future > versions of bluez and the AutoEnable option does not seem to take? I'm pretty sure the future solution is to use bluetoothctl as a console user interface or find a more scriptable alternative (I don't know of any) that also use the DBus interface. I just hit this problem with the upgrade as I was using scripts to manage turning bluetooth on and off and I was able to get by with just the AutoEnable option. I did not find much else in my cursory research as to a replacement for hciconfig. The following is from the release notes for BlueZ 5.35: > A noteworthy new feature is the ability to configure bluetoothd to > automatically enable (power on) all new adapters. One use of this is to > replace unreliable "hciconfig hci0 up" commands that some distributions > use in their init/udev scripts. The feature can be enabled by having > AutoEnable=true under the [Policy] section of /etc/bluetooth/main.conf. Foster
Re: [gentoo-user] KDE4.x installation blocks
Yep, sorry. Same question : how did you notice the problem was gksu? I didn't notice any dependency from bluez... (I'd like to be able to solve these problems without bother you) Thanks, Massimiliano
Re: [gentoo-user] bluetooth headset and espeak
espeak is not a pulse audio application but uses portaudio - something
quite different.
I dont have pulseaudio installed and seeing all the bad things people
say about it on other distributions I am leary about installing it on an
otherwise working system without good cause.
Note that as mentioned previously I have audio through the headset
already via mplayer, just not with espeak.
BillK
On Sun, 2010-05-23 at 13:27 -0500, Canek Peláez Valdés wrote:
> On Sun, May 23, 2010 at 7:20 AM, W.Kenworthy wrote:
> [...]
> > It looks like bluez is continually changing so most of the guides Ive
> > found dont apply - I am using bluez-4.39. alsamixer etc dont list the
> > bluetooth device and I cant see it in /proc/asound, but its obviously
> > there if mplayer can access it!
>
> With:
>
> gnome-base/gnome-2.28.2
> net-wireless/gnome-bluetooth-2.28.6
> media-sound/pulseaudio-0.9.21.1
>
> You only go to System->Preferences->Bluetooh, "Set new device...",
> detect and connect yo your headset, and then System->Sound, in the
> output tab you select your headset, and all the PulseAudio
> applications will output sound through your headset.
>
> If also you have
>
> pcm.!default {
> type pulse
> }
> ctl.!default {
> type pulse
> }
>
> in your ~/.asoundrc, all the ALSA applications will use PulseAudio,
> and then it will work for them too.
>
> Regards.
Re: [gentoo-user] nvidia module won't load after updates
On Tuesday 24 January 2006 14:39, a tiny voice compelled James Ausmus to write: > On 1/24/06, Ernie Schroder <[EMAIL PROTECTED]> wrote: > > from dmesg > > > > nvidia: version magic '2.6.14-gentoo-r4 K7 gcc-3.4' should be > > '2.6.14-gentoo-r42.6.14-r-4_new K7 gcc-3.3' > > > > This looks like the kernel was compiled with gcc-3.3 and nvidia-kernel > > was compiled with gcc-3.4. Do I need to rebuild my kernel? I know I've > > restarted x since updating gcc on 12/6/05 > > Yes, just recompile your kernel and modules, configure your bootloader > to point to the new kernel, reboot, then you should be good to go. > > HTH- > > James The point is, the machine has been rebooted a couple of times and X has been started and stopped 10 or 12 times recently without problems. I can't figure out why this has started to be a problem some 6 weeks after gcc and nvidia kernel were last updated. > > > $ gcc-config -c > > i686-pc-linux-gnu-3.4.4 > > How can I find what gcc version my kernel was built with? > > > > > > Recent updates: > > pygtk-2.8.2 > > bluez-utils-2.22-r1 > > bluez-libs-2.22 > > gst-plugins-flac-0.8.11 > > gst-plugins-vorbis-0.8.11 > > gst-plugins-ogg-0.8.11 > > gst-plugins-mad-0.8.11 > > gtk-gnutella-0.95.4-r1 > > coreutils-5.2.1-r7 > > nvidia-kernel-1.0.6629-r5 > > -- > > Regards, Ernie > > -- > > gentoo-user@gentoo.org mailing list -- Regards, Ernie -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] after last update hciconfig disappeared
On Mon, 27 Mar 2017 08:44:59 -0400, Mick wrote: > > [1 ] > On Monday 27 Mar 2017 13:45:08 Raffaele Belardi wrote: > > John Covici wrote: > > > Hi. After the last update of net-wireless/bluez hciconfig has > > > disappeared. Even downgrading did not bring it back, although it was > > > there in the previous release. How do I do hciconfig, scan and > > > friends now, or is there a way to get them back. > > > > > > As a workaround I put an old one back just copying the binary, so I > > > could proceed, but there has got to be a better way. > > > > > > Thanks in advance for any suggestions. > > > > https://wiki.archlinux.org/index.php/bluetooth#Deprecated_method_using_hcico > > nfig > > > > The ebuild lets you specify an extra-tools USE flag, maybe that one gets > > them back. > > > > raffaele > > > I'm on net-wireless/bluez-5.43-r1 with these USE flags: > > Installed versions: 5.43-r1(09:55:34 02/05/17)(cups obex readline udev - > debug -deprecated -doc -experimental -extra-tools -selinux -systemd -test - > test-programs -user-session ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" > ABI_S390="-32 -64" ABI_X86="64 -32 -x32" PYTHON_TARGETS="python2_7") > > I still have hciconfig, hcitools, et al. > I did as well, till I upgraded to 5.44 and then even downgrading did not bring back the tools. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
[gentoo-user] How to properly set up Bluetooth
Hi, i'm trying to set up a simple bluetooth keyboard, but somehow it won't work :-) This is my setup: Systemd + GDM + Fluxbox (this is the easiest way for me to use gnome-stuff like gnome-keyring-daemon, ... In the background my fluxbox is also running a gnome-settings-daemon) hcitool dev successfully detects my bluetooth device. According to [1] I tried to set up my keyboard using the command line. But actually simple-agent doesn't seem to be available in bluez 5.x. So I tried to use blueman-applet. This is a snippet of the output of blueman-applet: Function on_manager_state_changed on RecentConns Failed Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/blueman/main/PluginManager.py", line 220, in Run ret = getattr(inst, function)(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/blueman/plugins/applet/RecentConns.py", line 195, in on_manager_state_changed adapters = self.Applet.Manager.ListAdapters() File "/usr/lib64/python2.7/site-packages/blueman/bluez/utils.py", line 28, in warp raise errors.parse_dbus_error(exception) DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "ListAdapters" with signature "" on interface "org.bluez.Manager" doesn't exist It seems to me that this is a dbus problem or something like that, but I don't know what I am doing wrong. I started "systemctl start bluetooth" and my user is in the group plugdev. Any suggestions? [1] http://wiki.gentoo.org/wiki/Bluetooth Regards Ralf
Re: [gentoo-user] KDE4.x installation blocks
Thank you people!! I'm trying Alan's tip. I'll let you know when I'll finish : it must perform 26 compilations :-( ) Just one question : how did you notice the problem was kdesu? I didn't see any dependency from bluez... Thanks, Massimiliano
Re: [gentoo-user] Still not feeling familiar with emerge
On Friday 15 January 2010 00:36:16 h...@dfki.uni-kl.de wrote:
> Dear group,
>
> I'm using gentoo for more than three years now and using the gentoo
> packaging system in general is exactly what I expect from a packaging
> system. You just open a shell somewhere on your virtual desktop, start a
> process and the rest is done automatically (in general).
>
> But, when it comes to packages blocking each other I simply have to guess,
> what to do next and sometimes I fail in guessing the right things I once
> removed the wrong package, which left me with a system without working
> packaging system - a very bad experience. In fact I could only solve this
> problem by copying a dynamic library from another linux installation to
> reanimate emerge.
>
> So some weeks ago I was too busy to take care of some conflicts caused by
> the end of support for KDE 3.5). I stopped updating, because I didn't have
> the time to switch to newer KDE version and wanted to do that later on.
Everything above this line is fascinating but completely unrelated to your
post. Please omit such in future
> Now I want to upgrade, but I would like to better understand the messages
> telling me the conflicting packets. A current call to 'emerge --update
> --deep --ask world' gives me the following conflicts:
>
>
> * Error: The above package list contains packages which cannot be
> * installed at the same time on the same system.
>
> ('installed', '/', 'sys-fs/device-mapper-1.02.24-r1', 'nomerge') pulled
> in by
>
> >=sys-fs/device-mapper-1.00.07-r1 required by ('installed', '/',
> > 'sys-fs/cryptsetup-1.0.6-r2', 'nomerge')
Read it backwards from the bottom up. It means that cryptsetup requires
device-mapper (a version greater than 1.00.07-r1) and portage has chosen
device-mapper-1.02.24-r1
> ('ebuild', '/', 'kde-base/kdebase-data-4.3.3', 'merge') pulled in by
>
> >=kde-base/kdebase-data-4.3.3[-kdeprefix] required by ('ebuild', '/',
> > 'kde-base/kdelibs-4.3.3-r1', 'merge')
> > =kde-base/kdebase-data-4.3.3[-kdeprefix] required by ('ebuild', '/',
> > 'kde-base/kdebase-meta-4.3.3', 'merge')
Same as above, except that both kdelibs and kdebase-meta have pulled in
kdebase-data. Sometimes the list of package that pull in other gets very long
and the list might be truncated with a message something like "plus 33
others..."
> ('installed', '/', 'app-arch/lzma-utils-4.32.7', 'nomerge') pulled in by
> app-arch/lzma-utils required by ('ebuild', '/',
> 'dev-libs/mpfr-2.4.1_p5', 'merge') app-arch/lzma-utils required by
> ('ebuild', '/', 'dev-texlive/texlive-basic-2008-r1', 'merge')
> app-arch/lzma-utils required by ('ebuild', '/',
> 'dev-texlive/texlive-latex-2008-r2', 'merge') (and 5 more)
>
> ('installed', '/', 'kde-base/akregator-3.5.10', 'nomerge') pulled in by
>
> >=kde-base/akregator-3.5.10:3.5 required by ('installed', '/',
> > 'kde-base/konqueror-akregator-3.5.10', 'nomerge')
>
> ('ebuild', '/', 'sys-fs/udev-146-r1', 'merge') pulled in by
> virtual/dev-manager required by world
>
> >=sys-fs/udev-103 required by ('ebuild', '/', 'media-gfx/iscan-2.21.0',
> > 'merge') =sys-fs/udev-124 required by ('installed', '/',
> > 'sys-fs/cryptsetup-1.0.6-r2', 'nomerge')
>
> (and 3 more)
>
> ('ebuild', '/', 'net-wireless/bluez-4.39-r2', 'merge') pulled in by
> net-wireless/bluez required by ('ebuild', '/', 'gnome-base/gvfs-1.2.3',
> 'merge') net-wireless/bluez required by ('ebuild', '/',
> 'kde-base/solid-4.3.3', 'merge')
>
> ('ebuild', '/', 'kde-base/akregator-4.3.3', 'merge') pulled in by
>
> >=kde-base/akregator-4.3.3[-kdeprefix] required by ('ebuild', '/',
> > 'kde-base/kdepim-meta-4.3.3', 'merge')
>
> ('ebuild', '/', 'app-arch/xz-utils-4.999.9_beta', 'merge') pulled in by
> app-arch/xz-utils required by ('ebuild', '/',
> 'app-arch/libarc
[gentoo-user] bluetooth-test-network: connection refused
Hi everyone,
I have a problem to connect two bluetooth devices:
I have two gentoo-PCs with a Bluetooth3.0-Dongle at each PC.
I tried to use the bluetooth-test-network to connect them, but connection was
refused and I don't know how to fix it. Down below
you find the
# bluez-test-network
# monitor-bluetooth
and
# hcidump -i hci0
-messages of both PCs.
On top of that, there are *different* error
messages at both PCs!
Hope you can help me in this case& tell me how I can connect my PCs using the
bluetooth-test-network command.
Regards,
Steffen
So here it is:
PC1:
bluetooth1 ~ # bluez-test-discovery
[ 00:02:72:AE:58:73 ]
Name = bluetooth2-0
Paired = 1
LegacyPairing = 0
Alias = bluetooth2-0
UUIDs =
dbus.Array([dbus.String(u'1116--1000-8000-00805f9b34fb'),
dbus.String(u'1103--1000-8000-00805f9b34fb'),
dbus.String(u'110e--1000-8000-00805f9b34fb'),
dbus.String(u'110c--1000-8000-00805f9b34fb'),
dbus.String(u'110a--1000-8000-00805f9b34fb'),
dbus.String(u'111f--1000-8000-00805f9b34fb'),
dbus.String(u'1112--1000-8000-00805f9b34fb')],
signature=dbus.Signature('s'), variant_level=1)
Address = 00:02:72:AE:58:73
RSSI = -37
Class = 0x4a0100
Trusted = 1
Icon = computer
-----
bluetooth1 ~ # bluez-test-network 00:02:72:AE:58:73 nap
Traceback (most recent call last):
File "/usr/bin/bluez-test-network", line 45, in
iface = network.Connect(service)
File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 68,
in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 143,
in __call__
**keywords)
File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line
630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.Failed: Connection
refused (111)
-----
bluetooth1 ~ # monitor-bluetooth
{Device.PropertyChanged} [/org/bluez/2821/hci0/dev_00_02_72_AE_58_73]
Connected = 1
{Device.PropertyChanged} [/org/bluez/2821/hci0/dev_00_02_72_AE_58_73]
Connected = 0
-
bluetooth1 ~ # hcidump -i hci0
HCI sniffer - Bluetooth packet analyzer ver 2.3
device: hci0 snap_len: 1028 filter: 0x
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:02:72:AE:58:73 ptype 0xcc18 rswitch 0x01 clkoffset 0x
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
HCI Event: Command Status (0x0f) plen 4
Create Connection (0x01|0x0005) status 0x00 ncmd 1
HCI Event: Role Change (0x12) plen 8
status 0x00 bdaddr 00:02:72:AE:58:73 role 0x01
Role: Slave
HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 12 bdaddr 00:02:72:AE:58:73 type ACL encrypt 0x00
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
handle 12
HCI Event: Max Slots Change (0x1b) plen 3
handle 12 slots 5
HCI Event: Command Status (0x0f) plen 4
Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
HCI Event: Read Remote Supported Features (0x0b) plen 11
status 0x00 handle 12
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x87
< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
handle 12 page 1
HCI Event: Command Status (0x0f) plen 4
Read Remote Extended Features (0x01|0x001c) status 0x00 ncmd 1
HCI Event: Read Remote Extended Features (0x23) plen 13
status 0x00 handle 12 page 1 max 1
Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
bdaddr 00:02:72:AE:58:73 mode 2 clkoffset 0x
HCI Event: Command Status (0x0f) plen 4
Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
HCI Event: Remote Name Req Complete (0x07) plen 255
status 0x00 bdaddr 00:02:72:AE:58:73 name 'bluetooth2-0'
< HCI Command: Authentication Requested (0x01|0x0011) plen 2
handle 12
HCI Event: Command Status (0x0f) plen 4
Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
HCI Event: Link Key Request (0x17) plen 6
bdaddr 00:02:72:AE:58:73
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:02:72:AE:58:73 key C6A4D268E42E81CAD233A2C61FA7993A
HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:02:72:AE:58:73
HCI Event: Auth Complete (0x06) plen 3
status 0x00 handle 12
< HCI Command: Set Connection Encryption (0x01|0x0013) plen 3
handle 12 encrypt 0x01
HCI Event: Command Status (0x0f) plen 4
Set Connection Encryption (0x01|0x0013) status 0x00 ncmd 1
HCI Event:
Re: [gentoo-user] Bluetooth compatibility
On Thursday 02 November 2006 2:27 pm, Grant wrote: > I need a wireless headset to use with my softphone. My laptop doesn't > have bluetooth built-in so I need a USB bluetooth adapter and > bluetooth headset. Has anyone used bluetooth with Gentoo? Should I > be researching both devices' Linux compatibility, or just the adapter? > > - Grant Well as already mentioned, just about any adapter should be fine. If you feel like doing some research, find something with a Camridge Silicon Radio (CSR) chipset, they are the most common and consequently the best supported. As far as the headset goes, you should be fine. I use a Sony Ericsson HBH-IV835 with my gentoo/amd64 pc without too many issues. The driver that couples the headset to an alsa audio device is at http://bluetooth-alsa.sf.net As far as ebuilds go, they are in Liquidx's dev overlay (layman -a liquidx), called btsco and btsco-kernel. There is a marginally outdated but still useful howto at http://gentoo-wiki.com/HOWTO_use_a_bluetooth_headset Note: you will probably want to install bluez-libs and bluez-utils 2.25, 3.7 opens up a whole new set of problems with the dbus pin authentication, you really just don't want to go there. Your life will also be made a lot easier if you install kdebluetooth or gnome-bluetooth to get a frontend for configuration, device searches, file transfer (if you have a bluetooth phone also), etc. --Thomas pgpN596I1AHpg.pgp Description: PGP signature
Re: [gentoo-user] Bluetooth speakers
On Monday, 9 May 2022 15:38:30 BST Michael wrote: > On Monday, 9 May 2022 14:56:42 BST k...@aspodata.se wrote: > > Peter: > > ... > > > > > What would help is some idea of how the whole BT system works, > > > > ... > > > > There are two incompatible types of bluetooth: > > Bluetooth Low Energy (BLE) > > Bluetooth Classic > > > > see: > > https://www.bluetooth.com/learn-about-bluetooth/tech-overview/ > > > > You must check which generation of bluetooth your speaker uses. > > > > If your speaker uses the classic type, this might help you: > > https://wiki.debian.org/Bluetooth/Alsa > > > > /// > > > > More info about bluetooth: > > https://en.wikipedia.org/wiki/Bluetooth > > https://www.bluetooth.com/specifications/specs/ > > > > /// > > > > Current linux bluetooth tools (http://www.bluez.org/) doesn't > > handle bluetooth classic, unless you build bluez with > > --enable-deprecated configure option. > > > > Also, bluez has dropped direct /dev file access for users, you > > > > have to set up and go through dbus regardless wether you like it > > or not. > > > > Regards, > > /Karl Hammar > > I've met some success getting BT to work and I tend to follow these basic > steps: > > 1. Configure the kernel according to the BT chipset available on the PC. > > 2. Power the BT chip by using whatever hardware button is available and > check dmesg identified the device and loaded whatever module and firmware > is necessary. > > 3. Use 'rfkill list' to check the device is not blocked and unblock it if > necessary. > > 4. Run 'rc-service -v bluetooth start'. > > 5. Run 'bluetoothctl' to scan, list, pair and trust any peripherals - > exchange a PIN to facilitate pairing as necessary. > > These steps should be relatively easy to complete and GUI tools are also > available to assist with the above. Any problems thereafter are userspace > related, i.e. whether the applications I use will be able to work with the > BT peripherals. Audio has been problematic on a particular use case, where > neither alsa (bluez-alsa), nor pulseaudio allowed me to output audio via > BT. Eventually I tried blueman which after a couple of restarts helped > pulseaudio to recognise the device and output audio through it. Yes, I went through all that, just as you said, but still I got no sound. > In all cases I prefer cables to temperamental radio connectivity and where > quality matters, like it can be in some audio applications, I would seek to > connect with a cable. Indeed, and I've now replaced the speakers, the 3.5mm cable and the USB dongle - every sound component is new. When I tested it yesterday in the plasma control panel, I heard one "front left", very loud, and then nothing. I thought some BT stuff must still be lying around somewhere, so I've installed a new system from scratch, using a kernel .config from before I started with BT, and today I still hear no sound. This seems like witchcraft now. -- Regards, Peter.
Re: [gentoo-user] Bluetooth speakers
On Monday, 9 May 2022 15:38:30 BST Michael wrote: > On Monday, 9 May 2022 14:56:42 BST k...@aspodata.se wrote: > > Peter: > > ... > > > > > What would help is some idea of how the whole BT system works, > > > > ... > > > > There are two incompatible types of bluetooth: > > Bluetooth Low Energy (BLE) > > Bluetooth Classic > > > > see: > > https://www.bluetooth.com/learn-about-bluetooth/tech-overview/ > > > > You must check which generation of bluetooth your speaker uses. > > > > If your speaker uses the classic type, this might help you: > > https://wiki.debian.org/Bluetooth/Alsa > > > > /// > > > > More info about bluetooth: > > https://en.wikipedia.org/wiki/Bluetooth > > https://www.bluetooth.com/specifications/specs/ > > > > /// > > > > Current linux bluetooth tools (http://www.bluez.org/) doesn't > > handle bluetooth classic, unless you build bluez with > > --enable-deprecated configure option. > > > > Also, bluez has dropped direct /dev file access for users, you > > > > have to set up and go through dbus regardless wether you like it > > or not. > > > > Regards, > > /Karl Hammar > > I've met some success getting BT to work and I tend to follow these basic > steps: > > 1. Configure the kernel according to the BT chipset available on the PC. > > 2. Power the BT chip by using whatever hardware button is available and > check dmesg identified the device and loaded whatever module and firmware > is necessary. > > 3. Use 'rfkill list' to check the device is not blocked and unblock it if > necessary. > > 4. Run 'rc-service -v bluetooth start'. > > 5. Run 'bluetoothctl' to scan, list, pair and trust any peripherals - > exchange a PIN to facilitate pairing as necessary. > > These steps should be relatively easy to complete and GUI tools are also > available to assist with the above. Any problems thereafter are userspace > related, i.e. whether the applications I use will be able to work with the > BT peripherals. Audio has been problematic on a particular use case, where > neither alsa (bluez-alsa), nor pulseaudio allowed me to output audio via > BT. Eventually I tried blueman which after a couple of restarts helped > pulseaudio to recognise the device and output audio through it. Yes, I went through all that, just as you said, but still I got no sound. > In all cases I prefer cables to temperamental radio connectivity and where > quality matters, like it can be in some audio applications, I would seek to > connect with a cable. Indeed, and I've now replaced the speakers, the 3.5mm cable and the USB dongle - every sound component is new. When I tested it yesterday in the plasma control panel, I heard one "front left", very loud, and then nothing. I thought some BT stuff must still be lying around somewhere, so I've installed a new system from scratch, using a kernel .config from before I started with BT, and today I still hear no sound. This seems like witchcraft now. -- Regards, Peter.
Re: [gentoo-user] bluez
On 13 Mar 2010, at 21:15, dhk wrote: The Gentoo Linux Bluetooth Guide says to ... According to the last person who posted on this list on this subject, that guide is obsolete & incorrect. See: http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg97261.html http://tinyurl.com/yfobgoo Stroller
[gentoo-user] Bluetooth and KDE4
Does anyone know how to transfer files over bluetooth with KDE4? It used to "just work" in KDE3 by plugging in my bluetooth dongle, but I don't know if it's the recent masking of bluez stuff or KDE4 but now it just doesn't do anything. I feel like I'm missing something really simple :) Thanks, Paul
Re: [gentoo-user] How to get hid2hci command
net-wireless/bluez maybe? Kyle On Sep 16, 2010 1:01 PM, "Hung Dang" wrote: Hi all, I need to use hid2hci for my bluetooth keyboad. However, I could not figure out how to get the hid2hci command. Any suggestion would be appreciate? Thanks in advance Hung
[gentoo-user] no Affix bluetooth protocol stack on gentoo?
Hello, is there a reason (other than no one having created an ebuild) that the Affix bluetooth protocol stack is not in portage? I know there is Bluez, but it seams not to work as well with symbian os based smartphones. Thank you, Gabriel -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] How to properly set up Bluetooth
On Tue, Feb 18, 2014 at 8:34 AM, Ralf wrote: > Hi, > > i'm trying to set up a simple bluetooth keyboard, but somehow it won't work > :-) > > This is my setup: > Systemd + GDM + Fluxbox (this is the easiest way for me to use gnome-stuff > like gnome-keyring-daemon, ... In the background my fluxbox is also running > a gnome-settings-daemon) > > hcitool dev successfully detects my bluetooth device. > > According to [1] I tried to set up my keyboard using the command line. But > actually simple-agent doesn't seem to be available in bluez 5.x. > So I tried to use blueman-applet. This is a snippet of the output of > blueman-applet: > > Function on_manager_state_changed on RecentConns Failed > Traceback (most recent call last): > File "/usr/lib64/python2.7/site-packages/blueman/main/PluginManager.py", > line 220, in Run > ret = getattr(inst, function)(*args, **kwargs) > File > "/usr/lib64/python2.7/site-packages/blueman/plugins/applet/RecentConns.py", > line 195, in on_manager_state_changed > adapters = self.Applet.Manager.ListAdapters() > File "/usr/lib64/python2.7/site-packages/blueman/bluez/utils.py", line 28, > in warp > raise errors.parse_dbus_error(exception) > DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method > "ListAdapters" with signature "" on interface "org.bluez.Manager" doesn't > exist > > > It seems to me that this is a dbus problem or something like that, but I > don't know what I am doing wrong. > I started "systemctl start bluetooth" and my user is in the group plugdev. > > Any suggestions? Can you install gnome-bluetooth and run bluetooth-wizard? Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Xorg does not start after a recent system update.
On Sun, Sep 20, 2020 at 02:23:58PM +0300, gevisz wrote:
> вс, 20 сент. 2020 г. в 14:09, gevisz :
> > When installing my new Gentoo installation, I tried to make it as
> > close to the old one as it was possible, and it is strange to me that
> > the new one does not have a dbus startup in its runlevels. (As far as
> > I remember, in both cases I needed dbus to switch keyboard layout in
> > Awesome, and it did on both systems before the last update.)
> >
> > Probably, my first try should be to add dbus to the default runlevel
> > on my new Gentoo installation.
>
> Yes, after adding dbus to default runlevel, the xorg-server started.
It would be very peculiar if D-Bus was removed from your runlevels; it's more
probable that a service implicitly starting D-Bus as a dependency via `need` was
changed during your system upgrade. Regardless, since the service was never
starting, the socket file was never being created. X should probably try and
start the D-Bus service when it initialises, either as a part of the Gentoo
patchset, or as a bug to upstream. The BlueZ bluetooth service does this, for
example [1]:
depend() {
after coldplug
need dbus localmount hostname
}
Anyway, glad to see it fixed.
[1]
https://gitweb.gentoo.org/repo/gentoo.git/tree/net-wireless/bluez/files/bluetooth-init.d-r4
--
Ashley Dixon
suugaku.co.uk
2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA
signature.asc
Description: PGP signature
Re: [gentoo-user] KDE4.x installation blocks
On Tue, 8 Sep 2009 13:27:41 +0200, Massimiliano Ziccardi wrote: > So I guess I don't have bluez anymore > > Any other idea? Tell what command you are running. Add the --tree option to emerge Post the output. -- Neil Bothwick Assembler: (n.) a minor program of interest only to obsessed programmers. signature.asc Description: PGP signature
Re: [gentoo-user] KDE4.x installation blocks
On Dienstag 08 September 2009, Massimiliano Ziccardi wrote: > Thank you people!! > > I'm trying Alan's tip. I'll let you know when I'll finish : it must perform > 26 compilations :-( ) > > Just one question : how did you notice the problem was kdesu? I didn't see > any > dependency from bluez... > > Thanks, > Massimiliano > kdesu is not the problem gksu is. Entirely different app.
Re: [gentoo-user] after last update hciconfig disappeared
On Mon, Mar 27, 2017 at 12:28:11PM -0400, John Covici wrote: > On Mon, 27 Mar 2017 08:44:59 -0400, > Mick wrote: > > > > [1 ] > > On Monday 27 Mar 2017 13:45:08 Raffaele Belardi wrote: > > > John Covici wrote: > > > > Hi. After the last update of net-wireless/bluez hciconfig has > > > > disappeared. Even downgrading did not bring it back, although it was > > > > there in the previous release. How do I do hciconfig, scan and > > > > friends now, or is there a way to get them back. > > > > > > > > As a workaround I put an old one back just copying the binary, so I > > > > could proceed, but there has got to be a better way. > > > > > > > > Thanks in advance for any suggestions. > > > > > > https://wiki.archlinux.org/index.php/bluetooth#Deprecated_method_using_hcico > > > nfig > > > > > > The ebuild lets you specify an extra-tools USE flag, maybe that one gets > > > them back. > > > > > > raffaele > > > > > > I'm on net-wireless/bluez-5.43-r1 with these USE flags: > > > > Installed versions: 5.43-r1(09:55:34 02/05/17)(cups obex readline > > udev - > > debug -deprecated -doc -experimental -extra-tools -selinux -systemd -test - > > test-programs -user-session ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" > > ABI_S390="-32 -64" ABI_X86="64 -32 -x32" PYTHON_TARGETS="python2_7") > > > > I still have hciconfig, hcitools, et al. > > > > I did as well, till I upgraded to 5.44 and then even downgrading did > not bring back the tools. > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici > cov...@ccs.covici.com > If you are just using the tools in your terminal, 'bluetoothctl' has replaced those programs. If you are writing scripts with those commands, I do not know of any worthy replacements besides using the DBus interface manually. Foster
[gentoo-user] Bluetooth and hciconfig
A recent post had me investigating this. I'm on net-wireless/bluez-5.43-r1 which thankfully provides the hciconfig utility. I have used hciconfig for years now to enable the bluetooth adapter on my laptop. Starting /etc/init.d/bluetooth does not enable the adapter itself. Setting AutoEnable = true causes an error in the logs: in Mar 28 15:50:20 dell_xps bluetoothd[10619]: Bluetooth daemon 5.43 Mar 28 15:50:20 dell_xps bluetoothd[10619]: Unknown key AutoEnable in main.conf Mar 28 15:50:20 dell_xps bluetoothd[10619]: Starting SDP server Mar 28 15:50:20 dell_xps bluetoothd[10619]: Bluetooth management interface 1.14 initialized Mar 28 15:50:20 dell_xps bluetoothd[10619]: Failed to obtain handles for "Service Changed" characteristic Mar 28 15:50:20 dell_xps bluetoothd[10619]: Endpoint registered: sender=:1.34 path=/MediaEndpoint/A2DPSource Mar 28 15:50:20 dell_xps bluetoothd[10619]: Endpoint registered: sender=:1.34 path=/MediaEndpoint/A2DPSink The adapter remains disabled: # hciconfig hci0: Type: Primary Bus: USB BD Address: 90:4C:E5:FA:F2:A8 ACL MTU: 1021:8 SCO MTU: 64:8 DOWN RX bytes:1058 acl:0 sco:0 events:52 errors:0 TX bytes:951 acl:0 sco:0 commands:52 errors:0 Enabling it manually with hciconfig works as always had: # hciconfig hci0 up piscan # hciconfig hci0: Type: Primary Bus: USB BD Address: 90:4C:E5:FA:F2:A8 ACL MTU: 1021:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:1599 acl:0 sco:0 events:80 errors:0 TX bytes:1559 acl:0 sco:0 commands:80 errors:0 So, what's the solution if hciconfig et al are not installed with future versions of bluez and the AutoEnable option does not seem to take? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] How to properly set up Bluetooth
Ralf wrote: > Hi, > > i'm trying to set up a simple bluetooth keyboard, but somehow it won't > work :-) > > This is my setup: > Systemd + GDM + Fluxbox (this is the easiest way for me to use > gnome-stuff like gnome-keyring-daemon, ... In the background my fluxbox > is also running a gnome-settings-daemon) > > hcitool dev successfully detects my bluetooth device. > > According to [1] I tried to set up my keyboard using the command line. > But actually simple-agent doesn't seem to be available in bluez 5.x. > So I tried to use blueman-applet. This is a snippet of the output of > blueman-applet: > > Function on_manager_state_changed on RecentConns Failed > Traceback (most recent call last): > File > "/usr/lib64/python2.7/site-packages/blueman/main/PluginManager.py", > line 220, in Run > ret = getattr(inst, function)(*args, **kwargs) > File > > "/usr/lib64/python2.7/site-packages/blueman/plugins/applet/RecentConns.py", > line 195, in on_manager_state_changed > adapters = self.Applet.Manager.ListAdapters() > File "/usr/lib64/python2.7/site-packages/blueman/bluez/utils.py", > line 28, in warp > raise errors.parse_dbus_error(exception) > DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method > "ListAdapters" with signature "" on interface "org.bluez.Manager" > doesn't exist > > > It seems to me that this is a dbus problem or something like that, but I > don't know what I am doing wrong. > I started "systemctl start bluetooth" and my user is in the group plugdev. > > Any suggestions? > > [1] http://wiki.gentoo.org/wiki/Bluetooth I would like to have simple-agent back as well, at least the script part -- I think the other bits are still there, why they would take away something so ssimple I have no idea. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] Re: bluez 5 not connecting
On 29/05/14 18:18, Mick wrote: > On Thursday 29 May 2014 07:27:24 Mick wrote: >> On Thursday 29 May 2014 00:05:16 William Kenworthy wrote: >>> On 29/05/14 06:28, Mick wrote: >>>> On Wednesday 28 May 2014 20:02:29 Samuli Suominen wrote: >>>>> On 28/05/14 21:42, Mick wrote: >>>>>> Hmm ... am I alone in this quest? >>>>> >>>>> See here, http://bugs.gentoo.org/show_bug.cgi?id=505362 >>>> >>>> Thanks! I missed this bug when I glanced earlier. However, it does >>>> not mention rfcomm is now missing, or the fact that the gentoo rc >>>> script fails to initialise bluethooth and complains about rfcomm >>>> service not having started/exist, or that bluetoothctl now does not >>>> work at all. Is all this down to a missing udev rule? >>> >>> No its the fact that bluez 5 has been redesigned to fit in more with the >>> systemd world. >> I am not using systemd either - there is no bluetoothctl service (its an application and written with no remote control capabilities - why?: no idea - in my reading I came across a message saying that its designed for use with systemd but I thought it would still need the remote option unless bluetoothctl like functions are natively included in systemd) You will probably have to load the modules manually (/etc/conf.d/modules) - mine do load automatically though moriah ~ # lsmod|grep bt btusb 14099 0 bluetooth 191573 24 bnep,btusb,rfcomm usbcore 132770 10 btusb,usblp,uhci_hcd,usb_storage,usbserial,ehci_hcd,ehci_pci,usbhid,ftdi_sio,cdc_acm moriah ~ # Sounds like you have more than one problem and you need to get the modules loaded and working first, then you can run bluetoothctl manually. BillK
Re: [gentoo-user] Xorg does not start after a recent system update.
вс, 20 сент. 2020 г. в 15:37, Ashley Dixon :
>
> On Sun, Sep 20, 2020 at 02:23:58PM +0300, gevisz wrote:
> > вс, 20 сент. 2020 г. в 14:09, gevisz :
> > > When installing my new Gentoo installation, I tried to make it as
> > > close to the old one as it was possible, and it is strange to me that
> > > the new one does not have a dbus startup in its runlevels. (As far as
> > > I remember, in both cases I needed dbus to switch keyboard layout in
> > > Awesome, and it did on both systems before the last update.)
> > >
> > > Probably, my first try should be to add dbus to the default runlevel
> > > on my new Gentoo installation.
> >
> > Yes, after adding dbus to default runlevel, the xorg-server started.
>
> It would be very peculiar if D-Bus was removed from your runlevels; it's
> more
> probable that a service implicitly starting D-Bus as a dependency via `need`
> was
> changed during your system upgrade. Regardless, since the service was
> never
> starting, the socket file was never being created. X should probably try
> and
> start the D-Bus service when it initialises, either as a part of the
> Gentoo
> patchset, or as a bug to upstream. The BlueZ bluetooth service does this,
> for
> example [1]:
>
> depend() {
> after coldplug
> need dbus localmount hostname
> }
>
> Anyway, glad to see it fixed.
>
> [1]
> https://gitweb.gentoo.org/repo/gentoo.git/tree/net-wireless/bluez/files/bluetooth-init.d-r4
>
My guess was that it is /etc/X11/xinit/xinitrc.d/80-dbus that started
dbus on the problem computer but for some reason stopped to do it
after the system update, but of course it may be because of changed
dependency of the OpenRC dependencies.
Anyway, thank you once more for your help!
Re: [gentoo-user] How to get hid2hci command
maybe you need the "old-daemons" use flag? On Fri, Sep 17, 2010 at 10:34 AM, Kyle Bader wrote: > net-wireless/bluez maybe? > > Kyle > > On Sep 16, 2010 1:01 PM, "Hung Dang" wrote: > > Hi all, > > I need to use hid2hci for my bluetooth keyboad. However, I could not figure > out how to get the hid2hci command. > Any suggestion would be appreciate? > > Thanks in advance > Hung > -- Best Regards, Xi Shen (David) http://twitter.com/davidshen84/
[gentoo-user] bluetooth headset and espeak
I have set up sound to a jabra halo bluetooth headset and it works using "mplayer -ao alsa:device=bluetooth soundfile". This works fine for apps like mplayer which can specify the right output device. However, I want to use espeak (in a console) to play back text files - its a good method to check grammar - but I cant get it working? It works out of the box on a nokia n900, but I cant figure out how to get gentoo (gnome desktop) to do it. espeak doesnt support specifying a sound device that I can see - it uses portaudio which is supposed to work with alsa bluetooth but how? It looks like bluez is continually changing so most of the guides Ive found dont apply - I am using bluez-4.39. alsamixer etc dont list the bluetooth device and I cant see it in /proc/asound, but its obviously there if mplayer can access it! BillK bunyip linux # hciconfig -a hci0: Type: USB BD Address: 00:02:C7:E5:A1:65 ACL MTU: 384:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:199720 acl:43 sco:0 events:28229 errors:0 TX bytes:23638521 acl:82313 sco:0 commands:59 errors:0 Features: 0xff 0xff 0x8b 0xfe 0x9b 0xf9 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'bunyip-0' Class: 0x4a210c Service Classes: Networking, Capturing, Telephony Device Class: Computer, Laptop HCI Ver: 2.0 (0x3) HCI Rev: 0x77b LMP Ver: 2.0 (0x3) LMP Subver: 0x77b Manufacturer: Cambridge Silicon Radio (10) bunyip linux # hciconfig hci0 revision hci0: Type: USB BD Address: 00:02:C7:E5:A1:65 ACL MTU: 384:8 SCO MTU: 64:8 HCI 19.2 Chip version: BlueCore4-External Max key size: 56 bit SCO mapping: HCI
Re: [gentoo-user] USB automount
On Mon, Sep 17, 2012 at 10:45 AM, Stefan G. Weichinger wrote: > Am 16.09.2012 20:45, schrieb Canek Peláez Valdés: > >> This workaround also works in my systemd-only overlay. So, if you have >> the systemd flag in any of those four packages, disable it and >> everything should work. Just to be explicit, the versions are: >> >> gnome-base/gdm-3.4.1-r1 >> gnome-base/gnome-session-3.4.2.1 >> gnome-base/gnome-shell-3.4.2 >> sys-auth/polkit-0.107:0 > > confirming this. I have exactly your mentioned versions with > USE="-systemd" and suspend/hibernate option returns, I could mount/use a > DVD right now ... yes! OK; now I can put this whole thing behind me. You can read the bug again: https://bugs.freedesktop.org/show_bug.cgi?id=53905 but the short answer is that you cannot let both systemd and consolekit to manage sessions. The problem (in my case) was that I was using accountsservice 0.6.22, which depends on consolekit. I upgraded to accountsservice 0.6.24 (which can depend on systemd), I removed all consolekit USE-flags (except for bluez: bluez uses consolekit to pull either consolekit or systemd; I reported a bug[1]), and after an emerge -uDNv world, I removed consolekit (I didn't had any other package depending on it). Now everything works as it should, in both my overlay and in the vanilla Gentoo tree. Be aware: it works *with systemd*; maybe it works without it, but I don't know (nor care). All the GNOME session management is moving to systemd, and I think it's a great idea. Support for consolekit (which is no longer maintained) is still there, but I don't know for how long. If you want to keep using (the unmaintained) consolekit, be sure to set "-systemd" in your USE flags. Do not mix systemd and consolekit, or this bug will hit you. Regards. [1] https://bugs.gentoo.org/show_bug.cgi?id=436180 -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: bluez 5 not connecting
On Thursday 29 May 2014 00:05:16 William Kenworthy wrote: > On 29/05/14 06:28, Mick wrote: > > On Wednesday 28 May 2014 20:02:29 Samuli Suominen wrote: > >> On 28/05/14 21:42, Mick wrote: > >>> Hmm ... am I alone in this quest? > >> > >> See here, http://bugs.gentoo.org/show_bug.cgi?id=505362 > > > > Thanks! I missed this bug when I glanced earlier. However, it does not > > mention rfcomm is now missing, or the fact that the gentoo rc script > > fails to initialise bluethooth and complains about rfcomm service not > > having started/exist, or that bluetoothctl now does not work at all. Is > > all this down to a missing udev rule? > > No its the fact that bluez 5 has been redesigned to fit in more with the > systemd world. I see. No systemd here, other than systemd's udev. > it works if: > > remove rfcomm using rc-update I didn't have to remove it because it wasn't there ... no rfcomm service anymore, or any /etc/conf.d/rfcomm file. There is a /etc/conf.d/bluetooth showing: # Bluetooth configuraton file # Bind rfcomm devices (allowed values are "true" and "false") RFCOMM_ENABLE=true # Config file for rfcomm RFCOMM_CONFIG="/etc/bluetooth/rfcomm.conf" > /etc/init.d/bluetoothctl restart (get rid of any existing config) Ahh! I have no /etc/init.d/bluetoothctl service, only /etc/init.d/bluetooth Am I missing some package for it? Interestingly the module bt_rfcomm was not initialised by udev and I had to modprobe it manually ... # lsmod | grep bt btusb 14115 0 bluetooth 173578 5 btusb,rfcomm > bluetoothctl > power on > scan on > agent on > default-agent > trust [MAC ADDRESS OF CLIENT] > pair [MAC ADDRESS OF CLIENT] > enter PIN when requested > wait for "Connected: no" > exit Unfortunately, none of the above works anymore for me: [bluetooth]# power on No default controller available [bluetooth]# scan on No default controller available [bluetooth]# agent on Agent registration enabled [bluetooth]# default-agent No agent is registered [bluetooth]# > After this you should have an rfcomm channel available to the client. I > have the above in an expect script as bluetoothctl has no inate remote > controllability capabilities. No separate pairing app or rfcomm init > script needed. I do not get a /dev/rfcommX, unless I manually set it up like so: # rfcomm bind rfcomm0 hci0 # ls -la /dev/rfcomm* crw-rw 1 root uucp 216, 0 May 29 07:06 /dev/rfcomm0 and hci0 will not come up unless I start it with hciconfig. Despite all this manual intervention bluetooth does not have access or use the rfcomm device, although 'hcitool scan' and 'sdptool browse' return results from my mobile phone. Please note I have not used the previous patch you have posted on the list. These are the BT modules in my 3.12.20-gentoo kernel: $ grep -i BT /usr/src/linux/.config CONFIG_BT=m CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y CONFIG_BT_BNEP=m CONFIG_BT_BNEP_MC_FILTER=y CONFIG_BT_BNEP_PROTO_FILTER=y CONFIG_BT_HIDP=m CONFIG_BT_HCIBTUSB=m CONFIG_BT_HCIBTSDIO=m # CONFIG_BT_HCIUART is not set CONFIG_BT_HCIBCM203X=m # CONFIG_BT_HCIBPA10X is not set # CONFIG_BT_HCIBFUSB is not set # CONFIG_BT_HCIDTL1 is not set # CONFIG_BT_HCIBT3C is not set # CONFIG_BT_HCIBLUECARD is not set # CONFIG_BT_HCIBTUART is not set # CONFIG_BT_HCIVHCI is not set # CONFIG_BT_MRVL is not set # CONFIG_BT_ATH3K is not set CONFIG_MAC_EMUMOUSEBTN=y # CONFIG_INPUT_ATLAS_BTNS is not set # CONFIG_VIDEO_USBTV is not set # CONFIG_SND_BT87X is not set # CONFIG_USB_BTMTK is not set # CONFIG_TOSHIBA_BT_RFKILL is not set # CONFIG_BTRFS_FS is not set # CONFIG_RBTREE_TEST is not set CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=y and I don't recall changing any of them since the good ol' bluez-4 days. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Bluetooth is impossible
> All that is required is emerge bluez, reload dbus, start bluetooth, > emerge blueman-1.21, config asound.conf as above, and restart > alsasound. > > Has anyone gotten bluetooth pairing without a GUI tool such as > blueman? That's the "impossible" part. Thanks Grant for sharing your experience (I'll try blueman version 1.21). I've also struggled with the bluetooth configuration, and I agree: the gentoo guide is outdated (have you contacted the author?). I tried to pair devices from the command line, but it was impossible for me too. Greetings, Damian.
[gentoo-user] Bluetooth problem
Hi all, I have Logitech Dinovo Edge and it works fine before. I update my system recently and my bluetooth is messed up. Every time I start Bluetooth Manager in GNOME I receive this message "Bluez daemon is not running, blueman-manager cannot continue.". I am using Bluez-4.7.1 and Linux kernel 2.34 and 2.35. I also check the output of the lsmod command and modules bnep, hcid and sco are not loaded when bluetooth service start. Plus I get no device when scanning for devices using "hcitool scan" and the utility hid2hci is not in the system path. Any suggestion? Thanks in advance Hung Output of lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 004: ID 046d:c714 Logitech, Inc. Bus 008 Device 003: ID 046d:c713 Logitech, Inc. Bus 008 Device 002: ID 046d:0b04 Logitech, Inc. Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 041e:4055 Creative Technology, Ltd Live! Cam Video IM Pro Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 413c:3010 Dell Computer Corp. Optical Wheel Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Output of lsmod Module Size Used by nvidia 11087655 28 coretemp5654 0 rfcomm 38363 1 l2cap 33680 3 rfcomm snd_seq_dummy 1678 0 snd_seq_oss28171 0 snd_seq_midi_event 6939 1 snd_seq_oss snd_seq53057 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 6394 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss37296 0 snd_mixer_oss 16313 1 snd_pcm_oss snd_hda_codec_realtek 287298 1 snd_hda_intel 22483 1 snd_hda_codec 71101 2 snd_hda_codec_realtek,snd_hda_intel snd_hwdep 6386 1 snd_hda_codec snd_pcm76889 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec snd_timer 20930 2 snd_seq,snd_pcm snd66779 13 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer soundcore 7579 1 snd snd_page_alloc 8428 2 snd_hda_intel,snd_pcm i2c_i8018249 0
Re: [gentoo-user] USB automount
Am 25.09.2012 08:33, schrieb Canek Peláez Valdés: > On Mon, Sep 17, 2012 at 10:45 AM, Stefan G. Weichinger wrote: >> Am 16.09.2012 20:45, schrieb Canek Peláez Valdés: >> >>> This workaround also works in my systemd-only overlay. So, if you have >>> the systemd flag in any of those four packages, disable it and >>> everything should work. Just to be explicit, the versions are: >>> >>> gnome-base/gdm-3.4.1-r1 >>> gnome-base/gnome-session-3.4.2.1 >>> gnome-base/gnome-shell-3.4.2 >>> sys-auth/polkit-0.107:0 >> >> confirming this. I have exactly your mentioned versions with >> USE="-systemd" and suspend/hibernate option returns, I could mount/use a >> DVD right now ... yes! > > OK; now I can put this whole thing behind me. You can read the bug again: > > https://bugs.freedesktop.org/show_bug.cgi?id=53905 > > but the short answer is that you cannot let both systemd and > consolekit to manage sessions. The problem (in my case) was that I was > using accountsservice 0.6.22, which depends on consolekit. I upgraded > to accountsservice 0.6.24 (which can depend on systemd), I removed all > consolekit USE-flags (except for bluez: bluez uses consolekit to pull > either consolekit or systemd; I reported a bug[1]), and after an > emerge -uDNv world, I removed consolekit (I didn't had any other > package depending on it). > > Now everything works as it should, in both my overlay and in the > vanilla Gentoo tree. Be aware: it works *with systemd*; maybe it works > without it, but I don't know (nor care). All the GNOME session > management is moving to systemd, and I think it's a great idea. > Support for consolekit (which is no longer maintained) is still there, > but I don't know for how long. > > If you want to keep using (the unmaintained) consolekit, be sure to > set "-systemd" in your USE flags. Do not mix systemd and consolekit, > or this bug will hit you. > > Regards. > > [1] https://bugs.gentoo.org/show_bug.cgi?id=436180 Thanks a lot for the feedback. So if I don't use systemd right now, it would be better to keep consolekit? I give it a try now ... compiling stuff without that flag for a test. Stefan
Re: [gentoo-user] Systemd reaches "target Emergency Mode" every boot
Am 28.01.2013 22:27, schrieb Canek Peláez Valdés: > On Mon, Jan 28, 2013 at 3:08 PM, Stefan G. Weichinger wrote: >> Do I have to take special care of polkit/consolekit/pam/whatever? > > Yes, we had a long thread about that some months ago, around November. > Basically, there is lots of stuff that break if you mix up consolekit > and systemd (logind, actually). Maybe the situation has improved, but > in my case the simplest solution was to purge consolekit from my > systems (except in my media center, XBMC still uses its d-bus > interfaces). ConsoleKit is unmantained anyway. I removed consolekit already and I right now recompile all the packages depending on it. > I have USE="-consolekit" where necessary (basically gdm, pambase and > bluez), and USE="systemd" everywhere else. Please note that some > packages need to unmask the systemd flag: > > # cat /etc/portage/profile/package.use.mask > media-sound/pulseaudio-systemd > net-misc/networkmanager -systemd > sys-auth/polkit -systemd > sys-fs/udisks -systemd > sys-power/upower -systemd Followed that as well, thanks. > I believe polkit is the most important, since it's the one controlling > what program can do what, but since I switched completely to systemd > years ago, I just use it everywhere. Things "just work" most of the > time. The logs make me assume that pulseaudio/dbus/bluez drops me out of my session ... although if I use xdm to login, things work fine. No big deal, but gdm is nicer and it just should be possible to use it correctly with systemd. I will dig further ... >> Thanks, Stefan >> >> ps: my bigger hurdle will be the bridging-setup for running >> KVM-virtualization. This was one of the reasons to go back to openrc >> back then. > > I have no experience with that, but if it works in OpenRC it should > work in systemd. Probably better, even. I don't think it won't work, I just wonder how to do it in the right and most efficient way. I will think about that later/tomorrow maybe, already late here ... Best regards, Stefan
Re: [gentoo-user] after last update hciconfig disappeared
On Mon, 27 Mar 2017 12:46:18 -0400, Foster McLane wrote: > > On Mon, Mar 27, 2017 at 12:28:11PM -0400, John Covici wrote: > > On Mon, 27 Mar 2017 08:44:59 -0400, > > Mick wrote: > > > > > > [1 ] > > > On Monday 27 Mar 2017 13:45:08 Raffaele Belardi wrote: > > > > John Covici wrote: > > > > > Hi. After the last update of net-wireless/bluez hciconfig has > > > > > disappeared. Even downgrading did not bring it back, although it was > > > > > there in the previous release. How do I do hciconfig, scan and > > > > > friends now, or is there a way to get them back. > > > > > > > > > > As a workaround I put an old one back just copying the binary, so I > > > > > could proceed, but there has got to be a better way. > > > > > > > > > > Thanks in advance for any suggestions. > > > > > > > > https://wiki.archlinux.org/index.php/bluetooth#Deprecated_method_using_hcico > > > > nfig > > > > > > > > The ebuild lets you specify an extra-tools USE flag, maybe that one gets > > > > them back. > > > > > > > > raffaele > > > > > > > > > I'm on net-wireless/bluez-5.43-r1 with these USE flags: > > > > > > Installed versions: 5.43-r1(09:55:34 02/05/17)(cups obex readline > > > udev - > > > debug -deprecated -doc -experimental -extra-tools -selinux -systemd -test > > > - > > > test-programs -user-session ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" > > > ABI_S390="-32 -64" ABI_X86="64 -32 -x32" PYTHON_TARGETS="python2_7") > > > > > > I still have hciconfig, hcitools, et al. > > > > > > > I did as well, till I upgraded to 5.44 and then even downgrading did > > not bring back the tools. > > > > -- > > Your life is like a penny. You're going to lose it. The question is: > > How do > > you spend it? > > > > John Covici > > cov...@ccs.covici.com > > > > If you are just using the tools in your terminal, 'bluetoothctl' has replaced > those programs. If you are writing scripts with those commands, I do not > know of any worthy replacements besides using the DBus interface > manually. I need to make sure that hci0 is up before I start a program that wants to use it and when I start the bluetooth service, hci0 is down. How to put it up not using a terminal? Or how to get back those hci commands? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] Bluetooth Adapter???
On Saturday 09 July 2005 04:57, timothy johnson wrote: > I am thinking about getting a bluetooth usn adapter to use my old sony > cell phone as a remote for my music server. Just wondering if anyone > has use a bluetooth usb adapter, if there are any howtos to get this > setup??? And if it would be worth it to do it? I have one, works perfectly with BlueZ stuff. I am using it for typing sms with a real keyboard, saving the contacts, move around pictures and use the cell phone as a remote for amarok. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Slot war on my system
On Sun, 03 Jun 2012 12:51:37 -0500, Michael Sullivan wrote: > I try to keep my world file clean. I use -1 whenever merging anything I > don't actually want. I don't want bluedevil (or any of that wireless > crap), but a few years ago the system started requiring bluez and I > couldn't get out of it. I do not ever plan to use wireless on this > box... Do you have the bluetooth USE flag set? Have you emerged kde-meta? -- Neil Bothwick You have the capacity to learn from mistakes. You'll learn a lot today. signature.asc Description: PGP signature
RE: [gentoo-user] Mobile phone
Hi, not shure but maybe you can use the OBEX-Push Service of the Bluez Bluetooth Package... if your phone can handle BT. Cheerz NIC > -Original Message- > From: Keats [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 25, 2005 4:39 PM > To: gentoo-user@lists.gentoo.org > Subject: [gentoo-user] Mobile phone > > hi, > i wonder how to get the pictures from my phone ? > i have it to work with irda via gammu/wammu but this software seems to > be able only to get numbers phone and sms from the phone... > > anyone have done this ? > > thanks. > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
[gentoo-user] after last update hciconfig disappeared
Hi. After the last update of net-wireless/bluez hciconfig has disappeared. Even downgrading did not bring it back, although it was there in the previous release. How do I do hciconfig, scan and friends now, or is there a way to get them back. As a workaround I put an old one back just copying the binary, so I could proceed, but there has got to be a better way. Thanks in advance for any suggestions. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] Re: bluez 5 not connecting
On Wednesday 28 May 2014 20:02:29 Samuli Suominen wrote: > On 28/05/14 21:42, Mick wrote: > > Hmm ... am I alone in this quest? > > See here, http://bugs.gentoo.org/show_bug.cgi?id=505362 Thanks! I missed this bug when I glanced earlier. However, it does not mention rfcomm is now missing, or the fact that the gentoo rc script fails to initialise bluethooth and complains about rfcomm service not having started/exist, or that bluetoothctl now does not work at all. Is all this down to a missing udev rule? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] The story of a successful move from ~x86 back to x86.
Hey all, remember me? I'm the guy with the old desktop from this thread: http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg96277.html That post tells the beginning of the story pretty nicely. To pick up where I left off 11 months ago, I used the computer occasionally as a device to control general IO through the parallel port, but never did anything with portage. When it got cold about a week ago, I determined that it was time to bring the box back from the dead to work as a... space heater. I decided take the ~x86 system, up to date as of January 1st, 2010, and switch back to x86. This was the plan (outlined in a post, by Alan I do believe, from around the same time as the one linked to): 1. Change ACCEPT_KEYWORDS from "~x86" to "x86" in make.conf. 2. Keyword the specific version of all installed packages which are newer than the current stable. 3. Gradually wait for x86 to catch up to the installed system and unkeyword packages as newer versions are installed. In this case, I did most of the waiting for stable to catch up before doing anything else, and it turns out that it paid off (only sixteen packages were in need of keywording). Here's a retroactively simplified summary of what I did, with a more detailed listing below: Changed ACCEPT_KEYWORDS to "x86" in /etc/make.conf. emerge --sync Updated @system Did the layman symlink thing. Removed openrc due to file conflicts (seems to have been replaced?) Had a heck of a time with the libpng 1.2-1.4 update Was puzzled by with the move from dev-libs/poppler to app-text/poppler Updated @world Masked >=sys-apps/v86d-0.1.3-r1...it still won't build correctly. Removed firefox and xulrunner on account of weird slotting problems and xulrunner taking >1 hour to build. Removed xsane and sane-backends because it won't build and I won't be using it. Was slightly confused by the bluez move. Manually installed some grub stages. Keyworded 16 packages which are newer than the current stable (step 2 above). Was exceedingly confused by the gdbm format changes. The only offending database was /etc/sasl2/sasldb2, which I renamed hoping it wouldn't break anything. Updated the kernel according to my usual procedure. emerge -e world (took almost exactly 30.5 hours, no errors) So it's quite possible to move from unstable to stable, it's just not very pretty. Thanks for your advice way back when; it seems to have worked out in the end. Any opinions on what I did right/shouldn't have done the way I did? Marcus Wanner Here's my detailed log of all the commands I ran/changes I made, in chronological order, for those that are interested: changed /etc/make.conf from ~x86 to x86 emerge --sync ln -s /var/lib/layman /usr/local/portage/layman emerge -u system etc-update emerge -C openrc #was causing problem emerge -u system #completing after problem etc-update emerge -uD system (128 packs; 112 done) revdep-rebuild --library '/usr/lib/libpng12.so.0' (it failed because dev-libs/poppler had moved) emerge -C dev-libs/poppler (and 2 similar-named reverse deps) emerge -1 app-text/poppler (to replace it) revdep-rebuild --library '/usr/lib/libpng12.so.0' (42 packs; failed at pygtk again) emerge -av dev-util/lafilefixer lafilefixer --justfixit emerge -uD system (pygtk still failing about -lpng12) emerge libpng:1.2 emerge -uD system (no change) masked >=dev-python/pygtk-2.17.0 emerge -uD system (10 packs) perl-cleaner --all (17 packs) emerge -C dev-util/lafilefixer emerge -u world (49 packs; 6 done; v86d failed due to old kernel) (updated kernel to 2.6.36-r12) emerge -1uv x11-drivers/nvidia-drivers (module-rebuild wanted old version) emerge -u world (41 packs, failed at first one, v86d, again) masked >=sys-apps/v86d-0.1.3-r1 emerge -u world (38 packs; 11 done; failed at mousepad from "cannot find -lpng12") /usr/sbin/libpng-1.4.x-update.sh emerge -C libpng:1.2 emerge -u world (27 packs; 9 done; failed at awesome due to convert using the wrong libjpeg) unmasked pygtk since libpng seems to be fixed revdep-rebuild -L libjpeg.so.7 (failed because of xulrunner upgrade causing slotting problems) emerge -C xulrunner emerge -C firefox (didn't really need them...) Removed xulrunner and firefox from USE revdep-rebuild -L libjpeg.so.7 (failed because of sane-backends downgrade) emerge -uDav @world (to find to-be-downgraded packages) emerge -C bluez-libs bluez-utils cwiid (were bocking net-wireless/bluez-4.75) emerge -uDav @world (to find to-be-downgraded packages) Keyworded 16 to-be-downgraded packages; media-sound/lame-3.98.2-r2 and xfce-base/libxfce4util-4.7.1 were still to be downgraded but are not major so I unkeyworded them. revdep-rebuild -L libjpeg.so.7 (wanted to downgrade sane-backends AGAIN) emerge --oneshot media-gfx/imagemagick:0 (all the others will be rebuilt a
