https://wiki.archlinux.org/api.php?action=feedcontributions&user=Azu&feedformat=atomArchWiki - User contributions [en]2024-03-19T08:11:51ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Bluetooth_headset&diff=294125Bluetooth headset2014-01-23T10:18:36Z<p>Azu: Bluez5 regression bug with HSP/HFP profile support</p>
<hr />
<div>[[Category:Sound]]<br />
[[Category:Bluetooth]]<br />
{{Related articles start}}<br />
{{Related|Bluetooth}}<br />
{{Related|Bluez4}}<br />
{{Related articles end}}<br />
<br />
Before you get started, you have to make sure that [[bluetooth]] is set up and working.<br />
<br />
== ALSA-BTSCO method ==<br />
<br />
{{Out of date|Instructions rely on [[bluez4]].}}<br />
<br />
It is much easier to set up your bluetooth headset today, with bluez >= 3.16. You may want to try the out-of-box python script in [http://fosswire.com/2008/01/11/a2dp-stereo-linux/ this blog] (you need edit the script to work with gconftool-2). There is also a piece of equivalent bash script [http://lymanrb.blogspot.com/2008/05/linux.html here].<br />
<br />
You need your headset's bdaddr. It is of the form ''12:34:56:78:9A:BC''. Either find it in the documentation of your headset, on the headset itself or with the '''hcitool scan''' command.<br />
<br />
Install {{AUR|btsco}}.<br />
<br />
To load the kernel module, type:<br />
# modprobe snd-bt-sco<br />
There will now be an extra audio device. Use {{ic|alsamixer -cN}} (where N is most likely 1) to set the volume. You can access the device with any alsa-capable application by choosing the device ''BT headset'', or with any OSS application by using {{ic|/dev/dspN}} as the audio device.<br />
<br />
But to actually get any sound, you have to connect your headset to the computer first.<br />
<br />
=== Connecting the headset ===<br />
<br />
If you connect your headset for the first time, read the section about pairing first. To connect to your headset to the computer, use the command<br />
$ btsco -f <bdaddr><br />
for example<br />
$ btsco -f 12:34:56:78:9A:BC<br />
<br />
==== Pairing the headset with your computer ====<br />
<br />
The first time you connect the headset, you have to pair it with the computer. To do this, you need your headset's PIN. Depending on your headset you may have to reset the headset and repeat the pairing everytime you used the headset with another bluetooth device.<br />
<br />
There are two ways to pair your headset with the computer:<br />
<br />
===== Using ''bluez-gnome'' =====<br />
<br />
Install the ''bluez-gnome'' package from the community repository. Then start the '''bt-applet''' program. Once you try to connect to the headset, a window will open and ask for the PIN.<br />
<br />
===== Using ''passkey-agent'' =====<br />
<br />
Before connecting to the headset, enter the command<br />
$ passkey-agent --default <pin><br />
where ''<pin>'' is your headset's PIN. Then try to connect to the headset.<br />
<br />
=== Headset and Alsa Devices ===<br />
<br />
1. First if you have not already, [[pacman|install]] {{Pkg|bluez}} from the [[official repositories]].<br />
<br />
2. Scan for your device<br />
$ hcitool (-i <optional hci#>***) scan<br />
<br />
3. Pair your headset with your device:<br />
$ bluez-simple-agent (optional hci# ***) XX:XX:XX:XX:XX:XX<br />
and put in your pin (0000 or 1234, etc)<br />
<br />
4. Make sure your {{ic|/etc/bluetooth/audio.conf}} allows A2DP Audio Sinks. Place this line just bellow the [Genera] heading:<br />
Enable=Source,Sink,Media,Socket<br />
<br />
5. Add this to your {{ic|/etc/asound.conf}} file:<br />
#/etc/asound.conf<br />
<br />
pcm.btheadset {<br />
type plug<br />
slave {<br />
pcm {<br />
type bluetooth<br />
device XX:XX:XX:XX:XX:XX <br />
profile "auto"<br />
} <br />
} <br />
hint {<br />
show on<br />
description "BT Headset"<br />
} <br />
}<br />
ctl.btheadset {<br />
type bluetooth<br />
} <br />
<br />
6. Check to see if it has been added to alsa devices<br />
$ aplay -L<br />
<br />
7. Now play with aplay:<br />
$ aplay -D btheadset /path/to/audio/file<br />
<br />
or Mplayer:<br />
$ mplayer -ao alsa:device=btheadset /path/to/audio/or/video/file<br />
<br />
{{Tip|To find hci# for a usb dongle, type in <br />
$ hcitool dev<br />
}}<br />
<br />
=== Headset's multimedia buttons ===<br />
<br />
In order to get your bluetooth headset's multimedia buttons (play, pause, next, previous) working you need to create {{ic|/etc/modprobe.d/uinput.conf}} containing {{ic|uinput}}.<br />
<br />
== PulseAudio method ==<br />
<br />
{{Out of date|Instructions rely on [[bluez4]] (references to {{ic|/etc/bluetooth/audio.conf}} and ''bluez-simple-agent'').}}<br />
<br />
This one is much easier and more elegant. PulseAudio will seamlessly switch between output devices when the headset is turned on. If you have ALSA as the sound server, you need the following packages installed:<br />
{{Pkg|pulseaudio}} and {{Pkg|pulseaudio-alsa}}.<br />
<br />
Now, to configure the audio output to use bluetooth, just install {{Pkg|pavucontrol}} and run it to configure the audio output:<br />
$ pavucontrol<br />
<br />
See [http://dev.funkynerd.com/knowledgebase/articles/5 this blog] for further explanations. Make sure to take a look at the [[PulseAudio]] wiki entry for setting up PulseAudio, especially if you are running KDE.<br />
<br />
=== Troubleshooting ===<br />
<br />
==== Audio sink fails ====<br />
<br />
Bluetooth headset is connected, but ALSA/PulseAudio fails to pick up the connected device. You will get "Audio sink fails".<br />
According to [http://wiki.gentoo.org/wiki/Bluetooth_Headset gentoo wiki], you have to verify than in {{ic|/etc/bluetooth/audio.conf}} there is {{ic|<nowiki>Enable=Socket</nowiki>}} under the {{ic|[General]}} section heading.<br />
<br />
Just do a {{ic|# systemctl restart bluetooth}} to apply it.<br />
<br />
==== Page timeout issue ====<br />
<br />
If you receive this error whilst trying to pair your headset with your system using bluez-simple-agent, then you can try to restart your system and use the graphical bluez applet of your desktop environment.<br />
<br />
== ALSA, bluez5 and PulseAudio method ==<br />
<br />
<br />
[[ALSA]], [[bluez|bluez5]], and [[PulseAudio]] work together to allow a wireless [[Bluetooth]] headset to play audio. The following method works with a Lenovo T61p laptop and SoundBot SB220 wireless bluetooth headset. The required software stack is extensive and failure to include all components can produce errors which are difficult to understand. The following list of software packages might not be the minimum required set and needs to be examined more closely.<br />
<br />
Bluez5 has a regression causing HSP/HFP Telephone profile to not be available. This regression is documented in the [http://www.freedesktop.org/wiki/Software/PulseAudio/Notes/5.0/ draft release notes for Pulseaudio 5.0] which say (in "Notes for packagers"): "PulseAudio now supports BlueZ 5, but only the A2DP profile. BlueZ 4 is still the only way to make HSP/HFP work." ([https://fedoraproject.org/wiki/Common_F20_bugs#bluez5-profile from here])<br />
<br />
=== Install Software Packages ===<br />
<br />
The core software components are [[ALSA]], Bluez5, [[Pulseaudio]]. However there are additional libraries which are required. As well as a player which can play audio files. The following section lists the software packages installed in order to connect the headset and play audio over the headset.<br />
<br />
==== Install ALSA and associated libraries ====<br />
<br />
[[ALSA]] works with the linux kernel to provide audio services to user mode software. The following packages are used with the [[Bluetooth]] headset: {{Pkg|alsa-utils}}, {{Pkg|alsa-plugins}}, {{Pkg|alsa-tools}}.<br />
<br />
==== Install Bluez5 ====<br />
<br />
Bluez5 is the latest [[Bluetooth]] stack. It is required for [[PulseAudio]] to interface with wireless headsets. Required packages: {{Pkg|bluez}}, {{Pkg|bluez-utils}}, {{Pkg|bluez-libs}}.<br />
<br />
==== Install PulseAudio ====<br />
<br />
[[PulseAudio]] interfaces with [[ALSA]], Bluez and other user mode programs. The {{AUR|pulseaudio-git}} package from [[AUR]] has capabilities not provided by the stock {{Pkg|pulseaudio}} package. The additional capabilities are required by Bluez5. More info regarding the differences between Bluez5 and PulseAudio are [https://bbs.archlinux.org/viewtopic.php?pid=1302270#p1302270 here.]<br />
<br />
Required packages: {{AUR|pulseaudio-git}}, {{Pkg|pavucontrol}}.<br />
<br />
==== Install Audacious ====<br />
<br />
[[Audacious]] is a program which plays audio files. It can work directly with [[ALSA]] or with [[PulseAudio]]. Required packages: {{Pkg|audacious}}, {{Pkg|audacious-plugins}}.<br />
<br />
=== Procedure ===<br />
<br />
Once the required packages are installed, use this procedure to play audio with a bluetooth headset. The high level overview of the procedure is to pair the headset, connect the headset, configure the player and pulse audio controller and then play audio.<br />
<br />
Start the bluetooth service as root or use sudo<br />
# systemctl start bluetooth<br />
<br />
Verify Bluetooth is started<br />
# systemctl status bluetooth<br />
bluetooth.service - Bluetooth service<br />
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled)<br />
Active: active (running) since Sat 2013-12-07 12:31:14 PST; 12s ago<br />
Docs: man:bluetoothd(8)<br />
Main PID: 3136 (bluetoothd)<br />
Status: "Running"<br />
CGroup: /system.slice/bluetooth.service<br />
└─3136 /usr/lib/bluetooth/bluetoothd<br />
<br />
Dec 07 12:31:14 t61p systemd[1]: Starting Bluetooth service...<br />
Dec 07 12:31:14 t61p bluetoothd[3136]: Bluetooth daemon 5.11<br />
Dec 07 12:31:14 t61p systemd[1]: Started Bluetooth service.<br />
Dec 07 12:31:14 t61p bluetoothd[3136]: Starting SDP server<br />
Dec 07 12:31:14 t61p bluetoothd[3136]: Bluetooth management interface 1.3 i...ed<br />
Hint: Some lines were ellipsized, use -l to show in full.<br />
<br />
Start the pulseaudio daemon. This must be done after X windows is started and as a normal user.<br />
$ pulseaudio -D<br />
<br />
Verify the pulseaudio daemon is running.<br />
$ pulseaudio --check -v<br />
I: [pulseaudio] main.c: Daemon running as PID 3186<br />
<br />
Start up bluetoothctl as root and pair and connect your headset. As a regular user, bluetoothctl will pair but not connect. Perhaps this is related to the config file (shown below) which is setup for what appears to be the root user.<br />
Note: the procedure shown below is for an initial pair and connect of the headphone. If the headset is already paired, then the procedure below can be shortened to: power on, agent on, default-agent, connect <ip address>. The ip address can be seen from the devices command output.<br />
<br />
$ bluetoothctl <br />
[NEW] Controller 00:1E:4C:F4:98:5B t61p-0 [default]<br />
[NEW] Device 00:1A:7D:12:36:B9 SoundBot SB220<br />
[bluetooth]# show<br />
Controller 00:1E:4C:F4:98:5B<br />
Name: t61p<br />
Alias: t61p-0<br />
Class: 0x000000<br />
Powered: no<br />
Discoverable: no<br />
Pairable: yes<br />
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)<br />
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)<br />
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)<br />
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)<br />
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)<br />
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)<br />
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)<br />
Modalias: usb:v1D6Bp0246d050B<br />
Discovering: no<br />
[bluetooth]# power on<br />
[CHG] Controller 00:1E:4C:F4:98:5B Class: 0x0c010c<br />
Changing power on succeeded<br />
[CHG] Controller 00:1E:4C:F4:98:5B Powered: yes<br />
[bluetooth]# agent on<br />
Agent registered<br />
[bluetooth]# default-agent<br />
Default agent request successful<br />
<br />
<power on your headset in pairing mode. Eventually you will see what appears to be a mac address.><br />
[bluetooth]# scan on<br />
Discovery started<br />
[CHG] Controller 00:1E:4C:F4:98:5B Discovering: yes<br />
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -61<br />
[bluetooth]# pair 00:1A:7D:12:36:B9<br />
Attempting to pair with 00:1A:7D:12:36:B9<br />
[CHG] Device 00:1A:7D:12:36:B9 Connected: yes<br />
[CHG] Device 00:1A:7D:12:36:B9 UUIDs has unsupported type<br />
[CHG] Device 00:1A:7D:12:36:B9 Paired: yes<br />
Pairing successful<br />
[bluetooth]# connect 00:1A:7D:12:36:B9<br />
[CHG] Device 00:1A:7D:12:36:B9 Connected: yes<br />
Connection successful<br />
[bluetooth]# info 00:1A:7D:12:36:B9<br />
Device 00:1A:7D:12:36:B9<br />
Name: SoundBot SB220<br />
Alias: SoundBot SB220<br />
Class: 0x240404<br />
Icon: audio-card<br />
Paired: yes<br />
Trusted: no<br />
Blocked: no<br />
Connected: yes<br />
LegacyPairing: yes<br />
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)<br />
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)<br />
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)<br />
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)<br />
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)<br />
<br />
Start up alsamixer, for simplicity un-mute all your outputs. Oddly enough some can be muted though. The ones I had muted during playback were:<br />
* Headphones<br />
* SPIDF<br />
<br />
Start up audacious. Use the menu to select pulseaudio as your output. Somewhere I read that bluez5 requires pulseaudio-git and this jives with my experience.<br />
<br />
Start up pavucontrol in a terminal. In the Outputs tab select the bluetooth headset.<br />
<br />
[http://netskink.blogspot.com/2013/12/pulseaudio-pavucontrol-and-audacious.html screenshot of application settings]<br />
<br />
==== Miscellaneous Configuration Files ====<br />
<br />
For reference these settings were also done.<br />
<br />
===== ALSA /etc/asound.conf =====<br />
<br />
The settings shown at the top of this page was used, but the additional modification for intel laptop soundcards.<br />
<br />
{{bc|<nowiki><br />
pcm.btheadset {<br />
type plug<br />
slave {<br />
pcm {<br />
type bluetooth<br />
device 00:1A:7D:12:36:B9<br />
profile "auto"<br />
}<br />
}<br />
hint {<br />
show on<br />
description "BT Headset"<br />
}<br />
}<br />
ctl.btheadset {<br />
type bluetooth<br />
}<br />
options snd-hda-intel model=laptop<br />
</nowiki>}}<br />
<br />
===== /etc/dbus-1/system.d/bluetooth.conf =====<br />
<br />
The settings here seem to be enabled for root only. See the policy user="root" section. However, if a regular user is specified here, the system fails to start. Someone with more knowledge could explain why.<br />
<br />
{{hc|/etc/dbus-1/system.d/bluetooth.conf|<nowiki><br />
<!-- This configuration file specifies the required security policies for Bluetooth core daemon to work. --><br />
<br />
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"<br />
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"><br />
<busconfig><br />
<br />
<!-- ../system.conf have denied everything, so we just punch some holes --><br />
<br />
<policy user="root"><br />
<allow own="org.bluez"/><br />
<allow send_destination="org.bluez"/><br />
<allow send_interface="org.bluez.Agent1"/><br />
<allow send_interface="org.bluez.MediaEndpoint1"/><br />
<allow send_interface="org.bluez.MediaPlayer1"/><br />
<allow send_interface="org.bluez.ThermometerWatcher1"/><br />
<allow send_interface="org.bluez.AlertAgent1"/><br />
<allow send_interface="org.bluez.Profile1"/><br />
<allow send_interface="org.bluez.HeartRateWatcher1"/><br />
<allow send_interface="org.bluez.CyclingSpeedWatcher1"/><br />
</policy><br />
<br />
<policy at_console="true"><br />
<allow send_destination="org.bluez"/><br />
</policy><br />
<br />
<!-- allow users of lp group (printing subsystem) to communicate with bluetoothd --><br />
<policy group="lp"><br />
<allow send_destination="org.bluez"/><br />
</policy><br />
<br />
<policy context="default"><br />
<deny send_destination="org.bluez"/><br />
</policy><br />
<br />
</busconfig><br />
</nowiki>}}<br />
<br />
===== Tested applications =====<br />
<br />
As noted above this will work easily with audacious. Youtube videos with chromium and flashplayer will work on some videos. If the video has ads it will not work, but if the video does not have ads it will work. Just make sure that after audacious is working with bluetooth headset, start chromium and navigate to youtube. Find a video without leading ads and it should play the audio. If the settings icon has the a menu with two pulldown combo boxes for Speed and Quality it will play.<br />
<br />
== Switch between HSV and A2DP setting ==<br />
This can easily be achieved by the following command where 2 needs to be changed with the correct device number.<br />
<br />
pacmd set-card-profile 2 a2dp<br />
<br />
=== A2DP not working with pulseaudio ===<br />
<br />
If pulseaudio fails when changing the profile to A2DP with bluez 4.1+ and pulseaudio 3.0+, you can try disabling the Socket interface from /etc/bluetooth/audio.conf by removing the line Enable=Socket and adding line Disable=Socket<br />
<br />
Disable=Socket<br />
<br />
== Tested Headsets ==<br />
The following Bluetooth headsets have been tested with Arch Linux<br />
* Philips SHB9100 - Confirmed NOT TO WORK well. Have tried ''everything'' after a while they cut out. Pause and resume too is flakky and basically the whole wireless bluetooth experience is horrible. The following forum post[https://bbs.archlinux.org/viewtopic.php?pid=1315428#p1315428] explains an underlying issue and describes a temporary solution which can be used to improve the audio quality pending a proper fix.<br />
* Parrot Zik - Confirmed to work out of the box with firmware 1.04! The MIC however is detected, but does not work at all. Sometimes it can lag behind (not stutter) but most of the times it is not noticeable unless you playing a game, in which case I would switch to wired which resolves the issue.<br />
* Sony DR-BT50 works for a2dp both with bluez4 and bluez5 (instructions here[http://vlsd.blogspot.com/2013/11/bluetooth-headphones-and-arch-linux.html], subject to change)<br />
* SoundBot SB220 works with bluez5 and pulseaudio-git.<br />
* Auna Air 300 works well with bluez5, pulseaudio-git, and e.g. also mocp when running the latter through padsp. For some reason, a few restarts and re-tries were required, and eventually it just started working. <br />
* Sennheiser MM 400-X works out of the box with bluez5 and pulseaudio 4.0-6<br />
* Audionic BlueBeats (B-777) works out of the box with bluez5 and pulseaudio 4.0-6<br />
<br />
== See also ==<br />
<br />
Alternative method of connecting a BT headset to Linux:<br />
<br />
* [http://gablog.eu/online/node/80 GaBlog - Connect a bluetooth headset to linux]<br />
<br />
Using the same device on Windows and Linux without pairing the device over and over again<br />
<br />
* [http://ubuntuforums.org/showthread.php?p=9363229#post9363229 Dual booting with a bluetooth keyboard]</div>Azuhttps://wiki.archlinux.org/index.php?title=Trinity&diff=220089Trinity2012-08-28T07:43:52Z<p>Azu: /* Issues 3.5.13-sru */</p>
<hr />
<div>[[Category:Desktop environments]]<br />
{{Article summary start}}<br />
{{Article summary text|Trinity is a fork of KDE3 that has been updated to work with current software and libraries. The stable release is 3.5.13. The development release is 14.0.0. The old stable 3.5.12 release was packaged as an updated kdemod3. (note backwards compatibility with 3.5.X was dropped in 14.0.0 to allow install of TDE/TQt without conflict with KDE4/Qt4.}}<br />
{{Article summary heading|Trinity Repositories}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Creating Packages}}<br />
{{Article summary wiki|Custom local repository}}<br />
{{Article summary wiki|pacman Tips}}<br />
{{Article summary end}}<br />
<br />
Trinity Desktop Environment (TDE) is a fork of KDE3 developed by Timothy Pearson ([http://trinitydesktop.org/ trinitydesktop.org]). The goal of this project is to keep the KDE3.5 computing style alive, as well as polish off any rough edges that were present as of KDE 3.5.10. Along the way, new useful features have be added to keep the environment up-to-date. The current stable release of TDE (3.5.13) was released Nov 1st 2011. A software release update (SRU) for 3.5.13 is planned in late 2012. Current development is on 14.0.0. Both 3.5.13(sru) and 14.0.0 build on Arch with all current libraries.<br />
<br />
====The Difference Between 3.5.13 &amp; 14.0.0====<br />
<br />
The versioning change between 3.5.13 and 14.0.0 signifies that backwards compatibility with 3.5.X has been dropped to allow TDE/TQt to install along side KDE4/Qt4 without confict. 14.0.0 will continue to rely on HAL, but subsequent releases will do away with that dependency. 14.0.0 contains the first prototype of media:/ kioslave as a replacement for HAL. 3.5.13 continues backwards compatibility with KDE 3.5.10 code and provides an alternative choice for those that prefer. The 3.5 13 branch will be maintained for the forseeable future.<br />
<br />
Currently the remaining TQt name changes are being implemented after which a tentative code 'freeze' is anticipated to allow user testing and bug identification. 14.0.0 will be a true TDE release with all branding, artwork, and graphics changed and updated for this project rather than using the holdover KDE3 stock images. All in all, the desktop functions beautifully on current graphics libs, systemd-tools, libusbx, udisk2 and other newly implemented hardware paradigms.<br />
<br />
====Trinity Packages for Arch====<br />
<br />
Currently development packages for Arch Linux are available for both 3.5.13-sru and 14.0.0. If server space is available for hosting, binaries can be provided for testing for both i686 and x86_64.<br />
<br />
====Binary Packages====<br />
<br />
Server space has been graciously provided by Axilleas Pi. Install repositories are shown below. Meta package installation for tde is provided under the name 'tde-base'. To install TDE on Arch, simply install with:<br />
<br />
pacman -Sy tde-base<br />
<br />
{{Note|On install, you should expect conflicts with tde-sip and tde-sip4-tqt. The TDE packages 'tde-sip' and 'tde-sip4-tqt' are direct replacements for the 'sip' and 'python2-sip' packages. They simply contain additional extensions for TDE. If you encounter these conflicts, the recommended install is:<br />
<br />
pacman -Rdd sip python2-sip<br />
pacman -Sy tde-base<br />
}}<br />
<br />
{{Warning|If attempting to install 3.5.13 along side KDE4 you will experience conflicts with libart-lgpl and kdebase-workspace. The libart-lgpl packages are equivalent. The kdebase-workspace conflict is with /etc/ksysguarddrc. Both are in the process of being eliminated.}}<br />
<br />
=====TDE Repositories=====<br />
<br />
Repositories for stable 3.5.13-sru snapshots:<br />
<br />
'''Note:''' if you have installed packages before 8/18/12, tde-tdeartwork was misssing. Please install that package to insure your selection of screensavers are complete.<br />
<br />
[http://archlinux.us.to/3.5.13/i686/ http://archlinux.us.to/3.5.13/i686/]<br />
[http://archlinux.us.to/3.5.13/x86_64/ http://archlinux.us.to/3.5.13/x86_64/]<br />
<br />
Example /etc/pacman.conf settings:<br />
<br />
[tde3513]<br />
Server = http://archlinux.us.to/3.5.13/$arch<br />
<br />
Repositories for development 14.0.0 snapshots (expected by 9/1):<br />
<br />
[http://archlinux.us.to/14.0.0/i686/ http://archlinux.us.to/14.0.0/i686/]<br />
[http://archlinux.us.to/14.0.0/x86_64/ http://archlinux.us.to/14.0.0/x86_64/]<br />
<br />
Example /etc/pacman.conf settings:<br />
<br />
[tde1400]<br />
Server = http://archlinux.us.to/14.0.0/$arch<br />
<br />
===Starting and Running Trinity on Arch===<br />
After a successful install of TDE, starting TDE from the command line or configuring /etc/inittab to launch tdm is straightforward. The init script for the display manager has been renamed from kdm to tdm to avoid conflicts.<br />
<br />
====Configuring Trinity to work with startx====<br />
Trinity provides a normal &lsquo;starttde&rsquo; in /opt/trinity/bin. (symlink provided in 3.5.13) The easiest way to start Trinity is to simply add &lsquo;/opt/trinity/starttde&rsquo; entry at the end of ~/.xinitrc. If you do not presently have ~/.xinitrc, then simply create it with the following entry:<br />
<br />
exec /opt/trinity/bin/starttde<br />
<br />
Then from the command line, just type &lsquo;startx&rsquo;<br />
<br />
startx<br />
<br />
====Configuring Trinity kdm Greeter====<br />
Trinity provides a great looking tdm graphical interface. The tde-tdebase PKGBUILD has been updated to install the trinity.desktop file in /etc/X11/sessions. In order to automatically lauch tdm on boot, all that is needed is to edit /etc/inittab and change the runlevel 5 x startup to:<br />
<br />
x:5:respawn:/opt/trinity/bin/tdm -nodaemon<br />
<br />
If you modified inittab in runlevel 3, you can use &lsquo;# telinit 5&rsquo; to initialize the runlevel 5 services from the command line.<br />
<br />
If you experiment with other display managers (slim, etc..) please drop a quick howto here.<br />
<br />
===Known Issues===<br />
<br />
The following are known issues with the current builds and workarounds<br />
<br />
====Issues 3.5.13-sru====<br />
<br />
The following are issues that are specific to the 3.5.13-sru release:<br />
<br />
KHelpCenter documentation from packages built with autotools are installed in /opt/trinity/share/doc/HTML while documentation from CMake packages are installed in /opt/trinity/share/doc/kde/HTML. This means roughly one-half of the help files are missing from the khelpcenter browser. This is currently being fixed in the GIT tree and the next set of packages will have all help documentation in the chosen standard location of /opt/trinity/share/doc/tde/HTML. This also insures a future /usr install will not conflict with any 'kde' help files. As a workaround in the mean time, after installing 3.5.13-sru:<br />
<br />
cd /opt/trinity/share/doc/kde/HTML/en # substitute your &lt;lang&gt; for 'en'<br />
for i in ../../../HTML/en/*/; do ln -s $i; done<br />
<br />
<br />
Pkg tde-tdesvn for x86_64 had been built with libpath "/opt/trinity/lib64" and "/opt/trinity/lib64/trinity" , but there was no any records in libpath about them. Then, starting kdesvn you get error "libkdesvnpart.la not found in paths". As a workaround you may copy/ln libraries from "/opt/trinity/lib64" and "/opt/trinity/lib64/trinity" into "/opt/trinity/lib" and "/opt/trinity/lib/trinity" accordingly or try to create libpath record and ldconfig after it.<br />
<br />
====Issues 14.0.0====<br />
<br />
None known<br />
<br />
=== PKGBUILDS for Trinity - Current GIT Code ===<br />
<br />
For a snapshot of PKGBUILD sources for building against the current GIT tree, see: http://www.3111skyline.com/dl/dt/tde/src (R14) and http://www.3111skyline.com/dl/dt/tde/src3513 (3.5.13-sru), '''AND READ''' http://www.3111skyline.com/dl/dt/tde/src/README-building.txt<br />
<br />
{{Note|Final PKGBUILD source files will be moved to the tdepackaging GIT tree after 14.0.0 is released.}}<br />
<br />
===Contributors===<br />
At present, the Trinity project for Arch Linux is just beginning. Interest in the project and [http://trinitydesktop.org/contributors.php the list of contributors] is growing. Anyone wanting to help can simply join in. Please email Calvin Morrison.<br />
<br />
====Archlinux====<br />
* Calvin Morrison: Trinity and Arch a/k/a "mutantturkey", PKGBUILD development and collaboration.<br />
* Kaiting Chen: Arch Linux - server space for testing Trinity binaries in the past.<br />
* Albert Vaca: kdemod3 updated based on Trinity Stable codebase.<br />
* David C. Rankin: 14.0.0 (3.5.13-sru) Development &amp; Packaging<br />
<br />
====Developers====<br />
* Timothy Pearson: Project administrator, Primary developer, Build farm administrator, Debian/Ubuntu packaging maintainer.<br />
* Darrell Anderson: 3.5.13 -> 14.0.0 Lead coordinator for development and rebranding. Build system preprocessor improvements.<br />
* Sl&aacute;vek Banko: 3.5.13-sru developer, GIT maintainer, R14 backport selection and integration.<br />
* Serghei Amelian: General functionality enhancements, CMake build system developer/maintainer.<br />
* "Woodsman": Vanilla build testing, Slackware packaging maintainer.<br />
* Francois Andriot: Developer, Redhat/Fedora packaging maintainer.<br />
* David Rankin: 3.5.13-sru &amp; R14 development, upstream library change implementation, graphics, Arch Packaging.<br />
<br />
====Content Distribution====<br />
* University of Idaho: Mirror 1 [United States]<br />
* Jens Dunzweiler: Mirror 2 [Germany]<br />
* Inga Muste: Kubuntu LiveCD mirror<br />
<br />
====Web Team====<br />
*Calvin Morrison: Website design.<br />
*Inga Muste: Website design.<br />
<br />
===Trinity Resources===<br />
The Trinity site has a number of good resources available. As with any rapidly developing project, the documentation is somewhat sparse, but it does provide a good basic road-map to follow here. The mailing list has approximately the same volume as the arch-user list, so it will not overwhelm your inbox. If you want to help with this project, it is strongly recommended that you also join the trinity-devel mailing list. All of the following links are available from the Trinity project site. A quick list of helpful links to the project follows:<br />
* '''Main Project Site:''' [http://trinitydesktop.org/ http://trinitydesktop.org]<br />
* '''TDE GIT Repository:''' [http://git.trinitydesktop.org/cgit/ http://git.trinitydesktop.org/cgit/]<br />
* '''TDE GIT SCM Manager:''' [http://scm.trinitydesktop.org/scm/ http://scm.trinitydesktop.org/scm/]<br />
* '''Bug Reporting:''' [http://bugs.trinitydesktop.org/ http://bugs.trinitydesktop.org]<br />
* '''Mailing Lists:''' [http://trinitydesktop.org/mailinglist.php http://trinitydesktop.org/mailinglist.php]<br />
* '''Developers Web:''' [http://trinitydesktop.org/wiki/bin/view/Developers/WebHome http://trinitydesktop.org/wiki/bin/view/Developers/WebHome]<br />
* '''Trinity Qt4 Conversion:''' [http://trinitydesktop.org/wiki/bin/view/Developers/TrinityTQtforQt4Conversion http://trinitydesktop.org/wiki/bin/view/Developers/TrinityTQtforQt4Conversion]<br />
* '''How To Build:''' [http://trinitydesktop.org/wiki/bin/view/Developers/HowToBuild http://trinitydesktop.org/wiki/bin/view/Developers/HowToBuild]<br />
<br />
====Trinity Build Order====<br />
The required build order is specified in the [http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild Trinity-HowToBuild]. After building tdebase, you can start the desktop.<br />
<br />
{{Note|Trinity should be built from a '''clean''' build environment without KDE4 present. Using an Arch chroot (archroot) is the proper way to build. See: [https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot DeveloperWiki:Building in a Clean Chroot] for details. <br />
(1) 'sudo mkarchroot -u $CHROOT/root' # update the chroot<br />
&nbsp;<br />
(2) 'sudo makechrootpkg -c -r $CHROOT' # build first package with the -c option<br />
&nbsp;<br />
(3) 'sudo makechrootpkg -r $CHROOT' # build remaining packages without update <br />
}}<br />
<br />
====Trinity Build Issues====<br />
<br />
=====Build in a new Arch chroot=====<br />
{{Warning|Trinity on Arch must be built in a clean environment. }}<br />
Set up your chroot for building by referencing [https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot DeveloperWiki:Building in a Clean Chroot]. Make sure you configure your 'local' repository in $CHROOT/root/repo and add each package built to the repository as outlined in the DeveloperWiki.<br />
<br />
===Development Status===<br />
<br />
The following packages have been successfully built from the TDE GIT tree for the upcoming release.<br />
<br />
====Required AUR Packages====<br />
<br />
hal 0.5.14-14<br />
hal-info 0.20091130-7<br />
libutempter 1.1.5-8<br />
wv2 (dependency for koffice)<br />
<br />
====Completed Packages - 14.0.0 &amp; 3.5.13-sru====<br />
<br />
tde-abakus<br />
tde-amarok<br />
tde-arts<br />
tde-avahi-tqt<br />
tde-basket<br />
tde-dbus-1-tqt<br />
tde-dbus-tqt<br />
tde-digikam<br />
tde-dolphin<br />
tde-filelight<br />
tde-gtk-qt-engine<br />
tde-gwenview<br />
tde-k3b<br />
tde-k9copy<br />
tde-katapult<br />
tde-kaffeine<br />
tde-kbarcode<br />
tde-kbookreader<br />
tde-kdiff3<br />
tde-kdirstat<br />
tde-kgtk-qt3<br />
tde-kima<br />
tde-kio-locate<br />
tde-kipi-plugins<br />
tde-kmplayer<br />
tde-knemo<br />
tde-knetload<br />
tde-knetstats<br />
tde-knutclient<br />
tde-koffice<br />
tde-konversation<br />
tde-kpowersave<br />
tde-krename<br />
tde-krusader<br />
tde-ksplash-engine-moodin<br />
tde-libart-lgpl<br />
tde-libcaldav<br />
tde-libcarddav<br />
tde-libkdcraw<br />
tde-libkexiv2<br />
tde-libkipi<br />
tde-libksquirrel<br />
tde-python-tqt<br />
tde-rosegarden<br />
tde-sip<br />
tde-sip4-tqt<br />
tde-soundkonverter<br />
tde-tde-style-qtcurve<br />
tde-tdeaccessibility<br />
tde-tdeaddons<br />
tde-tdeadmin<br />
tde-tdeartwork<br />
tde-tdebase<br />
tde-tdeedu<br />
tde-tdegames<br />
tde-tdegraphics<br />
tde-tdelibs<br />
tde-tdemultimedia<br />
tde-tdenetwork<br />
tde-tdepim<br />
tde-tdesdk<br />
tde-tdesvn<br />
tde-tdetoys<br />
tde-tdeutils<br />
tde-tdevelop<br />
tde-tdewebdev<br />
tde-tqca-tls<br />
tde-tqt3<br />
tde-tqtinterface<br />
tde-twin-style-crystal<br />
tde-wlassistant<br />
tde-yakuake<br />
<br />
====TDE GIT Application in Need of Packaging/Updating====<br />
<br />
The following is a list of packages that need PKGBUILDs create and/or code fixes to build with current libraries. If you can help with the project and code updates then please join us on the trinity-devel list (trinity-devel@lists.pearsoncomputing.net). Visit http://www.trinitydesktop.org/mailinglist.php for more information.<br />
<br />
adept<br />
bibletime<br />
compizconfig-backend-kconfig<br />
desktop-effects-tde<br />
filelight-l10n<br />
fusion-icon<br />
kaffeine-mozilla<br />
kbfx<br />
kchmviewer<br />
kcmautostart<br />
kcpuload<br />
kdbusnotification<br />
kdpkg<br />
keep<br />
kerry<br />
kile<br />
kio-apt<br />
kio-umountwrapper<br />
kiosktool<br />
kmyfirewall<br />
kmymoney<br />
knetworkmanager8<br />
knetworkmanager9<br />
knights<br />
knowit<br />
kopete-otr<br />
kpicosim<br />
kpilot<br />
kpowersave-nohal<br />
kradio<br />
kstreamripper<br />
ksystemlog<br />
ktechlab<br />
ktorrent<br />
kvirc<br />
kvkbd<br />
kvpnc<br />
piklab<br />
potracegui<br />
qt4-tqt-theme-engine<br />
smartcardauth<br />
smb4k<br />
soundkonverter<br />
tde-guidance<br />
tde-style-lipstik<br />
tde-systemsettings<br />
tdesudo<br />
tdesvn<br />
tellico<br />
libtqt-perl<br />
pytdeextensions<br />
python-trinity<br />
tdebindings<br />
tdesdk</div>Azu