https://wiki.archlinux.org/api.php?action=feedcontributions&user=Catlover2&feedformat=atomArchWiki - User contributions [en]2024-03-29T02:33:39ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=CUPS/Printer-specific_problems&diff=575801CUPS/Printer-specific problems2019-06-17T08:07:23Z<p>Catlover2: Small wording fixes</p>
<hr />
<div>[[Category:Printers]]<br />
[[ja:CUPS/プリンター別の問題]]<br />
[[ru:CUPS (Русский)/Printer-specific problems]]<br />
{{Related articles start}}<br />
{{Related|CUPS}}<br />
{{Related|CUPS/Troubleshooting}}<br />
{{Related articles end}}<br />
<br />
This article contains printer or manufacturer-specific instructions for [[CUPS]].<br />
See [http://www.openprinting.org/printers OpenPrinting] if your printer is not already listed here, or if none of the listed drivers work.<br />
<br />
{{Note|If you add a printer to this list, consider contributing your entry to [https://wiki.linuxfoundation.org/openprinting/database/databaseintro OpenPrinting] - that way users of other distributions will also benefit!}}<br />
<br />
==Brother==<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| DCP-135C || {{AUR|brother-dcp135c}} ||<br />
|-<br />
| DCP-150C || {{AUR|brother-dcp150c}} ||<br />
|-<br />
| DCP-7020 || [[foomatic]] || Or Brother's driver.<br />
|-<br />
| DCP-7030 || {{AUR|brother-dcp7030}} ||<br />
|-<br />
| DCP-7065DN || {{AUR|brother-dcp7065dn}} ||<br />
|-<br />
| DCP-J515W || {{AUR|brother-dcp-j515w}} ||<br />
|-<br />
| FAX-2820 || {{AUR|brother-cups-wrapper-laser}} ||<br />
|-<br />
| FAX-2840 || {{AUR|brother-fax2840}} || Or [[foomatic]] - works mostly with {{ic|hpijs-pcl5e.ppd}}. Same as the HL-2170W.<br />
|-<br />
| FAX-2940 || {{AUR|brother-fax2940}} ||<br />
|-<br />
| HL-2030 || [[foomatic]] || Or {{AUR|brother-hl2030}}<br />
|-<br />
| HL-2035 || [[foomatic]] || Should be compatible with any drivers for the HL-2030.<br />
|-<br />
| HL-2040 || [[foomatic]] || Or {{AUR|brother-hl2040}}<br />
|-<br />
| HL-2130 || [[foomatic]] (using the HL-2140 driver) || Or {{Pkg|hplip}}<br />
|-<br />
| HL-2140 || [[foomatic]] || Or {{AUR|brother-hl2140}}<br />
|-<br />
| HL-2170W || [[foomatic]] || Or Brother's driver. <br />
|-<br />
| HL-2230 || [[foomatic]] || Same as HL-2170W. Select HL-2170W as the driver in CUPS admin when adding a printer.<br />
|-<br />
| HL-2250DN || {{AUR|brother-hl2250dn}} ||<br />
|-<br />
| HL-2270DW || {{AUR|brother-hl2270dw}} ||<br />
|-<br />
| HL-2280DW || {{AUR|brother-hl2280dw}} ||<br />
|-<br />
| HL-3045CN || Install Brother's driver. ||<br />
|-<br />
| HL-3140CW || {{AUR|brother-hl3140cw}} || Use IPP and Brother's driver to avoid page-shrinking and endless blank printouts<br />
|-<br />
| HL-3150CDW || {{AUR|brother-hl3150cdw}} ||<br />
|-<br />
| HL-3170CDW || {{AUR|brother-hl3170cdw}} ||<br />
|-<br />
| HL-4150CDN || {{AUR|brother-hl4150cdn}} ||<br />
|-<br />
| HL-5140 || [[foomatic]] || Or Brother's driver.<br />
|-<br />
| HL-5340 || [[foomatic]] || Using the ''Generic PCL 6/PCL XL Printer - CUPS+Gutenprint'' ({{pkg|gutenprint}} and {{pkg|foomatic-db-gutenprint-ppds}}). Or Brother's driver, which may result in failed prints with postscript errors.<br />
|-<br />
| HL-L2300D || {{AUR|brother-hll2300d}} || <br />
|-<br />
| HL-L2340DW || {{AUR|brother-hll2340dw}} ||<br />
|-<br />
| HL-L2350DW || {{AUR|brother-hll2350dw}} ||<br />
|-<br />
| HL-L2360DN || {{AUR|brother-hll2360d}} ||<br />
|-<br />
| HL-L2360DW || {{AUR|brother-hll2360d}} ||<br />
|-<br />
| HL-L2365DW || {{AUR|brother-hll2360d}} ||<br />
|-<br />
| HL-L2380DW || {{AUR|brother-hll2380dw}} ||<br />
|-<br />
| HL-L2395DW || {{AUR|brother-hll2395dw}} || Use the {{ic|socket}} protocol as described in [[#Network printers]]<br />
|-<br />
| HL-L5100DN || HP LaserJet Foomatic driver || This model will emulate a HP LaserJet. Use the {{ic|lpd}} protocol as described in [[#Network printers]].<br />
|-<br />
| HL-L8360CDW || {{AUR|brother-hll8360cdw-cups-bin}} ||<br />
|-<br />
| MFC-420CN || {{AUR|brother-mfc-420cn}} ||<br />
|-<br />
| MFC-440CN || {{AUR|brother-mfc-440cn}} ||<br />
|-<br />
| MFC-7360N || {{AUR|brother-mfc7360n}} ||<br />
|-<br />
| MFC-7460DN || [[Gutenprint]] || Use the ''Generic PCL 6 Printer wide margin - CUPS+Gutenprint'' driver, with address {{ic|ipp://hostname-or-ip/pcl_p1}}.<br />
|-<br />
| MFC-7840W || {{AUR|brother-mfc-7840w}} ||<br />
|-<br />
| MFC-9320CW || Install Brother's driver. ||<br />
|-<br />
| MFC-9332CDW || {{AUR|brother-mfc-9332cdw}} ||<br />
|-<br />
| MFC-9840CDW || [[foomatic]] || Or Brother's driver. This printer also works with the generic PCL-6 driver from the {{Pkg|gutenprint}} package. Use '''pcl_p1''' for the printer's address when using the PCL-6 driver.<br />
|-<br />
| MFC-J470DW || {{AUR|brother-mfc-j470dw}} || Use the {{ic|ipp}} protocol as described in [[#Network printers]].<br />
|-<br />
| MFC-J4710DW || {{AUR|brother-mfc-j4710dw}} ||<br />
|-<br />
| MFC-J480DW || {{AUR|brother-mfc-j480dw}} || Use the {{ic|ipp}} protocol as described in [[#Network printers]].<br />
|-<br />
| MFC-J5520DW || {{AUR|brother-mfc-j5520dw}} ||<br />
|-<br />
| MFC-J5910DW || {{AUR|brother-mfc-j5910dw}} ||<br />
|-<br />
| MFC-J650DW || Install Brother's driver. ||<br />
|-<br />
| MFC-J885DW || {{AUR|brother-mfc-j885dw}} ||<br />
|-<br />
| MFC-J985DW || {{AUR|brother-mfc-j985dw}} ||<br />
|-<br />
| MFC-L2700DW || {{AUR|brother-mfc-l2700dw}} || Please look also at the comments section of the AUR package page. <br />
|-<br />
| MFC-L8600CDW || {{AUR|brother-mfc-l8600cdw}} || Please follow the instructions on the AUR page.<br />
|-<br />
| QL-500 || {{AUR|brother-ql500}} ||<br />
|-<br />
| QL-570 || {{AUR|brother-ql570}} ||<br />
|-<br />
| QL-580N || {{AUR|brother-ql580n}} ||<br />
|-<br />
| QL-650TD || {{AUR|brother-ql650td}} ||<br />
|-<br />
| QL-700 || {{AUR|brother-ql700}} ||<br />
|-<br />
| QL-710W || {{AUR|brother-ql710w}} ||<br />
|-<br />
| QL-720NW || {{AUR|brother-ql720nw}} ||<br />
|-<br />
| QL-1050 || {{AUR|brother-ql1050}} || <br />
|-<br />
| QL-1050N || {{AUR|brother-ql1050n}} ||<br />
|-<br />
| QL-1060 || {{AUR|brother-ql1060n}} ||<br />
|-<br />
| TD-2020 || {{AUR|brother-td2020}} ||<br />
|-<br />
| TD-2120N || {{AUR|brother-td2120n}} ||<br />
|-<br />
| TD-2130N || {{AUR|brother-td2130n}} ||<br />
|-<br />
| TD-4000 || {{AUR|brother-td4000}} ||<br />
|-<br />
| TD-4100N || {{AUR|brother-td4100n}} ||<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
===Network printers===<br />
For network printers, use {{ic|ipp://'''printer_ip'''/ipp/port1}} as printer address.<br />
For some older printers, this might not work. If not, try {{ic|lpd://'''printer_ip'''/BINARY_P1}} instead.<br />
<br />
Some printers use the socket protocol. For these printers, use {{ic|socket://'''printer_ip''':9100}}.<br />
For http, use {{ic|http://'''printer_ip'''/POSTSCRIPT_P1}}.<br />
<br />
===Custom drivers===<br />
<br />
Brother provides custom drivers on their website, either in source tarball, rpm, or deb form. [[Packaging Brother printer drivers]] covers creating [[PKGBUILD]]s from the existing RPM packages.<br />
{{Note|The source packages might be a better alternative to the rpm packages, provided they contain all the needed files.}}<br />
<br />
====Manually installing from the RPM packages====<br />
<br />
{{Warning|This should ideally be automated in a [[PKGBUILD]]}}<br />
<br />
[[Install]] the {{Pkg|rpmextract}} package, and extract both rpm packages using {{ic|rpmextract.sh}}. Extracting both files will create a var and a usr directory - move the contents of both directories into the corresponding root directories.<br />
<br />
Run the cups wrapper file in {{ic|/usr/local/Brother/cupswrapper}}. This should automatically install and configure your brother printer.<br />
<br />
For some of the drivers 32 bit libraries may need to be installed from [[multilib]].<br />
<br />
===Updating the firmware===<br />
<br />
[[Install]] {{pkg|net-snmp}} and run:<br />
<br />
snmpwalk -c public $PRINTER_IP | grep -A 1 3.6.1.4.1.2435.2.4.3.99.3.1.6.1.2<br />
<br />
At this point, you will have the relevant data to get a valid firmware download link from Brother. The file should look similar to the one below:<br />
<br />
{{hc|request.xml|<br />
<REQUESTINFO><br />
<FIRMUPDATETOOLINFO><br />
<FIRMCATEGORY>MAIN</FIRMCATEGORY><br />
<OS>LINUX</OS><br />
<INSPECTMODE>1</INSPECTMODE><br />
</FIRMUPDATETOOLINFO><br />
<br />
<FIRMUPDATEINFO><br />
<MODELINFO><br />
<SELIALNO></SELIALNO><br />
<NAME>MFC-9330CDW</NAME><br />
<SPEC>0401</SPEC><br />
<DRIVER></DRIVER><br />
<FIRMINFO><br />
<FIRM><br />
<ID>MAIN</ID><br />
<VERSION>R1506121801:4504</VERSION><br />
</FIRM><br />
<FIRM><br />
<ID>SUB1</ID><br />
<VERSION>1.07</VERSION><br />
</FIRM><br />
<FIRM><br />
<ID>SUB2</ID><br />
<VERSION>L1505291600</VERSION><br />
</FIRM><br />
</FIRMINFO><br />
</MODELINFO><br />
<DRIVERCNT>1</DRIVERCNT><br />
<LOGNO>2</LOGNO><br />
<ERRBIT></ERRBIT><br />
<NEEDRESPONSE>1</NEEDRESPONSE><br />
</FIRMUPDATEINFO><br />
</REQUESTINFO><br />
}}<br />
<br />
Post this file to Brother:<br />
<br />
curl -X POST -d @request.xml https://firmverup.brother.co.jp/kne_bh7_update_nt_ssl/ifax2.asmx/fileUpdate -H "Content-Type:text/xml" > response.xml<br />
<br />
In {{ic|response.xml}} you will find a {{ic|<PATH>}} tag that contains the firmware download URL. Next, download the firmware, push it to the printer, and let the printer process it. Before that is done, change the Admin password to something known, it will be used as the user to log into the FTP site (VERY bad practice, don't do this). <br />
<br />
wget http://update-akamai.brother.co.jp/CS/LZ4266_W.djf<br />
ftp $PRINTER_IP<br />
bin<br />
hash<br />
send LZ4266_W.djf<br />
bye<br />
<br />
With that, the printer will restart, and the latest firmware will be installed and (hopefully) your printing woes will be solved.<br />
<br />
==Canon==<br />
<br />
There are many possible drivers for Canon printers. [http://gimp-print.sourceforge.net/p_Supported_Printers.php Many Canon printers] are supported by [[Gutenprint]]. Some of Canon's LBP, iR, and MF printers use a driver supporting the UFR II/UFR II LT/LIPSLX protocols, which is available as {{AUR|cndrvcups-lb}} or {{AUR|cndrvcups-lb-bin}}. Others use the [[#CARPS]], [[#cnijfilter]] ([[AUR|cnijfilter2]] / [[AUR|cnijfilter2-bin]]), or [[Canon CAPT]] drivers.<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| iP4300<br />
| [[Gutenprint]]<br />
| Or use the [http://www.turboprint.info/ TurboPrint] driver.<br />
|-<br />
| LBP810 || rowspan="34" | [[Canon CAPT]] ||<br />
|-<br />
| LBP1120 ||<br />
|-<br />
| LBP1210 ||<br />
|-<br />
| LBP2900 ||<br />
|-<br />
| LBP3000 ||<br />
|-<br />
| LBP3010 ||<br />
|-<br />
| LBP3018 ||<br />
|-<br />
| LBP3050 ||<br />
|-<br />
| LBP3100 ||<br />
|-<br />
| LBP3108 ||<br />
|-<br />
| LBP3150 ||<br />
|-<br />
| LBP3200 ||<br />
|-<br />
| LBP3210 ||<br />
|-<br />
| LBP3250 ||<br />
|-<br />
| LBP3300 ||<br />
|-<br />
| LBP3310 ||<br />
|-<br />
| LBP3500 ||<br />
|-<br />
| LBP5000 ||<br />
|-<br />
| LBP5050 series ||<br />
|-<br />
| LBP5100 ||<br />
|-<br />
| LBP5300 ||<br />
|-<br />
| LBP6000 ||<br />
|-<br />
| LBP6018 ||<br />
|-<br />
| LBP6020 ||<br />
|-<br />
| LBP6200 ||<br />
|-<br />
| LBP6300 ||<br />
|-<br />
| LBP6300n ||<br />
|-<br />
| LBP6310dn ||<br />
|-<br />
| LBP7010C ||<br />
|-<br />
| LBP7018C ||<br />
|-<br />
| LBP7200Cdn (network mode) ||<br />
|-<br />
| LBP7200C series ||<br />
|-<br />
| LBP7210Cdn ||<br />
|-<br />
| LBP9100C ||<br />
|-<br />
| MF635Cx || rowspan="2" | {{AUR|cndrvcups-lb-bin}} ||<br />
|-<br />
| MF4720w ||<br />
|-<br />
| MG4200 series || {{AUR|cnijfilter-mg4200}} || Avoid the [[CUPS#Web interface|web interface]] when adding the printer as it won't find the PPD file.<br />
|-<br />
| MX490 || rowspan="3" | {{AUR|cnijfilter2}}<br />{{AUR|cnijfilter2-bin}} ||<br />
|-<br />
| MX492 ||<br />
|-<br />
| TS8050 || Without {{AUR|cnijfilter2}} printing will fail with a filter error or you might get "Rendering Completed" and nothing will print<br />
|-<br />
| TS9020 || {{AUR|canon-ts9020}} ||<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
Some Canon printers will use a similar setup to the iP4500, so consider modifying the {{AUR|cnijfilter-ip4500}} package for other, similar printers.<br />
<br />
===CARPS===<br />
<br />
Some of Canon's printers use Canon's proprietary Canon Advanced Raster Printing System (CARPS) driver.<br />
[http://www.rainbow-software.org/2014/01/23/cups-driver-for-canon-carps-printers/ Rainbow Software] have managed to reverse engineer the CARPS data format and have successfully created a CARPS CUPS driver, which is available as {{AUR|carps-cups}}.<br />
The project's [https://github.com/ondrej-zary/carps-cups GitHub] page includes a list of working printers.<br />
<br />
===USB over IP (BJNP)===<br />
<br />
Some Canon printers use Canon's proprietary USB over IP BJNP protocol to communicate over the network. There is a CUPS backend for this, which is available as {{AUR|cups-bjnp}}.<br />
<br />
===cnijfilter===<br />
<br />
Some printers using the cnijfilter drivers support the {{ic|cnijnet}} protocol. To find the [[CUPS#Printer URI|printer URI]] run<br />
<br />
$ cnijnetprn --search auto<br />
<br />
and use the {{ic|cnijnet:/}} URI in the output.<br />
<br />
{{Expansion|The URI appears to be of the form {{ic|cnijnet:/}} followed by the MAC address of the printer. If this is the case it would be good to mention it here.}}<br />
<br />
==Dell==<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| 1250C<br />
| {{AUR|foo2zjs-nightly}}<br />
| See http://cybercom.net/~dcoffin/hbpl, the patch has been merged into upstream. The printer may also work with the [[#Phaser 6000B|Xerox Phaser 6000B driver]].<br />
|-<br />
| C1660NW<br />
| {{AUR|foo2zjs-nightly}}<br />
| The printer may also work with the [[#Phaser 6000B|Xerox Phaser 6000B driver]].<br />
|-<br />
| E515,<br />
E515dw<br />
| Install [http://downloads.dell.com/FOLDER03040853M/1/Printer_E515dw_Driver_Dell_A00_LINUX.zip Dell's driver].<br />
| Both ''e515dwcupswrapper-3.2.0-1.i386.deb'' and ''e515dwlpr-3.2.0-1.i386.deb'' need to be installed. You could either write a [[PKGBUILD]], use {{AUR|debtap}}, or use {{AUR|dpkg}} (using dpkg is not recommended as the files will not be managed by [[pacman]]). The driver works on both the x86_64 and i386 platforms, but may require [[multilib]].<br />
|-<br />
| S1130n || rowspan="16" | {{aur|dell-unified-printer-driver}} || rowspan="16" | Driver conflicts with samsung-unified-driver-printer (both create rastertospl and libscmssc.so)<br />
|-<br />
|1130 ||<br />
|-<br />
|1133 ||<br />
|-<br />
|1135n ||<br />
|-<br />
|1815 ||<br />
|-<br />
|2145cn ||<br />
|-<br />
|2335dn ||<br />
|-<br />
|2355dn ||<br />
|-<br />
|5330 ||<br />
|-<br />
|B1160 ||<br />
|-<br />
|B1160w ||<br />
|-<br />
|B1165nfw ||<br />
|-<br />
|B1260dn ||<br />
|-<br />
|B1265dfw ||<br />
|-<br />
|B1265dnf ||<br />
|-<br />
|B2365dnf ||<br />
|-<br />
<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
==Epson==<br />
<br />
{{AUR|epson-inkjet-printer-escpr}} and {{AUR|epson-inkjet-printer-escpr2}} are sets of drivers using the Epson Inkjet Printer Driver (ESC/P-R) for Linux.<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| AcuLaser CX11(NF) || {{AUR|epson-alcx11-filter}} ||<br />
|-<br />
| AcuLaser C900 || || This printer uses Epson's driver, with a device URI of ''''usb://EPSON/AL-C900'''', and may need the pipsplus service to be running.<br />
|-<br />
| EP-50V || rowspan="3" | {{AUR|epson-inkjet-printer-escpr2}} ||<br />
|-<br />
| EP-879A ||<br />
|-<br />
| EP-880A ||<br />
|-<br />
| ET-2700 || rowspan="2" | {{AUR|epson-inkjet-printer-escpr}} ||<br />
|-<br />
| ET-2750 ||<br />
|-<br />
| ET-3700 || rowspan="3" | {{AUR|epson-inkjet-printer-escpr2}} ||<br />
|-<br />
| ET-3750 ||<br />
|-<br />
| ET-4750 ||<br />
|-<br />
| EW-M571T || {{AUR|epson-inkjet-printer-escpr}} ||<br />
|-<br />
| EW-M670FT || {{AUR|epson-inkjet-printer-escpr2}} ||<br />
|-<br />
| L380 || rowspan="2" | {{AUR|epson-inkjet-printer-201601w}} ||<br />
|-<br />
| L382 ||<br />
|-<br />
| L4150 || rowspan="2" | {{AUR|epson-inkjet-printer-escpr}} ||<br />
|-<br />
| L4160 ||<br />
|-<br />
| L6160 || rowspan="3" | {{AUR|epson-inkjet-printer-escpr2}} ||<br />
|-<br />
| L6170 ||<br />
|-<br />
| L6190 ||<br />
|-<br />
| LP-S5000 || || This printer requires a [[#Avasys|custom driver from Avasys]].<br />
|-<br />
| PM-520 || rowspan="11" | {{AUR|epson-inkjet-printer-escpr2}} ||<br />
|-<br />
| PX-M5080F ||<br />
|-<br />
| PX-M5081F ||<br />
|-<br />
| PX-M680F ||<br />
|-<br />
| PX-M7070FX ||<br />
|-<br />
| PX-M780F ||<br />
|-<br />
| PX-M781F ||<br />
|-<br />
| PX-M884F ||<br />
|-<br />
| PX-S5080 ||<br />
|-<br />
| PX-S7070X ||<br />
|-<br />
| PX-S884 ||<br />
|-<br />
| TX125 || {{AUR|epson-inkjet-printer-n10-nx127}} ||<br />
|-<br />
| WF-3620 || {{AUR|epson-inkjet-printer-escpr}} ||<br />
|-<br />
| WF-3720 || rowspan="8" | {{AUR|epson-inkjet-printer-escpr2}} ||<br />
|-<br />
| WF-4720 ||<br />
|-<br />
| WF-4730 ||<br />
|-<br />
| WF-4740 ||<br />
|-<br />
| WF-7210 ||<br />
|-<br />
| WF-7710 ||<br />
|-<br />
| WF-7720 ||<br />
|-<br />
| WF-C869R ||<br />
|-<br />
| XP-446 || {{AUR|epson-inkjet-printer-escpr}} ||<br />
|-<br />
| XP-5100 || rowspan="4" | {{AUR|epson-inkjet-printer-escpr2}} ||<br />
|-<br />
| XP-6000 ||<br />
|-<br />
| XP-8500 ||<br />
|-<br />
| XP-15000 ||<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
===Utilities===<br />
====escputil====<br />
escputil is part of the {{Pkg|gutenprint}} package, and performs some utility functions on Epson printers such as nozzle cleaning.<br />
<br />
====mtink====<br />
This is a printer status monitor which enables to get the remaining ink quantity, to print test patterns, to reset printer and to clean nozzle. It use an intuitive graphical user interface.<br />
<br />
====Stylus-toolbox====<br />
This is a GUI using escputil and cups drivers. It supports nearly all USB printer of Epson and displays ink quantity, can clean and align print heads and print test patterns.<br />
<br />
===Custom drivers===<br />
====Avasys====<br />
{{Warning|This section involves installing packages without [[pacman]]. These directions should ideally be automated with a [[PKGBUILD]].}}<br />
"Source" code of the driver is available on the [http://www.avasys.jp avasys website], in Japanese, however it includes a 32 bit binary which will cause problem on 64 bit system.<br />
<br />
*[[Install]] the {{Pkg|psutils}}, {{Pkg|bc}}, {{Pkg|libstdc++5}} packages ({{AUR|lib32-libstdc++5}} on 64bit).<br />
<br />
* Download the source code of the driver.<br />
* Compile and install the driver. <br />
<br />
$ ./configure --prefix=/usr<br />
$ make<br />
# make install<br />
<br />
If you have any problems on a 64 system, some other lib32 libraries may be required. Please adjust this page if that is the case.<br />
<br />
===Adding missing paper sizes===<br />
Some of the PPD files in {{AUR|epson-inkjet-printer-escpr2}} are missing paper size definitions for media that is supported by the printers and the filter. It is relatively straightforward to add the missing media types to the PPD files.<br />
<br />
To begin, download the PKGBUILD for the {{AUR|epson-inkjet-printer-escpr2}} package, either with an AUR helper or from a snapshot tarball. Once in the directory with the PKGBUILD, download and extract the source of the package by running<br />
$ makepkg --nobuild<br />
<br />
Change directory to to {{ic|src/epson-inkjet-printer-escpr2-$PKGVER}}. Open the file {{ic|src/optBase.h}} in a text editor for reference.<br />
<br />
Identify the PPD used by your printer in the {{ic|ppd}} directory. For example, a Workforce 7710 printer uses {{ic|Epson-WF-7710_Series-epson-escpr2-en.ppd}}. Let's call it {{ic|your_ppd_filename}}. Convert the relevant PPD to a PPD compiler source file using the {{ic|ppdi}} utility from the {{Pkg|cups}} package.<br />
<br />
$ ppdi -o your_ppd_filename.drv ppd/your_ppd_filename.ppd<br />
<br />
Open the newly-created {{ic|your_ppd_filename.drv}} in a text editor. Identify the section of the file with a lot of lines starting with {{ic|CustomMedia}}. Duplicate one such line to modify. For example:<br />
<br />
CustomMedia "Legal/US Legal" 612.00 1008.00 8.40 8.40 8.40 8.40 "<</PageSize[612.00 1008.00]/ImagingBBox null>>setpagedevice" "<</PageRegion[612.00 1008.00]/ImagingBBox null>>setpagedevice"<br />
<br />
The pair of numbers {{ic|612.00 1008.00}} represents the width and height of the paper in inches, multiplied by 72. Replace all three instances of these numbers with the dimensions of the paper you want to add. For example to add 11"x17" paper, replace the numbers with {{ic|792.00 1224.00}}.<br />
<br />
The string {{ic|"Legal/US Legal"}} identifies the paper. On the left side of the slash, {{ic|Legal}} is a magic identifier that the filter uses to identify the paper size. Replace it with the one you want to use. Refer to the {{ic|mediaSizeData}} array in {{ic|optBase.h}} for a list of possible values. The string to the right of the slash can be set to any human-readable value.<br />
<br />
If you want to enable borderless printing for a paper size, prefix the magic identifier string you just found with the letter T. So {{ic|Letter}} would become {{ic|TLetter}}. Additionally, change the four numbers {{ic|8.40 8.40 8.40 8.40}} to {{ic|0.00 0.00 0.00 0.00}}.<br />
<br />
For example, I was able to add 11x17 paper to the PPD for a Workforce 7710 by adding the following lines:<br />
<br />
CustomMedia "USB/US B(11x17 in)" 792.00 1224.00 8.40 8.40 8.40 8.40 "<</PageSize[792.00 1224.00]/ImagingBBox null>>setpagedevice" "<</PageRegion[792.00 1224.00]/ImagingBBox null>>setpagedevice"<br />
CustomMedia "TUSB/US B(11x17 in) (Borderless)" 792.00 1224.00 0.00 0.00 0.00 0.00 "<</PageSize[792.00 1224.00]/ImagingBBox null>>setpagedevice" "<</PageRegion[792.00 1224.00]/ImagingBBox null>>setpagedevice"<br />
<br />
Once you've added your custom size, recompile {{ic|your_ppd_filename.drv}} into a PPD file with ppdc (also from {{Pkg|cups}}):<br />
<br />
$ ppdc your_ppd_filename.drv<br />
<br />
This will create a ppd file in the {{ic|ppd}} directory with a file name derived from the {{ic|PCFileName}} parameter in {{ic|your_ppd_filename.drv}}. You can test this file by uploading it to the CUPS web interface, or install it permanently by overwriting the original PPD file and making the package with {{ic|makepkg}}.<br />
<br />
<br />
<br />
==HP==<br />
<br />
See also [[CUPS/Troubleshooting#HP issues]].<br />
<br />
Most HP printers will use {{Pkg|hplip}}, but some may use {{AUR|hpoj}}. Some laser printers are also supported by {{AUR|foo2zjs-nightly}}.<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| DeskJet 710C || rowspan="8" | {{AUR|pnm2ppa}} ||<br />
|-<br />
| DeskJet 712C ||<br />
|-<br />
| DeskJet 720C ||<br />
|-<br />
| DeskJet 722C ||<br />
|-<br />
| DeskJet 820se ||<br />
|-<br />
| DeskJet 820Cxi ||<br />
|-<br />
| DeskJet 1000Cse ||<br />
|-<br />
| DeskJet 1000Cxi ||<br />
|-<br />
| LaserJet P1606dn || {{pkg|hplip}} + {{aur|hplip-plugin}} || Or {{aur|foo2zjs-nightly}}, or [[CUPS#CUPS|AirPrint]].<br />
|-<br />
| LaserJet Pro MFP M126nw || {{pkg|hplip}} + {{aur|hplip-plugin}} ||<br />
|-<br />
| LaserJet Pro MFP M281fdw || {{pkg|hplip}} || No proprietary drivers as of 2019-04-18 <br />
|-<br />
| Photosmart 2575 || {{Pkg|hplip}} || Or use the hpijs driver in [[foomatic]].<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
=== HPLIP ===<br />
{{Note|As of hplip v3.17.11 hpijs is not longer available. If you have printers using hpijs they will fail to print. You must modify them and select the new hpcups driver instead.}}<br />
<br />
{{pkg|hplip}} provides drivers for HP DeskJet, OfficeJet, Photosmart, Business Inkjet, and some LaserJet printers, and also provides an easy to use setup tool. See https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/index for the list of supported printers.<br />
<br />
To run the setup tool with the GUI qt frontend:<br />
# hp-setup -u<br />
<br />
To run the setup tool with the command line frontend:<br />
# hp-setup -i<br />
<br />
To set up directly the configuration of a network connected HP printer:<br />
# hp-setup -i ''<ip address>''<br />
<br />
To run systray spool manager:<br />
$ hp-systray<br />
<br />
To generate a URI for a given ip address:<br />
# hp-makeuri ''<ip address>''<br />
<br />
PPD files are in {{ic|/usr/share/ppd/HP/}}.<br />
<br />
If your printer is [https://developers.hp.com/hp-linux-imaging-and-printing/binary_plugin.html listed as requiring a binary plugin], install the {{AUR|hplip-plugin}} package from [[AUR]].<br />
If the binary plugin {{AUR|hplip-plugin}} is a requirement you will need to [[start]] the {{ic|org.cups.cupsd.service}} before the PPD is recognized by {{pkg|hplip}}.<br />
<br />
{{Note|<br />
{{Pkg|hplip}} depends on {{Pkg|foomatic-db-engine}} which prevents the drivers list from appearing when a printer is added to CUPS via the web user interface (following error : "Unable to get list of printer drivers"). Possible workarounds:<br />
* '''Either:''' Install {{Pkg|hplip}} first, then retrieve the PPD file that matches your printer from {{ic|/usr/share/ppd/HP/}}. Next, remove {{Pkg|hplip}} entirely as well as any unnecessary dependencies. Finally, install the printer manually using the CUPS web UI, selecting the PPD file you retrieved, and then re-install {{Pkg|hplip}}. After a reboot, you should have a fully working printer.<br />
* '''Or:''' Remove {{Pkg|hplip}}, {{Pkg|foomatic-db}} and {{Pkg|foomatic-db-engine}} along with any unnecessary dependencies. Reinstall {{Pkg|hplip}} and restart CUPS. Install your printer using the CUPS web UI, which should now be able to find the drivers automatically. No reboot needed.}}<br />
<br />
=== foo2zjs ===<br />
<br />
[http://foo2zjs.rkkda.com/ foo2zjs] supports some HP LaserJet printers. As of June 2018 the hplip package interferes with {{aur|foo2zjs-nightly}}, as described at [https://bbs.archlinux.org/viewtopic.php?pid=1662809 this forum post] and {{Bug|58815}}.<br />
<br />
==Konica Minolta==<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| Minolta Magicolor 1600W || rowspan=7 | [[foomatic]] ||<br />
|-<br />
| Minolta Magicolor 1680MF ||<br />
|-<br />
| Minolta Magicolor 1690MF ||<br />
|-<br />
| Minolta Magicolor 2480MF ||<br />
|-<br />
| Minolta Magicolor 2490MF ||<br />
|-<br />
| Minolta Magicolor 2530DL ||<br />
|-<br />
| Minolta Magicolor 4690MF ||<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
===foo2zjs===<br />
[[#foo2zjs]], mentioned above for supporting some HP printers, also support some Minolta printers.<br />
==Lexmark==<br />
<br />
===Utilities===<br />
<br />
Lexmark provides a utility called lexijtools with the drivers.<br />
<br />
===Custom drivers===<br />
<br />
Lexmark does provide Linux drivers for all their hardware.<br />
The following packages are required:<br />
<br />
*{{Pkg|cups}}<br />
*{{Pkg|sane}}<br />
*{{Pkg|ncurses}}<br />
*{{Pkg|libusb}}<br />
*{{Pkg|libxext}}<br />
*{{Pkg|libxtst}}<br />
*{{Pkg|libxi}}<br />
*{{Pkg|libstdc++5}}<br />
*{{Pkg|krb5}}<br />
*{{Pkg|lua}} (for the automated installer)<br />
*[[Java]] (for the automated installer, and some of the Lexmark tools)<br />
<br />
The drivers will need to be [http://support.lexmark.com/index?page=driversdownloads downloaded] from Lexmark's website. Preferably, create a package (see [[Creating packages]]) and install it. Here is a basic [[PKGBUILD]] that still needs work but will give an idea of what is required.<br />
<br />
{{hc|PKGBUILD|<nowiki><br />
# Contributor: Todd Partridge (Gen2ly) toddrpartridge (at) yahoo<br />
<br />
pkgname=cups-lexmark-Z2300-2600<br />
pkgver=1<br />
pkgrel=1<br />
pkgdesc="Lexmark Z2300 and 2600 Series printer driver for cups"<br />
arch=('i686')<br />
url="http://www.lexmark.com/"<br />
license=('custom')<br />
depends=('cups' 'glibc' 'ncurses' 'libusb' 'libxext' 'libxtst' 'libxi' 'libstdc++5' 'krb5' 'lua' 'java-runtime')<br />
conflicts=('z600' 'cjlz35le-cups' 'cups-lexmark-700')<br />
source=(lexmark-inkjet-08-driver-1.0-1.i386.tar.gz.sh)<br />
md5sums=(3c37eb87e3dad4853bf29344f9695134)<br />
<br />
<br />
package() {<br />
# Extract installer<br />
sh lexmark-inkjet-08-driver-1.0-1.i386.tar.gz.sh --target Installer-Files<br />
cd Installer-Files<br />
mkdir Driver<br />
tar xvvf instarchive_all --lzma -C Driver/<br />
cd Driver<br />
tar xv lexmark-inkjet-08-driver-1.0-1.i386.tar.gz -C $pkgdir<br />
}<br />
</nowiki>}}<br />
<br />
Keep in mind you can use the automated installer but doing so will leave the resulting changes untracked. The PPD will be installed into {{ic|/usr/local/lexmark/lxk08/etc/}} or similar, depending on the printer model.<br />
<br />
==Oki==<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| C110|| [[foomatic]] ||<br />
|-<br />
| MC561|| [[CUPS#Foomatic|foomatic-db-nonfree]] ||<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
==Ricoh==<br />
<br />
Install {{AUR|openprinting-ppds-pxlmono-ricoh}} if your device is black and white, or {{AUR|openprinting-ppds-pxlcolor-ricoh}} if it's color. Note that Ricoh copiers are sometimes branded as Savin, Gestetner, Lanier, Rex-Rotary, Nashuatec, and/or IKON. So, if you have a device bearing one of these brands, it may be supported by these drivers as well.<br />
<br />
* [https://www.openprinting.org/driver/pxlmono-Ricoh List of supported black and white models]<br />
* [https://www.openprinting.org/driver/pxlcolor-Ricoh List of supported color models]<br />
<br />
For winprinters (Ricoh series SP100 and SP200) try out {{AUR|ricoh-sp100-git}}. <br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| SP 112 || {{AUR|ricoh-sp100-git}} ||<br />
|-<br />
| SP 201n || {{AUR|ricoh-sp100-git}} ||<br />
|-<br />
| 213W || ''Generic PCL Laser'' || Obtain a WPS code by holding down the wifi button for 2 seconds, then hitting the stop/start button.<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
==Samsung==<br />
<br />
{{Accuracy|All the cnijfilter drivers appear to be for Canon printers - maybe the cnijfilter comment would be better off in the Canon section?}}<br />
<br />
For printers requiring the ''cnijfilter'' drivers, search for the correct driver [https://aur.archlinux.org/packages.php?K=cnijfilter in the AUR]<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| ML-2010 || {{Pkg|splix}} ||<br />
|-<br />
| SCX-4200 || {{Pkg|splix}} ||<br />
|-<br />
| Newer printers? || {{AUR|samsung-unified-driver}} ||<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
==Xerox or FujiXerox==<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| DocuPrint 203A || {{Pkg|hplip}} || Using the '''DocuPrint P8e(hpijs)''' driver, or the Brother driver on FujiXerox's website (see [[#Brother]] for more information on how to install custom Brother drivers).<br />
|-<br />
| Phaser 3100MFP || Install Xerox's driver || See [[#Phaser 3100MFP]] for more instructions.<br />
|-<br />
| Phaser 6115MFP || [[foomatic]] ||<br />
|-<br />
| Phaser 6121MFP || [[foomatic]] ||<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
===Custom drivers===<br />
<br />
====Phaser 3100MFP====<br />
<br />
{{Warning|This section involves installing packages without [[pacman]]. These directions should ideally be automated with a [[PKGBUILD]].}}<br />
<br />
Once you have downloaded the drivers, execute the driver installer and accept the licence:<br />
# cd printer<br />
# ./XeroxPhaser3100.install<br />
Note that the driver is 32 bit, so some 32 bit libraries will be required on an x86_64 system.<br />
<br />
For the scanner, create an /etc/sane.d directory if it doesn't already exist, because it's need by the installer:<br />
# mkdir -p /etc/sane.d<br />
Now install the driver:<br />
# cd scanner/<br />
# ./XeroxPhaser3100sc.install<br />
Again, on an x86_64 install, 32 bit libraries will be needed.<br />
<br />
====Phaser 6000B====<br />
<br />
[[Install]] the [https://github.com/aur-archive/xerox-phaser-6010 xerox-phaser-6010] package (archived from the AUR).<br />
The driver may require older versions of {{Pkg|nettle}} and {{Pkg|gnutls}} to be installed, since the binary blob linked against older versions of the shared libraries provided by those packages. The oldest known-good versions are {{ic|nettle-2.7.1-1}} and {{ic|gnutls-3.3.13-1}}.<br />
<br />
====Phaser 6125N====<br />
<br />
{{Warning|This section involves installing packages without [[pacman]]. These directions should ideally be automated with a [[PKGBUILD]].}}<br />
<br />
FujiXerox does not support Linux on this model. An old rpm [http://onlinesupport.fujixerox.com/tiles/common/hc_drivers_download.jsp?system=%27Linux%27&shortdesc=null&xcrealpath=http://www.fujixeroxprinters.com/downloads/uploaded/dpc525a_linux_.0.0.tar_81c2.zip is available] but does not seem to work.<br />
<br />
A slightly adapted [https://rickvanderzwet.nl/trac/personal/wiki/XeroxPhaser6125N custom driver] has been found to work out of the box.<br />
<br />
To install the tarball, run<br />
# tar -C / --keep-newer-files -xvzf cups-xerox-phaser-6125n-1.0.0.tar.gz</div>Catlover2https://wiki.archlinux.org/index.php?title=CUPS/Printer-specific_problems&diff=575800CUPS/Printer-specific problems2019-06-17T07:53:52Z<p>Catlover2: Add section describing how to add missing paper sizes to Epson PPD files</p>
<hr />
<div>[[Category:Printers]]<br />
[[ja:CUPS/プリンター別の問題]]<br />
[[ru:CUPS (Русский)/Printer-specific problems]]<br />
{{Related articles start}}<br />
{{Related|CUPS}}<br />
{{Related|CUPS/Troubleshooting}}<br />
{{Related articles end}}<br />
<br />
This article contains printer or manufacturer-specific instructions for [[CUPS]].<br />
See [http://www.openprinting.org/printers OpenPrinting] if your printer is not already listed here, or if none of the listed drivers work.<br />
<br />
{{Note|If you add a printer to this list, consider contributing your entry to [https://wiki.linuxfoundation.org/openprinting/database/databaseintro OpenPrinting] - that way users of other distributions will also benefit!}}<br />
<br />
==Brother==<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| DCP-135C || {{AUR|brother-dcp135c}} ||<br />
|-<br />
| DCP-150C || {{AUR|brother-dcp150c}} ||<br />
|-<br />
| DCP-7020 || [[foomatic]] || Or Brother's driver.<br />
|-<br />
| DCP-7030 || {{AUR|brother-dcp7030}} ||<br />
|-<br />
| DCP-7065DN || {{AUR|brother-dcp7065dn}} ||<br />
|-<br />
| DCP-J515W || {{AUR|brother-dcp-j515w}} ||<br />
|-<br />
| FAX-2820 || {{AUR|brother-cups-wrapper-laser}} ||<br />
|-<br />
| FAX-2840 || {{AUR|brother-fax2840}} || Or [[foomatic]] - works mostly with {{ic|hpijs-pcl5e.ppd}}. Same as the HL-2170W.<br />
|-<br />
| FAX-2940 || {{AUR|brother-fax2940}} ||<br />
|-<br />
| HL-2030 || [[foomatic]] || Or {{AUR|brother-hl2030}}<br />
|-<br />
| HL-2035 || [[foomatic]] || Should be compatible with any drivers for the HL-2030.<br />
|-<br />
| HL-2040 || [[foomatic]] || Or {{AUR|brother-hl2040}}<br />
|-<br />
| HL-2130 || [[foomatic]] (using the HL-2140 driver) || Or {{Pkg|hplip}}<br />
|-<br />
| HL-2140 || [[foomatic]] || Or {{AUR|brother-hl2140}}<br />
|-<br />
| HL-2170W || [[foomatic]] || Or Brother's driver. <br />
|-<br />
| HL-2230 || [[foomatic]] || Same as HL-2170W. Select HL-2170W as the driver in CUPS admin when adding a printer.<br />
|-<br />
| HL-2250DN || {{AUR|brother-hl2250dn}} ||<br />
|-<br />
| HL-2270DW || {{AUR|brother-hl2270dw}} ||<br />
|-<br />
| HL-2280DW || {{AUR|brother-hl2280dw}} ||<br />
|-<br />
| HL-3045CN || Install Brother's driver. ||<br />
|-<br />
| HL-3140CW || {{AUR|brother-hl3140cw}} || Use IPP and Brother's driver to avoid page-shrinking and endless blank printouts<br />
|-<br />
| HL-3150CDW || {{AUR|brother-hl3150cdw}} ||<br />
|-<br />
| HL-3170CDW || {{AUR|brother-hl3170cdw}} ||<br />
|-<br />
| HL-4150CDN || {{AUR|brother-hl4150cdn}} ||<br />
|-<br />
| HL-5140 || [[foomatic]] || Or Brother's driver.<br />
|-<br />
| HL-5340 || [[foomatic]] || Using the ''Generic PCL 6/PCL XL Printer - CUPS+Gutenprint'' ({{pkg|gutenprint}} and {{pkg|foomatic-db-gutenprint-ppds}}). Or Brother's driver, which may result in failed prints with postscript errors.<br />
|-<br />
| HL-L2300D || {{AUR|brother-hll2300d}} || <br />
|-<br />
| HL-L2340DW || {{AUR|brother-hll2340dw}} ||<br />
|-<br />
| HL-L2350DW || {{AUR|brother-hll2350dw}} ||<br />
|-<br />
| HL-L2360DN || {{AUR|brother-hll2360d}} ||<br />
|-<br />
| HL-L2360DW || {{AUR|brother-hll2360d}} ||<br />
|-<br />
| HL-L2365DW || {{AUR|brother-hll2360d}} ||<br />
|-<br />
| HL-L2380DW || {{AUR|brother-hll2380dw}} ||<br />
|-<br />
| HL-L2395DW || {{AUR|brother-hll2395dw}} || Use the {{ic|socket}} protocol as described in [[#Network printers]]<br />
|-<br />
| HL-L5100DN || HP LaserJet Foomatic driver || This model will emulate a HP LaserJet. Use the {{ic|lpd}} protocol as described in [[#Network printers]].<br />
|-<br />
| HL-L8360CDW || {{AUR|brother-hll8360cdw-cups-bin}} ||<br />
|-<br />
| MFC-420CN || {{AUR|brother-mfc-420cn}} ||<br />
|-<br />
| MFC-440CN || {{AUR|brother-mfc-440cn}} ||<br />
|-<br />
| MFC-7360N || {{AUR|brother-mfc7360n}} ||<br />
|-<br />
| MFC-7460DN || [[Gutenprint]] || Use the ''Generic PCL 6 Printer wide margin - CUPS+Gutenprint'' driver, with address {{ic|ipp://hostname-or-ip/pcl_p1}}.<br />
|-<br />
| MFC-7840W || {{AUR|brother-mfc-7840w}} ||<br />
|-<br />
| MFC-9320CW || Install Brother's driver. ||<br />
|-<br />
| MFC-9332CDW || {{AUR|brother-mfc-9332cdw}} ||<br />
|-<br />
| MFC-9840CDW || [[foomatic]] || Or Brother's driver. This printer also works with the generic PCL-6 driver from the {{Pkg|gutenprint}} package. Use '''pcl_p1''' for the printer's address when using the PCL-6 driver.<br />
|-<br />
| MFC-J470DW || {{AUR|brother-mfc-j470dw}} || Use the {{ic|ipp}} protocol as described in [[#Network printers]].<br />
|-<br />
| MFC-J4710DW || {{AUR|brother-mfc-j4710dw}} ||<br />
|-<br />
| MFC-J480DW || {{AUR|brother-mfc-j480dw}} || Use the {{ic|ipp}} protocol as described in [[#Network printers]].<br />
|-<br />
| MFC-J5520DW || {{AUR|brother-mfc-j5520dw}} ||<br />
|-<br />
| MFC-J5910DW || {{AUR|brother-mfc-j5910dw}} ||<br />
|-<br />
| MFC-J650DW || Install Brother's driver. ||<br />
|-<br />
| MFC-J885DW || {{AUR|brother-mfc-j885dw}} ||<br />
|-<br />
| MFC-J985DW || {{AUR|brother-mfc-j985dw}} ||<br />
|-<br />
| MFC-L2700DW || {{AUR|brother-mfc-l2700dw}} || Please look also at the comments section of the AUR package page. <br />
|-<br />
| MFC-L8600CDW || {{AUR|brother-mfc-l8600cdw}} || Please follow the instructions on the AUR page.<br />
|-<br />
| QL-500 || {{AUR|brother-ql500}} ||<br />
|-<br />
| QL-570 || {{AUR|brother-ql570}} ||<br />
|-<br />
| QL-580N || {{AUR|brother-ql580n}} ||<br />
|-<br />
| QL-650TD || {{AUR|brother-ql650td}} ||<br />
|-<br />
| QL-700 || {{AUR|brother-ql700}} ||<br />
|-<br />
| QL-710W || {{AUR|brother-ql710w}} ||<br />
|-<br />
| QL-720NW || {{AUR|brother-ql720nw}} ||<br />
|-<br />
| QL-1050 || {{AUR|brother-ql1050}} || <br />
|-<br />
| QL-1050N || {{AUR|brother-ql1050n}} ||<br />
|-<br />
| QL-1060 || {{AUR|brother-ql1060n}} ||<br />
|-<br />
| TD-2020 || {{AUR|brother-td2020}} ||<br />
|-<br />
| TD-2120N || {{AUR|brother-td2120n}} ||<br />
|-<br />
| TD-2130N || {{AUR|brother-td2130n}} ||<br />
|-<br />
| TD-4000 || {{AUR|brother-td4000}} ||<br />
|-<br />
| TD-4100N || {{AUR|brother-td4100n}} ||<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
===Network printers===<br />
For network printers, use {{ic|ipp://'''printer_ip'''/ipp/port1}} as printer address.<br />
For some older printers, this might not work. If not, try {{ic|lpd://'''printer_ip'''/BINARY_P1}} instead.<br />
<br />
Some printers use the socket protocol. For these printers, use {{ic|socket://'''printer_ip''':9100}}.<br />
For http, use {{ic|http://'''printer_ip'''/POSTSCRIPT_P1}}.<br />
<br />
===Custom drivers===<br />
<br />
Brother provides custom drivers on their website, either in source tarball, rpm, or deb form. [[Packaging Brother printer drivers]] covers creating [[PKGBUILD]]s from the existing RPM packages.<br />
{{Note|The source packages might be a better alternative to the rpm packages, provided they contain all the needed files.}}<br />
<br />
====Manually installing from the RPM packages====<br />
<br />
{{Warning|This should ideally be automated in a [[PKGBUILD]]}}<br />
<br />
[[Install]] the {{Pkg|rpmextract}} package, and extract both rpm packages using {{ic|rpmextract.sh}}. Extracting both files will create a var and a usr directory - move the contents of both directories into the corresponding root directories.<br />
<br />
Run the cups wrapper file in {{ic|/usr/local/Brother/cupswrapper}}. This should automatically install and configure your brother printer.<br />
<br />
For some of the drivers 32 bit libraries may need to be installed from [[multilib]].<br />
<br />
===Updating the firmware===<br />
<br />
[[Install]] {{pkg|net-snmp}} and run:<br />
<br />
snmpwalk -c public $PRINTER_IP | grep -A 1 3.6.1.4.1.2435.2.4.3.99.3.1.6.1.2<br />
<br />
At this point, you will have the relevant data to get a valid firmware download link from Brother. The file should look similar to the one below:<br />
<br />
{{hc|request.xml|<br />
<REQUESTINFO><br />
<FIRMUPDATETOOLINFO><br />
<FIRMCATEGORY>MAIN</FIRMCATEGORY><br />
<OS>LINUX</OS><br />
<INSPECTMODE>1</INSPECTMODE><br />
</FIRMUPDATETOOLINFO><br />
<br />
<FIRMUPDATEINFO><br />
<MODELINFO><br />
<SELIALNO></SELIALNO><br />
<NAME>MFC-9330CDW</NAME><br />
<SPEC>0401</SPEC><br />
<DRIVER></DRIVER><br />
<FIRMINFO><br />
<FIRM><br />
<ID>MAIN</ID><br />
<VERSION>R1506121801:4504</VERSION><br />
</FIRM><br />
<FIRM><br />
<ID>SUB1</ID><br />
<VERSION>1.07</VERSION><br />
</FIRM><br />
<FIRM><br />
<ID>SUB2</ID><br />
<VERSION>L1505291600</VERSION><br />
</FIRM><br />
</FIRMINFO><br />
</MODELINFO><br />
<DRIVERCNT>1</DRIVERCNT><br />
<LOGNO>2</LOGNO><br />
<ERRBIT></ERRBIT><br />
<NEEDRESPONSE>1</NEEDRESPONSE><br />
</FIRMUPDATEINFO><br />
</REQUESTINFO><br />
}}<br />
<br />
Post this file to Brother:<br />
<br />
curl -X POST -d @request.xml https://firmverup.brother.co.jp/kne_bh7_update_nt_ssl/ifax2.asmx/fileUpdate -H "Content-Type:text/xml" > response.xml<br />
<br />
In {{ic|response.xml}} you will find a {{ic|<PATH>}} tag that contains the firmware download URL. Next, download the firmware, push it to the printer, and let the printer process it. Before that is done, change the Admin password to something known, it will be used as the user to log into the FTP site (VERY bad practice, don't do this). <br />
<br />
wget http://update-akamai.brother.co.jp/CS/LZ4266_W.djf<br />
ftp $PRINTER_IP<br />
bin<br />
hash<br />
send LZ4266_W.djf<br />
bye<br />
<br />
With that, the printer will restart, and the latest firmware will be installed and (hopefully) your printing woes will be solved.<br />
<br />
==Canon==<br />
<br />
There are many possible drivers for Canon printers. [http://gimp-print.sourceforge.net/p_Supported_Printers.php Many Canon printers] are supported by [[Gutenprint]]. Some of Canon's LBP, iR, and MF printers use a driver supporting the UFR II/UFR II LT/LIPSLX protocols, which is available as {{AUR|cndrvcups-lb}} or {{AUR|cndrvcups-lb-bin}}. Others use the [[#CARPS]], [[#cnijfilter]] ([[AUR|cnijfilter2]] / [[AUR|cnijfilter2-bin]]), or [[Canon CAPT]] drivers.<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| iP4300<br />
| [[Gutenprint]]<br />
| Or use the [http://www.turboprint.info/ TurboPrint] driver.<br />
|-<br />
| LBP810 || rowspan="34" | [[Canon CAPT]] ||<br />
|-<br />
| LBP1120 ||<br />
|-<br />
| LBP1210 ||<br />
|-<br />
| LBP2900 ||<br />
|-<br />
| LBP3000 ||<br />
|-<br />
| LBP3010 ||<br />
|-<br />
| LBP3018 ||<br />
|-<br />
| LBP3050 ||<br />
|-<br />
| LBP3100 ||<br />
|-<br />
| LBP3108 ||<br />
|-<br />
| LBP3150 ||<br />
|-<br />
| LBP3200 ||<br />
|-<br />
| LBP3210 ||<br />
|-<br />
| LBP3250 ||<br />
|-<br />
| LBP3300 ||<br />
|-<br />
| LBP3310 ||<br />
|-<br />
| LBP3500 ||<br />
|-<br />
| LBP5000 ||<br />
|-<br />
| LBP5050 series ||<br />
|-<br />
| LBP5100 ||<br />
|-<br />
| LBP5300 ||<br />
|-<br />
| LBP6000 ||<br />
|-<br />
| LBP6018 ||<br />
|-<br />
| LBP6020 ||<br />
|-<br />
| LBP6200 ||<br />
|-<br />
| LBP6300 ||<br />
|-<br />
| LBP6300n ||<br />
|-<br />
| LBP6310dn ||<br />
|-<br />
| LBP7010C ||<br />
|-<br />
| LBP7018C ||<br />
|-<br />
| LBP7200Cdn (network mode) ||<br />
|-<br />
| LBP7200C series ||<br />
|-<br />
| LBP7210Cdn ||<br />
|-<br />
| LBP9100C ||<br />
|-<br />
| MF635Cx || rowspan="2" | {{AUR|cndrvcups-lb-bin}} ||<br />
|-<br />
| MF4720w ||<br />
|-<br />
| MG4200 series || {{AUR|cnijfilter-mg4200}} || Avoid the [[CUPS#Web interface|web interface]] when adding the printer as it won't find the PPD file.<br />
|-<br />
| MX490 || rowspan="3" | {{AUR|cnijfilter2}}<br />{{AUR|cnijfilter2-bin}} ||<br />
|-<br />
| MX492 ||<br />
|-<br />
| TS8050 || Without {{AUR|cnijfilter2}} printing will fail with a filter error or you might get "Rendering Completed" and nothing will print<br />
|-<br />
| TS9020 || {{AUR|canon-ts9020}} ||<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
Some Canon printers will use a similar setup to the iP4500, so consider modifying the {{AUR|cnijfilter-ip4500}} package for other, similar printers.<br />
<br />
===CARPS===<br />
<br />
Some of Canon's printers use Canon's proprietary Canon Advanced Raster Printing System (CARPS) driver.<br />
[http://www.rainbow-software.org/2014/01/23/cups-driver-for-canon-carps-printers/ Rainbow Software] have managed to reverse engineer the CARPS data format and have successfully created a CARPS CUPS driver, which is available as {{AUR|carps-cups}}.<br />
The project's [https://github.com/ondrej-zary/carps-cups GitHub] page includes a list of working printers.<br />
<br />
===USB over IP (BJNP)===<br />
<br />
Some Canon printers use Canon's proprietary USB over IP BJNP protocol to communicate over the network. There is a CUPS backend for this, which is available as {{AUR|cups-bjnp}}.<br />
<br />
===cnijfilter===<br />
<br />
Some printers using the cnijfilter drivers support the {{ic|cnijnet}} protocol. To find the [[CUPS#Printer URI|printer URI]] run<br />
<br />
$ cnijnetprn --search auto<br />
<br />
and use the {{ic|cnijnet:/}} URI in the output.<br />
<br />
{{Expansion|The URI appears to be of the form {{ic|cnijnet:/}} followed by the MAC address of the printer. If this is the case it would be good to mention it here.}}<br />
<br />
==Dell==<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| 1250C<br />
| {{AUR|foo2zjs-nightly}}<br />
| See http://cybercom.net/~dcoffin/hbpl, the patch has been merged into upstream. The printer may also work with the [[#Phaser 6000B|Xerox Phaser 6000B driver]].<br />
|-<br />
| C1660NW<br />
| {{AUR|foo2zjs-nightly}}<br />
| The printer may also work with the [[#Phaser 6000B|Xerox Phaser 6000B driver]].<br />
|-<br />
| E515,<br />
E515dw<br />
| Install [http://downloads.dell.com/FOLDER03040853M/1/Printer_E515dw_Driver_Dell_A00_LINUX.zip Dell's driver].<br />
| Both ''e515dwcupswrapper-3.2.0-1.i386.deb'' and ''e515dwlpr-3.2.0-1.i386.deb'' need to be installed. You could either write a [[PKGBUILD]], use {{AUR|debtap}}, or use {{AUR|dpkg}} (using dpkg is not recommended as the files will not be managed by [[pacman]]). The driver works on both the x86_64 and i386 platforms, but may require [[multilib]].<br />
|-<br />
| S1130n || rowspan="16" | {{aur|dell-unified-printer-driver}} || rowspan="16" | Driver conflicts with samsung-unified-driver-printer (both create rastertospl and libscmssc.so)<br />
|-<br />
|1130 ||<br />
|-<br />
|1133 ||<br />
|-<br />
|1135n ||<br />
|-<br />
|1815 ||<br />
|-<br />
|2145cn ||<br />
|-<br />
|2335dn ||<br />
|-<br />
|2355dn ||<br />
|-<br />
|5330 ||<br />
|-<br />
|B1160 ||<br />
|-<br />
|B1160w ||<br />
|-<br />
|B1165nfw ||<br />
|-<br />
|B1260dn ||<br />
|-<br />
|B1265dfw ||<br />
|-<br />
|B1265dnf ||<br />
|-<br />
|B2365dnf ||<br />
|-<br />
<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
==Epson==<br />
<br />
{{AUR|epson-inkjet-printer-escpr}} and {{AUR|epson-inkjet-printer-escpr2}} are sets of drivers using the Epson Inkjet Printer Driver (ESC/P-R) for Linux.<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| AcuLaser CX11(NF) || {{AUR|epson-alcx11-filter}} ||<br />
|-<br />
| AcuLaser C900 || || This printer uses Epson's driver, with a device URI of ''''usb://EPSON/AL-C900'''', and may need the pipsplus service to be running.<br />
|-<br />
| EP-50V || rowspan="3" | {{AUR|epson-inkjet-printer-escpr2}} ||<br />
|-<br />
| EP-879A ||<br />
|-<br />
| EP-880A ||<br />
|-<br />
| ET-2700 || rowspan="2" | {{AUR|epson-inkjet-printer-escpr}} ||<br />
|-<br />
| ET-2750 ||<br />
|-<br />
| ET-3700 || rowspan="3" | {{AUR|epson-inkjet-printer-escpr2}} ||<br />
|-<br />
| ET-3750 ||<br />
|-<br />
| ET-4750 ||<br />
|-<br />
| EW-M571T || {{AUR|epson-inkjet-printer-escpr}} ||<br />
|-<br />
| EW-M670FT || {{AUR|epson-inkjet-printer-escpr2}} ||<br />
|-<br />
| L380 || rowspan="2" | {{AUR|epson-inkjet-printer-201601w}} ||<br />
|-<br />
| L382 ||<br />
|-<br />
| L4150 || rowspan="2" | {{AUR|epson-inkjet-printer-escpr}} ||<br />
|-<br />
| L4160 ||<br />
|-<br />
| L6160 || rowspan="3" | {{AUR|epson-inkjet-printer-escpr2}} ||<br />
|-<br />
| L6170 ||<br />
|-<br />
| L6190 ||<br />
|-<br />
| LP-S5000 || || This printer requires a [[#Avasys|custom driver from Avasys]].<br />
|-<br />
| PM-520 || rowspan="11" | {{AUR|epson-inkjet-printer-escpr2}} ||<br />
|-<br />
| PX-M5080F ||<br />
|-<br />
| PX-M5081F ||<br />
|-<br />
| PX-M680F ||<br />
|-<br />
| PX-M7070FX ||<br />
|-<br />
| PX-M780F ||<br />
|-<br />
| PX-M781F ||<br />
|-<br />
| PX-M884F ||<br />
|-<br />
| PX-S5080 ||<br />
|-<br />
| PX-S7070X ||<br />
|-<br />
| PX-S884 ||<br />
|-<br />
| TX125 || {{AUR|epson-inkjet-printer-n10-nx127}} ||<br />
|-<br />
| WF-3620 || {{AUR|epson-inkjet-printer-escpr}} ||<br />
|-<br />
| WF-3720 || rowspan="8" | {{AUR|epson-inkjet-printer-escpr2}} ||<br />
|-<br />
| WF-4720 ||<br />
|-<br />
| WF-4730 ||<br />
|-<br />
| WF-4740 ||<br />
|-<br />
| WF-7210 ||<br />
|-<br />
| WF-7710 ||<br />
|-<br />
| WF-7720 ||<br />
|-<br />
| WF-C869R ||<br />
|-<br />
| XP-446 || {{AUR|epson-inkjet-printer-escpr}} ||<br />
|-<br />
| XP-5100 || rowspan="4" | {{AUR|epson-inkjet-printer-escpr2}} ||<br />
|-<br />
| XP-6000 ||<br />
|-<br />
| XP-8500 ||<br />
|-<br />
| XP-15000 ||<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
===Utilities===<br />
====escputil====<br />
escputil is part of the {{Pkg|gutenprint}} package, and performs some utility functions on Epson printers such as nozzle cleaning.<br />
<br />
====mtink====<br />
This is a printer status monitor which enables to get the remaining ink quantity, to print test patterns, to reset printer and to clean nozzle. It use an intuitive graphical user interface.<br />
<br />
====Stylus-toolbox====<br />
This is a GUI using escputil and cups drivers. It supports nearly all USB printer of Epson and displays ink quantity, can clean and align print heads and print test patterns.<br />
<br />
===Custom drivers===<br />
====Avasys====<br />
{{Warning|This section involves installing packages without [[pacman]]. These directions should ideally be automated with a [[PKGBUILD]].}}<br />
"Source" code of the driver is available on the [http://www.avasys.jp avasys website], in Japanese, however it includes a 32 bit binary which will cause problem on 64 bit system.<br />
<br />
*[[Install]] the {{Pkg|psutils}}, {{Pkg|bc}}, {{Pkg|libstdc++5}} packages ({{AUR|lib32-libstdc++5}} on 64bit).<br />
<br />
* Download the source code of the driver.<br />
* Compile and install the driver. <br />
<br />
$ ./configure --prefix=/usr<br />
$ make<br />
# make install<br />
<br />
If you have any problems on a 64 system, some other lib32 libraries may be required. Please adjust this page if that is the case.<br />
<br />
===Adding missing paper sizes===<br />
Some of the PPD files in {{AUR|epson-inkjet-printer-escpr2}} are missing paper size definitions for media that is supported by the printers and the filter. It is relatively straightforward to add the missing media types to the PPD files.<br />
<br />
To begin, download the PKGBUILD for the {{AUR|epson-inkjet-printer-escpr2}} package, either with an AUR helper or from a snapshot tarball. Once in the directory with the PKGBUILD, download and extract the source of the package by running<br />
$ makepkg --nobuild<br />
<br />
Change directory to to {{ic|src/epson-inkjet-printer-escpr2-$PKGVER}}. Open the file {{ic|src/optBase.h}} in a text editor for reference.<br />
<br />
Identify the PPD used by your printer in the {{ic|ppd}} directory. For example, a Workforce 7710 printer uses {{ic|Epson-WF-7710_Series-epson-escpr2-en.ppd}}. Let's call it {{ic|your_ppd_filename}}. Convert the relevant PPD to a PPD compiler source file using the {{ic|ppdi}} utility from the {{Pkg|cups}} package.<br />
<br />
$ ppdi -o your_ppd_filename.drv ppd/your_ppd_filename.ppd<br />
<br />
Open the newly-created {{ic|your_ppd_filename.drv}} in a text editor. Identify the section of the file with a lot of lines starting with {{ic|CustomMedia}}. Duplicate one such line to modify. For example:<br />
<br />
CustomMedia "Legal/US Legal" 612.00 1008.00 8.40 8.40 8.40 8.40 "<</PageSize[612.00 1008.00]/ImagingBBox null>>setpagedevice" "<</PageRegion[612.00 1008.00]/ImagingBBox null>>setpagedevice"<br />
<br />
The pair of numbers {{ic|612.00 1008.00}} represents the width and height of the paper in inches, multiplied by 72. Replace all three instances of these number with the dimensions of the paper you want to add. For example to add 11"x17" paper, replace the numbers with {{ic|792.00 1224.00}}.<br />
<br />
The string {{ic|"Legal/US Legal"}} identifies the paper. On the left side of the slash, {{ic|Legal}} is a magic identifier that the filter uses to identify the paper size. Replace it with the one you want to use. Refer to the {{ic|mediaSizeData}} array in {{ic|optBase.h}} for a list of possible values. The string to the right of the slash can be set to any human-readable value.<br />
<br />
If you want to enable borderless printing for a paper size, prefix the magic identifier string you just found with the letter T. So {{ic|Letter}} would become {{ic|TLetter}}. Additionally, change the four numbers {{ic|8.40 8.40 8.40 8.40}} to {{ic|0.00 0.00 0.00 0.00}}.<br />
<br />
For example, I was able to add 11x17 paper to the PPD for a Workforce 7710 by adding the following lines:<br />
<br />
CustomMedia "USB/US B(11x17 in)" 792.00 1224.00 8.40 8.40 8.40 8.40 "<</PageSize[792.00 1224.00]/ImagingBBox null>>setpagedevice" "<</PageRegion[792.00 1224.00]/ImagingBBox null>>setpagedevice"<br />
CustomMedia "TUSB/US B(11x17 in) (Borderless)" 792.00 1224.00 0.00 0.00 0.00 0.00 "<</PageSize[792.00 1224.00]/ImagingBBox null>>setpagedevice" "<</PageRegion[792.00 1224.00]/ImagingBBox null>>setpagedevice"<br />
<br />
Once you've added your custom size, recompile {{ic|your_ppd_filename.drv}} into a PPD file with ppdc (also from {{Pkg|cups}}):<br />
<br />
$ ppdc your_ppd_filename.drv<br />
<br />
This will create a ppd file in the {{ic|ppd}} directory with file name derived from the {{ic|PCFileName}} parameter in {{ic|your_ppd_filename.drv}}. You can test this file by uploading it to the CUPS web interface, or install it permanently by overwriting the original PPD file and making the package with {{ic|makepkg}}.<br />
<br />
<br />
<br />
==HP==<br />
<br />
See also [[CUPS/Troubleshooting#HP issues]].<br />
<br />
Most HP printers will use {{Pkg|hplip}}, but some may use {{AUR|hpoj}}. Some laser printers are also supported by {{AUR|foo2zjs-nightly}}.<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| DeskJet 710C || rowspan="8" | {{AUR|pnm2ppa}} ||<br />
|-<br />
| DeskJet 712C ||<br />
|-<br />
| DeskJet 720C ||<br />
|-<br />
| DeskJet 722C ||<br />
|-<br />
| DeskJet 820se ||<br />
|-<br />
| DeskJet 820Cxi ||<br />
|-<br />
| DeskJet 1000Cse ||<br />
|-<br />
| DeskJet 1000Cxi ||<br />
|-<br />
| LaserJet P1606dn || {{pkg|hplip}} + {{aur|hplip-plugin}} || Or {{aur|foo2zjs-nightly}}, or [[CUPS#CUPS|AirPrint]].<br />
|-<br />
| LaserJet Pro MFP M126nw || {{pkg|hplip}} + {{aur|hplip-plugin}} ||<br />
|-<br />
| LaserJet Pro MFP M281fdw || {{pkg|hplip}} || No proprietary drivers as of 2019-04-18 <br />
|-<br />
| Photosmart 2575 || {{Pkg|hplip}} || Or use the hpijs driver in [[foomatic]].<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
=== HPLIP ===<br />
{{Note|As of hplip v3.17.11 hpijs is not longer available. If you have printers using hpijs they will fail to print. You must modify them and select the new hpcups driver instead.}}<br />
<br />
{{pkg|hplip}} provides drivers for HP DeskJet, OfficeJet, Photosmart, Business Inkjet, and some LaserJet printers, and also provides an easy to use setup tool. See https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/index for the list of supported printers.<br />
<br />
To run the setup tool with the GUI qt frontend:<br />
# hp-setup -u<br />
<br />
To run the setup tool with the command line frontend:<br />
# hp-setup -i<br />
<br />
To set up directly the configuration of a network connected HP printer:<br />
# hp-setup -i ''<ip address>''<br />
<br />
To run systray spool manager:<br />
$ hp-systray<br />
<br />
To generate a URI for a given ip address:<br />
# hp-makeuri ''<ip address>''<br />
<br />
PPD files are in {{ic|/usr/share/ppd/HP/}}.<br />
<br />
If your printer is [https://developers.hp.com/hp-linux-imaging-and-printing/binary_plugin.html listed as requiring a binary plugin], install the {{AUR|hplip-plugin}} package from [[AUR]].<br />
If the binary plugin {{AUR|hplip-plugin}} is a requirement you will need to [[start]] the {{ic|org.cups.cupsd.service}} before the PPD is recognized by {{pkg|hplip}}.<br />
<br />
{{Note|<br />
{{Pkg|hplip}} depends on {{Pkg|foomatic-db-engine}} which prevents the drivers list from appearing when a printer is added to CUPS via the web user interface (following error : "Unable to get list of printer drivers"). Possible workarounds:<br />
* '''Either:''' Install {{Pkg|hplip}} first, then retrieve the PPD file that matches your printer from {{ic|/usr/share/ppd/HP/}}. Next, remove {{Pkg|hplip}} entirely as well as any unnecessary dependencies. Finally, install the printer manually using the CUPS web UI, selecting the PPD file you retrieved, and then re-install {{Pkg|hplip}}. After a reboot, you should have a fully working printer.<br />
* '''Or:''' Remove {{Pkg|hplip}}, {{Pkg|foomatic-db}} and {{Pkg|foomatic-db-engine}} along with any unnecessary dependencies. Reinstall {{Pkg|hplip}} and restart CUPS. Install your printer using the CUPS web UI, which should now be able to find the drivers automatically. No reboot needed.}}<br />
<br />
=== foo2zjs ===<br />
<br />
[http://foo2zjs.rkkda.com/ foo2zjs] supports some HP LaserJet printers. As of June 2018 the hplip package interferes with {{aur|foo2zjs-nightly}}, as described at [https://bbs.archlinux.org/viewtopic.php?pid=1662809 this forum post] and {{Bug|58815}}.<br />
<br />
==Konica Minolta==<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| Minolta Magicolor 1600W || rowspan=7 | [[foomatic]] ||<br />
|-<br />
| Minolta Magicolor 1680MF ||<br />
|-<br />
| Minolta Magicolor 1690MF ||<br />
|-<br />
| Minolta Magicolor 2480MF ||<br />
|-<br />
| Minolta Magicolor 2490MF ||<br />
|-<br />
| Minolta Magicolor 2530DL ||<br />
|-<br />
| Minolta Magicolor 4690MF ||<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
===foo2zjs===<br />
[[#foo2zjs]], mentioned above for supporting some HP printers, also support some Minolta printers.<br />
==Lexmark==<br />
<br />
===Utilities===<br />
<br />
Lexmark provides a utility called lexijtools with the drivers.<br />
<br />
===Custom drivers===<br />
<br />
Lexmark does provide Linux drivers for all their hardware.<br />
The following packages are required:<br />
<br />
*{{Pkg|cups}}<br />
*{{Pkg|sane}}<br />
*{{Pkg|ncurses}}<br />
*{{Pkg|libusb}}<br />
*{{Pkg|libxext}}<br />
*{{Pkg|libxtst}}<br />
*{{Pkg|libxi}}<br />
*{{Pkg|libstdc++5}}<br />
*{{Pkg|krb5}}<br />
*{{Pkg|lua}} (for the automated installer)<br />
*[[Java]] (for the automated installer, and some of the Lexmark tools)<br />
<br />
The drivers will need to be [http://support.lexmark.com/index?page=driversdownloads downloaded] from Lexmark's website. Preferably, create a package (see [[Creating packages]]) and install it. Here is a basic [[PKGBUILD]] that still needs work but will give an idea of what is required.<br />
<br />
{{hc|PKGBUILD|<nowiki><br />
# Contributor: Todd Partridge (Gen2ly) toddrpartridge (at) yahoo<br />
<br />
pkgname=cups-lexmark-Z2300-2600<br />
pkgver=1<br />
pkgrel=1<br />
pkgdesc="Lexmark Z2300 and 2600 Series printer driver for cups"<br />
arch=('i686')<br />
url="http://www.lexmark.com/"<br />
license=('custom')<br />
depends=('cups' 'glibc' 'ncurses' 'libusb' 'libxext' 'libxtst' 'libxi' 'libstdc++5' 'krb5' 'lua' 'java-runtime')<br />
conflicts=('z600' 'cjlz35le-cups' 'cups-lexmark-700')<br />
source=(lexmark-inkjet-08-driver-1.0-1.i386.tar.gz.sh)<br />
md5sums=(3c37eb87e3dad4853bf29344f9695134)<br />
<br />
<br />
package() {<br />
# Extract installer<br />
sh lexmark-inkjet-08-driver-1.0-1.i386.tar.gz.sh --target Installer-Files<br />
cd Installer-Files<br />
mkdir Driver<br />
tar xvvf instarchive_all --lzma -C Driver/<br />
cd Driver<br />
tar xv lexmark-inkjet-08-driver-1.0-1.i386.tar.gz -C $pkgdir<br />
}<br />
</nowiki>}}<br />
<br />
Keep in mind you can use the automated installer but doing so will leave the resulting changes untracked. The PPD will be installed into {{ic|/usr/local/lexmark/lxk08/etc/}} or similar, depending on the printer model.<br />
<br />
==Oki==<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| C110|| [[foomatic]] ||<br />
|-<br />
| MC561|| [[CUPS#Foomatic|foomatic-db-nonfree]] ||<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
==Ricoh==<br />
<br />
Install {{AUR|openprinting-ppds-pxlmono-ricoh}} if your device is black and white, or {{AUR|openprinting-ppds-pxlcolor-ricoh}} if it's color. Note that Ricoh copiers are sometimes branded as Savin, Gestetner, Lanier, Rex-Rotary, Nashuatec, and/or IKON. So, if you have a device bearing one of these brands, it may be supported by these drivers as well.<br />
<br />
* [https://www.openprinting.org/driver/pxlmono-Ricoh List of supported black and white models]<br />
* [https://www.openprinting.org/driver/pxlcolor-Ricoh List of supported color models]<br />
<br />
For winprinters (Ricoh series SP100 and SP200) try out {{AUR|ricoh-sp100-git}}. <br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| SP 112 || {{AUR|ricoh-sp100-git}} ||<br />
|-<br />
| SP 201n || {{AUR|ricoh-sp100-git}} ||<br />
|-<br />
| 213W || ''Generic PCL Laser'' || Obtain a WPS code by holding down the wifi button for 2 seconds, then hitting the stop/start button.<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
==Samsung==<br />
<br />
{{Accuracy|All the cnijfilter drivers appear to be for Canon printers - maybe the cnijfilter comment would be better off in the Canon section?}}<br />
<br />
For printers requiring the ''cnijfilter'' drivers, search for the correct driver [https://aur.archlinux.org/packages.php?K=cnijfilter in the AUR]<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| ML-2010 || {{Pkg|splix}} ||<br />
|-<br />
| SCX-4200 || {{Pkg|splix}} ||<br />
|-<br />
| Newer printers? || {{AUR|samsung-unified-driver}} ||<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
==Xerox or FujiXerox==<br />
<br />
{| class="wikitable"<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|-<br />
| DocuPrint 203A || {{Pkg|hplip}} || Using the '''DocuPrint P8e(hpijs)''' driver, or the Brother driver on FujiXerox's website (see [[#Brother]] for more information on how to install custom Brother drivers).<br />
|-<br />
| Phaser 3100MFP || Install Xerox's driver || See [[#Phaser 3100MFP]] for more instructions.<br />
|-<br />
| Phaser 6115MFP || [[foomatic]] ||<br />
|-<br />
| Phaser 6121MFP || [[foomatic]] ||<br />
|-<br />
! Printer<br />
! Driver/filter<br />
! Notes<br />
|}<br />
<br />
===Custom drivers===<br />
<br />
====Phaser 3100MFP====<br />
<br />
{{Warning|This section involves installing packages without [[pacman]]. These directions should ideally be automated with a [[PKGBUILD]].}}<br />
<br />
Once you have downloaded the drivers, execute the driver installer and accept the licence:<br />
# cd printer<br />
# ./XeroxPhaser3100.install<br />
Note that the driver is 32 bit, so some 32 bit libraries will be required on an x86_64 system.<br />
<br />
For the scanner, create an /etc/sane.d directory if it doesn't already exist, because it's need by the installer:<br />
# mkdir -p /etc/sane.d<br />
Now install the driver:<br />
# cd scanner/<br />
# ./XeroxPhaser3100sc.install<br />
Again, on an x86_64 install, 32 bit libraries will be needed.<br />
<br />
====Phaser 6000B====<br />
<br />
[[Install]] the [https://github.com/aur-archive/xerox-phaser-6010 xerox-phaser-6010] package (archived from the AUR).<br />
The driver may require older versions of {{Pkg|nettle}} and {{Pkg|gnutls}} to be installed, since the binary blob linked against older versions of the shared libraries provided by those packages. The oldest known-good versions are {{ic|nettle-2.7.1-1}} and {{ic|gnutls-3.3.13-1}}.<br />
<br />
====Phaser 6125N====<br />
<br />
{{Warning|This section involves installing packages without [[pacman]]. These directions should ideally be automated with a [[PKGBUILD]].}}<br />
<br />
FujiXerox does not support Linux on this model. An old rpm [http://onlinesupport.fujixerox.com/tiles/common/hc_drivers_download.jsp?system=%27Linux%27&shortdesc=null&xcrealpath=http://www.fujixeroxprinters.com/downloads/uploaded/dpc525a_linux_.0.0.tar_81c2.zip is available] but does not seem to work.<br />
<br />
A slightly adapted [https://rickvanderzwet.nl/trac/personal/wiki/XeroxPhaser6125N custom driver] has been found to work out of the box.<br />
<br />
To install the tarball, run<br />
# tar -C / --keep-newer-files -xvzf cups-xerox-phaser-6125n-1.0.0.tar.gz</div>Catlover2https://wiki.archlinux.org/index.php?title=Alienware_M14xR2&diff=292397Alienware M14xR22014-01-11T11:15:21Z<p>Catlover2: /* Video */ Fixed some small typos.</p>
<hr />
<div>[[Category:Alienware]]<br />
This wiki page documents the configuration and troubleshooting specific to the Alienware M14xR2 laptop.<br />
<br />
See the [[Beginners' Guide]] for installation instructions.<br />
<br />
==System Specifications==<br />
The [http://www.dell.com/us/p/alienware-m14x-r2/pd.aspx?c=en&cs=esdhs1&l=en&s=dhs&~ck=mn&ST=alienware%20m14x&dgc=ST&cid=41193&lid=1069556&acd=240415599220560 M14xR2 base model] comes with the following options:<br />
<br />
====Base model====<br />
* Intel® Core™ i5 or i7<br />
* 6GB or 8GB or 12GB or 16GB of 1600MHz DDR3 RAM<br />
* 1GB or 2GB GDDR5 NVIDIA® GeForce® GT 650M<br />
* 1366x768 or 1600x900 WLED TrueLife 14" screen<br />
* 750GB or 1000GB SATA drives and SSD until 500GB<br />
* SuperMulti 8x DVD±R/RW or Blu-ray double layer reader BD-ROM, DVD+RW, CD-RW<br />
* 8 cell Lithium-ion battery (63 W/h)<br />
* 1,3 megapixel webcap with 2 microphones<br />
* Optional 4.0 bluetooth<br />
* Wireless N capable<br />
<br />
====Ports====<br />
* RJ-45 Gigabit Ethernet<br />
* SuperSpeed USB 3.0 (2x)<br />
* Hi-Speed USB 2.0 with PowerShare technology<br />
* Mini display port<br />
* HDMI 1.4<br />
* VGA port<br />
* 9 in 1 card reader<br />
* Audio jack 1/8" (2x)<br />
* Input audio jack 1/8" (can be used for 5.1 audio output)<br />
* Security port<br />
<br />
===={{Ic|lspci}} output====<br />
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)<br />
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)<br />
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)<br />
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)<br />
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)<br />
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)<br />
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)<br />
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)<br />
00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4)<br />
00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4)<br />
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)<br />
00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04)<br />
00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04)<br />
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)<br />
01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GT 650M] (rev ff)<br />
01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev ff)<br />
07:00.0 Ethernet controller: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet (rev c0)<br />
08:00.0 Network controller: Atheros Communications Inc. AR9462 Wireless Network Adapter (rev 01)<br />
09:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)<br />
09:00.1 SD Host controller: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)<br />
<br />
== Ethernet ==<br />
The AR8132 Ethernet controller uses the '''atl1c''' module and works out-of-the-box with Linux kernel 3.x.<br />
<br />
# lspci -kv<br />
07:00.0 Ethernet controller: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet (rev c0)<br />
Subsystem: Dell Device 0552<br />
Flags: bus master, fast devsel, latency 0, IRQ 48<br />
Memory at d2600000 (64-bit, non-prefetchable) [size=256K]<br />
I/O ports at 2000 [size=128]<br />
Capabilities: <access denied><br />
Kernel driver in use: atl1c<br />
<br />
# modinfo atl1c<br />
filename: /lib/modules/3.7.9-2-ARCH/kernel/drivers/net/ethernet/atheros/atl1c/atl1c.ko.gz<br />
version: 1.0.1.0-NAPI<br />
license: GPL<br />
description: Qualcom Atheros 100/1000M Ethernet Network Driver<br />
author: Qualcomm Atheros Inc., <nic-devel@qualcomm.com><br />
author: Jie Yang<br />
srcversion: 1A550ECB609B4B690B47528<br />
alias: pci:v00001969d00001083sv*sd*bc*sc*i*<br />
alias: pci:v00001969d00001073sv*sd*bc*sc*i*<br />
alias: pci:v00001969d00002062sv*sd*bc*sc*i*<br />
alias: pci:v00001969d00002060sv*sd*bc*sc*i*<br />
alias: pci:v00001969d00001062sv*sd*bc*sc*i*<br />
alias: pci:v00001969d00001063sv*sd*bc*sc*i*<br />
depends: <br />
intree: Y<br />
vermagic: 3.7.9-2-ARCH SMP preempt mod_unload modversions <br />
<br />
# dmesg | grep -i atl1c<br />
[ 6.052602] atl1c 0000:07:00.0: version 1.0.1.0-NAPI<br />
[ 17.706845] atl1c 0000:07:00.0: irq 48 for MSI/MSI-X<br />
<br />
== Wireless LAN & Bluetooth ==<br />
Alienware M14xR2 comes with the [http://www.qca.qualcomm.com/networking/brand.php?brand=4&product=112 AR9462 chipset] which provides WLAN and Bluetooth capabilities.<br />
<br />
# lspci -kv<br />
08:00.0 Network controller: Atheros Communications Inc. AR9462 Wireless Network Adapter (rev 01)<br />
Subsystem: Bigfoot Networks, Inc. Device 2003<br />
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-<br />
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-<br />
Latency: 0, Cache Line Size: 64 bytes<br />
Interrupt: pin A routed to IRQ 18<br />
Region 0: Memory at d2500000 (64-bit, non-prefetchable) [size=512K]<br />
Expansion ROM at 9fb00000 [disabled] [size=64K]<br />
Capabilities: [40] Power Management version 3<br />
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-)<br />
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-<br />
Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+<br />
Address: 0000000000000000 Data: 0000<br />
Masking: 00000000 Pending: 00000000<br />
Capabilities: [70] Express (v2) Endpoint, MSI 00<br />
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us<br />
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-<br />
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-<br />
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-<br />
MaxPayload 128 bytes, MaxReadReq 512 bytes<br />
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-<br />
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <4us, L1 <64us<br />
ClockPM- Surprise- LLActRep- BwNot-<br />
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+<br />
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-<br />
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-<br />
DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported<br />
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled<br />
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-<br />
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-<br />
Compliance De-emphasis: -6dB<br />
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-<br />
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-<br />
Capabilities: [100 v1] Advanced Error Reporting<br />
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-<br />
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-<br />
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-<br />
CESta: RxErr+ BadTLP- BadDLLP+ Rollover- Timeout- NonFatalErr-<br />
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+<br />
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-<br />
Capabilities: [140 v1] Virtual Channel<br />
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1<br />
Arb: Fixed- WRR32- WRR64- WRR128-<br />
Ctrl: ArbSelect=Fixed<br />
Status: InProgress-<br />
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-<br />
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-<br />
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff<br />
Status: NegoPending- InProgress-<br />
Capabilities: [160 v1] Device Serial Number 00-00-00-00-00-00-00-00<br />
Kernel driver in use: ath9k<br />
<br />
Wireless LAN is working out of the box with the ath9k module:<br />
<br />
# modinfo ath9k<br />
filename: /lib/modules/3.7.9-2-ARCH/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko.gz<br />
license: Dual BSD/GPL<br />
description: Support for Atheros 802.11n wireless LAN cards.<br />
author: Atheros Communications<br />
alias: platform:qca955x_wmac<br />
alias: platform:ar934x_wmac<br />
alias: platform:ar933x_wmac<br />
alias: platform:ath9k<br />
alias: pci:v0000168Cd00000036sv*sd*bc*sc*i*<br />
alias: pci:v0000168Cd00000037sv*sd*bc*sc*i*<br />
alias: pci:v0000168Cd00000034sv*sd*bc*sc*i*<br />
alias: pci:v0000168Cd00000033sv*sd*bc*sc*i*<br />
alias: pci:v0000168Cd00000032sv*sd*bc*sc*i*<br />
alias: pci:v0000168Cd00000030sv*sd*bc*sc*i*<br />
alias: pci:v0000168Cd0000002Esv*sd*bc*sc*i*<br />
alias: pci:v0000168Cd0000002Dsv*sd*bc*sc*i*<br />
alias: pci:v0000168Cd0000002Csv*sd*bc*sc*i*<br />
alias: pci:v0000168Cd0000002Bsv*sd*bc*sc*i*<br />
alias: pci:v0000168Cd0000002Asv*sd*bc*sc*i*<br />
alias: pci:v0000168Cd00000029sv*sd*bc*sc*i*<br />
alias: pci:v0000168Cd00000027sv*sd*bc*sc*i*<br />
alias: pci:v0000168Cd00000024sv*sd*bc*sc*i*<br />
alias: pci:v0000168Cd00000023sv*sd*bc*sc*i*<br />
depends: ath9k_hw,ath9k_common,mac80211,ath,cfg80211<br />
intree: Y<br />
vermagic: 3.7.9-2-ARCH SMP preempt mod_unload modversions <br />
parm: debug:Debugging mask (uint)<br />
parm: nohwcrypt:Disable hardware encryption (int)<br />
parm: blink:Enable LED blink on activity (int)<br />
parm: btcoex_enable:Enable wifi-BT coexistence (int)<br />
parm: enable_diversity:Enable Antenna diversity for AR9565 (int)<br />
<br />
Bluetooth:<br />
<br />
TODO<br />
<br />
== Sound ==<br />
<br />
This computer is using the CA0132 chipset.<br />
Alsa should work out of the box except for some bugs.<br />
<br />
For those using 3.8 kernel note that card sometimes will do random noise that can be fixed by reloading the corresponding module saying that buffer position should be fixed:<br />
<br />
rmmod snd_hda_intel<br />
modprobe snd_hda_intel position_fix=1<br />
<br />
If you loose sound after system wake you can recover it by rebooting into Windows and booting Linux again. I believe this has to do with a firmware problem.<br />
There's also no headphone detection.<br />
<br />
In kernel 3.9 firmware problem seems to be fixed and headphone detection is working (If speakers don't automute go to alsamixer and unmute HP/Speaker Auto Detect). A lot of channels and fx were added to alsa. Automute only works with the one headphone and microphone jack and not with the earphones jack. This should be reported.<br />
<br />
== Touchpad ==<br />
<br />
Works out of the box.<br />
See [https://wiki.archlinux.org/index.php/Synaptics Synaptics]<br />
<br />
== Video ==<br />
<br />
Since kernel 3.5, PRIME technology is officially supported by the Nouveau graphic drivers. This means that the Nvidia Optimus GPU used in this computer is supported. You need to install [https://wiki.archlinux.org/index.php/Bumblebee bumblebee] to let vgaswitcheroo disable your graphics card.<br />
<br />
In kernel 3.7 power managing methods were added, so battery life increased a lot.<br />
<br />
Kernel 3.10 is coming with a lot of fixes in the Nouveau driver for our NVE0 (Kepler) graphics card. We are expecting a lot of power management improvements.<br />
<br />
== AlienFX ==<br />
<br />
AlienFX on Alienware M14xR2 is only supported by [https://aur.archlinux.org/packages/pyalienfx pyalienfx] that can be installed from AUR.<br />
<br />
You can visit [https://code.google.com/p/pyalienfx/ pyalienfx project webpage] for reporting issues.<br />
<br />
== BIOS ==<br />
<br />
Current latest version is A12 from InsydeH20.<br />
<br />
The updater provided by Dell is windows only. If you want to update and you don't have Windows I recomend you using HirensBoot CD and Unetbooting for creating an Windows Live USB in order to flash the bios.<br />
<br />
It contains the flasing utility and the update file (isflashWin.bin).<br />
WARNING: This file should not be used with the DOS flashit utility!<br />
As it seems this file is an MSDOS executable file which holds LZMA data inside. I could never get it working.</div>Catlover2https://wiki.archlinux.org/index.php?title=X11vnc&diff=291858X11vnc2014-01-07T03:08:34Z<p>Catlover2: /* SSH Tunnel */ No need for notice; SSH tunneling definitely works.</p>
<hr />
<div>[[Category:Security]]<br />
[[Category:Remote Desktop]]<br />
[[zh-CN:X11vnc]]<br />
{{Related articles start}}<br />
{{Related|Vncserver}}<br />
{{Related articles end}}<br />
x11vnc allows one to view remotely and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows.<br />
<br />
== Setting up x11vnc ==<br />
<br />
=== Installation ===<br />
<br />
{{Pkg|x11vnc}} is available in the [[Official Repositories|official repositories]].<br />
<br />
=== Starting ===<br />
<br />
First, start X either by ''startx'' or through a manager such as [[GDM]] or [[SLiM]]. Then, open a terminal and type<br />
$ x11vnc -display :0<br />
<br />
Another option is to place the x11vnc line in a script which is called at login.<br />
<br />
#!/bin/bash<br />
x11vnc -nap -wait 50 -noxdamage -passwd PASSWORD -display :0 -forever -o /var/log/x11vnc.log -bg<br />
<br />
{{Note|The password "PASSWORD" above is not secured; anyone who can run {{ic|ps}} on the machine will see it. Also note that {{ic|/var/log/x11vnc.log}} needs to be created manually and its ownership needs to match that of the user who will run it.}}<br />
<br />
==== Setting X authority ====<br />
<br />
You may set an X authority file for the VNC server. This is accomplished by using the {{ic|-auth}} argument followed by the appropriate file, which will depend on how your X server was started. Generally, assigning an X authority file requires running ''x11vnc'' as root.<br />
<br />
===== Start X =====<br />
<br />
$ x11vnc -display :0 -auth ~/.Xauthority<br />
If that fails, you may have to run (as root)<br />
# x11vnc -display :0 -auth /home/''user''/.Xauthority<br />
Where ''user'' is the username of the user who is running the X server.<br />
<br />
===== GDM =====<br />
<br />
# x11vnc -display :0 -auth /var/lib/gdm/:0.Xauth<br />
<br />
or see [[#Troubleshooting|Troubleshooting]] section below<br />
<br />
===== SLIM =====<br />
<br />
# x11vnc -display :0 -auth /var/run/slim.auth<br />
<br />
{{Warning|This will set up VNC with NO PASSWORD. This means that ANYBODY who has access to the network the computer is on CAN SEE YOUR XSERVER. It is a fairly simple matter to tunnel your VNC connection through SSH to avoid this. Or, simply set a password, as described below.}}<br />
<br />
{{Note|The password will only encrypt the login process itself. The transmission is still unencrypted[http://security.web.cern.ch/security/ssh/encrypt_vnc.htm].}}<br />
<br />
===== LXDM =====<br />
<br />
# x11vnc -display :0 -auth /var/run/lxdm/lxdm-\:0.auth<br />
<br />
==== Setting a password ====<br />
<br />
$ mkdir ~/.x11vnc<br />
$ x11vnc -storepasswd ''password'' ~/.x11vnc/passwd<br />
<br />
To connect using the stored password use the {{ic|-rfbauth}} argument and point to the passwd file you created, like so:<br />
$ x11vnc -display :0 -rfbauth ~/.x11vnc/passwd <br />
Your viewer should prompt for a password when connecting.<br />
<br />
==== Running constantly ====<br />
<br />
By default, x11vnc will accept the first VNC session and shutdown when the session disconnects.<br />
In order to avoid that, start x11vnc with the '''-many''' or '''-forever''' argument, like this:<br />
$ x11vnc -many -display :0<br />
or<br />
$ x11vnc -forever -display :0<br />
<br />
=== Accessing ===<br />
<br />
Get a VNC client on another computer, and type in the IP address of the computer running x11vnc. Hit connect, and you should be set.<br />
<br />
If you are attempting to access a VNC server / computer (running x11vnc) from outside of its network then you will need to ensure that it has port 5900 forwarded.<br />
<br />
== SSH Tunnel ==<br />
<br />
You need to have [[SSH]] installed and configured.<br />
<br />
Use the {{ic|-localhost}} flag with x11vnc for it to bind to the local interface. Once that is done, you can use SSH to tunnel the port; then, connect to VNC through SSH.<br />
<br />
Simple example (from http://www.karlrunge.com/x11vnc/index.html#tunnelling ):<br />
$ ssh -t -L 5900:localhost:5900 remote_host 'sudo x11vnc -display :0 -auth /home/USER/.Xauthority'<br />
where USER is the username of the user who is running the X server.<br />
<br />
(You will likely have to provide passwords/passphrases to login from your current location into your remote_host Unix account; we assume you have a login account on remote_host and it is running the SSH server)<br />
<br />
And then in another terminal window on your current machine run the command:<br />
<br />
$ vncviewer -encodings "copyrect tight zrle hextile" localhost:0<br />
<br />
== Troubleshooting ==<br />
<br />
1. You can check your ip address and make sure port 5900 is forwarded by visiting [http://www.realvnc.com/cgi-bin/nettest.cgi this] website.<br />
<br />
{{Accuracy}}<br />
<br />
2. Tested only on [[GNOME]] + [[GDM]]<br />
<br />
If you cannot start the tunnel, and get error like XOpenDisplay(":0") failed,<br />
Check if you have a {{ic|~/.Xauthority}} directory.<br />
If that does not exist, You can create one easily (Actually a symlink to actual one) by running command given below as normal user NOT ROOT OR USING [[Sudo]] as below:<br />
<br />
$ ln -sv $(dirname $(xauth info | awk '/Authority file/{print $3}')) ~/.Xauthority<br />
<br />
then try above [[#SSH Tunnel|tunneling]] example and it should work fine.<br />
Further if you want this to be automatically done each time [[Xorg]] is restarted, create the [[Xprofile]] file & make is executable as below<br />
<br />
$ ln -sf $(dirname $(xauth info | awk '/Authority file/{print $3}')) ~/.Xauthority<br />
<br />
3.''' GNOME 3''' and '''x11vnc'''<br />
<br />
If you are using GNOME 3 and x11vnc and you get the following errors<br />
<br />
*** XOpenDisplay failed (:0) <br />
<br />
*** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue.<br />
<br />
Try running x11vnc like<br />
<br />
$ x11vnc -noxdamage -many -display :0 -auth /var/run/gdm/$(sudo ls /var/run/gdm | grep $(whoami))/database -forever -bg<br />
<br />
Please update if this works / not works for any other [[Display Manager|display manager]] or [[Desktop Environment|desktop environment]].<br />
<br />
4. Screensaver problem<br />
<br />
If screensaver starts every 1-2 second, start x11vnc with -nodpms key.</div>Catlover2https://wiki.archlinux.org/index.php?title=Vim&diff=291313Vim2014-01-02T05:19:12Z<p>Catlover2: Improved wording and grammar in ==Merging files (vimdiff)==</p>
<hr />
<div>[[Category:Development]]<br />
[[Category:Text editors]]<br />
[[es:Vim]]<br />
[[de:Vim]]<br />
[[it:Vim]]<br />
[[lt:Vim]]<br />
[[ru:Vim]]<br />
[[zh-CN:Vim]]<br />
[[zh-TW:Vim]]<br />
''"[http://www.vim.org/about.php Vim] is an advanced text editor that seeks to provide the power of the de-facto UNIX editor ‘vi’, with a more complete feature set."'' <br />
<br />
Vim focuses on keyboard usage, and offers useful features such as syntax highlighting and scripting capabilities. Vim is not a simple text editor, like nano or pico. It does require some time to learn, and a great amount of time to master.<br />
<br />
== Installation ==<br />
<br />
[[pacman|Install]] the command line version with the {{Pkg|vim}} package, or you can install the GUI version (which also provides {{ic|vim}}) by installing the {{Pkg|gvim}} package.<br />
<br />
{{Note|<br />
* The {{Pkg|vim}} package is meant to be as lightweight as possible; hence, it does not support Python, Lua, and Ruby interpreters, nor does it support X server options (this means that it will not support copy and paste from the X clipboard). If you require these options, install the {{Pkg|gvim}} package instead (it includes the {{ic|vim}} binary as well). The {{ic|herecura-stable}} unofficial repository also provides a couple different Vim / gVim variants:<br />
{{hc|$ pacman -Slq herecura-stable &#124; grep vim|<br />
vim-cli<br />
vim-gvim-gtk<br />
vim-gvim-motif<br />
vim-gvim-qt<br />
vim-gvim-x11<br />
vim-rt<br />
vim-tiny<br />
}}<br />
<br />
* There are some visualization problems in KDE using {{Pkg|gvim}} from official repositories. In that case you can install {{ic|vim-gvim-qt}} from {{ic|herecura-stable}} or {{AUR|vim-qt}}<br />
}}<br />
<br />
==Usage==<br />
<br />
This is a basic overview on how to use Vim. Alternately, running {{Ic|vimtutor}} or {{Ic|gvimtutor}} will launch vim's tutorial, which takes about 25-30 minutes.<br />
<br />
Vim has four different modes:<br />
<br />
* Command mode: keystrokes are interpreted as commands.<br />
* Insert mode: keystrokes are entered into the file.<br />
* Visual mode: keystrokes select, cut, or copy text<br />
* Ex mode: input mode for additional commands (e.g. saving a file, replacing text...)<br />
<br />
===Basic editing===<br />
<br />
If you start Vim with:<br />
<br />
$ vim somefile.txt<br />
<br />
you will see a blank document (providing that somefile.txt does not exist. If it does, you will see what is in there). You will not be able to edit right away – you are in Command Mode. In this mode you are able to issue commands to Vim with the keyboard.<br />
<br />
{{Note|Vim is an example of classic Unix-style ware. It has a steep learning curve, but once you get started, you will find that it is extremely powerful. Also, all commands are case sensitive. Sometimes the uppercase versions are “blunter” versions ({{ic|s}} will replace a character, {{ic|S}} will replace a line), other times they are completely different commands ({{ic|j}} will move down, {{ic|J}} will join two lines).}}<br />
<br />
You insert text (stick it before the cursor) with the {{ic|i}} command. {{ic|I}} (uppercase '''i''') inserts text at the beginning of the line. You append text (place text after the cursor, what most people expect) with {{ic|a}}. Typing {{ic|A}} will place the cursor at the end of the line.<br />
<br />
Return to command mode at any time by pressing {{ic|Esc}}.<br />
<br />
===Moving around===<br />
<br />
In Vim, you can move the cursor with the arrow keys, but this isn't the '''Vim way'''. You’d have to move your right hand all the way from the standard typing position all the way to the arrow keys, and then back. Not fun.<br />
<br />
In Vim you can move down by pressing {{ic|j}}. You can remember this because the “j” hangs down. You move the cursor back up by pressing {{ic|k}}. Left is {{ic|h}} (it's left of the “j”), and right is {{ic|l}} (lowercase '''L''').<br />
<br />
{{ic|^}} will put the cursor at the beginning of the line, and {{ic|$}} will place it at the end.<br />
<br />
{{Note|{{ic|^}} and {{ic|$}} are commonly used in regular expressions to match the beginning and ending of the line. Regular expressions are very powerful and are commonly used in *nix environment, so maybe it is a little bit tricky now, but later you will notice “the idea” behind the use of most of these key mappings.}}<br />
<br />
To advance a word, press the {{ic|w}} key. {{ic|W}} will include more characters in what it thinks is a word (e.g. underscores and dashes as a part of a word). To go back a word, {{ic|b}} is used. Once again, {{ic|B}} will include more characters in what Vim considers a word. To advance to the end of a word, use {{ic|e}}, {{ic|E}} includes more characters.<br />
<br />
To advance to the beginning of a sentence, {{ic|(}} will get the job done. {{ic|)}} will do the opposite, moving to the end of a sentence. For an even bigger jump, {{ic|{}} will move the the beginning a whole paragraph. {{ic|<nowiki>}</nowiki>}} will advance to the end of a whole paragraph.<br />
<br />
To advance to the header (top) of the screen, {{ic|H}} will get the job done. {{ic|M}} will advance to the middle of the screen, and {{ic|L}} will advance to the last (bottom). {{ic|gg}} will go to the beginning of the file, {{ic|G}} will go to the end of the file. {{ic|Ctrl+D}} will let you scroll page by page.<br />
<br />
===Repeating commands===<br />
<br />
If a command is prefixed by a number, then that command will be executed that number of times over (there are exceptions, but they still make sense, like the {{ic|s}} command). For example, pressing {{ic|3i}} then “Help! ” then {{ic|Esc}} will print “Help! Help! Help!“. Pressing {{ic|<nowiki>2}</nowiki>}} will advance you two paragraphs. This comes in handy with the next few commands…<br />
<br />
===Deleting===<br />
<br />
The {{ic|x}} command will delete the character under the cursor. {{ic|X}} will delete the character before the cursor. This is where those number functions get fun. {{ic|6x}} will delete 6 characters. Pressing {{ic|.}} (dot) will repeat the previous command. So, lets say you have the word "foobar" in a few places, but after thinking about it, you’d like to see just “foo”. Move the cursor under the "b", hit {{ic|3x}}, move to the next "foobar" and hit {{ic|.}} (dot).<br />
<br />
The {{ic|d}} will tell Vim that you want to delete something. After pressing {{ic|d}}, you need to tell Vim what to delete. Here you can use the movement commands. {{ic|dW}} will delete up to the next word. {{ic|d^}} will delete up unto the beginning of the line. Prefacing the delete command with a number works well too: {{ic|3dW}} will delete the next three words. {{ic|D}} (uppercase) is a shortcut to delete until the end of the line (basically {{ic|d$}}). Pressing {{ic|dd}} will delete the whole line.<br />
<br />
To delete then replace the current word, place the cursor on the word and execute the command {{ic|cw}}. This will delete the word and change to insert mode. To replace only a single letter use {{ic|r}}.<br />
<br />
===Undo and redo===<br />
<br />
Vim has a built-in clipboard (also known as a buffer). Actions can be undone with {{ic|u}} and redone with {{ic|Ctrl+r}}.<br />
<br />
===Visual mode===<br />
<br />
Pressing {{ic|v}} will put you in visual mode . Here you can move around to select text, when you’re done, you press {{ic|y}} to yank the text into the buffer (copy), or you may use {{ic|c}} to cut. {{ic|p}} pastes after the cursor, {{ic|P}} pastes before. {{ic|V}}, Visual Line mode, is the same for entire lines. {{ic|Ctrl+v}} is for blocks of text.<br />
<br />
{{Note|Whenever you delete something, that something is placed inside a buffer and is available for pasting.}}<br />
<br />
===Search and replace===<br />
<br />
To search for a word or character in the file, simply use {{ic|/}} and then the characters your are searching for and press enter. To view the next match in the search press {{ic|n}}, press {{ic|N}} for the previous match.<br />
<br />
To search and replace use the substitute {{ic|:s/}} command. The syntax is: {{Ic|[range]s///[arguments]}}. For example:<br />
<br />
{{bc|<br />
Command Outcome<br />
:s/xxx/yyy/ Replace xxx with yyy at the first occurence<br />
:s/xxx/yyy/g Replace xxx with yyy first occurrence, global (whole sentence)<br />
:s/xxx/yyy/gc Replace xxx with yyy global with confirm<br />
:%s/xxx/yyy/g Replace xxx with yyy global in the whole file<br />
}}<br />
<br />
You can use the global {{ic|:g/}} command to search for patterns and then execute a command for each match. The syntax is: {{Ic|[range]:g//[cmd]}}.<br />
<br />
{{bc|<br />
Command Outcome<br />
:g/^#/d Delete all lines that begins with #<br />
:g/^$/d Delete all lines that are empty<br />
}}<br />
<br />
===Saving and quitting===<br />
<br />
To save and/or quit, you will need to use Ex mode. Ex mode commands are preceded by a {{ic|:}}. To write a file use {{ic|:w}} or if the file doesn’t have a name {{ic|''':w''' filename}}. Quitting is done with {{ic|:q}}. If you choose not to save your changes, use {{ic|:q!}}. To save and quit {{ic|:x}}.<br />
<br />
=== Additional commands ===<br />
<br />
# Pressing {{ic|s}} will erase the current letter under the cursor, and place you in insert mode. {{ic|S}} will erase the whole line, and place you in insert mode.<br />
# {{ic|o}} will create a newline below the line and put you insert mode, {{ic|O}} will create a newline above the line and put you in insert mode.<br />
# {{ic|yy}} will yank an entire line<br />
# {{ic|cc}} will delete the current line and place you in insert mode.<br />
# {{ic|*}} will highlight the current word and {{ic|n}} will search it<br />
<br />
==Configuration==<br />
<br />
Vim's user-specific configuration file is located in the home directory: {{ic|~/.vimrc}}, and files are located inside {{ic|~/.vim/}} The global configuration file is located at {{ic|/etc/vimrc}}. Global files are located inside {{ic|/usr/share/vim/}}.<br />
<br />
The Vim global configuration in Arch Linux is very basic and differs from many other distributions' default Vim configuration file. To get some commonly expected behaviors (such as syntax highlighting, returning to the last known cursor position), consider using Vim's example configuration file:<br />
<br />
# mv /etc/vimrc /etc/vimrc.bak<br />
# cp /usr/share/vim/vim74/vimrc_example.vim /etc/vimrc<br />
<br />
===Wrap searches===<br />
<br />
With this option the ''search next'' behaviour allows to jump to the beginning of the file, when the end of file is reached. Similarly, ''search previous'' jumps to the end of the file when the start is reached. <br />
<br />
set wrapscan<br />
<br />
=== Spell checking ===<br />
<br />
set spell<br />
<br />
With this setting, Vim will highlight incorrectly spelled words. Place the cursor on a misspelled word and enter {{ic|1=z=}} to view spelling suggestions.<br />
<br />
Only English language dictionaries are installed by default, more can be found in the [[Official Repositories|official repositories]]. To get the list of available languages type:<br />
<br />
# pacman -Ss vim-spell<br />
<br />
Language dictionaries can also be found at the [http://ftp.vim.org/vim/runtime/spell/ Vim FTP archive]. Put the downloaded dictionar(y/ies) into the {{ic|~/.vim/spell}} folder and set the dictionary by typing: {{ic|1=:setlocal spell spelllang=LL}}<br />
<br />
{{Tip|<br />
* To enable spell checking for LaTeX (or TeX) documents only, add {{ic|1=autocmd FileType tex setlocal spell spelllang=en_us}} into your {{ic|~/.vimrc}} or {{ic|/etc/vimrc}}, and then restart Vim. For spell checking of languages other than English, simply replace {{ic|en_us}} with the value appropriate for your language.<br />
* To enable spelling in two languages (for instance English and German), add {{ic|1=set spelllang=en,de}} into your {{ic|~/.vimrc}} or {{ic|/etc/vimrc}}, and then restart Vim.<br />
* You can enable spell checking for arbitrary file types (e.g. *.txt) by using the FileType plugin and a custom rule for file type detection. To enable spell checking for any file ending in {{ic|*.txt}}, create the file {{ic|/usr/share/vim/vimfiles/ftdetect/plaintext.vim}}, and insert the line {{ic|autocmd BufRead,BufNewFile *.txt setfiletype plaintext}} into that file. Next, insert the line {{ic|1=autocmd FileType plaintext setlocal spell spelllang=en_us}} into your {{ic|~/.vimrc}} or {{ic|/etc/vimrc}}, and then restart Vim.}}<br />
<br />
===Syntax highlighting===<br />
<br />
To enable syntax highlighting (Vim supports a huge list of programming languages):<br />
<br />
:filetype plugin on<br />
:syntax on<br />
<br />
===Using the mouse===<br />
<br />
Vim has the ability to make use of the mouse, but requires xterm's mouse reporting feature.<br />
<br />
# See the example .vimrc below to enable the mouse.<br />
# Use xterm. In your console: {{ic|1=export TERM=xterm-256color}} or {{ic|1=export TERM=xterm}}<br />
<br />
Notes:<br />
* This even works in PuTTY over SSH.<br />
* In PuTTY, the normal highlight/copy behaviour is changed because Vim enters visual mode when the mouse is used. To select text with the mouse normally, hold down the {{ic|Shift}} key while selecting text.<br />
<br />
===Traverse line breaks with arrow keys===<br />
<br />
By default, pressing {{ic|←}} at the beginning of a line, or pressing {{ic|→}} at the end of a line, will not let the cursor traverse to the previous, or following, line.<br />
<br />
The default behavior can be changed by adding {{ic|1=set whichwrap=b,s,<,>,[,]}} to your {{ic|~/.vimrc}} file.<br />
<br />
=== Example ~/.vimrc ===<br />
<br />
An example [[Vim/.vimrc|Vim configuration]].<br />
<br />
==Plugins==<br />
Adding plugins to vim can increase your productivity. The group vim-plugins has many plugins to choose from(there are more in the repos though ie: vim-supertab).<br />
pacman -Ss vim-plugins<br />
===cscope===<br />
[http://cscope.sourceforge.net/ Cscope] is a tool for browsing a project. By navigating to a word/symbol/function and calling cscope(usually with shortcut keys) it can find: functions calling the function, the function definition, and more. Multiple steps are required to search a code base.<br />
<br />
Install the {{Pkg|cscope}} package.<br />
<br />
Copy the cscope default file where it will be automatically read by vim:<br />
mkdir -p ~/.vim/plugin<br />
wget -P ~/.vim/plugin http://cscope.sourceforge.net/cscope_maps.vim <br />
<br />
Create a file which contains the files you wish cscope to index(Cscope can handle many languages but this example finds .c, .cpp, and .h files):<br />
cd ''/path/to/projectfolder/''<br />
find . -type f -print | grep -E '\.(c(pp)?|h)$' > cscope.files<br />
Create database files that cscope will read:<br />
cscope -bq<br />
{{note|You must browse your project files from this location or set and export the $CSCOPE_DB variable, pointing it to the cscope.out file.}}<br />
<br />
Default keyboard shortcuts<br />
Ctrl-\ and<br />
c: Find functions calling this function<br />
d: Find functions called by this function<br />
e: Find this egrep pattern<br />
f: Find this file<br />
g: Find this definition<br />
i: Find files #including this file<br />
s: Find this C symbol<br />
t: Find assignments to<br />
<br />
Feel free to change the shortcuts.<br />
#Maps ctrl-c to find functions calling the function <br />
nnoremap <C-c> :cs find c <C-R>=expand("<cword>")<CR><CR><br />
<br />
===Taglist===<br />
[http://vim-taglist.sourceforge.net/ Taglist] provides an overview of the structure of source code files and allows you to efficiently browse through source code files in different programming languages.<br />
<br />
Install the {{Pkg|vim-taglist}} package.<br />
<br />
Usefull options to be put in ~/.vimrc<br />
let Tlist_Compact_Format = 1<br />
let Tlist_GainFocus_On_ToggleOpen = 1<br />
let Tlist_Close_On_Select = 1<br />
nnoremap <C-l> :TlistToggle<CR><br />
<br />
==Merging files (vimdiff)==<br />
<br />
Vim includes a diff editor, a program that aids the merging of differences between two (or more, with limited usefulness) files. {{ic|vimdiff}} opens a horizontally multi-paned view that colorfully highlights differences, each pane containing one of the files to be examined/edited. Vim has [[#Usage|several modes]], two important ones being '''Insert mode''', which lets text be edited, and '''Command mode''', which lets the cursor be moved move across windows and lines. Begin by running {{ic|vimdiff file1 file2}}. Some example commands follow.<br />
<br />
;{{ic|]c}} : next difference<br />
;{{ic|[c}} : previous difference<br />
;{{ic|Ctrl+w+w}} : switch windows<br />
;{{ic|i}} : enter Insert mode<br />
;{{ic|Esc}} : exit Insert mode<br />
;{{ic|p}} : paste<br />
;{{ic|do}} : diff obtain. When the cursor is on a (highlighted) difference, copies the changes from the other window to the current one.<br />
;{{ic|dp}} : diff put. Inverse of diff obtain; copies the changes from current windows to the other one.<br />
;{{ic|zo}} : open folded text<br />
;{{ic|zc}} : close folded text<br />
;{{ic|<nowiki>:</nowiki>diffupdate}} : re-scan the files for differences<br />
;{{ic|yy}} : copy a line<br />
;{{ic|dd}} : cut a line<br />
;{{ic|:wq}} : save and exit the current window<br />
;{{ic|:wqa}} : save and exit both windows<br />
;{{ic|:q!}} : exit without saving<br />
<br />
Once your file has been correctly edited, taking into account changes in file.pacnew:<br />
# mv file file.bck<br />
# mv file.pacnew file<br />
Check whether your new file is correct, then remove your backup:<br />
# rm file.bck<br />
<br />
==Vim tips==<br />
<br />
Specific user tricks to accomplish tasks.<br />
<br />
===Line numbers===<br />
<br />
# Show line numbers by {{Ic|:set number}}.<br />
# Jump to line number {{Ic|:<line number>}}.<br />
<br />
===Substitute on lines===<br />
<br />
To only substitute between certain lines:<br />
<br />
:''n'',''n''s/one/two/g<br />
<br />
For example, to replace instances of 'one' with 'two' between lines 3 and 4, one would execute:<br />
<br />
:3,4s/one/two/g<br />
<br />
===Make Vim restore cursor position in files===<br />
<br />
If you want the cursor to appear in its previous position after you open a file, add the following to your {{ic|~/.vimrc}}:<br />
<br />
{{bc|<nowiki><br />
if has("autocmd")<br />
au BufReadPost * if line("'\"") > 1 && line("'\"") <= line("$") | exe "normal! g`\"" | endif<br />
endif<br />
</nowiki>}}<br />
<br />
See also [http://vim.wikia.com/wiki/Restore_cursor_to_file_position_in_previous_editing_session this] tip in Vim Wiki.<br />
<br />
===Empty space at the bottom of gVim windows===<br />
When using a [[window manager]] configured to ignore window size hints, gVim will fill the non-functional area with the GTK theme background color. <br />
<br />
The solution is to adjust how much space gVim reserves at the bottom of the window. Take note that if you set it to zero, you won't be able to see the bottom horizontal scrollbar, if you have one. Put the following line in {{ic|~/.vimrc}}:<br />
<br />
set guiheadroom=0<br />
<br />
===Replace vi command with vim===<br />
<br />
Create an [[Bash#Aliases|alias]] for {{ic|vi}} to {{ic|vim}}.<br />
<br />
==Troubleshooting==<br />
<br />
==="^M"===<br />
There is a "^M" at the end of each line. This usually happens when you are editing a text file which was created in MS-DOS or Windows.<br />
<br />
Solution:<br />
Replace all "^M" using the command:<br />
<br />
{{bc|:%s/^M//g}}<br />
<br />
Pay attention, "^" is the control letter, press {{ic|Ctrl+Q}} to get the right "^".<br />
<br />
Alternatively, install the package {{pkg|dos2unix}} from the official repositories, and run {{ic|dos2unix <file name here>}}.<br />
<br />
==See also==<br />
<br />
===Official===<br />
* [http://www.vim.org/ Homepage]<br />
* [http://vimdoc.sourceforge.net/ Documentation]<br />
* [http://vim.wikia.com Tips Wiki]<br />
<br />
===Tutorials===<br />
* [http://usalug.org/vi.html vi Tutorial and Reference Guide]<br />
* [http://www.viemu.com/a_vi_vim_graphical_cheat_sheet_tutorial.html Graphical vi-Vim Cheat Sheet and Tutorial]<br />
* [http://blog.interlinked.org/tutorials/vim_tutorial.html Vim Introduction and Tutorial]<br />
* [http://www.openvim.com/ Open Vim] - Collection of Vim learning tools<br />
* [http://yannesposito.com/Scratch/en/blog/Learn-Vim-Progressively/ Learn Vim Progressively]<br />
* [http://www.knowvim.com/ know vim]<br />
<br />
====Videos====<br />
* [http://vimcasts.org/ Vimcasts] - Screencasts in .ogg format.<br />
* [http://www.derekwyatt.org/vim/vim-tutorial-videos/vim-novice-tutorial-videos/ Tutorial Videos] - Covering the basics up to advanced topics.<br />
<br />
====Games====<br />
* [http://vim-adventures.com/ Vim Adventures]<br />
* [http://vimgolf.com/ VimGolf]<br />
<br />
===Example configurations===<br />
* [http://nion.modprobe.de/setup/vimrc nion's]<br />
* [http://amix.dk/vim/vimrc.html A detailed configuration from Amir Salihefendic]<br />
* [http://www.jukie.net/~bart/conf/vimrc Bart Trojanowski]<br />
* [https://github.com/spf13/spf13-vim Steve Francia's Vim Distribution]<br />
* [https://github.com/W4RH4WK/dotVim W4RH4WK's Vim configuration]<br />
* [http://www.askapache.com/linux/fast-vimrc.html Fast vimrc/colorscheme from askapache]<br />
<br />
===Other===<br />
* [http://www.gentoo-wiki.info/HOWTO_VIM HOWTO Vim] - Gentoo wiki article which this article was based on (author unknown).<br />
* [http://bytefluent.com/vivify/ Vivify] - A ColorScheme Editor for Vim</div>Catlover2https://wiki.archlinux.org/index.php?title=HP_ProBook_4530s&diff=288018HP ProBook 4530s2013-12-15T04:52:36Z<p>Catlover2: Function keys for adjusting brightness work on KDE too.</p>
<hr />
<div>[[Category: HP]]<br />
{| style="float:right; border: 1px solid #000;" <br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|- <br />
| Graphics || style="color:green" | '''Working''' || xf86-video-intel <br />
|-<br />
| Bluetooth || style="color:green" | '''Working''' || bluetooth<br />
|-<br />
| Ethernet || style="color:green" | '''Working''' || r8169<br />
|-<br />
| Wireless || style="color:green" | '''Working''' || ath9k<br />
|-<br />
| Audio || style="color:green" | '''Working''' || snd_hda_intel<br />
|-<br />
| Camera || style="color:green" | '''Working''' || uvcvideo <br />
|-<br />
| Card Reader || style="color:green" | '''Working''' || sdhci/sdhci_pci, jmb38x_ms<br />
|-<br />
| Function Keys || style="color:green" | '''Working''' || hp_wmi<br />
|}<br />
<br />
== Device information==<br />
<br />
This model has many hardware configurations. Mine has an i3 processor, Intel HD Graphics 3000 video card, and an Atheros AR9285 Wi-Fi card. <br />
<br />
=== lspci ===<br />
<br />
{{bc|00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)<br />
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)<br />
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)<br />
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)<br />
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)<br />
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)<br />
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4)<br />
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4)<br />
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4)<br />
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b4)<br />
00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 8 (rev b4)<br />
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)<br />
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 04)<br />
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04)<br />
23:00.0 System peripheral: JMicron Technology Corp. SD/MMC Host Controller (rev 30)<br />
23:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller (rev 30)<br />
23:00.3 System peripheral: JMicron Technology Corp. MS Host Controller (rev 30)<br />
24:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)<br />
25:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)<br />
26:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)}}<br />
<br />
== Configuration ==<br />
<br />
=== Network ===<br />
<br />
Both the wired and wireless network cards works out-of-the-box. The Atheros card requires the '''ath9k''' module, and the Realtek ethernet card requires the '''r8169''' module. More information can be found at [[Wireless Setup#ath9k]]<br />
{{Note|With some revisions of this Realtek ethernet card, better performance may be obtained with the Realtek provided {{Pkg|r8168}} module, available in the [[Official Repositories|official repositories]].}}<br />
<br />
=== Bluetooth ===<br />
<br />
Sending/receiving files and switching bluetooth on/off works. The '''ath3k''' module is required.<br />
<br />
==== hciconfig -a ====<br />
<br />
{{bc|hci0: Type: BR/EDR Bus: USB<br />
BD Address: D0:DF:9A:91:B2:51 ACL MTU: 1022:8 SCO MTU: 121:3<br />
UP RUNNING PSCAN ISCAN <br />
RX bytes:1823103 acl:11471 sco:0 events:10296 errors:0<br />
TX bytes:334040 acl:9846 sco:0 commands:259 errors:0<br />
Features: 0xff 0xfe 0x0d 0xfe 0x98 0x7f 0x79 0x87<br />
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 <br />
Link policy: RSWITCH HOLD SNIFF <br />
Link mode: SLAVE ACCEPT <br />
Name: '4530s'<br />
Class: 0x580100<br />
Service Classes: Capturing, Object Transfer, Telephony<br />
Device Class: Computer, Uncategorized<br />
HCI Version: 3.0 (0x5) Revision: 0x9999<br />
LMP Version: 3.0 (0x5) Subversion: 0x9999<br />
Manufacturer: Atheros Communications, Inc. (69)<br />
}}<br />
<br />
=== Graphics ===<br />
<br />
Intel HD Graphics 3000 is supported by the open-source {{Pkg|xf86-video-intel}} driver. Dual-head with HDMI works.<br />
<br />
==== Brightness ====<br />
<br />
Controlling screen brightness with the keystrokes {{ic|Fn+F2}} and {{ic|Fn+F3}} works in Gnome 3 and KDE and has not been tested in other desktop environments.<br />
<br />
=== Touchpad ===<br />
<br />
Works with {{Pkg|xf86-input-synaptics}} package. Could not get it to switch off while double tapped in top-left corner, like it worked in Suse Linux Enterprise Desktop, which was factory OS. Tested tapping, two and three finger tapping and two-finger scrolling. <br />
<br />
=== Miscellaneous hardware ===<br />
<br />
==== Card reader ====<br />
<br />
{{bc|23:00.0 System peripheral: JMicron Technology Corp. SD/MMC Host Controller (rev 30)<br />
23:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller (rev 30)<br />
23:00.3 System peripheral: JMicron Technology Corp. MS Host Controller (rev 30)<br />
}}<br />
SD cards tested and working. <strike>Memory Stick cards do not work, despite having module '''jmb38x_ms''' loaded. Dmesg does not show any info about Memory Stick card being inserted.</strike> With 3.4.7 kernel, Memory Stick card works as intended.<br />
<br />
====Function keys====<br />
<br />
Module '''hp-wmi''' is likely to be required for the keys to work. In Gnome 3 every {{ic|Fn+F*}} key works. {{ic|Fn-F6}} key requires gnome-power-manager installed.<br />
Keys above numeric keypad are also recognized. The Web key has a XF86HomePage symbol (opens home page) and Wi-Fi key has NoSymbol and does nothing.<br />
<br />
====Camera====<br />
<br />
Works with '''uvcvideo''' module.<br />
<br />
===Power===<br />
<br />
Module '''acpi-cpufreq''' and at least one of CPU governors ('''cpufreq_ondemand''', '''cpufreq_conservative''', etc.) are required. More informations on [[CPU Frequency Scaling]].<br />
{{Note|<s>i915 module parameter i915_enable_rc6 can give up to 2 hours of additional battery life. However it is considered unstable and might cause crashes and graphical glitches. Add '''i915.i915_enable_rc6&#61;1''' to the kernel command line of your bootloader to try it.</s><br />
* With laptop-mode-tools, tune from powertop2 and i915_enable_rc6 parameter I was able to get about 5:30h of estimated battery life.<br />
* Keep in mind that the powertop "good/bad" parameters will not survive a reboot. [http://intellinuxgraphics.org/2012.07.html As of 3.4.x] rc6 is enabled by default for Ivy Bridge and Sandy Bridge processors. The default (marked -1) is equivalent of i915_enable_rc6&#61;3 which enables rc6 and rc6p. An additional, lower power state can also be enabled by using i915_enable_rc6&#61;7, though this has been reported to sometimes come at the cost of stability. Also, as of [http://intellinuxgraphics.org/2011Q4.html 2011Q4] the i915 module in Sandy Bridge and Ivy Bridge also have framebuffer compression enabled by default.<br />
}}<br />
<br />
=== Suspend and hibernation ===<br />
<br />
Both suspend and hibernation work with pm-utils and kernel backend.<br />
<br />
==== Sensors ====<br />
<br />
{{Pkg|lm_sensors}} shows one acpitz-virtual device with 4 working temperature readings and coretemp-isa device which has one sensor for each CPU core.<br />
It does not show any info about fans RPMs.<br />
<br />
{{bc|1=acpitz-virtual-0<br />
Adapter: Virtual device<br />
temp1: +51.0°C (crit = +128.0°C)<br />
temp2: +0.0°C (crit = +128.0°C)<br />
temp3: +38.0°C (crit = +128.0°C)<br />
temp4: +50.0°C (crit = +128.0°C)<br />
temp5: +26.0°C (crit = +128.0°C)<br />
temp6: +0.0°C (crit = +128.0°C)<br />
temp7: +0.0°C (crit = +128.0°C)<br />
temp8: +0.0°C (crit = +128.0°C)<br />
<br />
coretemp-isa-0000<br />
Adapter: ISA adapter<br />
Physical id 0: +53.0°C (high = +80.0°C, crit = +85.0°C)<br />
Core 0: +49.0°C (high = +80.0°C, crit = +85.0°C)<br />
Core 1: +50.0°C (high = +80.0°C, crit = +85.0°C)<br />
}}</div>Catlover2https://wiki.archlinux.org/index.php?title=Epson_TX125&diff=287907Epson TX1252013-12-14T02:09:19Z<p>Catlover2: Removed unneeded {{bc|}}.</p>
<hr />
<div>[[es:Epson TX125]]<br />
[[Category:Printers]]<br />
{{Stub}}<br />
<br />
This page provides instructions for installing the Epson TX125 printer driver.<br />
<br />
First, install {{Pkg|cups}} from the official repositories and {{AUR|epson-inkjet-printer-n10-nx127}} from the AUR.<br />
<br />
Create a new udev rule, {{ic|/etc/udev/rules.d/10-usbprinter.rules}}, with the following content.<br />
ATTR{idVendor}=="04b8", ATTR{idProduct}=="085c", MODE:="0666", GROUP:={"lp"}, E$<br />
Verify {{ic|idVendor}} and {{ic|idProduct}} by running {{ic|# lsusb -v}}.</div>Catlover2https://wiki.archlinux.org/index.php?title=Epson_TX125_(Espa%C3%B1ol)&diff=287906Epson TX125 (Español)2013-12-14T02:08:05Z<p>Catlover2: Edited to be more like the English page.</p>
<hr />
<div>[[en:Epson TX125]]<br />
[[Category:Printers (Español)]]<br />
{{Stub}}<br />
<br />
Estas son las instrucciones para instalar el controlador de la impresora Epson TX125.<br />
<br />
Primero, instale {{Pkg|cups}} de los repositorios oficiales y {{AUR|epson-inkjet-printer-n10-nx127}} del AUR.<br />
<br />
Cree una nueva regla de udev, {{ic|/etc/udev/rules.d/10-usbprinter.rules}}, con el contiendo siguiente.<br />
ATTR{idVendor}=="04b8", ATTR{idProduct}=="085c", MODE:="0666", GROUP:={"lp"}, E$<br />
<br />
{{ic|idVendor}} e {{ic|idProduct}} lo obtengo con {{ic|# lsusb -v}}.</div>Catlover2https://wiki.archlinux.org/index.php?title=File_recovery&diff=287820File recovery2013-12-13T12:21:43Z<p>Catlover2: A lot of grammatical corrections, some clarifications and rewording.</p>
<hr />
<div>[[Category:File systems]]<br />
[[Category:System recovery]]<br />
== Preface/Introduction ==<br />
<br />
=== Page Overview ===<br />
<br />
This article lists data recovery and undeletion options for [[Arch Linux]]. Please contribute to this page using the general format below, keeping it brief if possible.<br />
<br />
=== Special Notes===<br />
<br />
==== Before you start ====<br />
<br />
This page is mostly intended to be used for educational purposes. If you have accidentally deleted or otherwise damaged your '''valuable and irreplaceable''' data and have no previous experience with data recovery, turn off your computer immediately (Just press and hold the off button or pull the plug; do not use the system shutdown function) and seek professional help. It is quite possible and even probable that, if you follow any of the steps described below without fully understanding them, you will worsen your situation.<br />
<br />
==== Failing Drives ====<br />
<br />
In the area of data recovery, it is best to work on images of disks rather than physical disks themselves. Generally, a failing drive's condition worsens over time. The goal ought to be to first rescue as much data as possible as early as possible in the failure of the disk and to then abandon the disk. The {{Pkg|ddrescue}} and {{Pkg|dd_rescue}} utilities, unlike {{ic|dd}}, will repeatedly try to recover from errors and will read the drive front to back, then back to front, attempting to salvage data. They keep log files so that recovery can be paused and resumed without losing progress.<br />
<br />
See [[Disk Cloning]].<br />
<br />
The image files created from a utility like ddrescue can then be mounted like a physical device and can be worked on safely. Always make a copy of the original image so that you can revert if things go sour!<br />
<br />
A tried and true method of improving failing drive reads is to keep the drive cold. A bit of time in the freezer is appropriate, but be careful to avoid bringing the drive from cold to warm too quickly, as condensation will form. Keeping the drive in the freezer with cables connected to the recovering PC works great.<br />
<br />
Do not attempt a filesystem check on a failing drive, as this will likely make the problem '''worse'''. Mount it read-only.<br />
<br />
====Backup Flash Media/Small Partitions====<br />
As an alternative to working with a 'live' partition (mounted or not), it is often preferable to work with an image, provided that the filesystem in question is not too large and that you have sufficient free HDD space to accommodate the image file. For example, flash memory devices like thumb drives, digital cameras, portable music players, cellular phones, etc. are likely to be small enough to image in many cases.<br />
<br />
Be sure to read the man pages for the utilities listed below to verify that they are capable of working with image files.<br />
<br />
To make an image, one can use {{ic|dd}} as follows:<br />
# dd if=/dev/target_partition of=/home/user/partition.image<br />
<br />
====Working with Digital Cameras====<br />
In order for some of the utilities listed in the next section to work with flash media, the device in question needs to be mounted as a block device (i.e., listed under /dev). Digital cameras operating in PTP (Picture Transfer Protocol) mode will not work in this regard. PTP cameras are transparently handled by libgphoto and/or libptp. In this case, "transparently" means that PTP devices do not get block devices. The alternative to PTP mode, USB Mass Storage (UMS) mode, is not supported by all cameras. Some cameras have a menu item that allows switching between the two modes; refer to your camera's user manual. If your camera does not support UMS mode and therefore cannot be accessed as a block device, your only alternative is to use a flash media reader and physically remove the storage media from your camera.<br />
<br />
==Foremost==<br />
===Description===<br />
[[Foremost]] is a console program to recover files based on their headers, footers, and internal data structures. This process is commonly referred to as data carving. Foremost can work on disk image files (such as those generated by dd, Safeback, Encase, etc.) or directly on a drive. The headers and footers can be specified by a configuration file or command line switches can be used to specify built-in file types. These built-in types look at the data structures of a given file format, allowing for more reliable and faster recovery. <br />
===Installation===<br />
{{AUR|foremost}} is available in the [[AUR]].<br />
===External Links===<br />
*Wiki: <br />
*Homepage: http://foremost.sourceforge.net<br />
<br />
==Extundelete==<br />
===Description===<br />
'''[http://extundelete.sourceforge.net/ Extundelete]''' is a terminal-based utility designed to recover deleted files from ext3 and ext4 partitions. It can recover all the recently deleted files from a partition and/or a specific file(s) given by relative path or inode information. Note that it works only when the partition is unmounted. The recovered files are saved in the current directory under the folder named {{ic|RECOVERED_FILES/}}.<br />
===Installation===<br />
{{Pkg|extundelete}} is available in the [[official repositories]].<br />
<br />
===Usage===<br />
''Derived from the post on [http://linuxpoison.blogspot.com/2010/09/utility-to-recover-deleted-files-from.html Linux Poison].''<br />
<br />
To recover data from a specific partition, the device name for the partition, which will be in the format {{ic|/dev/sdXN}} ({{ic|X}} is a letter and {{ic|N}} is a number.), must be known. The example used here is {{ic|/dev/sda4}}, but your system might use something different (For example, mmc card readers use {{ic|/dev/mmcblkNpN}} as their naming scheme.) depending on your filesystem and device configuration. If you are unsure, run {{ic|df}}, which prints currently mounted partitions.<br />
<br />
Once which partition data is to be recovered from has been determined, simply run:<br />
# extundelete /dev/sda4 --restore-file directory/file<br />
Any subdirectories must be specified, and the command runs from the highest level of the partition, so, to recover a file in {{ic|/home/SomeUserName/}}, assuming {{ic|/home}} is on its own partition, run:<br />
# extundelete /dev/sda4 restore-file <SomeUserName>/<SomeFile><br />
To speed up multi-file recovery, extundelete has a {{ic|--restore-files}} option as well.<br />
<br />
To recover an entire directory, run:<br />
# extundelete /dev/sda4 --restore-directory <SomeUserName>/<SomeDirectory><br />
<br />
For advanced users, to manually recover blocks or inodes with extundelete, debugfs can be used to find the inode to be recovered; then, run:<br />
# extundelete --restore-inode <inode><br />
"<inode>" stands for any valid inode. Additional inodes to recover can be listed in an unspaced, comma-separated fashion.<br />
<br />
Finally, to recover all deleted files from an entire partition, run:<br />
# extundelete /dev/sda4 --restore-all<br />
<br />
==Testdisk and PhotoRec==<br />
===Description===<br />
'''TestDisk''' and '''Photorec''' are both open-source data recovery utilities licensed under the terms of the [http://www.gnu.org/licenses/gpl.html GNU Public License] (GPL).<br />
<br />
'''TestDisk''' is primarily designed to help recover lost partitions and/or make non-booting disks bootable again when these symptoms are caused by faulty software, certain types of viruses, or human error, such as the accidental deletion of partition tables.<br />
<br />
'''PhotoRec''' is file recovery software designed to recover lost files including photographs (Hint: '''Photo'''graph'''Rec'''overy), videos, documents, archives from hard disks and CD-ROMs. PhotoRec ignores the filesystem and goes after the underlying data, so it will still work even with a re-formatted or severely damaged filesystems and/or partition tables.<br />
<br />
===Installation===<br />
{{Pkg|testdisk}} from the [[official repositories]] provides both '''TestDisk''' and '''PhotoRec'''.<br />
<br />
===External Links===<br />
*Wiki (TestDisk): http://www.cgsecurity.org/wiki/TestDisk<br />
*Wiki (Photorec): http://www.cgsecurity.org/wiki/PhotoRec<br />
*Homepage: http://www.cgsecurity.org/<br />
<br />
==e2fsck==<br />
===Description===<br />
'''e2fsck''' is the ext2/ext3 filesystem checker included in the base install of Arch. e2fsck relies on a valid superblock. A superblock is a description of the entire filesystem's parameters. Because this data is so important, several copies of the superblock are distributed throughout the partition. With the {{ic|-b}} option, e2fsck can take an alternate superblock argument; this is useful if the main, first superblock is damaged.<br />
<br />
To determine where the superblocks are, run {{ic|dumpe2fs -h}} on the target, unmounted partition. Superblocks are spaced differently depending on the filesystem's blocksize, which is set when the filesystem is created.<br />
<br />
An alternate method to determine the locations of superblocks is to use the -n option with mke2fs. Be '''sure''' to use the -n flag, which, according to the {{ic|mke2fs}} manpage, "''Causes mke2fs to not actually create a filesystem, but display what it would do if it were to create a filesystem. This can be used to determine the location of the backup superblocks for a particular filesystem, so long as the mke2fs parameters that were passed when the filesystem was originally created are used again. (With the -n option added, of course!)''".<br />
<br />
===Installation===<br />
Both {{Pkg|e2fsck}} and {{Pkg|dumpe2fs}} are included in the base Arch install.<br />
<br />
===External Links===<br />
*e2fsck man page: http://phpunixman.sourceforge.net/index.php/man/e2fsck/8<br />
*dumpe2fs man page: http://phpunixman.sourceforge.net/index.php?parameter=dumpe2fs&mode=man<br />
<br />
==Working with Raw Disk Images==<br />
If you have backed up a drive using ddrescue or dd and you need to mount this image as a physical drive, see this section.<br />
===Mount the Entire Disk===<br />
To mount a complete disk image to the next free loop device, use the {{ic|losetup}} command:<br />
# losetup -f -P /path/to/image<br />
{{Tip|The {{ic|-f}} flag mounts the image to the next available loop device.}}<br />
{{Tip|The {{ic|-P}} flag creates additional devices for every partition.}}<br />
===Mounting Partitions===<br />
In order to be able to mount a partiton of a whole disk image, follow [[File_Recovery#Mount_the_Entire_Disk|the steps above]].<br />
<br />
Once the whole disk image is mounted, a normal {{ic|mount}} command can be used on the loop device:<br />
# mount /dev/loop0p1 /mnt/example<br />
This command mounts the first partition of the image in loop0 to the folder to the mountpoint {{ic|/mnt/example}}. Remember that the mountpoint directory must exist!<br />
====Getting Disk Geometry====<br />
Once the entire disk image has been mounted as a loopback device, its drive layout can be inspected.<br />
===Using QEMU to Repair NTFS===<br />
With a disk image that contains one or more NTFS partitions that need to be {{ic|chkdsk}}ed by Windows since no good NTFS filesystem checker for Linux exists, QEMU can use a raw disk image as a real hard disk inside a virtual machine:<br />
# qemu -hda /path/to/primary.img -hdb /path/to/DamagedDisk.img<br />
Then, assuming Windows is installed on {{ic|primary.img}}, it can be used to check partitions on {{ic|/path/to/DamagedDisk.img}}.<br />
<br />
== Text file recovery ==<br />
It's possible to find deleted plain text on a hard drive with a few commands. A preferably unique string from the file you are trying to recover is needed.<br />
<br />
First, use the {{ic|strings}} command to dump all the text from a partition:<br />
<br />
# strings /dev/sdXN > BigStringsFile<br />
<br />
Then use {{ic|grep}} to filter through the content of {{ic|BigStringsFile}}:<br />
<br />
$ grep -i -200 "Unique string in text file" BigStringsFile > GrepOutputFile<br />
<br />
{{Note|The {{ic|-200}} option tells grep to print 200 lines of context from before and after each mach of the string. You may need to adjust this if the text you are looking for is very long.}}<br />
Hopefully, the correct deleted data is now in GrepOutputFile.<br />
<br />
==External links==<br />
*[https://help.ubuntu.com/community/DataRecovery Data Recovery] on the Ubuntu wiki</div>Catlover2https://wiki.archlinux.org/index.php?title=KDE&diff=284797KDE2013-11-27T06:32:44Z<p>Catlover2: Changed some wording, added link.</p>
<hr />
<div>[[Category:KDE]]<br />
[[cs:KDE]]<br />
[[de:KDE]]<br />
[[es:KDE]]<br />
[[fr:KDE]]<br />
[[it:KDE]]<br />
[[ja:KDE]]<br />
[[pl:KDE]]<br />
[[ru:KDE]]<br />
[[tr:KDE_Masaüstü_Ortamı]]<br />
[[zh-CN:KDE]]<br />
[[zh-TW:KDE]]<br />
{{Related articles start}}<br />
{{Related|Desktop Environment}}<br />
{{Related|Display Manager}}<br />
{{Related|Window Manager}}<br />
{{Related|Plasma}}<br />
{{Related|Qt}}<br />
{{Related|KDM}}<br />
{{Related|KDevelop 4}}<br />
{{Related|Uniform Look for Qt and GTK Applications}}<br />
{{Related articles end}}<br />
<br />
From [http://www.kde.org/community/whatiskde/softwarecompilation.php KDE Software Compilation] and [http://www.kde.org/download/ Getting KDE Software]:<br />
<br />
:''The KDE Software Compilation is the set of frameworks, workspaces, and applications produced by KDE to create a beautiful, functional and free desktop computing environment for Linux and similar operating systems. It consists of a large number of individual applications and a desktop workspace as a shell to run these applications. ''<br />
<br />
The KDE upstream has a well maintained [http://userbase.kde.org/ UserBase wiki]. Users can get detailed information about most KDE applications there.<br />
<br />
== Installation ==<br />
<br />
Before installing KDE, make sure you have a working [[Xorg]] installation on your system.<br />
<br />
KDE 4.x is ''modular''. You can install an entire set of packages or only install your preferred KDE applications.<br />
<br />
=== Full install ===<br />
<br />
[[pacman|Install]] {{Grp|kde}} or {{Grp|kde-meta}} available in the [[official repositories]]. For differences between {{Grp|kde}} and {{Grp|kde-meta}} see the [[KDE Packages]] article.<br />
<br />
=== Minimal install ===<br />
<br />
If you want to have a minimal installation of the KDE Software Compilation, install {{Grp|kdebase}}.<br />
<br />
=== Language pack ===<br />
<br />
If you need language files, install {{ic|kde-l10n-yourlanguagehere}} (e.g. {{Pkg|kde-l10n-de}} for the German language).<br />
<br />
For a full list of available languages see [https://www.archlinux.org/packages/extra/any/kde-l10n/ this link].<br />
<br />
== Upgrading ==<br />
<br />
'''KDE 4.11''' Software Compilation is the current major [http://kde.org/announcements/ release of KDE]. Important hints for upgraders:<br />
* Always check if your mirror is '''up to date'''.<br />
* '''Do not force an update using {{ic|# pacman --force}}'''. If pacman complains about conflicts please '''file a bug report'''.<br />
* You can remove the meta packages and the sub packages you do not need after the update.<br />
* If you do not like split packages just keep using the kde-meta packages.<br />
<br />
== Starting KDE ==<br />
<br />
Starting KDE depends on your preferences. Basically there are two ways of starting KDE. Using '''KDM''' or '''xinitrc'''.<br />
<br />
=== Using a Display Manager ===<br />
A [[display manager]], or login manager, is typically a graphical user interface that is displayed at the end of the boot process in place of the default shell. It allows easily logging in straight to KDE. KDE has its own display manager, KDM.<br />
<br />
==== KDM (KDE Display Manager) ====<br />
<br />
''See the [[KDM]] page for more information.''<br />
<br />
[[systemd#Using units|Enable/start]] {{ic|kdm.service}} to start the display manager.<br />
<br />
=== Using xinitrc ===<br />
<br />
''See the [[xinitrc]] page for more information.''<br />
<br />
{{hc|~/.xinitrc|<br />
exec startkde<br />
}}<br />
<br />
Execute {{ic|startx}} or {{ic|xinit}} to start KDE.<br />
<br />
{{Note|If you want to start Xorg at boot, please read the [[Start X at Login]] article.}}<br />
<br />
== Configuration ==<br />
<br />
All KDE configuration is saved in the {{ic|~/.kde4}} folder. If KDE is giving you a lot of trouble or if you ever want a fresh installation of KDE, just backup and rename this folder and restart your X session. KDE will re-create it with all the default configuration files. If you want very fine-grained control over KDE programs, you may want to edit the files in this folder.<br />
<br />
However, configuring KDE is primarily done in '''System Settings'''. A few other options for the desktop are available in '''Default Desktop Settings''' in the desktop's context menu.<br />
<br />
For other personalization options not covered below such as activities, different wallpapers on one cube, etc., please refer to the [[Plasma]] wiki page.<br />
<br />
=== Personalization ===<br />
<br />
How to set up the KDE desktop to your personal style: use different Plasma themes, window decorations and icon themes.<br />
<br />
==== Plasma desktop ====<br />
<br />
[[Plasma]] is a desktop integration technology that provides many functions like displaying the wallpaper, adding widgets to the desktop, and handling the panel(s), or "taskbar(s)".<br />
<br />
===== Themes =====<br />
<br />
[http://kde-look.org/index.php?xcontentmode=76 Plasma themes] can be installed through the Desktop Settings control panel. Plasma themes define the look of panels and plasmoids. For easy system-wide installation, some such themes are available in both the official repositories and the [https://aur.archlinux.org/packages.php?O=0&K=plasmatheme&do_Search=Go AUR].<br />
<br />
===== Widgets =====<br />
<br />
Plasmoids are little scripted (plasmoid scripts) or coded (plasmoid binaries) KDE applications designed to enhance the functionality of your desktop.<br />
<br />
Plasmoid binaries can be installed using PKGBUILDs from [https://aur.archlinux.org/packages.php?O=0&K=plasmoid&do_Search=Go&PP=25&SO=d&SB=v AUR], or you can write your own PKGBUILD.<br />
<br />
The easiest way to install plasmoid scripts is by right-clicking onto a panel or the desktop:<br />
<br />
Add Widgets > Get new Widgets > Download Widgets<br />
<br />
This will present a nice frontend for [http://www.kde-look.org/ kde-look.org] that allows you to install, uninstall, or update third-party plasmoid scripts with literally just one click.<br />
<br />
Most plasmoids are not created officially by KDE developers. You can also try installing Mac OS X widgets, Microsoft Windows Vista/7 widgets, Google Widgets, and even SuperKaramba widgets.<br />
<br />
===== Sound applet in the system tray =====<br />
<br />
Install Kmix ({{Pkg|kdemultimedia-kmix}}) from the official repositories and start it from the application launcher. Since KDE, by default, autostarts programs from the previous session, it does not need to be started manually upon every login.<br />
<br />
===== Adding a Global Menu to the desktop =====<br />
<br />
Install {{Pkg|appmenu-qt}} from the official repositories and {{aur|appmenu-gtk}} and {{aur|appmenu-qt5}} from the AUR in order to complete the preliminaries for a Mac OS X style always-on global menu. To get Firefox and LibreOffice to use the global menu as well, install {{aur|firefox-extension-globalmenu}} and {{aur|libreoffice-extension-menubar}} from the AUR.<br />
<br />
{{Warning|{{aur|firefox-extension-globalmenu}} has been deprecated as of Firefox 25 and there is no other recommended method for getting the global menu. However, there is a patched package, {{aur|firefox-ubuntu}} available in the AUR which has Canonical's patch for getting the global menu to work with the current version of Firefox (as of this writing).}}<br />
<br />
To actually get the global menu, install {{aur|kdeplasma-applets-menubar}} from the AUR. Create a plasma-panel on top of your screen and add the window menubar applet to the panel. To export the menus to your global menu, go to ''System Settings > Application Appearance > Style''. Now click the fine-tuning tab and use the drop-down list to select ''only export'' as your menubar style.<br />
<br />
==== Window decorations ====<br />
<br />
[http://kde-look.org/index.php?xcontentmode=75 Window decorations] can be changed in:<br />
System Settings > Workspace Appearance > Window Decorations<br />
There you can also directly download and install more themes with one click, and some are available in the [https://aur.archlinux.org/packages.php?O=0&K=kdestyle&do_Search=Go&PP=25&SO=d&SB=v AUR].<br />
<br />
==== Icon themes ====<br />
<br />
Not many full system icons themes are available for KDE 4. You can open up ''System Settings > Application Appearance > Icons'' and browse for new ones or install them manually. Many of them can be found on [http://www.kde-look.org/ kde-look.org].<br />
<br />
Official logos, icons, CD labels and other artwork for Arch Linux are provided in the {{AUR|archlinux-artwork}} package. After installing you can find such artwork at {{ic|/usr/share/archlinux/}}.<br />
<br />
==== Fonts ====<br />
<br />
===== Fonts in KDE look poor =====<br />
<br />
Try installing the {{Pkg|ttf-dejavu}} and {{Pkg|ttf-liberation}} packages.<br />
<br />
After the installation, be sure to log out and back in. You should not have to modify anything in ''System Settings > Fonts''.<br />
<br />
If you have personally set up how your [[Fonts]] render, be aware that System Settings may alter their appearance. When you go ''System Settings > Appearance > Fonts'', System Settings will likely alter your font configuration file ({{ic|fonts.conf}}).<br />
<br />
There is no way to prevent this, but, if you set the values to match your {{ic|fonts.conf}} file, the expected font rendering will return (it will require you to restart your application or in a few cases restart your desktop). Note that Gnome's Font Preferences also does this.<br />
<br />
===== Fonts are huge or seem disproportional =====<br />
<br />
Try to force font DPI to '''96''' in ''System Settings > Application Appearance > Fonts''.<br />
<br />
If that does not work, try setting the DPI directly in your Xorg configuration as documented [[Xorg#Setting_DPI_manually|here]].<br />
<br />
==== Space efficiency ====<br />
<br />
Users with small screens (e.g. netbooks) can change some setting to make KDE more space efficient. See the [http://userbase.kde.org/KWin#Using_with_small_screens_(eg_Netbooks) upstream wiki] for more information. Also, you can use [http://www.kde.org/workspaces/plasmanetbook/ KDE's Plasma Netbook] which is a workspace made specifically for small, lightweight netbook devices.<br />
<br />
=== Networking ===<br />
<br />
You can choose from the following tools:<br />
* NetworkManager. See [[NetworkManager#KDE4|NetworkManager]] for more information.<br />
* Wicd. See [[Wicd]] for more information.<br />
<br />
=== Printing ===<br />
<br />
{{Tip|Use the [[CUPS]] web interface for faster configuration. Printers configured in this way can be used in KDE applications. }}<br />
<br />
You can also configure printers in ''System Settings > Printer Configuration''. To use this method, you must first install {{Pkg|kdeutils-print-manager}} and {{Pkg|cups}}.<br />
<br />
The {{ic|avahi-daemon}} and {{ic|cupsd}} daemons must be started first; otherwise, you will get the following error:<br />
The service 'Printer Configuration' does not provide an interface 'KCModule'<br />
with keyword 'system-config- printer-kde/system-config-printer-kde.py'<br />
The factory does not support creating components of the specified type.<br />
<br />
If you are getting the following error, you need to give your user the right to manage printers.<br />
There was an error during CUPS operation: 'cups-authorization-canceled'<br />
<br />
For CUPS, this is set in {{ic|/etc/cups/cupsd.conf}}.<br />
<br />
Adding {{ic|lp}} to {{ic|SystemGroup}} allows anyone who can print to configure printers. You can, of course, add another group instead of {{ic|lp}}.<br />
{{hc|/etc/cups/cupsd.conf|# Administrator user group...<br />
SystemGroup sys root lp}}<br />
<br />
=== Samba/Windows support ===<br />
<br />
If you want to have access to Windows services, install [[Samba]] (package {{Pkg|samba}}).<br />
<br />
You can then configure Samba shares through:<br />
<br />
System Settings > Sharing > Samba<br />
<br />
=== KDE Desktop activities ===<br />
<br />
KDE Desktop Activities are Plasma-based virtual-desktop-like sets of Plasma Widgets where you can independently configure widgets as if you have more than one screen or desktop.<br />
<br />
On your desktop, click the Cashew Plasmoid and, on the pop-up window, press "Activities".<br />
<br />
A plasma bar presenting you the current existing Plasma Desktop Activities will appear at the bottom of the screen. You can navigate between them by pressing the correspondent icons.<br />
<br />
=== Power saving ===<br />
<br />
KDE has an integrated power saving service called "'''Powerdevil Power Management'''" that may adjust the power saving profile of the system and/or the brightness of the screen (if supported).<br />
<br />
Since KDE 4.6, CPU frequency scaling is no longer managed by KDE. Instead it is assumed to be handled automatically by the the hardware and/or kernel. Arch has used {{ic|ondemand}} as the default CPU frequency governor since kernel version 3.3, so no additional configuration in needed in most cases. For details on fine-tuning the governor, see [[CPU Frequency Scaling]].<br />
<br />
=== Monitoring changes on local files and directories ===<br />
<br />
KDE now uses '''inotify''' directly from the kernel with '''kdirwatch''' (included in kdelibs), so Gamin or FAM are no longer needed. You may want to install this {{AUR|kdirwatch}} from AUR which is a GUI frontend for kdirwatch.<br />
<br />
== System administration ==<br />
<br />
=== Set keyboard ===<br />
<br />
Navigate to:<br />
System Settings > Hardware > Input Devices > Keyboard<br />
In the first tab, you can choose your keyboard model.<br />
<br />
In the "'''Layouts'''" tab, you can choose the languages you may want to use by pressing the "Add Layout" button and subsequently choosing the variant and the language.<br />
<br />
In the "'''Advanced'''" tab, you can choose the keyboard combination you want in order to change the layouts in the "Key(s) to change layout" sub-menu.<br />
<br />
=== Terminate Xorg server through KDE system settings ===<br />
<br />
Navigate to the submenu:<br />
System Settings > Input Devices > Keyboard > Advanced (tab) > "Key Sequence to kill the X server"<br />
and tick the checkbox.<br />
<br />
=== KCM ===<br />
<br />
KCM stands for '''KC'''onfig '''M'''odule. KCMs can help you configure your system by providing interfaces in System Settings.<br />
<br />
'''Configuration for look and feel of GTK applications.'''<br />
* {{Pkg|kde-gtk-config}}<br />
* {{AUR|kcm-gtk}}<br />
* {{AUR|kcm-qt-graphicssystem}}<br />
<br />
'''Configuration for the GRUB bootloader.'''<br />
* {{AUR|grub2-editor}}<br />
* {{AUR|kcm-grub2}}<br />
<br />
'''Configuration for Synaptics touchpads.'''<br />
* {{AUR|synaptiks}}<br />
* {{AUR|kcm_touchpad}}<br />
<br />
'''Configuration for the [[Uncomplicated Firewall]] (UFW)'''<br />
* {{AUR|kcm-ufw}}<br />
<br />
'''Configuration for [[PolicyKit]]'''<br />
* {{AUR|kcm-polkit-kde-git}}<br />
<br />
'''Configuration for Wacom tablets'''<br />
* {{AUR|kcm-wacomtablet}}<br />
<br />
More KCMs can be found at [http://kde-apps.org/index.php?xcontentmode=273 kde-apps.org].<br />
<br />
== Desktop search and semantic desktop ==<br />
<br />
According to [[wikipedia:Semantic_desktop|Wikipedia]], ''"the Semantic Desktop is a collective term for ideas related to changing a computer's user interface and data handling capabilities so that data is more easily shared between different applications or tasks and so that data that once could not be automatically processed by a computer can be (automatically processed)."''<br />
<br />
The KDE implementation of this concept is tied to (as of KDE 4.10) two major pieces of software, Akonadi and Nepomuk. Between the two of them, these programs look at your data and make an easily searchable index of it. The idea behind these pieces of software is to make your system "aware" of your data and give it context using meta-data and user-supplied tags.<br />
<br />
Soprano and Virtuoso are two dependencies of the Nepomuk Semantic Desktop. Since the relationship between the two major components and their dependencies is not very clear, the following sections try to shed some light on their inner workings.<br />
<br />
=== Virtuoso and Soprano ===<br />
<br />
The database used to store all the metadata used by the semantic desktop is a ''[[wikipedia:Resource_Description_Framework|Resource Description Framework (RDF)]]'' database called Virtuoso. Internally, Virtuoso may be looked as a relational database. (A [[wikipedia:Relational_model|relational database]] is different from a traditional single-table based database in the sense that it uses multiple tables related by a single key in order to store data.) It is currently controlled by OpenLink and is available under a commercial and an open source license.<br />
<br />
From the [http://techbase.kde.org/Projects/Nepomuk/ComponentOverview#Soprano KDE Techbase], ''Soprano is a Qt abstraction over databases. It provides a friendly Qt-based API for accessing different RDF stores. It currently supports 3 database backends - Sesame, Redland and Virtuoso. The KDE Semantic Stack only works with Virtuoso. Soprano also provides additional features such as serializing, parsing RDF data, and a client server architecture that is heavily used in Nepomuk.''<br />
<br />
=== Nepomuk ===<br />
<br />
Nepomuk stands for "Networked Environment for Personal, Ontology-based Management of Unified Knowledge". It is what allows all the tagging and labeling of files as well to take place and also serves as the way to actually read the Virtuoso databases. It provides an API to application developers which allows them to read the data collected by it.<br />
<br />
In the past, the "Strigi" service was used to collect data about the various files present on the system. However, due to many reasons, the most important of them being CPU and Memory usage, Strigi was replaced by a homegrown indexing service which is integrated with Nepomuk-Core.<br />
<br />
For further information about Nepomuk, [http://techbase.kde.org/Projects/Nepomuk/ComponentOverview#Nepomuk_Components this page] is a good resource. However, some of the information in the previous page has been rendered outdated according to [http://vhanda.in/blog/2012/11/nepomuk-without-strigi/ this blog post].<br />
<br />
==== Using and configuring Nepomuk ====<br />
<br />
In order to search using Nepouk on the KDE desktop, press {{ic|ALT+F2}} and type in your query. Nepomuk is enabled by default. It can be turned on and off in:<br />
System Settings > Desktop Search<br />
<br />
Nepomuk has to keep track of a lot of files. It is for this reason that it is recommended to increase the number of files that can be watched with inotify. In order to do that this command is a good option.<br />
# sysctl fs.inotify.max_user_watches=524288<br />
<br />
To do it persistently:<br />
# echo "fs.inotify.max_user_watches = 524288" >> /etc/sysctl.d/99-inotify.conf<br />
<br />
Restart Nepomuk to see the changes.<br />
<br />
==== KDE without Nepomuk ====<br />
<br />
If you wish to run KDE without Nepomuk, there exists a {{AUR|nepomuk-core-fake}} package in the AUR.<br />
{{Warning|As of now, Dolphin depends on {{Pkg|nepomuk-widgets}} and hence will break if used with the fake Nepomuk package.}}<br />
<br />
=== Akonadi ===<br />
<br />
Akonadi is a system meant to act as a local cache for PIM data, regardless of its origin, which can be then used by other applications. This includes the user's emails, contacts, calendars, events, journals, alarms, notes, and so on. It interfaces with the Nepomuk libraries to provide searching capabilities.<br />
<br />
Akonadi does not store any data by itself: the storage format depends on the nature of the data (for example, contacts may be stored in vCard format).<br />
<br />
For more information on Akonadi and its relationship with Nepomuk, see [http://blogs.kde.org/node/4503] and [http://cmollekopf.wordpress.com/2013/02/13/kontact-nepomuk-integration-why-data-from-akonadi-is-indexed-in-nepomuk/].<br />
<br />
==== Disabling Akonadi ====<br />
<br />
See this [http://userbase.kde.org/Akonadi#Disabling_the_Akonadi_subsystem section in the KDE userbase].<br />
<br />
==== Database configuration ====<br />
<br />
Start {{ic|akonaditray}} from package {{Pkg|kdepim-runtime}}. Right click on it and select '''configure'''. In the Akonadi server configure tab, you can:<br />
* Configuring Akonadi to use MySQL/MariaDB Server<br />
* Configuring Akonadi to use PostgreSQL Server<br />
* Configuring Akonadi to use SQLite<br />
<br />
==== Running KDE without Akonadi ====<br />
<br />
The package {{AUR|akonadi-fake}} is a good option for those who wish to run KDE without Akonadi.<br />
<br />
== Phonon ==<br />
<br />
=== What is Phonon? ===<br />
<br />
From [[Wikipedia:Phonon|Wikipedia]]:<br />
''Phonon is the multimedia API for KDE 4. Phonon was created to allow KDE 4 to be independent of any single multimedia framework such as GStreamer or xine and to provide a stable API for KDE 4's lifetime. It was done for various reasons: to create a simple KDE/Qt style multimedia API, to better support native multimedia frameworks on Windows and Mac OS X, and to fix problems of frameworks becoming unmaintained or having API or ABI instability.<br />
''<br />
<br />
'''Phonon''' is being widely used within KDE, for both audio (e.g., the System notifications or KDE audio apps) and video (e.g., the Dolphin video thumbnails).<br />
<br />
=== Which backend should I choose? ===<br />
<br />
You can choose between various backends like GStreamer ({{Pkg|phonon-gstreamer}}) or VLC ({{Pkg|phonon-vlc}}), available in the [[official repositories]], and MPlayer ({{AUR|phonon-mplayer-git}}), ({{AUR|phonon-quicktime-git}}), and ({{AUR|phonon-avkode-git}}); available in the [[AUR]]. Most users will want GStreamer or VLC which have the best upstream support. Note that multiple backends can be installed at once and chosen at ''System Settings > Multimedia > Phonon > Backend''.<br />
<br />
{{Note|According to the [http://userbase.kde.org/Phonon#Backend_libraries KDE UserBase], Phonon-MPlayer is currently unmaintained}}<br />
<br />
According to [http://lists.kde.org/?l=kde-multimedia&m=137994906723790&w=2 this mail in the KDE-Multimedia mailing list], users should prefer VLC over GStreamer.<br />
<br />
== Useful applications ==<br />
<br />
The official set of KDE applications may be found [http://www.kde.org/applications/ here].<br />
<br />
=== Yakuake ===<br />
<br />
[http://yakuake.kde.org/ Yakuake] provides a Quake-like terminal emulator whose visibility is toggled by the F12 key. It also has support for multiple tabs. Yakuake is available in the package {{Pkg|yakuake}}.<br />
<br />
=== KDE Telepathy ===<br />
<br />
[http://community.kde.org/KTp KDE Telepathy] is a project with the goal to closely integrate Instant Messaging with the KDE desktop. It utilizes the Telepathy framework as a backend and is intended to replace Kopete.<br />
<br />
To install all Telepathy protocols, install the {{Grp|telepathy}} group.<br />
To use the KDE Telepathy client, install the {{Pkg|kde-telepathy-meta}} package that includes all the packages contained in the {{Grp|kde-telepathy}} group .<br />
<br />
== Tips and tricks ==<br />
<br />
=== Integrate Android with the KDE Desktop ===<br />
<br />
Install {{AUR|kdeconnect}} from the AUR and [https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp&hl=en KDE Connect] from the Google Play store for great Android-KDE integration.<br />
<br />
=== Get notifications for software updates ===<br />
<br />
Install {{Pkg|apper}} to get notifications about package updates in your KDE system tray and a basic package manager GUI. See the [http://www.packagekit.org/index.html PackageKit website] for more information.<br />
<br />
=== Configure KWin to use OpenGL ES ===<br />
<br />
Beginning with KWin version 4.8 it is possible to use the separately built binary '''kwin_gles''' as a replacement for kwin. It behaves almost the same as the kwin executable in OpenGL2 mode with the slight difference that it uses ''egl'' instead of ''glx'' as the native platform interface. To test kwin_gles you just have to run {{ic|kwin_gles --replace}} in Konsole.<br />
If you want to make this change permanent you have to create a script in {{ic|$(kde4-config --localprefix)/env/}} which exports {{ic|1=KDEWM=kwin_gles}}.<br />
<br />
=== Enabling audio thumbnails under Konqueror/Dolphin file managers ===<br />
<br />
For thumbnails of audio files in Konqueror and Dolphin install {{AUR|audiothumbs}} from AUR.<br />
<br />
=== Enabling video thumbnails under Konqueror/Dolphin file managers ===<br />
<br />
For thumbnails of videos in konqueror and dolphin install {{Pkg|kdemultimedia-mplayerthumbs}} or {{Pkg|kdemultimedia-ffmpegthumbs}}.<br />
<br />
=== Speed up application startup ===<br />
<br />
User Rob wrote on his blog this "[http://kdemonkey.blogspot.nl/2008/04/magic-trick.html magic trick]" to improve application start-up time by 50-150ms.<br />
To enable it, create this folder in your home:<br />
$ mkdir -p ~/.compose-cache/<br />
<br />
{{Note|For those curious about what is going on here, this enables an optimization which Lubos (of general KDE speediness fame) came up with some time ago and was then rewritten and integrated into libx11. Ordinarily, on startup, applications read input method information from {{ic|/usr/share/X11/locale/''your locale''/Compose}}. This file is quite long (>5000 lines for the en_US.UTF-8 one) and takes some time to process. libX11 can create a cache of the parsed information which is much quicker to read subsequently, but it will only re-use an existing cache or create a new one in {{ic|~/.compose-cache}} if the directory already exists.}}<br />
<br />
=== Hiding partitions ===<br />
<br />
In Dolphin, it is as simple as right-clicking on the partition in the {{ic|Places}} sidebar and selecting {{ic|Hide ''partition''}}. Otherwise...<br />
<br />
If you wish to prevent your internal partitions from appearing in your file manager, you can create an udev rule, e.g:<br />
<br />
{{hc|/etc/udev/rules.d/10-local.rules|2=<br />
KERNEL=="sda[0-9]", ENV{UDISKS_IGNORE}="1"<br />
}}<br />
<br />
The same thing for a certain partition:<br />
<br />
KERNEL=="sda1", ENV{UDISKS_IGNORE}="1"<br />
KERNEL=="sda2", ENV{UDISKS_IGNORE}="1"<br />
<br />
=== Konqueror tips ===<br />
<br />
==== Disabling smart key tooltips (browser) ====<br />
<br />
To disable those smart key tooltips in Konqueror (pressing {{ic|Ctrl}} on a web page), use ''Settings > Configure Konqueror > Web Browsing'' and uncheck ''Enable Access Key activation with Ctrl key'' o<br />
<br />
{{hc|~/.kde4/share/config/konquerorrc|2=<br />
[Access Keys]<br />
Enabled=false<br />
}}<br />
<br />
==== Using WebKit ====<br />
<br />
WebKit is an open source browser engine developed by Apple Inc. It is a derivative from the KHTML and KJS libraries and contains many improvements. WebKit is used by Safari, Google Chrome and rekonq.<br />
<br />
It is possible to use WebKit in Konqueror instead of KHTML. First install the {{Pkg|kwebkitpart}} package.<br />
<br />
Then, after executing Konqueror, navigate to ''Settings > Configure Konqueror > General > Default web browser engine'' and set it as {{ic|WebKit}}.<br />
<br />
=== Firefox integration ===<br />
<br />
See [[Firefox#KDE_integration|Firefox]].<br />
<br />
=== Setting the screensaver background to the same as the current one ===<br />
<br />
Kscreensaver's background can be changed from the default.<br />
<br />
KDE by default is [https://bugs.kde.org/show_bug.cgi?id=312828 not able] to change this for the 'Simple Lock', but a [http://lists.opensuse.org/opensuse-kde/2013-02/msg00082.html workaround] [http://forum.kde.org/viewtopic.php?f=66&t=110039 exists]:<br />
<br />
{{hc|/usr/share/apps/ksmserver/screenlocker/org.kde.passworddialog/contents/ui/|<br />
[...]<br />
''#source: theme.wallpaperPathForSize(parent.width, parent.height)''<br />
source: "1920x1080.jpg"<br />
[...]<br />
}}<br />
<br />
Now you copy your current background image to {{ic|"1920x1080.jpg"}}.<br />
<br />
Note you have to redo this for each update of the package {{Pkg|kdebase-workspace}}.<br />
<br />
=== Setting lockscreen wallpaper to arbitrary image ===<br />
<br />
Copy an existing wallpaper profile as a template:<br />
$ cp -r /usr/share/wallpapers/''ExistingWallpaper'' ~/.kde4/share/wallpapers/<br />
<br />
Change the name of the directory, and edit {{ic|metadata.desktop}}:<br />
<br />
{{hc|~/.kde4/share/wallpapers/''MyWallpaper''/metadata.desktop|2=<br />
[Desktop Entry]<br />
Name=MyWallpaper<br />
X-KDE-PluginInfo-Name=MyWallpaper<br />
}}<br />
<br />
Remove existing images ({{ic|contents/screenshot.png}} and {{ic|images/*}}):<br />
$ rm ~/.kde4/share/wallpapers/MyWallpaper/contents/screenshot.png<br />
$ rm ~/.kde4/share/wallpapers/MyWallpaper/contents/images/*<br />
<br />
Copy new image in:<br />
$ cp ''path/to/MyWallpaper.png'' MyWallpaper/contents/images/1920x1080.png<br />
<br />
Edit the metadata profile for the current theme:<br />
{{hc|~/.kde4/share/apps/desktoptheme/MyTheme/metadata.desktop|2=<br />
[Wallpaper]<br />
defaultWallpaperTheme=NewWallpaper<br />
defaultFileSuffix=.png<br />
defaultWidth=1920<br />
defaultHeight=1080<br />
}}<br />
<br />
Lock the screen to check that it worked.<br />
<br />
{{Note|This method sets the lockscreen background without changing any system-wide settings. For a system-wide change, create the new wallpaper profile in {{ic|/usr/share/wallpapers}}.}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Configuration related ===<br />
<br />
Many issues in KDE are related to configuration. One way to resolve upgrade problems is to start over with a fresh KDE config.<br />
<br />
==== Reset all KDE configuration ====<br />
<br />
To test whether your config is the problem try quitting your KDE session by logging out and, in a tty, run<br />
$ cp ~/.kde4 ~/.kde4.safekeeping<br />
$ rm .kde4/{cache,socket,tmp}-$(hostname)<br />
<br />
The ''rm'' command just removes symbolic links which will be recreated by KDE automatically. Now start a new KDE session to see the results.<br />
<br />
If the problem is resolved, you will have a fresh, problem-free {{ic|~/.kde4/}}. You can gradually move parts of your saved configuration back, restarting your session regularly to test, to identify the problematic parts of your config. Some files here are named after applications so you will probably be able to test these without needing to restart KDE.<br />
<br />
==== File Indexer Service not working even after enabling everything properly ====<br />
<br />
This is caused due to a corrupted Nepomuk database. It may be remedied by moving the database or deleting it all together. Log out of KDE and issue this command from a virtual console:<br />
<br />
$ mv ~/.kde4/share/apps/nepomuk ~/.kde4/share/apps/nepomuk_backup<br />
<br />
to move your existing (and corrupt) nepomuk database. It will be recreated when you log in again.<br />
<br />
==== Plasma desktop behaves strangely ====<br />
<br />
Plasma issues are usually caused by unstable '''plasmoids''' or '''plasma themes'''. First, find which was the last plasmoid or plasma theme you had installed and disable it or uninstall it.<br />
<br />
So, if your desktop suddenly exhibits "locking up", this is likely caused by a faulty installed widget. If you cannot remember which widget you installed before the problem began (sometimes it can be an irregular problem), try to track it down by removing each widget until the problem ceases. Then you can uninstall the widget, and file a bug report (bugs.kde.org) '''only if it is an official widget'''. If it is not, it is recommended you find the entry on kde-look.org and inform the developer of that widget about the issue (detailing steps to reproduce, etc).<br />
<br />
If you cannot find the problem, but you do not want ''all'' the KDE settings to be lost, do:<br />
<br />
$ rm -r ~/.kde4/share/config/plasma*<br />
<br />
This command will '''delete all plasma related configs''' of your user and when you will relogin into KDE, you will have the '''default''' settings back. You should know that this action '''cannot be undone'''. You should create a backup folder and copy all the plasma related configs in it.<br />
<br />
==== Clean cache to resolve upgrade problems ====<br />
<br />
The [https://bbs.archlinux.org/viewtopic.php?id=135301 problem] may be caused by old cache. Sometimes after an upgrade, the old cache might introduce strange, hard to debug behaviour such as unkillable shells, hangs when changing various settings and several other problems such as ark being unable to unrar or unzip or amarok not recognizing any of your musics. This solution can also resolve problems with KDE and QT programmes looking bad following upgrade.<br />
<br />
Rebuild your cache with the following commands:<br />
<br />
$ rm ~/.config/Trolltech.conf<br />
$ kbuildsycoca4 --noincremental<br />
<br />
Hopefully, your problems are now fixed.<br />
<br />
=== Clean akonadi configuration to fix KMail ===<br />
<br />
First, make sure that KMail is not running. Then backup configuration:<br />
$ mv ~/.local/share/akonadi ~/.local/share/akonadi-old<br />
$ mv ~/.config/akonadi ~/.config/akonadi-old<br />
<br />
Start ''SystemSettings > Personal'' and remove all the resources. Go back to Dolphin and remove the original {{ic|~/.local/share/akonadi}} and<br />
{{ic|~/.config/akonadi}} - the copies you made ensure that you can back-track if necessary.<br />
<br />
Now go back to the System Settings page and carefully add the necessary resources. You should see the resource reading in your mail folders. Then start Kontact/KMail to see if it work properly.<br />
<br />
=== Getting current state of KWin for support and debug purposes ===<br />
<br />
This command prints out a wonderful summary of the current state of KWin including used options, used compositing backend and relevant OpenGL driver capabilities. See more on [http://blog.martin-graesslin.com/blog/2012/03/on-getting-help-for-kwin-and-helping-kwin/ Martin's blog].<br />
<br />
$ qdbus org.kde.kwin /KWin supportInformation<br />
<br />
=== KDE4 does not finish loading ===<br />
<br />
There might be a situation in which the graphic driver might create a conflict when starting KDE4. This situation happens after the login but before finishing loading the desktop, making the user wait indefinitely at the loading screen. Until now the only users confirmed to be affected by this are the ones that use [[NVIDIA|Nvidia drivers]] and KDE4.<br />
<br />
A solution for Nvidia users:<br />
<br />
{{hc|~/.kde4/share/config/kwinrc|2=<br />
[Compositing]<br />
Enabled=false<br />
}}<br />
For more information, see [https://bbs.archlinux.org/viewtopic.php?pid=932598 this] thread.<br />
<br />
If a minimal install was done, make sure you installed the required font by your phonon backend listed here: [[#Minimal install]]<br />
<br />
=== KDE and Qt programs look bad when in a different window manager ===<br />
<br />
If you are using KDE or Qt programs but not in a full KDE session (specifically, you did not run {{ic|startkde}}), then as of KDE 4.6.1 you will need to tell Qt how to find KDE's styles (Oxygen, QtCurve etc.)<br />
<br />
You just need to set the environment variable {{ic|QT_PLUGIN_PATH}}. E.g. put:<br />
<br />
export QT_PLUGIN_PATH=$HOME/.kde4/lib/kde4/plugins/:/usr/lib/kde4/plugins/<br />
<br />
into your {{ic|/etc/profile}} (or {{ic|~/.profile}} if you do not have root access). qtconfig should then be able to find your KDE styles and everything should look nice again!<br />
<br />
Alternatively, you can symlink the Qt styles directory to the KDE styles one:<br />
# ln -s /usr/lib/kde4/plugins/styles/ /usr/lib/qt/plugins/styles<br />
<br />
Under Gnome you can try to install the package libgnomeui.<br />
<br />
=== Graphical related issues ===<br />
<br />
==== Low 2D desktop performance (or) artifacts appear when on 2D ====<br />
<br />
===== GPU driver problem =====<br />
<br />
Make sure you have the proper driver for your card installed, so that your desktop is at least 2D accelerated. Follow these articles for more information: [[ATI]], [[NVIDIA]], [[Intel]] for more information, in order to make sure that everything is all right.<br />
The open-source ATI and Intel drivers and the proprietary (binary) Nvidia driver should theoretically provide the best 2D and 3D acceleration.<br />
<br />
===== The Raster engine workaround =====<br />
<br />
If this does not solve your problems, your driver may not provide a good '''XRender''' acceleration which the current Qt painter engine relies on by default.<br />
<br />
You can change the painter engine to software based only by invoking the application with the {{ic|-graphicssystem raster}} command line. This rendering engine can be set as the default one by recompiling Qt with the same as configure option, {{ic|-graphicssystem raster}}.<br />
<br />
The raster paint engine enables the CPU to do the majority of the painting, as opposed to the GPU. You may get better performance, depending on your system. This is basically a work-around for the terrible Linux driver stack, since the CPU should obviously not be doing graphical computations since it is designed for fewer threads of greater complexity, as opposed to the GPU which is many threads but lesser computational strength. So, only use Raster engine if you are having problems or your GPU is much slower than you CPU, otherwise is better to use XRender.<br />
<br />
Since Qt 4.7+, recompiling Qt is not needed. Simply export {{ic|1=QT_GRAPHICSSYSTEM=raster}}, or {{ic|opengl}}, or {{ic|native}} (for the default). Raster depends on the CPU, OpenGL depends on the GPU and high driver support, and Native is just using the X11 rendering (mixture, usually).<br />
<br />
'''The best and automatic way to do that''' is to install {{AUR|kcm-qt-graphicssystem}} from AUR and configure this particular Qt setting through:<br />
<br />
System Settings > Qt Graphics System<br />
<br />
For more information, consult this [http://apachelog.wordpress.com/2010/09/05/qt-graphics-system-kcm/ KDE Developer blog entry] and/or this [http://labs.trolltech.com/blogs/2009/12/18/qt-graphics-and-performance-the-raster-engine/ Qt Developer blog entry].<br />
<br />
==== Low 3D desktop performance====<br />
<br />
KDE begins with desktop effects enabled. Older cards may be insufficient for 3D desktop acceleration. You can disable desktop effects in:<br />
System Settings > Desktop Effects<br />
and you can toggle desktop effects with {{ic|Alt+Shift+F12}}.<br />
<br />
{{Note| You may encounter such problems with 3D desktop performance even when using a more powerful graphics card, especially the catalyst proprietary driver ({{ic|fglrx}}). This driver is known for having issues with 3D acceleration. Visit [[ATI|the ATI Wiki page]] for more troubleshooting.}}<br />
<br />
==== Desktop compositing is disabled on my system with a modern Nvidia GPU ====<br />
<br />
Sometimes, KWin may have settings in its configuration file ({{ic|kwinrc}}) that ''may'' cause a problem on re-activating the 3D desktop {{ic|OpenGL}} compositing. That could be caused randomly (for example, due to a sudden Xorg crash or restart, and it gets corrupted), so, in case that happens, delete your {{ic|~/.kde4/share/config/kwinrc}} file and relogin. The KWin settings will turn to the KDE default ones and the problem should be probably gone.<br />
<br />
==== Flickering in fullscreen when compositing is enabled ====<br />
<br />
As of KDE SC 4.6.0, there is an option in ''Sytem Settings > Desktop Effect > Advanced > Suspend desktop effects for fullscreen windows''. Uncheck it would tell kwin to disable unredirect fullscren.<br />
<br />
==== Screen Tearing with desktop compositing enabled ====<br />
<br />
{{Note|With the recent update of KDE to 4.11, several new Vsync options have been added, which may help with screen tearing.}}<br />
<br />
KWin may suffer from screen tearing while desktop effects are enabled. Uncheck the VSync option under ''System Settings > Desktop Effects > Advanced > Use Vsync''.<br />
<br />
For proprietary driver users, ensure that the driver's VSync option is enabled ({{ic|amdccle}} for [[Catalyst]] users, and nvidia-settings for [[NVIDIA]] users).<br />
<br />
==== Display settings lost on reboot (multiple monitors) ====<br />
Installing {{Pkg|kscreen}} might fix the problem unless your screens share the same EDID. Kscreen is the improved screen management software for KDE, more information can be found [https://fedoraproject.org/wiki/Changes/KScreen?rd=Features/KScreen here].<br />
<br />
=== Sound problems under KDE ===<br />
<br />
==== ALSA related problems ====<br />
<br />
{{Note|First make sure you have {{Pkg|alsa-lib}} and {{Pkg|alsa-utils}} installed.}}<br />
<br />
===== "Falling back to default" messages when trying to listen to any sound in KDE =====<br />
<br />
When you encounter such messages:<br />
The audio playback device ''name_of_the_sound_device'' does not work.<br />
Falling back to default<br />
Go to:<br />
System Settings > Multimedia > Phonon<br />
and set the device named {{ic|default}} above all the other devices in each box you see.<br />
<br />
===== MP3 files cannot be played when using the GStreamer Phonon backend =====<br />
<br />
This can be solved by installing the GStreamer plugins (package group {{Grp|gstreamer0.10-plugins}}). If you still encounter problems, you can try changing the Phonon backend used by installing another such as {{Pkg|phonon-vlc}}.<br />
Then, make sure the backend is preferred via:<br />
<br />
System Settings > Multimedia > Phonon > Backend (tab)<br />
<br />
=== Konsole does not save commands' history ===<br />
<br />
By default console command history is saved only when you type 'exit' in console. When you close Konsole with 'x' in the corner it does not happen.<br />
To enable autosaving after every command execution:<br />
<br />
{{hc|~/.bashrc|<nowiki><br />
shopt -s histappend<br />
[[ "${PROMPT_COMMAND}" ]] && PROMPT_COMMAND="$PROMPT_COMMAND;history -a" || PROMPT_COMMAND="history -a"<br />
</nowiki>}}<br />
<br />
=== KDE password prompts display three bullets per char ===<br />
<br />
This setting can be changed at ''System Settings > Account Details > Password & User Account'':<br />
* Show one bullet for each letter<br />
* Show three bullets for each letter<br />
* Show nothing<br />
<br />
=== Nepomukserver process still autostarts even with semantic desktop disabled ===<br />
<br />
Go to ''System Settings > Startup and Shutdown > Service Manager > Startup Services'' and uncheck the Nepomuk Search Module.<br />
<br />
=== Dolphin and File Dialogs are extremely slow to start ===<br />
<br />
This may be caused by the upower service. If the upower service is not needed on your system, it can be disabled:<br />
<br />
# systemctl disable upower<br />
# systemctl mask upower<br />
<br />
Obviously this will not have any side effect on a desktop system.<br />
<br />
=== Default PDF viewer in GTK applications under KDE ===<br />
<br />
In some cases when you have installed [[Inkscape]], [[Gimp]] or other graphic programs, GTK applications ([[Firefox]] among all) might not select Okular as the default PDF application, and they are not going to follow the KDE settings on default applications. You can use the following user command to make Okular the default application again.<br />
<br />
$ xdg-mime default kde4-okularApplication_pdf.desktop application/pdf<br />
<br />
If you are using a different PDF viewer application, or a different mime-type is misbehaving, you should change {{ic|kde4-okularApplication_pdf.desktop}} and {{ic|application/pdf}} respectively according to your needs.<br />
<br />
For more information, consult [[Default Applications]] wiki page.<br />
<br />
== Unstable releases ==<br />
<br />
When KDE is reaching beta or RC milestone, KDE "unstable" packages are uploaded to the [kde-unstable] repository. They stay there until KDE is declared stable and passes to [extra].<br />
<br />
You can add [kde-unstable] with:<br />
<br />
{{hc|/etc/pacman.conf|2=<br />
[kde-unstable]<br />
Include = /etc/pacman.d/mirrorlist<br />
}}<br />
<br />
# [kde-unstable] is based upon testing. Therefore, you need to enable the repositories in the following order: [kde-unstable], [testing], [core], [extra], [community-testing], [community].<br />
# To update from a previous KDE installation, run: {{ic|# pacman -Syu}} or {{ic|# pacman -S kde-unstable/kde}}<br />
# If you do not have KDE installed, you might have difficulties to install it by using groups (limitation of pacman)<br />
# '''Subscribe and read the [https://mailman.archlinux.org/pipermail/arch-dev-public/ arch-dev-public] mailing list'''<br />
# Make sure [[#Distro_and_Upstream_bug_report|you make bug reports]] if you find any issues.<br />
<br />
== Other KDE projects ==<br />
<br />
=== Trinity ===<br />
<br />
From the release of KDE 4.x, the developers dropped support for KDE 3.5.x. Trinity Desktop Environment is a fork of KDE3 developed by Timothy Pearson ([http://trinitydesktop.org/ trinitydesktop.org]). This project aims 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. See [[Trinity]] for more info.<br />
<br />
{{Warning|KDE 3 is no longer maintained and supported by the KDE developers. The "Trinity KDE" is maintained by the Trinity project commmunity. Use KDE 3 on your own risk, regarding any bugs, performance issues or security risks.}}<br />
<br />
== Bugs ==<br />
<br />
It is preferrable that if you find a minor or serious bug, you should visit [https://bugs.archlinux.org the Arch Bug Tracker] or/and [http://bugs.kde.org KDE Bug Tracker] in order to report that. Make sure that you are clear about what you want to report.<br />
<br />
If you have any issue and you write about in on the Arch forums, first make sure that you have '''fully''' updated your system using a good sync mirror (check [https://www.archlinux.de/?page=MirrorStatus here]) or try [[Reflector]].<br />
<br />
== See also ==<br />
<br />
* [http://www.kde.org] - KDE homepage<br />
* [https://bugs.kde.org] - KDE bug tracker<br />
* [https://bugs.archlinux.org] - Arch Linux bug tracker<br />
* [https://projects.kde.org] - KDE Projects</div>Catlover2https://wiki.archlinux.org/index.php?title=KDE&diff=284667KDE2013-11-26T06:44:18Z<p>Catlover2: Generally cleaned up article: improved grammar, clarified and reworded, removed stray spaces, and such.</p>
<hr />
<div>[[Category:KDE]]<br />
[[cs:KDE]]<br />
[[de:KDE]]<br />
[[es:KDE]]<br />
[[fr:KDE]]<br />
[[it:KDE]]<br />
[[ja:KDE]]<br />
[[pl:KDE]]<br />
[[ru:KDE]]<br />
[[tr:KDE_Masaüstü_Ortamı]]<br />
[[zh-CN:KDE]]<br />
[[zh-TW:KDE]]<br />
{{Related articles start}}<br />
{{Related|Desktop Environment}}<br />
{{Related|Display Manager}}<br />
{{Related|Window Manager}}<br />
{{Related|Plasma}}<br />
{{Related|Qt}}<br />
{{Related|KDM}}<br />
{{Related|KDevelop 4}}<br />
{{Related|Uniform Look for Qt and GTK Applications}}<br />
{{Related articles end}}<br />
<br />
From [http://www.kde.org/community/whatiskde/softwarecompilation.php KDE Software Compilation] and [http://www.kde.org/download/ Getting KDE Software]:<br />
<br />
:''The KDE Software Compilation is the set of frameworks, workspaces, and applications produced by KDE to create a beautiful, functional and free desktop computing environment for Linux and similar operating systems. It consists of a large number of individual applications and a desktop workspace as a shell to run these applications. ''<br />
<br />
The KDE upstream has a well maintained [http://userbase.kde.org/ UserBase wiki]. Users can get detailed information about most KDE applications there.<br />
<br />
== Installation ==<br />
<br />
Before installing KDE, make sure you have a working [[Xorg]] installation on your system.<br />
<br />
KDE 4.x is ''modular''. You can install an entire set of packages or only install your preferred KDE applications.<br />
<br />
=== Full install ===<br />
<br />
[[pacman|Install]] {{Grp|kde}} or {{Grp|kde-meta}} available in the [[official repositories]]. For differences between {{Grp|kde}} and {{Grp|kde-meta}} see the [[KDE Packages]] article.<br />
<br />
=== Minimal install ===<br />
<br />
If you want to have a minimal installation of the KDE Software Compilation, install {{Grp|kdebase}}.<br />
<br />
=== Language pack ===<br />
<br />
If you need language files, install {{ic|kde-l10n-yourlanguagehere}} (e.g. {{Pkg|kde-l10n-de}} for the German language).<br />
<br />
For a full list of available languages see [https://www.archlinux.org/packages/extra/any/kde-l10n/ this link].<br />
<br />
== Upgrading ==<br />
<br />
'''KDE 4.11''' Software Compilation is the current major [http://kde.org/announcements/ release of KDE]. Important hints for upgraders:<br />
* Always check if your mirror is '''up to date'''.<br />
* '''Do not force an update using {{ic|# pacman --force}}'''. If pacman complains about conflicts please '''file a bug report'''.<br />
* You can remove the meta packages and the sub packages you do not need after the update.<br />
* If you do not like split packages just keep using the kde-meta packages.<br />
<br />
== Starting KDE ==<br />
<br />
Starting KDE depends on your preferences. Basically there are two ways of starting KDE. Using '''KDM''' or '''xinitrc'''.<br />
<br />
=== Using a Display Manager ===<br />
A [[display manager]], or login manager, is typically a graphical user interface that is displayed at the end of the boot process in place of the default shell. It allows easily logging in straight to KDE. KDE has its own display manager, KDM.<br />
<br />
==== KDM (KDE Display Manager) ====<br />
<br />
''See the [[KDM]] page for more information.''<br />
<br />
[[systemd#Using units|Enable/start]] {{ic|kdm.service}} to start the display manager.<br />
<br />
=== Using xinitrc ===<br />
<br />
''See the [[xinitrc]] page for more information.''<br />
<br />
{{hc|~/.xinitrc|<br />
exec startkde<br />
}}<br />
<br />
Execute {{ic|startx}} or {{ic|xinit}} to start KDE.<br />
<br />
{{Note|If you want to start Xorg at boot, please read the [[Start X at Login]] article.}}<br />
<br />
== Configuration ==<br />
<br />
All KDE configuration is saved in the {{ic|~/.kde4}} folder. If KDE is giving you a lot of trouble or if you ever want a fresh installation of KDE, just backup and rename this folder and restart your X session. KDE will re-create it with all the default configuration files. If you want very fine-grained control over KDE programs, you may want to edit the files in this folder.<br />
<br />
However, configuring KDE is primarily done in '''System Settings'''. A few other options for the desktop are available in '''Default Desktop Settings''' in the desktop's context menu.<br />
<br />
For other personalization options not covered below such as activities, different wallpapers on one cube, etc., please refer to the [[Plasma]] wiki page.<br />
<br />
=== Personalization ===<br />
<br />
How to set up the KDE desktop to your personal style: use different Plasma themes, window decorations and icon themes.<br />
<br />
==== Plasma desktop ====<br />
<br />
[[Plasma]] is a desktop integration technology that provides many functions like displaying the wallpaper, adding widgets to the desktop, and handling the panel(s), or "taskbar(s)".<br />
<br />
===== Themes =====<br />
<br />
[http://kde-look.org/index.php?xcontentmode=76 Plasma themes] can be installed through the Desktop Settings control panel. Plasma themes define the look of panels and plasmoids. For easy system-wide installation, some such themes are available in both the official repositories and the [https://aur.archlinux.org/packages.php?O=0&K=plasmatheme&do_Search=Go AUR].<br />
<br />
===== Widgets =====<br />
<br />
Plasmoids are little scripted (plasmoid scripts) or coded (plasmoid binaries) KDE applications designed to enhance the functionality of your desktop.<br />
<br />
Plasmoid binaries can be installed using PKGBUILDs from [https://aur.archlinux.org/packages.php?O=0&K=plasmoid&do_Search=Go&PP=25&SO=d&SB=v AUR], or you can write your own PKGBUILD.<br />
<br />
The easiest way to install plasmoid scripts is by right-clicking onto a panel or the desktop:<br />
<br />
Add Widgets > Get new Widgets > Download Widgets<br />
<br />
This will present a nice frontend for [http://www.kde-look.org/ kde-look.org] that allows you to install, uninstall, or update third-party plasmoid scripts with literally just one click.<br />
<br />
Most plasmoids are not created officially by KDE developers. You can also try installing Mac OS X widgets, Microsoft Windows Vista/7 widgets, Google Widgets, and even SuperKaramba widgets.<br />
<br />
===== Sound applet in the system tray =====<br />
<br />
Install Kmix ({{Pkg|kdemultimedia-kmix}}) from the official repositories and start it from the application launcher. Since KDE, by default, autostarts programs from the previous session, it does not need to be started manually upon every login.<br />
<br />
===== Adding a Global Menu to the desktop =====<br />
<br />
Install {{Pkg|appmenu-qt}} from the official repositories and {{aur|appmenu-gtk}} and {{aur|appmenu-qt5}} from the AUR in order to complete the preliminaries for a Mac OS X style always-on global menu. To get Firefox and LibreOffice to use the global menu as well, install {{aur|firefox-extension-globalmenu}} and {{aur|libreoffice-extension-menubar}} from the AUR.<br />
<br />
{{Warning|{{aur|firefox-extension-globalmenu}} has been deprecated as of Firefox 25 and there is no other recommended method for getting the global menu. However, there is a patched package, {{aur|firefox-ubuntu}} available in the AUR which has Canonical's patch for getting the global menu to work with the current version of Firefox (as of this writing).}}<br />
<br />
To actually get the global menu, install {{aur|kdeplasma-applets-menubar}} from the AUR. Create a plasma-panel on top of your screen and add the window menubar applet to the panel. To export the menus to your global menu, go to ''System Settings > Application Appearance > Style''. Now click the fine-tuning tab and use the drop-down list to select ''only export'' as your menubar style.<br />
<br />
==== Window decorations ====<br />
<br />
[http://kde-look.org/index.php?xcontentmode=75 Window decorations] can be changed in:<br />
System Settings > Workspace Appearance > Window Decorations<br />
There you can also directly download and install more themes with one click, and some are available in the [https://aur.archlinux.org/packages.php?O=0&K=kdestyle&do_Search=Go&PP=25&SO=d&SB=v AUR].<br />
<br />
==== Icon themes ====<br />
<br />
Not many full system icons themes are available for KDE 4. You can open up ''System Settings > Application Appearance > Icons'' and browse for new ones or install them manually. Many of them can be found on [http://www.kde-look.org/ kde-look.org].<br />
<br />
Official logos, icons, CD labels and other artwork for Arch Linux are provided in the {{AUR|archlinux-artwork}} package. After installing you can find such artwork at {{ic|/usr/share/archlinux/}}.<br />
<br />
==== Fonts ====<br />
<br />
===== Fonts in KDE look poor =====<br />
<br />
Try installing the {{Pkg|ttf-dejavu}} and {{Pkg|ttf-liberation}} packages.<br />
<br />
After the installation, be sure to log out and back in. You should not have to modify anything in ''System Settings > Fonts''.<br />
<br />
If you have personally set up how your [[Fonts]] render, be aware that System Settings may alter their appearance. When you go ''System Settings > Appearance > Fonts'', System Settings will likely alter your font configuration file ({{ic|fonts.conf}}).<br />
<br />
There is no way to prevent this, but, if you set the values to match your {{ic|fonts.conf}} file, the expected font rendering will return (it will require you to restart your application or in a few cases restart your desktop). Note that Gnome's Font Preferences also does this.<br />
<br />
===== Fonts are huge or seem disproportional =====<br />
<br />
Try to force font DPI to '''96''' in ''System Settings > Application Appearance > Fonts''.<br />
<br />
If that does not work, try setting the DPI directly in your Xorg configuration as documented [[Xorg#Setting_DPI_manually|here]].<br />
<br />
==== Space efficiency ====<br />
<br />
Users with small screens (e.g. netbooks) can change some setting to make KDE more space efficient. See the [http://userbase.kde.org/KWin#Using_with_small_screens_(eg_Netbooks) upstream wiki] for more information. Also, you can use [http://www.kde.org/workspaces/plasmanetbook/ KDE's Plasma Netbook] which is a workspace made specifically for small, lightweight netbook devices.<br />
<br />
=== Networking ===<br />
<br />
You can choose from the following tools:<br />
* NetworkManager. See [[NetworkManager#KDE4|NetworkManager]] for more information.<br />
* Wicd. See [[Wicd]] for more information.<br />
<br />
=== Printing ===<br />
<br />
{{Tip|Use the [[CUPS]] web interface for faster configuration. Printers configured in this way can be used in KDE applications. }}<br />
<br />
You can also configure printers in ''System Settings > Printer Configuration''. To use this method, you must first install {{Pkg|kdeutils-print-manager}} and {{Pkg|cups}}.<br />
<br />
The {{ic|avahi-daemon}} and {{ic|cupsd}} daemons must be started first; otherwise, you will get the following error:<br />
The service 'Printer Configuration' does not provide an interface 'KCModule'<br />
with keyword 'system-config- printer-kde/system-config-printer-kde.py'<br />
The factory does not support creating components of the specified type.<br />
<br />
If you are getting the following error, you need to give your user the right to manage printers.<br />
There was an error during CUPS operation: 'cups-authorization-canceled'<br />
<br />
For CUPS, this is set in {{ic|/etc/cups/cupsd.conf}}.<br />
<br />
Adding {{ic|lp}} to {{ic|SystemGroup}} allows anyone who can print to configure printers. You can, of course, add another group instead of {{ic|lp}}.<br />
{{hc|/etc/cups/cupsd.conf|# Administrator user group...<br />
SystemGroup sys root lp}}<br />
<br />
=== Samba/Windows support ===<br />
<br />
If you want to have access to Windows services, install [[Samba]] (package {{Pkg|samba}}).<br />
<br />
You can then configure Samba shares through:<br />
<br />
System Settings > Sharing > Samba<br />
<br />
=== KDE Desktop activities ===<br />
<br />
KDE Desktop Activities are Plasma-based virtual-desktop-like sets of Plasma Widgets where you can independently configure widgets as if you have more than one screen or desktop.<br />
<br />
On your desktop, click the Cashew Plasmoid and, on the pop-up window, press "Activities".<br />
<br />
A plasma bar presenting you the current existing Plasma Desktop Activities will appear at the bottom of the screen. You can navigate between them by pressing the correspondent icons.<br />
<br />
=== Power saving ===<br />
<br />
KDE has an integrated power saving service called "'''Powerdevil Power Management'''" that may adjust the power saving profile of the system and/or the brightness of the screen (if supported).<br />
<br />
Since KDE 4.6, CPU frequency scaling is no longer managed by KDE. Instead it is assumed to be handled automatically by the the hardware and/or kernel. Arch has used {{ic|ondemand}} as the default CPU frequency governor since kernel version 3.3, so no additional configuration in needed in most cases. For details on fine-tuning the governor, see [[CPU Frequency Scaling]].<br />
<br />
=== Monitoring changes on local files and directories ===<br />
<br />
KDE now uses '''inotify''' directly from the kernel with '''kdirwatch''' (included in kdelibs), so Gamin or FAM are no longer needed. You may want to install this {{AUR|kdirwatch}} from AUR which is a GUI frontend for kdirwatch.<br />
<br />
== System administration ==<br />
<br />
=== Set keyboard ===<br />
<br />
Navigate to:<br />
System Settings > Hardware > Input Devices > Keyboard<br />
In the first tab, you can choose your keyboard model.<br />
<br />
In the "'''Layouts'''" tab, you can choose the languages you may want to use by pressing the "Add Layout" button and subsequently choosing the variant and the language.<br />
<br />
In the "'''Advanced'''" tab, you can choose the keyboard combination you want in order to change the layouts in the "Key(s) to change layout" sub-menu.<br />
<br />
=== Terminate Xorg server through KDE system settings ===<br />
<br />
Navigate to the submenu:<br />
System Settings > Input Devices > Keyboard > Advanced (tab) > "Key Sequence to kill the X server"<br />
and tick the checkbox.<br />
<br />
=== KCM ===<br />
<br />
KCM stands for '''KC'''onfig '''M'''odule. KCMs can help you configure your system by providing interfaces in System Settings.<br />
<br />
'''Configuration for look and feel of GTK applications.'''<br />
* {{Pkg|kde-gtk-config}}<br />
* {{AUR|kcm-gtk}}<br />
* {{AUR|kcm-qt-graphicssystem}}<br />
<br />
'''Configuration for the GRUB bootloader.'''<br />
* {{AUR|grub2-editor}}<br />
* {{AUR|kcm-grub2}}<br />
<br />
'''Configuration for Synaptics touchpads.'''<br />
* {{AUR|synaptiks}}<br />
* {{AUR|kcm_touchpad}}<br />
<br />
'''Configuration for the [[Uncomplicated Firewall]] (UFW)'''<br />
* {{AUR|kcm-ufw}}<br />
<br />
'''Configuration for [[PolicyKit]]'''<br />
* {{AUR|kcm-polkit-kde-git}}<br />
<br />
'''Configuration for Wacom tablets'''<br />
* {{AUR|kcm-wacomtablet}}<br />
<br />
More KCMs can be found at [http://kde-apps.org/index.php?xcontentmode=273 kde-apps.org].<br />
<br />
== Desktop search and semantic desktop ==<br />
<br />
According to [[wikipedia:Semantic_desktop|Wikipedia]], ''"the Semantic Desktop is a collective term for ideas related to changing a computer's user interface and data handling capabilities so that data is more easily shared between different applications or tasks and so that data that once could not be automatically processed by a computer can be (automatically processed)."''<br />
<br />
The KDE implementation of this concept is tied to (as of KDE 4.10) two major pieces of software, Akonadi and Nepomuk. Between the two of them, these programs look at your data and make an easily searchable index of it. The idea behind these pieces of software is to make your system "aware" of your data and give it context using meta-data and user-supplied tags.<br />
<br />
Soprano and Virtuoso are two dependencies of the Nepomuk Semantic Desktop. Since the relationship between the two major components and their dependencies is not very clear, the following sections try to shed some light on their inner workings.<br />
<br />
=== Virtuoso and Soprano ===<br />
<br />
The database used to store all the metadata used by the semantic desktop is a ''[[wikipedia:Resource_Description_Framework|Resource Description Framework (RDF)]]'' database called Virtuoso. Internally, Virtuoso may be looked as a relational database. (A [[wikipedia:Relational_model|relational database]] is different from a traditional single-table based database in the sense that it uses multiple tables related by a single key in order to store data.) It is currently controlled by OpenLink and is available under a commercial and an open source license.<br />
<br />
From the [http://techbase.kde.org/Projects/Nepomuk/ComponentOverview#Soprano KDE Techbase], ''Soprano is a Qt abstraction over databases. It provides a friendly Qt-based API for accessing different RDF stores. It currently supports 3 database backends - Sesame, Redland and Virtuoso. The KDE Semantic Stack only works with Virtuoso. Soprano also provides additional features such as serializing, parsing RDF data, and a client server architecture that is heavily used in Nepomuk.''<br />
<br />
=== Nepomuk ===<br />
<br />
Nepomuk stands for "Networked Environment for Personal, Ontology-based Management of Unified Knowledge". It is what allows all the tagging and labeling of files as well to take place and also serves as the way to actually read the Virtuoso databases. It provides an API to application developers which allows them to read the data collected by it.<br />
<br />
In the past, the "Strigi" service was used to collect data about the various files present on the system. However, due to many reasons, the most important of them being CPU and Memory usage, Strigi was replaced by a homegrown indexing service which is integrated with Nepomuk-Core.<br />
<br />
For further information about Nepomuk, [http://techbase.kde.org/Projects/Nepomuk/ComponentOverview#Nepomuk_Components this page] is a good resource. However, some of the information in the previous page has been rendered outdated according to [http://vhanda.in/blog/2012/11/nepomuk-without-strigi/ this blog post].<br />
<br />
==== Using and configuring Nepomuk ====<br />
<br />
In order to search using Nepouk on the KDE desktop, press {{ic|ALT+F2}} and type in your query. Nepomuk is enabled by default. It can be turned on and off in:<br />
System Settings > Desktop Search<br />
<br />
Nepomuk has to keep track of a lot of files. It is for this reason that it is recommended to increase the number of files that can be watched with inotify. In order to do that this command is a good option.<br />
# sysctl fs.inotify.max_user_watches=524288<br />
<br />
To do it persistently:<br />
# echo "fs.inotify.max_user_watches = 524288" >> /etc/sysctl.d/99-inotify.conf<br />
<br />
Restart Nepomuk to see the changes.<br />
<br />
==== KDE without Nepomuk ====<br />
<br />
If you wish to run KDE without Nepomuk, there exists a {{AUR|nepomuk-core-fake}} package in the AUR.<br />
{{Warning|As of now, Dolphin depends on {{Pkg|nepomuk-widgets}} and hence will break if used with the fake Nepomuk package.}}<br />
<br />
=== Akonadi ===<br />
<br />
Akonadi is a system meant to act as a local cache for PIM data, regardless of its origin, which can be then used by other applications. This includes the user's emails, contacts, calendars, events, journals, alarms, notes, and so on. It interfaces with the Nepomuk libraries to provide searching capabilities.<br />
<br />
Akonadi does not store any data by itself: the storage format depends on the nature of the data (for example, contacts may be stored in vCard format).<br />
<br />
For more information on Akonadi and its relationship with Nepomuk, see [http://blogs.kde.org/node/4503] and [http://cmollekopf.wordpress.com/2013/02/13/kontact-nepomuk-integration-why-data-from-akonadi-is-indexed-in-nepomuk/].<br />
<br />
==== Disabling Akonadi ====<br />
<br />
See this [http://userbase.kde.org/Akonadi#Disabling_the_Akonadi_subsystem section in the KDE userbase].<br />
<br />
==== Database configuration ====<br />
<br />
Start {{ic|akonaditray}} from package {{Pkg|kdepim-runtime}}. Right click on it and select '''configure'''. In the Akonadi server configure tab, you can:<br />
* Configuring Akonadi to use MySQL/MariaDB Server<br />
* Configuring Akonadi to use PostgreSQL Server<br />
* Configuring Akonadi to use SQLite<br />
<br />
==== Running KDE without Akonadi ====<br />
<br />
The package {{AUR|akonadi-fake}} is a good option for those who wish to run KDE without Akonadi.<br />
<br />
== Phonon ==<br />
<br />
=== What is Phonon? ===<br />
<br />
From [[Wikipedia:Phonon|Wikipedia]]:<br />
''Phonon is the multimedia API for KDE 4. Phonon was created to allow KDE 4 to be independent of any single multimedia framework such as GStreamer or xine and to provide a stable API for KDE 4's lifetime. It was done for various reasons: to create a simple KDE/Qt style multimedia API, to better support native multimedia frameworks on Windows and Mac OS X, and to fix problems of frameworks becoming unmaintained or having API or ABI instability.<br />
''<br />
<br />
'''Phonon''' is being widely used within KDE, for both audio (e.g., the System notifications or KDE audio apps) and video (e.g., the Dolphin video thumbnails).<br />
<br />
=== Which backend should I choose? ===<br />
<br />
You can choose between various backends like GStreamer ({{Pkg|phonon-gstreamer}}) or VLC ({{Pkg|phonon-vlc}}), available in the [[official repositories]], and MPlayer ({{AUR|phonon-mplayer-git}}), ({{AUR|phonon-quicktime-git}}), and ({{AUR|phonon-avkode-git}}); available in the [[AUR]]. Most users will want GStreamer or VLC which have the best upstream support. Note that multiple backends can be installed at once and chosen at ''System Settings > Multimedia > Phonon > Backend''.<br />
<br />
{{Note|According to the [http://userbase.kde.org/Phonon#Backend_libraries KDE UserBase], Phonon-MPlayer is currently unmaintained}}<br />
<br />
According to [http://lists.kde.org/?l=kde-multimedia&m=137994906723790&w=2 this mail in the KDE-Multimedia mailing list], users should prefer VLC over GStreamer.<br />
<br />
== Useful applications ==<br />
<br />
The official set of KDE applications may be found [http://www.kde.org/applications/ here].<br />
<br />
=== Yakuake ===<br />
<br />
[http://yakuake.kde.org/ Yakuake] provides a Quake-like terminal emulator whose visibility is toggled by the F12 key. It also has support for multiple tabs. Yakuake is available in the package {{Pkg|yakuake}}.<br />
<br />
=== KDE Telepathy ===<br />
<br />
[http://community.kde.org/KTp KDE Telepathy] is a project with the goal to closely integrate Instant Messaging with the KDE desktop. It utilizes the Telepathy framework as a backend and is intended to replace Kopete.<br />
<br />
To install all Telepathy protocols, install the {{Grp|telepathy}} group.<br />
To use the KDE Telepathy client, install the {{Pkg|kde-telepathy-meta}} package that includes all the packages contained in the {{Grp|kde-telepathy}} group .<br />
<br />
== Tips and tricks ==<br />
<br />
=== Configure KWin to use OpenGL ES ===<br />
<br />
Beginning with KWin version 4.8 it is possible to use the separately built binary '''kwin_gles''' as a replacement for kwin. It behaves almost the same as the kwin executable in OpenGL2 mode with the slight difference that it uses ''egl'' instead of ''glx'' as the native platform interface. To test kwin_gles you just have to run {{ic|kwin_gles --replace}} in Konsole.<br />
If you want to make this change permanent you have to create a script in {{ic|$(kde4-config --localprefix)/env/}} which exports {{ic|1=KDEWM=kwin_gles}}.<br />
<br />
=== Enabling audio thumbnails under Konqueror/Dolphin file managers ===<br />
<br />
For thumbnails of audio files in Konqueror and Dolphin install {{AUR|audiothumbs}} from AUR.<br />
<br />
=== Enabling video thumbnails under Konqueror/Dolphin file managers ===<br />
<br />
For thumbnails of videos in konqueror and dolphin install {{Pkg|kdemultimedia-mplayerthumbs}} or {{Pkg|kdemultimedia-ffmpegthumbs}}.<br />
<br />
=== Speed up application startup ===<br />
<br />
User Rob wrote on his blog this "[http://kdemonkey.blogspot.nl/2008/04/magic-trick.html magic trick]" to improve application start-up time by 50-150ms.<br />
To enable it, create this folder in your home:<br />
$ mkdir -p ~/.compose-cache/<br />
<br />
{{Note|For those curious about what is going on here, this enables an optimization which Lubos (of general KDE speediness fame) came up with some time ago and was then rewritten and integrated into libx11. Ordinarily, on startup, applications read input method information from {{ic|/usr/share/X11/locale/''your locale''/Compose}}. This file is quite long (>5000 lines for the en_US.UTF-8 one) and takes some time to process. libX11 can create a cache of the parsed information which is much quicker to read subsequently, but it will only re-use an existing cache or create a new one in {{ic|~/.compose-cache}} if the directory already exists.}}<br />
<br />
=== Hiding partitions ===<br />
<br />
In Dolphin, it is as simple as right-clicking on the partition in the {{ic|Places}} sidebar and selecting {{ic|Hide ''partition''}}. Otherwise...<br />
<br />
If you wish to prevent your internal partitions from appearing in your file manager, you can create an udev rule, e.g:<br />
<br />
{{hc|/etc/udev/rules.d/10-local.rules|2=<br />
KERNEL=="sda[0-9]", ENV{UDISKS_IGNORE}="1"<br />
}}<br />
<br />
The same thing for a certain partition:<br />
<br />
KERNEL=="sda1", ENV{UDISKS_IGNORE}="1"<br />
KERNEL=="sda2", ENV{UDISKS_IGNORE}="1"<br />
<br />
=== Konqueror tips ===<br />
<br />
==== Disabling smart key tooltips (browser) ====<br />
<br />
To disable those smart key tooltips in Konqueror (pressing {{ic|Ctrl}} on a web page), use ''Settings > Configure Konqueror > Web Browsing'' and uncheck ''Enable Access Key activation with Ctrl key'' o<br />
<br />
{{hc|~/.kde4/share/config/konquerorrc|2=<br />
[Access Keys]<br />
Enabled=false<br />
}}<br />
<br />
==== Using WebKit ====<br />
<br />
WebKit is an open source browser engine developed by Apple Inc. It is a derivative from the KHTML and KJS libraries and contains many improvements. WebKit is used by Safari, Google Chrome and rekonq.<br />
<br />
It is possible to use WebKit in Konqueror instead of KHTML. First install the {{Pkg|kwebkitpart}} package.<br />
<br />
Then, after executing Konqueror, navigate to ''Settings > Configure Konqueror > General > Default web browser engine'' and set it as {{ic|WebKit}}.<br />
<br />
=== Firefox integration ===<br />
<br />
See [[Firefox#KDE_integration|Firefox]].<br />
<br />
=== Setting the screensaver background to the same as the current one ===<br />
<br />
Kscreensaver's background can be changed from the default.<br />
<br />
KDE by default is [https://bugs.kde.org/show_bug.cgi?id=312828 not able] to change this for the 'Simple Lock', but a [http://lists.opensuse.org/opensuse-kde/2013-02/msg00082.html workaround] [http://forum.kde.org/viewtopic.php?f=66&t=110039 exists]:<br />
<br />
{{hc|/usr/share/apps/ksmserver/screenlocker/org.kde.passworddialog/contents/ui/|<br />
[...]<br />
''#source: theme.wallpaperPathForSize(parent.width, parent.height)''<br />
source: "1920x1080.jpg"<br />
[...]<br />
}}<br />
<br />
Now you copy your current background image to {{ic|"1920x1080.jpg"}}.<br />
<br />
Note you have to redo this for each update of the package {{Pkg|kdebase-workspace}}.<br />
<br />
=== Setting lockscreen wallpaper to arbitrary image ===<br />
<br />
Copy an existing wallpaper profile as a template:<br />
$ cp -r /usr/share/wallpapers/''ExistingWallpaper'' ~/.kde4/share/wallpapers/<br />
<br />
Change the name of the directory, and edit {{ic|metadata.desktop}}:<br />
<br />
{{hc|~/.kde4/share/wallpapers/''MyWallpaper''/metadata.desktop|2=<br />
[Desktop Entry]<br />
Name=MyWallpaper<br />
X-KDE-PluginInfo-Name=MyWallpaper<br />
}}<br />
<br />
Remove existing images ({{ic|contents/screenshot.png}} and {{ic|images/*}}):<br />
$ rm ~/.kde4/share/wallpapers/MyWallpaper/contents/screenshot.png<br />
$ rm ~/.kde4/share/wallpapers/MyWallpaper/contents/images/*<br />
<br />
Copy new image in:<br />
$ cp ''path/to/MyWallpaper.png'' MyWallpaper/contents/images/1920x1080.png<br />
<br />
Edit the metadata profile for the current theme:<br />
{{hc|~/.kde4/share/apps/desktoptheme/MyTheme/metadata.desktop|2=<br />
[Wallpaper]<br />
defaultWallpaperTheme=NewWallpaper<br />
defaultFileSuffix=.png<br />
defaultWidth=1920<br />
defaultHeight=1080<br />
}}<br />
<br />
Lock the screen to check that it worked.<br />
<br />
{{Note|This method allows you to set the lockscreen background without changing any system-wide settings. For a system-wide change, create the new wallpaper profile in {{ic|/usr/share/wallpapers}}.}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Configuration related ===<br />
<br />
Many issues in KDE are related to configuration. One way to resolve upgrade problems is to start over with a fresh KDE config.<br />
<br />
==== Reset all KDE configuration ====<br />
<br />
To test whether your config is the problem try quitting your KDE session by logging out and, in a tty, run<br />
$ cp ~/.kde4 ~/.kde4.safekeeping<br />
$ rm .kde4/{cache,socket,tmp}-$(hostname)<br />
<br />
The ''rm'' command just removes symbolic links which will be recreated by KDE automatically. Now start a new KDE session to see the results.<br />
<br />
If the problem is resolved, you will have a fresh, problem-free {{ic|~/.kde4/}}. You can gradually move parts of your saved configuration back, restarting your session regularly to test, to identify the problematic parts of your config. Some files here are named after applications so you will probably be able to test these without needing to restart KDE.<br />
<br />
==== File Indexer Service not working even after enabling everything properly ====<br />
<br />
This is caused due to a corrupted Nepomuk database. It may be remedied by moving the database or deleting it all together. Log out of KDE and issue this command from a virtual console:<br />
<br />
$ mv ~/.kde4/share/apps/nepomuk ~/.kde4/share/apps/nepomuk_backup<br />
<br />
to move your existing (and corrupt) nepomuk database. It will be recreated when you log in again.<br />
<br />
==== Plasma desktop behaves strangely ====<br />
<br />
Plasma issues are usually caused by unstable '''plasmoids''' or '''plasma themes'''. First, find which was the last plasmoid or plasma theme you had installed and disable it or uninstall it.<br />
<br />
So, if your desktop suddenly exhibits "locking up", this is likely caused by a faulty installed widget. If you cannot remember which widget you installed before the problem began (sometimes it can be an irregular problem), try to track it down by removing each widget until the problem ceases. Then you can uninstall the widget, and file a bug report (bugs.kde.org) '''only if it is an official widget'''. If it is not, it is recommended you find the entry on kde-look.org and inform the developer of that widget about the issue (detailing steps to reproduce, etc).<br />
<br />
If you cannot find the problem, but you do not want ''all'' the KDE settings to be lost, do:<br />
<br />
$ rm -r ~/.kde4/share/config/plasma*<br />
<br />
This command will '''delete all plasma related configs''' of your user and when you will relogin into KDE, you will have the '''default''' settings back. You should know that this action '''cannot be undone'''. You should create a backup folder and copy all the plasma related configs in it.<br />
<br />
==== Clean cache to resolve upgrade problems ====<br />
<br />
The [https://bbs.archlinux.org/viewtopic.php?id=135301 problem] may be caused by old cache. Sometimes after an upgrade, the old cache might introduce strange, hard to debug behaviour such as unkillable shells, hangs when changing various settings and several other problems such as ark being unable to unrar or unzip or amarok not recognizing any of your musics. This solution can also resolve problems with KDE and QT programmes looking bad following upgrade.<br />
<br />
Rebuild your cache with the following commands:<br />
<br />
$ rm ~/.config/Trolltech.conf<br />
$ kbuildsycoca4 --noincremental<br />
<br />
Hopefully, your problems are now fixed.<br />
<br />
=== Clean akonadi configuration to fix KMail ===<br />
<br />
First, make sure that KMail is not running. Then backup configuration:<br />
$ mv ~/.local/share/akonadi ~/.local/share/akonadi-old<br />
$ mv ~/.config/akonadi ~/.config/akonadi-old<br />
<br />
Start ''SystemSettings > Personal'' and remove all the resources. Go back to Dolphin and remove the original {{ic|~/.local/share/akonadi}} and<br />
{{ic|~/.config/akonadi}} - the copies you made ensure that you can back-track if necessary.<br />
<br />
Now go back to the System Settings page and carefully add the necessary resources. You should see the resource reading in your mail folders. Then start Kontact/KMail to see if it work properly.<br />
<br />
=== Getting current state of KWin for support and debug purposes ===<br />
<br />
This command prints out a wonderful summary of the current state of KWin including used options, used compositing backend and relevant OpenGL driver capabilities. See more on [http://blog.martin-graesslin.com/blog/2012/03/on-getting-help-for-kwin-and-helping-kwin/ Martin's blog].<br />
<br />
$ qdbus org.kde.kwin /KWin supportInformation<br />
<br />
=== KDE4 does not finish loading ===<br />
<br />
There might be a situation in which the graphic driver might create a conflict when starting KDE4. This situation happens after the login but before finishing loading the desktop, making the user wait indefinitely at the loading screen. Until now the only users confirmed to be affected by this are the ones that use [[NVIDIA|Nvidia drivers]] and KDE4.<br />
<br />
A solution for Nvidia users:<br />
<br />
{{hc|~/.kde4/share/config/kwinrc|2=<br />
[Compositing]<br />
Enabled=false<br />
}}<br />
For more information, see [https://bbs.archlinux.org/viewtopic.php?pid=932598 this] thread.<br />
<br />
If a minimal install was done, make sure you installed the required font by your phonon backend listed here: [[#Minimal install]]<br />
<br />
=== KDE and Qt programs look bad when in a different window manager ===<br />
<br />
If you are using KDE or Qt programs but not in a full KDE session (specifically, you did not run {{ic|startkde}}), then as of KDE 4.6.1 you will need to tell Qt how to find KDE's styles (Oxygen, QtCurve etc.)<br />
<br />
You just need to set the environment variable {{ic|QT_PLUGIN_PATH}}. E.g. put:<br />
<br />
export QT_PLUGIN_PATH=$HOME/.kde4/lib/kde4/plugins/:/usr/lib/kde4/plugins/<br />
<br />
into your {{ic|/etc/profile}} (or {{ic|~/.profile}} if you do not have root access). qtconfig should then be able to find your KDE styles and everything should look nice again!<br />
<br />
Alternatively, you can symlink the Qt styles directory to the KDE styles one:<br />
# ln -s /usr/lib/kde4/plugins/styles/ /usr/lib/qt/plugins/styles<br />
<br />
Under Gnome you can try to install the package libgnomeui.<br />
<br />
=== Graphical related issues ===<br />
<br />
==== Low 2D desktop performance (or) artifacts appear when on 2D ====<br />
<br />
===== GPU driver problem =====<br />
<br />
Make sure you have the proper driver for your card installed, so that your desktop is at least 2D accelerated. Follow these articles for more information: [[ATI]], [[NVIDIA]], [[Intel]] for more information, in order to make sure that everything is all right.<br />
The open-source ATI and Intel drivers and the proprietary (binary) Nvidia driver should theoretically provide the best 2D and 3D acceleration.<br />
<br />
===== The Raster engine workaround =====<br />
<br />
If this does not solve your problems, your driver may not provide a good '''XRender''' acceleration which the current Qt painter engine relies on by default.<br />
<br />
You can change the painter engine to software based only by invoking the application with the {{ic|-graphicssystem raster}} command line. This rendering engine can be set as the default one by recompiling Qt with the same as configure option, {{ic|-graphicssystem raster}}.<br />
<br />
The raster paint engine enables the CPU to do the majority of the painting, as opposed to the GPU. You may get better performance, depending on your system. This is basically a work-around for the terrible Linux driver stack, since the CPU should obviously not be doing graphical computations since it is designed for fewer threads of greater complexity, as opposed to the GPU which is many threads but lesser computational strength. So, only use Raster engine if you are having problems or your GPU is much slower than you CPU, otherwise is better to use XRender.<br />
<br />
Since Qt 4.7+, recompiling Qt is not needed. Simply export {{ic|1=QT_GRAPHICSSYSTEM=raster}}, or {{ic|opengl}}, or {{ic|native}} (for the default). Raster depends on the CPU, OpenGL depends on the GPU and high driver support, and Native is just using the X11 rendering (mixture, usually).<br />
<br />
'''The best and automatic way to do that''' is to install {{AUR|kcm-qt-graphicssystem}} from AUR and configure this particular Qt setting through:<br />
<br />
System Settings > Qt Graphics System<br />
<br />
For more information, consult this [http://apachelog.wordpress.com/2010/09/05/qt-graphics-system-kcm/ KDE Developer blog entry] and/or this [http://labs.trolltech.com/blogs/2009/12/18/qt-graphics-and-performance-the-raster-engine/ Qt Developer blog entry].<br />
<br />
==== Low 3D desktop performance====<br />
<br />
KDE begins with desktop effects enabled. Older cards may be insufficient for 3D desktop acceleration. You can disable desktop effects in:<br />
System Settings > Desktop Effects<br />
and you can toggle desktop effects with {{ic|Alt+Shift+F12}}.<br />
<br />
{{Note| You may encounter such problems with 3D desktop performance even when using a more powerful graphics card, especially the catalyst proprietary driver ({{ic|fglrx}}). This driver is known for having issues with 3D acceleration. Visit [[ATI|the ATI Wiki page]] for more troubleshooting.}}<br />
<br />
==== Desktop compositing is disabled on my system with a modern Nvidia GPU ====<br />
<br />
Sometimes, KWin may have settings in its configuration file ({{ic|kwinrc}}) that ''may'' cause a problem on re-activating the 3D desktop {{ic|OpenGL}} compositing. That could be caused randomly (for example, due to a sudden Xorg crash or restart, and it gets corrupted), so, in case that happens, delete your {{ic|~/.kde4/share/config/kwinrc}} file and relogin. The KWin settings will turn to the KDE default ones and the problem should be probably gone.<br />
<br />
==== Flickering in fullscreen when compositing is enabled ====<br />
<br />
As of KDE SC 4.6.0, there is an option in ''Sytem Settings > Desktop Effect > Advanced > Suspend desktop effects for fullscreen windows''. Uncheck it would tell kwin to disable unredirect fullscren.<br />
<br />
==== Screen Tearing with desktop compositing enabled ====<br />
<br />
{{Note|With the recent update of KDE to 4.11, several new Vsync options have been added, which may help with screen tearing.}}<br />
<br />
KWin may suffer from screen tearing while desktop effects are enabled. Uncheck the VSync option under ''System Settings > Desktop Effects > Advanced > Use Vsync''.<br />
<br />
For proprietary driver users, ensure that the driver's VSync option is enabled ({{ic|amdccle}} for [[Catalyst]] users, and nvidia-settings for [[NVIDIA]] users).<br />
<br />
==== Display settings lost on reboot (multiple monitors) ====<br />
Installing {{Pkg|kscreen}} might fix the problem unless your screens share the same EDID. Kscreen is the improved screen management software for KDE, more information can be found [https://fedoraproject.org/wiki/Changes/KScreen?rd=Features/KScreen here].<br />
<br />
=== Sound problems under KDE ===<br />
<br />
==== ALSA related problems ====<br />
<br />
{{Note|First make sure you have {{Pkg|alsa-lib}} and {{Pkg|alsa-utils}} installed.}}<br />
<br />
===== "Falling back to default" messages when trying to listen to any sound in KDE =====<br />
<br />
When you encounter such messages:<br />
The audio playback device ''name_of_the_sound_device'' does not work.<br />
Falling back to default<br />
Go to:<br />
System Settings > Multimedia > Phonon<br />
and set the device named {{ic|default}} above all the other devices in each box you see.<br />
<br />
===== MP3 files cannot be played when using the GStreamer Phonon backend =====<br />
<br />
This can be solved by installing the GStreamer plugins (package group {{Grp|gstreamer0.10-plugins}}). If you still encounter problems, you can try changing the Phonon backend used by installing another such as {{Pkg|phonon-vlc}}.<br />
Then, make sure the backend is preferred via:<br />
<br />
System Settings > Multimedia > Phonon > Backend (tab)<br />
<br />
=== Konsole does not save commands' history ===<br />
<br />
By default console command history is saved only when you type 'exit' in console. When you close Konsole with 'x' in the corner it does not happen.<br />
To enable autosaving after every command execution:<br />
<br />
{{hc|~/.bashrc|<nowiki><br />
shopt -s histappend<br />
[[ "${PROMPT_COMMAND}" ]] && PROMPT_COMMAND="$PROMPT_COMMAND;history -a" || PROMPT_COMMAND="history -a"<br />
</nowiki>}}<br />
<br />
=== KDE password prompts display three bullets per char ===<br />
<br />
This setting can be changed at ''System Settings > Account Details > Password & User Account'':<br />
* Show one bullet for each letter<br />
* Show three bullets for each letter<br />
* Show nothing<br />
<br />
=== Nepomukserver process still autostarts even with semantic desktop disabled ===<br />
<br />
Go to ''System Settings > Startup and Shutdown > Service Manager > Startup Services'' and uncheck the Nepomuk Search Module.<br />
<br />
=== Dolphin and File Dialogs are extremely slow to start ===<br />
<br />
This may be caused by the upower service. If the upower service is not needed on your system, it can be disabled:<br />
<br />
# systemctl disable upower<br />
# systemctl mask upower<br />
<br />
Obviously this will not have any side effect on a desktop system.<br />
<br />
=== Default PDF viewer in GTK applications under KDE ===<br />
<br />
In some cases when you have installed [[Inkscape]], [[Gimp]] or other graphic programs, GTK applications ([[Firefox]] among all) might not select Okular as the default PDF application, and they are not going to follow the KDE settings on default applications. You can use the following user command to make Okular the default application again.<br />
<br />
$ xdg-mime default kde4-okularApplication_pdf.desktop application/pdf<br />
<br />
If you are using a different PDF viewer application, or a different mime-type is misbehaving, you should change {{ic|kde4-okularApplication_pdf.desktop}} and {{ic|application/pdf}} respectively according to your needs.<br />
<br />
For more information, consult [[Default Applications]] wiki page.<br />
<br />
== Unstable releases ==<br />
<br />
When KDE is reaching beta or RC milestone, KDE "unstable" packages are uploaded to the [kde-unstable] repository. They stay there until KDE is declared stable and passes to [extra].<br />
<br />
You can add [kde-unstable] with:<br />
<br />
{{hc|/etc/pacman.conf|2=<br />
[kde-unstable]<br />
Include = /etc/pacman.d/mirrorlist<br />
}}<br />
<br />
# [kde-unstable] is based upon testing. Therefore, you need to enable the repositories in the following order: [kde-unstable], [testing], [core], [extra], [community-testing], [community].<br />
# To update from a previous KDE installation, run: {{ic|# pacman -Syu}} or {{ic|# pacman -S kde-unstable/kde}}<br />
# If you do not have KDE installed, you might have difficulties to install it by using groups (limitation of pacman)<br />
# '''Subscribe and read the [https://mailman.archlinux.org/pipermail/arch-dev-public/ arch-dev-public] mailing list'''<br />
# Make sure [[#Distro_and_Upstream_bug_report|you make bug reports]] if you find any issues.<br />
<br />
== Other KDE projects ==<br />
<br />
=== Trinity ===<br />
<br />
From the release of KDE 4.x, the developers dropped support for KDE 3.5.x. Trinity Desktop Environment is a fork of KDE3 developed by Timothy Pearson ([http://trinitydesktop.org/ trinitydesktop.org]). This project aims 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. See [[Trinity]] for more info.<br />
<br />
{{Warning|KDE 3 is no longer maintained and supported by the KDE developers. The "Trinity KDE" is maintained by the Trinity project commmunity. Use KDE 3 on your own risk, regarding any bugs, performance issues or security risks.}}<br />
<br />
== Bugs ==<br />
<br />
It is preferrable that if you find a minor or serious bug, you should visit [https://bugs.archlinux.org the Arch Bug Tracker] or/and [http://bugs.kde.org KDE Bug Tracker] in order to report that. Make sure that you are clear about what you want to report.<br />
<br />
If you have any issue and you write about in on the Arch forums, first make sure that you have '''fully''' updated your system using a good sync mirror (check [https://www.archlinux.de/?page=MirrorStatus here]) or try [[Reflector]].<br />
<br />
== See also ==<br />
<br />
* [http://www.kde.org] - KDE homepage<br />
* [https://bugs.kde.org] - KDE bug tracker<br />
* [https://bugs.archlinux.org] - Arch Linux bug tracker<br />
* [https://projects.kde.org] - KDE Projects</div>Catlover2https://wiki.archlinux.org/index.php?title=ArchWiki:Translation_Team&diff=276169ArchWiki:Translation Team2013-09-20T21:21:13Z<p>Catlover2: Removed Epson TX125 from list of non-English-only articles. Other grammatical and formatting changes to hopefully make it easier to understand.</p>
<hr />
<div>[[Category:ArchWiki]]<br />
[[es:ArchWiki Translation Team]]<br />
[[hr:ArchWiki Translation Team]]<br />
[[it:ArchWiki Translation Team]]<br />
[[ja:ArchWiki Translation Team]]<br />
[[pl:ArchWiki Translation Team]]<br />
[[pt:ArchWiki Translation Team]]<br />
[[tr:ArchWiki_Çeviri_Ekibi]]<br />
[[zh-CN:ArchWiki Translation Team]]<br />
{{stub}}<br />
<br />
== Create a new page and its translation ==<br />
# If you do not know how to edit wiki pages, read [[Help:Editing]].<br />
# Read [[Help:i18n]], which contains comprehensive guidelines for ArchWiki internationalization and localization.<br />
# [[Special:UserLogin|Login]] to be able to edit the wiki.<br />
# Choose a page to translate. You can use the [[Special:Random|random page function]] or translate a page in the [[ArchWiki Translation Day#List of priority pages|list of priority pages]]. The non-existent page [[Some Page]] is used as an example here.<br />
# On the page you chose, click '''edit''' in the horizontal menu.<br />
# Add an interlanguage link for the translation you are going to create. (See [[Help:i18n#Interlanguage links]].)<br />
# Copy the entire page's source code.<br />
# Save the page with the new interlanguage link.<br />
# Visit the interlanguage link you have just created which will lead you to [[Some Page (Some Language)]], where ''Some Language'' is the [[Help:I18n#Languages|language name]] associated with the translation you are about to create.<br />
# Since the new page does not exist, create it by clicking on '''create''' in the horizontal menu.<br />
# You will be shown a simple WYSIWYG editor. Paste the source code of the page to be translated here.<br />
# Change the ''Category'' to the localized version. For example, change {{ic|<nowiki>[[Category:Internationalization]]</nowiki>}} to {{ic|<nowiki>[[Category:Internationalization (Some Language)]]</nowiki>}}. See [[Help:Category]] for more info.<br />
# Change the interlanguage link that you created earlier to point to the article ''from'' which you are translating.<br />
# Translate the copied page text and save everything properly.<br />
# Update the interlanguage lists of all other translations of the article (if any) to inculde the interlanguage link of the newly-created translation.<br />
# Create a new ArchWiki page, {{ic|<nowiki>https://wiki.archlinux.org/index.php/</nowiki>''Localized name of translated page''}}, whose title is a localized version of [[Some Page (Some Language)]]. Enter {{ic|<nowiki>#REDIRECT [[Some_Page_(Some Language)</nowiki>]]}} as its only content.<br />
<br />
== Page list ==<br />
List here articles that only exist in non-English languages, or that exist in English but are either not fully translated, or are in a worse state than the non-English version. Keep alphabetical order.<br />
<br />
{| class="wikitable sortable collapsible" border="1"<br />
|-<br />
! Page<br />
! Language<br />
! class="unsortable" | Notes<br />
|-<br />
| [[Acer Aspire 5740G (Español)]]<br />
| Spanish<br />
|<br />
|-<br />
| [[Acer Aspire 5740G (Polski)]]<br />
| Polish<br />
|<br />
|-<br />
| [[Bootsplash (Русский)]]<br />
| Russian<br />
|<br />
|-<br />
| [[Collect system information (Español)]]<br />
| Spanish<br />
|<br />
|-<br />
| [[DeaDBeeF (正體中文)]]<br />
| Chinese (Traditional)<br />
|<br />
|-<br />
| [[GtkD (Русский)]]<br />
| Russian<br />
|<br />
|-<br />
| [[IBM T43 (Česky)]]<br />
| Czech<br />
|-<br />
| [[Internet key Momo Design (Italiano)]]<br />
| Italian<br />
|<br />
|-<br />
| [[Media Center (Italiano)]]<br />
| Italian<br />
|<br />
|-<br />
|[[Mikutter (日本語)]]<br />
| Japanese<br />
|<br />
|-<br />
| [[MYTHTV UNDERTHESTAIRS (Dansk)]]<br />
| Dansk<br />
|<br />
|-<br />
| [[HP Nx7400 (Česky)]]<br />
| Czech<br />
|<br />
|-<br />
| [[Osiris (Italiano)]]<br />
| Italian<br />
|<br />
|-<br />
| [[Palm Pre (Italiano)]]<br />
| Italian<br />
|<br />
|-<br />
| [[PHC (Русский)]]<br />
| Russian<br />
| [[PHC]] contains older info<br />
|-<br />
| [[Small Business Server (Italiano)]]<br />
| Italian<br />
| See also [[:Category:Small Business Server (Italiano)]]<br />
|-<br />
| [[Tavolette Trust Aiptek (Italiano)]]<br />
| Italian<br />
|<br />
|-<br />
| [[Tencent QQ (简体中文)]]<br />
| Chinese (Simplified)<br />
|<br />
|-<br />
| [[Wineasio (Русский)]]<br />
| Russian<br />
|<br />
|-<br />
| [[Zabbix (Русский)]]<br />
| Russian<br />
|<br />
|}<br />
<br />
== See also ==<br />
[[Arch Translation Day]]</div>Catlover2https://wiki.archlinux.org/index.php?title=Epson_TX125&diff=276167Epson TX1252013-09-20T20:45:41Z<p>Catlover2: Translated from the Spanish page, shortened, and removed some unneeded information about permissions.</p>
<hr />
<div>[[es:Epson TX125]]<br />
[[Category:Printers]]<br />
{{Stub}}<br />
<br />
This page provides instructions for installing the Epson TX125 printer driver.<br />
<br />
First, install {{Pkg|cups}} from the official repositories and {{AUR|epson-inkjet-printer-n10-nx127}} from the AUR.<br />
<br />
Create a new udev rule, {{ic|/etc/udev/rules.d/10-usbprinter.rules}}, with the following content.<br />
{{bc|ATTR{idVendor}&#61;&#61;"04b8", ATTR{idProduct}&#61;&#61;"085c", MODE:&#61;"0666", GROUP:&#61;{"lp"}, E$}}<br />
Verify idVendor and idProduct by running {{ic|# lsusb -v}}.</div>Catlover2https://wiki.archlinux.org/index.php?title=Epson_TX125_(Espa%C3%B1ol)&diff=276165Epson TX125 (Español)2013-09-20T20:24:25Z<p>Catlover2: </p>
<hr />
<div>[[en:Epson TX125]]<br />
[[Category:Printers (Español)]]<br />
{{Stub}}<br />
<br />
Estas son las instrucciones para instalar la impresora Epson TX125.<br />
<br />
Se debe tener instalado udev, yaourt y cups.<br />
<br />
Instalar el Driver<br />
<br />
yaourt -S epson-inkjet-printer-n10-nx127<br />
<br />
Crear regla de udev:<br />
<br />
nano /etc/udev/rules.d/10-usbprinter.rules<br />
<br />
Agrego lo siguiente:<br />
<br />
ATTR{idVendor}=="04b8", ATTR{idProduct}=="085c", MODE:="0666", GROUP:={"lp"}, E$<br />
<br />
(idVendor e idProduct lo obtengo con lsusb -v)<br />
<br />
Guardo y cierro.<br />
<br />
Cambio permisos:<br />
<br />
sudo chmod -R 755 /opt/epson-inkjet-printer-n10-nx127</div>Catlover2https://wiki.archlinux.org/index.php?title=Logitech_Marble_Mouse&diff=249075Logitech Marble Mouse2013-03-03T20:59:22Z<p>Catlover2: </p>
<hr />
<div>[[Category:Mice]]<br />
The '''Logitech Marble Mouse''' is a pointing device with four buttons and a trackball. It is also known as the '''Trackman Marble'''. The Marble Mouse is symmetrical, making it well-suited for use with either hand. [http://www.logitech.com/assets/21083/21083.png Picture]. Out-of-the box it does not scroll, but you can configure it to enable this.<br />
<br />
== Installation ==<br />
<br />
No driver installation is required. Your system detects the Logitech Marble Mouse at system boot, or whenever it is "hot-plugged" into a booted system.<br />
<br />
The Marble Mouse is treated like any regular mouse — you do not need to configure it. You will probably want to, however, in order to enable scrolling or customize button actions.<br />
<br />
== Basic function ==<br />
<br />
Hardware IDs for the Marble Mouse buttons remain constant, regardless of device configuration.<br />
<br />
When no additional configuration is specified, buttons are mapped to these functions:<br />
<br />
{| border="0"<br />
! ID !! Hardware Action !! Result <br />
|-<br />
| 1 || Large button left || normal click<br />
|-<br />
| 2 || Both large buttons || middle-click †<br />
|-<br />
| 3 || Large button right || right-click<br />
|-<br />
| 4 || ''(not a button)'' || -<br />
|-<br />
| 5 || ''(not a button)'' || -<br />
|-<br />
| 6 || ''(not a button)'' || -<br />
|-<br />
| 7 || ''(not a button)'' || -<br />
|-<br />
| 8 || Small button left || browser back<br />
|-<br />
| 9 || Small button right || browser forward<br />
|}<br />
<br />
{{Note|<br />
* Both large buttons pressed simultaneously creates a '''middle-click'''.<br />
* † The simultaneous click is enabled by a configuration directive. It requires {{Ic|Emulate3buttons}}.<br />
* Terms ''middle-click'' and ''wheel-click'' are used interchangeably in this document.<br />
* ''Alternate-click'' may be used instead of ''right-click''. Typically, this pops up a context menu.<br />
* The result shown above occurs when no modifier key is pressed.<br />
* A different result may occur when a modifier key such as ''Ctrl'' is held while a button is clicked.}}<br />
<br />
{| border="0"<br />
|- Non-button Input Actions<br />
! ID !! Hardware Action !! Result <br />
|-<br />
|-<br />
| 4 || ''Roll ball down'' || move cursor down<br />
|-<br />
| 5 || ''Roll ball up'' || move cursor up<br />
|-<br />
| 6 || ''Roll ball left'' || move cursor left<br />
|-<br />
| 7 || ''Roll ball right'' || move cursor right<br />
|}<br />
<br />
{{Note|<br />
* Cursor motion occurs when no modifier is used.<br />
* A modifier used in conjunction with rolling motion may create an alternate result.<br />
* "Modifier" refers to a key (such as ''Ctrl'') or button (as in ''mouse button'') being held while the trackball is rolled.}}<br />
<br />
{{Note|The Marble Mouse trackball can perform document scrolling, much like a wheel mouse. Scrolling occurs when the '''[[#Scroll modifier|scroll mod&shy;ifier]]''' is held down while the trackball is rolled. You must provide at least a '''[[#Minimal configuration|minimal configuration]]''' to enable this feature.}}<br />
<br />
Using the trackball in "wheel mode" can require some unusual gestures on the user's part. Using a wheel mouse, for example, you can resize the display font in your web browser using the ''Ctrl + wheel_roll'' gesture. With the trackball, this operation becomes ''Ctrl + hold_button + ball_roll''.<br />
<br />
== Configuration ==<br />
<br />
You may find it helpful to simply jump to the [[#Sample configuration | sample configuration]] and try it.<br />
<br />
The configuration sections contain information which may not be of interest to you. Most Arch users will be using a modern version of the X server which requires udev hot plugging.<br />
<br />
{{Note|There is currently (as at May 2012) an issue with [http://who-t.blogspot.com.au/2011/04/gnome-30-middle-mouse-button-emulation.html Gnome 3 and middle click emulation]. See [[#"Both-large-buttons" combination-click]] below.}}<br />
<br />
Gnome 3 is used, for example, in Ubuntu 12.04.<br />
<br />
=== Buttons and trackball ===<br />
<br />
After you locate the [[#Configuration file |sample configuration file]] you may wish to alter it. You need only concern yourself with three or four setup lines.<br />
<br />
==== Assigning buttons ====<br />
<br />
You may want to assign new actions for button presses. This is done by setting positional parameters.<br />
<br />
Values may be changed for buttons '''1, 2, 3, 8,''' and '''9'''. (Button '''2''' is simply a combination press of the two large buttons.) Do not alter parameters 4, 5, 6, or 7.<br />
<br />
# This line makes the default button assignments.<br />
<br />
Option "ButtonMapping" "1 2 3 4 5 6 7 8 9"<br />
<br />
One obvious reason to assign different button actions is to accommodate left-handed placement:<br />
<br />
# This line switches the left and right large buttons, and nothing else. For left-handed user.<br />
<br />
Option "ButtonMapping" "3 2 1 4 5 6 7 8 9"<br />
<br />
Another reason to reassign is when you do not like the "normal" assignments — especially the small buttons.<br />
<br />
The line below changes the button '''2''' action to '''''browser forward'''''. Parameter two (both-large-button click) is given value '''9''' for ''browser forward''. The line below also reassigns both small buttons. We want them to emit '''''middle-click'''''. (Either button may be clicked separately.) Parameters eight and nine are given values of '''2''' for ''middle-click''.<br />
<br />
# Three buttons are given new assignments. For right-handed user.<br />
<br />
Option "ButtonMapping" "1 9 3 4 5 6 7 2 2"<br />
<br />
Parameters are positioned in numeric order. Parameters you might modify are 1, 2, 3, 8, and 9. Parameters 4, 5, 6, and 7 should be left alone; they correspond to trackball movements.<br />
<br />
==== "Both-large-buttons" combination-click ====<br />
<br />
As stated, button '''2''' is a simultaneous press of the two large buttons.<br />
<br />
Experimentation shows, in the absence of a configuration directive, this action produces an indeterminate result. It appears to issue ''some'' command, but the result is inconsistent with my expectation of ''middle-click.'' The result seems dependent on whichever object is foremost. It is inconsistent regardless. You need to enable the combination-click:<br />
<br />
# Emulate3Buttons refers to the act of pressing buttons A and D<br />
# simultaneously to emulate a middle-click or wheel click.<br />
Option "Emulate3Buttons" "true"<br />
<br />
This is sufficient to enable the default mapping of button '''2''', which is ''wheel-click''. See [[#Minimal configuration|minimal configuration]]. <br />
<br />
As at May 2012, there is an issue with [http://who-t.blogspot.com.au/2011/04/gnome-30-middle-mouse-button-emulation.html Gnome 3 and middle click emulation]. Gnome 3 is used, for example, in Ubuntu 12.04. Gnome 3 also sets the middle click property, and defaults to "false". Since Gnome does its settings '''after''' Xorg, the Gnome setting overrides the xorg setting, and emulation is disabled. The Gnome setting can be changed with this command:<br />
<br />
gsettings set org.gnome.settings-daemon.peripherals.mouse middle-button-enabled true<br />
<br />
You only need to do this once (per user) as Gnome remembers the settings between sessions. There is a [https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/874237/comments/13 launchpad bug] on the issue in case you are interested.<br />
<br />
==== Scroll modifier ====<br />
<br />
One huge limitation for the Marble Mouse is the lack of a scroll wheel or scroll ring. This limitation is overcome by assigning a ''scroll modifier'': a mouse button which allows the trackball to scroll. When the scroll modifier is held, the trackball scrolls. Although a scroll modifier is ''assigned'' by default (see [[#Basic function | basic function]]), the scroll modifier is '''not enabled''' by default. In addition to enabling the scroll modifier, you may ''also'' assign it to a different button.<br />
<br />
{{Note|The scroll button has a "click" function in addition to its scroll function. The scroll modifier is a "press and hold" function separate from the "click" function. The best choice for scroll modifier is one of the small buttons. Unfortunately, standard "click" actions for those buttons are awkward. I recommend you reassign click actions for the small buttons.}}<br />
<br />
The standard scroll setting defines the small button for scrolling — that is good, — but the same button has a default ''"click"'' action that is '''''browser back'''''. A better choice is '''''middle-click'''''. ''Middle-click'' corresponds to what you would expect from years of wheel mouse usage.<br />
<br />
Putting complaints aside (these are addressed by reassigning small buttons), you specify a button to be the '''''scroll modifier''''':<br />
<br />
Option "EmulateWheel" "true"<br />
Option "EmulateWheelButton" "8"<br />
<br />
# Button 8 is the small button on the left side, which works well for right-handed users.<br />
# Button 9 is the small button on the right side, which works well for left-handed users.<br />
# Button 2 cannot be assigned as the scroll modifier; AKA "EmulateWheelButton".<br />
<br />
'''Disable horizontal scrolling'''<br />
<br />
A particular configuration line enables horizontal scrolling. You disable horizontal scrolling by commenting that line out.<br />
<br />
# A hash mark disables a configuration line.<br />
<br />
# Option "XAxisMapping" "6 7"<br />
<br />
I use both scrolling directions, but some may find this restriction helpful. You cannot disable vertical scrolling in a similar fashion — not that you would want to, anyway.<br />
<br />
=== Right-side or left-side ===<br />
<br />
Previous sections explain how to modify your configuration file for either left or right placement.<br />
<br />
* On occasion, you may wish to switch between left-handed and right-handed usage.<br />
* I do this when I feel the early signs of repetitive strain injury.<br />
<br />
To switch to the opposite placement, I manually edit my configuration file and [[#Restarting X|restart the X server.]] Comments in the file remind me which lines to change. You could devise a script to make switching more automatic, if you wanted to.<br />
<br />
* With Arch Linux, I prefer a lightweight or non-existent desktop environment running the '''[[Openbox]]''' window manager.<br />
<br />
Other desktop environments may have widgets to simplify — or complicate, depending how you view it — switching between right and left. With Ubuntu 10.10, for example, you need only mark a box in the mouse control panel to effect a button switch. ''(You must change the configuration file to get the correct scroll modifier assignment, however. Also, Ubuntu ignores large button assignments in the configuration file; the control panel makes them unnecessary.)''<br />
<br />
=== System-wide or per-user ===<br />
<br />
{{Note| Section undergoing revision. Please jump to the sample configuration }}<br />
<br />
If you want the configuration to be system wide, you can add this line to the InputDevice-Section.<br />
<br />
Option "ButtonMapping" "1 8 3 2 9"<br />
<br />
For a per-user-configuration you need to put this in your ~/.Xmodmap<br />
<br />
pointer = 1 8 3 4 5 6 7 2 9 10 11 12 13<br />
<br />
or this in your ~/.xinitrc.<br />
<br />
xmodmap -e "pointer = 1 8 3 4 5 6 7 2 9 10 11 12 13"<br />
<br />
=== Xorg input hotplugging ===<br />
<br />
{{Note| Section undergoing revision. Please jump to the sample configuration }}<br />
<br />
Two expositions help you configure a trackball with buttons for click, middle-click, right-click, and scrolling. The first exposition uses [[Xorg Input Hotplugging]]; the second does not. Edit them to suit your preferences.<br />
<br />
Add this entry to your {{Ic|/etc/X11/xorg.conf}}:<br />
<br />
Section "InputClass"<br />
Identifier "Logitech Trackball"<br />
MatchProduct "Trackball"<br />
Option "ButtonMapping" "1 8 3 4 5 6 7 2 9"<br />
Option "EmulateWheel" "True"<br />
Option "EmulateWheelButton" "9"<br />
Option "XAxisMapping" "6 7"<br />
EndSection<br />
<br />
To learn more about the used parameters you should read the apropriate section in the evdev man page.<br />
<br />
=== Without Xorg hotplugging ===<br />
<br />
{{Note| Section undergoing revision. Please jump to the sample configuration }}<br />
<br />
The mouse device entry in {{Ic|/etc/X11/xorg.conf}} should look like this:<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "CorePointer"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "ExplorerPS/2"<br />
Option "Buttons" "9"<br />
Option "ZAxisMapping" "4 5"<br />
Option "XAxisMapping" "6 7"<br />
Option "EmulateWheelButton" "9"<br />
Option "EmulateWheel" "true"<br />
EndSection<br />
<br />
The {{Ic|"Auto"}} option for {{Ic|"Protocol"}} works fine, too.<br />
Of course you can use the name you prefer as the {{Ic|Identifier}}, as long as it is the same you use as {{Ic|InputDevice}} in the {{Ic|Section "ServerLayout"}} .<br />
<br />
== Sample configuration ==<br />
<br />
The sample configuration modifies and extends the [[#Basic function|basic function]] of the Marble Mouse.<br />
<br />
In this example, either of the two small buttons may be clicked to send a '''''wheel-click'''''. Wheel-click means the same as "middle-click" here. In addition, one of the small buttons provides '''''scrolling''''' in conjunction with the trackball. Note that only ''one'' small button has the ability for scrolling, although both small buttons are able to ''wheel-click.''<br />
<br />
Finally, clicking both large buttons simultaneously sends the '''''browser back''''' event. There is no button to send ''browser forward''.<br />
<br />
{| border="0"<br />
! ID !! Hardware Action !! Result (this configuration) !! New assignment<br />
|-<br />
| 1 || Large button left || normal click || 1<br />
|-<br />
| 2 || Both large buttons || browser back || 8<br />
|-<br />
| 3 || Large button right || right-click || 3<br />
|-<br />
| 8 || Small button left † || wheel-click || 2<br />
|-<br />
| 9 || Small button right ‡ || wheel-click || 2<br />
|}<br />
<br />
{{Note|<br />
* Both large buttons pressed simultaneously results in ''browser back''.<br />
* Either small button, when clicked, results in ''middle-click''.<br />
* † This small button allows trackball scrolling when held down. It is the scroll modifier.<br />
* ‡ This button can be mapped for scrolling function instead. This button works better for left-side placement because it lies near the thumb of one's left-hand. Only one button can be assigned as the scroll modifier as far as I know.}}<br />
<br />
=== Configuration file ===<br />
<br />
The following lines are appended to '''{{ic|/etc/X11/xorg.conf.d/10-evdev.conf}}'''.<br />
<br />
This example is set up for right-hand placement. Horizontal scrolling is disabled as well.<br />
<br />
# - - - Logitech Marble Mouse Settings - - -<br />
#<br />
# For the sake of comments below, a Logitech Marble Mouse has buttons<br />
# labeled from left to right: A (large), B, C, D (large). <br />
<br />
# Preferred options for right-handed usage are:<br />
# Left to right: A=1,normal click B=2,middle-click C=2,middle-click D=3,right-click<br />
# Press button B (hold button while rolling trackball) to emulate wheel-scrolling. <br />
<br />
# Preferred options for left-handed usage (saying 'alternate-click' instead of 'right click'):<br />
# Left to right: A=3,alternate-click B=2,middle-click C=2,middle-click D=1,normal click<br />
# Press button C (hold button while rolling trackball) to emulate wheel-scrolling.<br />
<br />
# The trackball can scroll in two-axes, unlike a typical wheel mouse. Adjust the<br />
# settings to constrain the scroll action to vertical-axis-only if you prefer.<br />
<br />
# Pressing both large buttons simultaneously (b) produces a "back" action (=8). Finally,<br />
# pressing and holding button B while rolling the trackball emulates wheel-rolling action.<br />
<br />
Section "InputClass"<br />
Identifier "Marble Mouse"<br />
MatchProduct "Logitech USB Trackball"<br />
MatchIsPointer "on"<br />
MatchDevicePath "/dev/input/event*"<br />
Driver "evdev"<br />
# Physical button #s: A b D - - - - B C b = A & D simultaneously; - = no button<br />
Option "ButtonMapping" "1 8 3 4 5 6 7 2 2"<br />
# Option "ButtonMapping" "1 8 3 4 5 6 7 2 2" # For right-hand placement<br />
# Option "ButtonMapping" "3 8 1 4 5 6 7 2 2" # For left-hand placement<br />
#<br />
# EmulateWheel refers to emulating a mouse wheel using Marble Mouse trackball.<br />
Option "EmulateWheel" "true"<br />
# Option "EmulateWheelButton" "8" # Factory default; use "9" for left-side placement.<br />
Option "EmulateWheelButton" "8"<br />
# Option "ZAxisMapping" "4 5"<br />
Option "ZAxisMapping" "4 5"<br />
# Option "XAxisMapping" "6 7" # Disable this for vertical-only scrolling.<br />
# Option "XAxisMapping" "6 7"<br />
# Emulate3Buttons refers to the act of pressing buttons A and D<br />
# simultaneously to emulate a middle-click or wheel click.<br />
Option "Emulate3Buttons" "true"<br />
# Option "Emulate3Buttons" "true" # Factory default.<br />
EndSection<br />
<br />
=== Restarting X ===<br />
<br />
Changes made to '''{{ic|/etc/X11/xorg.conf.d/10-evdev.conf}}''' do not take effect until the '''X''' session is restarted. To restart the X session, logout from your window manager and log back in.<br />
<br />
Users of other Linux distributions may find the configuration file in another location. Ubuntu 10.10 uses '''{{ic|/usr/share/X11/xorg.conf.d/10-evdev.conf}}'''.<br />
<br />
== Minimal configuration ==<br />
<br />
At times it can be useful to start with the absolute minimum and build from there. This is one facet of [[The_Arch_Way|The Arch Way]]. In this spirit, I decided to see how few lines I might use to create a usable Marble Mouse configuration.<br />
<br />
You can omit ''all'' configuration lines and the Marble Mouse is still usable for basic pointing and clicking. However, it will not be able to scroll. The "both-large-button" simultaneous click produces indeterminate results — experimentation shows this.<br />
<br />
Given that you are satisfied with [[#Basic function|default button settings]] and you wish only to enable scrolling and the "both-large-button" click, you need these lines. The following lines are appended to '''{{ic|/etc/X11/xorg.conf.d/10-evdev.conf}}'''.<br />
<br />
Section "InputClass"<br />
Identifier "Marble Mouse"<br />
MatchProduct "Logitech USB Trackball"<br />
Option "EmulateWheel" "true"<br />
Option "EmulateWheelButton" "8"<br />
Option "XAxisMapping" "6 7"<br />
Option "Emulate3Buttons" "true"<br />
EndSection<br />
<br />
== Additional tweaks ==<br />
<br />
=== Console (gpm) ===<br />
<br />
See [[Console_Mouse_Support | Console Mouse Support]] for details. Within the console you can use {{Ic|gpm}} with type option set to '''imps2'''. Edit '''{{ic|/etc/conf.d/gpm}}''' such that:<br />
<br />
GPM_ARGS="-m /dev/input/mice -t imps2"<br />
<br />
This lets you use the large left button for selecting text and the right button to extend the selection. The small left button acts as a middle-click; it pastes the selection.<br />
<br />
=== Chromium browser ===<br />
<br />
By default, Chromium treats a middle-click as a ''paste'' command. This choice stems from "Linux tradition", not the capricious whim of one developer. Like myself, you may prefer a '''''Windows''''' approach. I want the middle button(s) to initiate ''automatic scrolling,'' not ''pasting'':<br />
<br />
* A browser extension '''AutoScroll''' allows middle-click to initiate automatic scrolling.<br />
* This extension is helpful for any Linux user with a wheel mouse, not just Marble Mouse users.<br />
* A middle-click initiates automatic scrolling when clicked on a blank area of a web page.<br />
<br />
* When you program both small buttons to emit middle-click, either button can initiate automatic scrolling. That is a click function.<br />
* When you program one of the small buttons to act as scroll modifier (mouse setup), you can manually scroll web pages '''without''' fixing the browser. That is a press‑and‑hold function. (I recommend installing AutoScroll even though it is not absolutely necessary for scrolling.)<br />
* After you assign the scroll modifier to one of the small buttons, the small buttons act a bit differently from one another. The difference is seen when you compare their "press‑and‑hold" behaviors.<br />
<br />
Be sure to install '''''AutoScroll'''''; the similarly-named ''Auto Scroll'' extension implements a different feature.<br />
<br />
This information also applies to the browser called '''Google Chrome'''.<br />
<br />
=== Firefox browser ===<br />
<br />
Older versions of Firefox map horizontal-scrolling hardware to perform '''''browser back''''' and '''''browser forward''''' navigation.<br />
<br />
This makes vertical scrolling using the trackball almost impossible.<br />
<br />
The slightest horizontal motion triggers a URL redirection. To fix this:<br />
<br />
* Enter {{Ic|about:config}} in the location bar<br />
* Find the internal variable named {{Ic|mousewheel.horizscroll.withnokey.action}}. Set its value to '''0'''.<br />
* It may be useful to set {{Ic|mousewheel.horizscroll.withnokey.numlines}} to '''1''' as well.<br />
<br />
== See also ==<br />
* Arch wiki documentation: [[All Mouse Buttons Working | All mouse buttons working]]<br />
* Arch wiki documentation: [[Xorg#Configuring | Description of 10-evdev.conf]]<br />
* Marble mouse scroll wheel: [http://simans.net/marble/ Replacement for SetPoint driver]<br />
* Joe Shaw blog post: [http://joeshaw.org/2010/10/01/681/ Linux input ecosystem]<br />
* Ubuntu community: [https://help.ubuntu.com/community/Logitech_Marblemouse_USB Logitech Marble Mouse]<br />
* Chrome web store: [https://chrome.google.com/webstore/detail/occjjkgifpmdgodlplnacmkejpdionan AutoScroll extension]</div>Catlover2https://wiki.archlinux.org/index.php?title=User:Catlover2&diff=246008User:Catlover22013-02-02T09:25:00Z<p>Catlover2: </p>
<hr />
<div>Amazing! I didn't think anyone would even read this!<br />
<br />
Anyway, I'm just a person on the Internet who likes cats. I switched from Windows XP (Hint: Missing Operating System Press CTRL+ALT+DEL to restart.) to Ubuntu 9.10 in early 2009, then to Arch sometime in late 2011.</div>Catlover2https://wiki.archlinux.org/index.php?title=Scrollback_buffer&diff=245912Scrollback buffer2013-02-01T18:50:55Z<p>Catlover2: </p>
<hr />
<div>[[Category:Terminal emulators]]<br />
Scrollback is a function that is implemented in a text console to allow the user to go back to view the lines of text which have scrolled off the screen. This is made possible by a buffer created just for this purpose between the video adapter and the display device; the scrollback buffer. Normally, the key combinations of Shift-PageUp or Shift-PageDown allows the user to scroll up or down a page or two by default.<br />
<br />
However, what if one wishes to keep track of more than that small amount? During boot this is particularly necessary, as the text scrolls off by quite a few pages. To solve this need, the scrollback buffer must be increased. It is a simple process to do so.<br />
<br />
The basic buffer size is 32K, equal to approximately 4 half pages of text. The easy way to increase this is to use a device called fbcon (the framebuffer console). To find out about fbcon, this [http://www.mjmwired.net/kernel/Documentation/fb/fbcon.txt link] can give you more information. Just follow these instructions.<br />
<br />
== The Easy Way ==<br />
Edit the appropriate kernel line as used by your bootloader (e.g. {{ic|/boot/grub/grub.cfg}} for [[GRUB]], or {{ic|/boot/syslinux/syslinux.cfg}} for [[syslinux]]). Make the following changes:<br />
* If {{ic|vga&#61;XXX}} exists, delete it. <br />
* Append {{ic|XXXfb}}, replacing XXX with the name of your video driver.<br />
* Append {{ic|fbcon&#61;scrollback:Nk}}, where N is the amount of scrollback desired.<br />
Then reboot.</div>Catlover2https://wiki.archlinux.org/index.php?title=User_talk:Catlover2&diff=245911User talk:Catlover22013-02-01T18:48:19Z<p>Catlover2: Created page with "I just didn't want this page to be a redlink. --~~~~"</p>
<hr />
<div>I just didn't want this page to be a redlink. --[[User:Catlover2|Catlover2]] ([[User talk:Catlover2|talk]]) 18:48, 1 February 2013 (UTC)</div>Catlover2https://wiki.archlinux.org/index.php?title=User:Catlover2&diff=245910User:Catlover22013-02-01T18:46:45Z<p>Catlover2: Created page with "Amazing! I didn't think anyone would even read this! Anyway, I'm just a person on the Internet who likes cats. I switched from Windows XP (Hint: Missing Operating System Pres..."</p>
<hr />
<div>Amazing! I didn't think anyone would even read this!<br />
<br />
Anyway, I'm just a person on the Internet who likes cats. I switched from Windows XP (Hint: Missing Operating System Press CTRL+ALT+DEL to restart.) to Ubuntu 9.10 in late 2009, then to Arch sometime in late 2011.</div>Catlover2