The simple-scan package on SlackBuilds.org lists two dependencies: vala and libgusb. If you look at the README via sbopkg, it lists them as libgusb and vala. Order is important in this case. vala has to be installed first for simple-scan to compile properly as libgusb apparently has some vala hooks that simple-scan relies upon. If you build libgusb first and then vala, simple-scan's build will report an error (I didn't keep track of the exact error message, but it amounted to libgusb not having some sort of vala reference). Re-building libgusb resolved the issue for me.
Showing posts with label slackware. Show all posts
Showing posts with label slackware. Show all posts
Sunday, February 12, 2017
Saturday, December 6, 2014
GNOME Orca on Slackware 14.1
On Slackware 14.1 I wanted to get Orca up and running without a full GNOME install just like I had in the past with 13.37. With the GNOME Slackbuilds project no longer active I took a different route.
From Slackbuilds.org I installed the following packages because I am going to be using espeak as my speech synthesizer:
I got everything else from the dropline GNOME project. I am only installing selected packages from their 3.10 packages just to get Orca running, but you could simply use their installer to install the full GNOME desktop for an overall better accessibility experience on the desktop.
Download and install/upgrade the following packages from their 3.10 site:
How you rebuild speech-dispatcher is up to you. I was playing around with some alternate instructions I found before I just used the dropline packages. Since I still had Aiyumi's slackbuilds on my system I modified the speech-dispatcher slackbuild to install 0.8.1 and build it that way. Orca 3.10 requires speech-dispatcher 0.8 or greater which is why I had to change the version.
On a final note, Firefox on Slackware is built without accessibility support enabled. You either need to rebuild after modifying Patrick's slackbuild to enable it, or you just need to download it directly. I do the latter, but I us Ruario's latest-firefox script in order to repackage it as a Slackware package.
From Slackbuilds.org I installed the following packages because I am going to be using espeak as my speech synthesizer:
I got everything else from the dropline GNOME project. I am only installing selected packages from their 3.10 packages just to get Orca running, but you could simply use their installer to install the full GNOME desktop for an overall better accessibility experience on the desktop.
Download and install/upgrade the following packages from their 3.10 site:
- at-spi2-atk-2.10.2-x86_64-1dl (use upgradepkg)
- at-spi2-core-2.10.2-x86_64-1dl (use upgradepkg)
- atk-2.10.0-x86_64-1dl (use upgradepkg)
- dotconf-1.3-x86_64-1dl
- glib2-2.38.2-x86_64-1dl (use upgradepkg)
- gobject-introspection-1.38.0-x86_64-1dl (use upgradepkg)
- orca-3.10.2-x86_64-1dl
- py3gobject-3.10.2-x86_64-1dl
- pyatspi-2.10.0-x86_64-1dl
- pygobject3-3.10.2-x86_64-1dl (use upgradepkg)
- python3-3.3.2-x86_64-1dl
How you rebuild speech-dispatcher is up to you. I was playing around with some alternate instructions I found before I just used the dropline packages. Since I still had Aiyumi's slackbuilds on my system I modified the speech-dispatcher slackbuild to install 0.8.1 and build it that way. Orca 3.10 requires speech-dispatcher 0.8 or greater which is why I had to change the version.
On a final note, Firefox on Slackware is built without accessibility support enabled. You either need to rebuild after modifying Patrick's slackbuild to enable it, or you just need to download it directly. I do the latter, but I us Ruario's latest-firefox script in order to repackage it as a Slackware package.
Thursday, September 5, 2013
Slackware 14 & Epson XP-410
We replaced our old Multifunction Printer (MFP). I looked for an affordable replacement compatible with Linux (specifically Slackware), OS X, and Windows. I chose the Epson XP-410 printer. Epson provides Linux drivers on their website, research indicated it works perfectly with Linux, and I found it on sale locally.
The OS X and Windows installs were done via the Epson provided software. So what about Slackware?
Slackware 14 does not ship with a PPD file for the XP-410. I went to SlackBuilds.org and found the epson-inkjet-printer-escpr package, which corresponds to the driver I saw on the Epson site. However, the source URL provided does not exist. So I downloaded the epson-inkjet-printer-escpr-1.2.3-1lsb3.2.tar.gz source from Epson.
I used the CUPS localhost:631 web interface for setup. I set it up as a AppSocket/JetDirect network printer as it is not directly connected to my machine. The XP-410 PPD from the installed package showed up as expected. I added the printer and the test page was successful.
I use SimpleScan for scanning and the XP-410 did not show up as an available scanner unless I disable my firewall. I did some poking around, expecting to have to add a firewall rule, but found that adding 'net <printer ip address>' to /etc/sane.d/epson2.conf was the only thing necessary to get it to work.
Overall, setup was pretty simple within the context of Slackware. Other distributions may ship the PPD's by default. I tried the openSUSE 12.3 Live CD. The package is available in their repository, but does not come with the XP-410 driver. Epson indicates the XP-410 is "new" so I assume openSUSE 12.3 shipped before the driver was released (I failed to note the installed version).
I am pleased with the purchase as far as OS compatibility and setup goes. I have not used it enough to comment on it as a MFP in general, but initial use has been satisfactory.
On a tangent, for those reading this newer to Slackware and/or Slackbuilds.org, I use Sbopkg to manage my SlackBuilds.org packages. As mentioned, I downloaded the source from Epson and placed it in /var/cache/sbopkg. In Sbopkg, I edited the Slackbuild and Info files for the package to use the downloaded source. In the Slackbulid script, I changed the version from 1.2.2 to 1.2.3. In the Info file, I made the same version change everywhere I saw it, and I changed the MD5SUM to match the downloaded source MD5SUM. The MD5SUM is not required, but it eliminates a warning during the build and install process. After that, the build and install worked fine.
The OS X and Windows installs were done via the Epson provided software. So what about Slackware?
Slackware 14 does not ship with a PPD file for the XP-410. I went to SlackBuilds.org and found the epson-inkjet-printer-escpr package, which corresponds to the driver I saw on the Epson site. However, the source URL provided does not exist. So I downloaded the epson-inkjet-printer-escpr-1.2.3-1lsb3.2.tar.gz source from Epson.
I used the CUPS localhost:631 web interface for setup. I set it up as a AppSocket/JetDirect network printer as it is not directly connected to my machine. The XP-410 PPD from the installed package showed up as expected. I added the printer and the test page was successful.
I use SimpleScan for scanning and the XP-410 did not show up as an available scanner unless I disable my firewall. I did some poking around, expecting to have to add a firewall rule, but found that adding 'net <printer ip address>' to /etc/sane.d/epson2.conf was the only thing necessary to get it to work.
Overall, setup was pretty simple within the context of Slackware. Other distributions may ship the PPD's by default. I tried the openSUSE 12.3 Live CD. The package is available in their repository, but does not come with the XP-410 driver. Epson indicates the XP-410 is "new" so I assume openSUSE 12.3 shipped before the driver was released (I failed to note the installed version).
I am pleased with the purchase as far as OS compatibility and setup goes. I have not used it enough to comment on it as a MFP in general, but initial use has been satisfactory.
On a tangent, for those reading this newer to Slackware and/or Slackbuilds.org, I use Sbopkg to manage my SlackBuilds.org packages. As mentioned, I downloaded the source from Epson and placed it in /var/cache/sbopkg. In Sbopkg, I edited the Slackbuild and Info files for the package to use the downloaded source. In the Slackbulid script, I changed the version from 1.2.2 to 1.2.3. In the Info file, I made the same version change everywhere I saw it, and I changed the MD5SUM to match the downloaded source MD5SUM. The MD5SUM is not required, but it eliminates a warning during the build and install process. After that, the build and install worked fine.
Monday, August 1, 2011
GNOME Orca on Slackware 13.37
I am trying to learn more about web accessibility. Since I am a Linux user, GNOME Orca with Firefox is the route to go (right now at least). The only problem with that for me is that I am a Slackware user right now and GNOME is not available out of the box on Slackware. Plus I do not really want a full GNOME install, I would prefer to just install Orca and the components needed by it.
Thankfully, the GNOME SlackBuild project makes this relatively easy to do. The first thing you want to do is to install slapt-get using their manual instructions. I am running Slackware 13.37 but I used the 13.1 64-bit package (I was having trouble getting this going with the work-in-progress that they had for Slackware 13.37). I did not have to worry about any of the configuration, it worked out of the box as is, however you still need to update it:
slapt-get --update
slapt-get --add-keys
Once that is done, you can install Orca itself via slapt-get:
slapt-get --install orca
This installed the following packages:
GConf-2.28.1-x86_64-1gsb
gnome-keyring-2.28.2-x86_64-1gsb
gnome-vfs-2.24.3-x86_64-1gsb
libgnomeui-2.24.3-x86_64-1gsb
at-spi-1.30.1-x86_64-1gsb
espeak-1.43.03-x86_64-1gsb
gail-1.22.3-x86_64-3gsb
gnome-mag-0.16.1-x86_64-1gsb
gnome-speech-0.4.25-x86_64-4gsb
libgail-gnome-1.20.3-x86_64-1gsb
ORBit2-2.14.18-x86_64-1gsb
gnome-mime-data-2.18.0-x86_64-3gsb
libbonobo-2.24.3-x86_64-1gsb
libbonoboui-2.24.3-x86_64-1gsb
libdaemon-0.14-x86_64-1gsb
libgnome-2.30.0-x86_64-1gsb
libgnomecanvas-2.30.1-x86_64-1gsb
libtasn1-2.7-x86_64-1gsb
portaudio-V19-x86_64-1gsb
pyorbit-2.24.0-x86_64-2gsb
speex-1.2rc1-x86_64-3gsb
avahi-0.6.27-x86_64-1gsb
orca-2.30.2-x86_64-1gsb
There is one more package that is needed that was not installed:
slapt-get --install gnome-python
Which will just install gnome-python-2.28.1-x86_64-1gsb. I did have to reboot after all of this to get Orca to run. There was probably something else that could be done but I took the quick and easy route for that part.
Next there is a gconf2 setting needed that I found on the Orca mailing list:
gconftool-2 --set /desktop/gnome/interface/accessibility --type boolean true
Once that is set you should be able to run Orca from a terminal to go through its setup. After that Orca should run just fine if you are running KDE (as I am) due to the dbus dependency. But you can just run Orca with dbus-launch if you are running something like Fluxbox (I am currently testing it in Fluxbox as I type this).
There is one final issue. Orca is relatively useless without applications that provide it the necessary information. Firefox normally would do this but Pat's SlackBuild script configures it with the --disable-accessibility option. So you either need to alter the SlackBuild script to enable accessibility and rebuild the package or just download Firefox from its site (this is what I did as I didn't want to wait for the build) and you will be set.
I don't have much experience at all with using screen readers so I cannot comment on how well Orca works compared to others, but it is reading Firefox for me and should be good enough to validate accessibility techniques for me.
On a side note, I did try Orca on a couple of other distros just in case I wanted to switch for this reason or at least dual boot. I was happy that I got it working on Slackware though. But Orca Ubuntu 11.04 worked great out of the box for me in both fallback and Unity (once again, I don't have experience with screen readers so my assessment may not reflect reality for someone that has to depend on this technology). It worked relatively well on Fedora 15 as well with Gnome 3 but I did have to set the gconf setting manually there.
So I consider this a success for my purposes (a sighted developer looking to learn more about accessibility).
Thankfully, the GNOME SlackBuild project makes this relatively easy to do. The first thing you want to do is to install slapt-get using their manual instructions. I am running Slackware 13.37 but I used the 13.1 64-bit package (I was having trouble getting this going with the work-in-progress that they had for Slackware 13.37). I did not have to worry about any of the configuration, it worked out of the box as is, however you still need to update it:
slapt-get --update
slapt-get --add-keys
Once that is done, you can install Orca itself via slapt-get:
slapt-get --install orca
This installed the following packages:
GConf-2.28.1-x86_64-1gsb
gnome-keyring-2.28.2-x86_64-1gsb
gnome-vfs-2.24.3-x86_64-1gsb
libgnomeui-2.24.3-x86_64-1gsb
at-spi-1.30.1-x86_64-1gsb
espeak-1.43.03-x86_64-1gsb
gail-1.22.3-x86_64-3gsb
gnome-mag-0.16.1-x86_64-1gsb
gnome-speech-0.4.25-x86_64-4gsb
libgail-gnome-1.20.3-x86_64-1gsb
ORBit2-2.14.18-x86_64-1gsb
gnome-mime-data-2.18.0-x86_64-3gsb
libbonobo-2.24.3-x86_64-1gsb
libbonoboui-2.24.3-x86_64-1gsb
libdaemon-0.14-x86_64-1gsb
libgnome-2.30.0-x86_64-1gsb
libgnomecanvas-2.30.1-x86_64-1gsb
libtasn1-2.7-x86_64-1gsb
portaudio-V19-x86_64-1gsb
pyorbit-2.24.0-x86_64-2gsb
speex-1.2rc1-x86_64-3gsb
avahi-0.6.27-x86_64-1gsb
orca-2.30.2-x86_64-1gsb
There is one more package that is needed that was not installed:
slapt-get --install gnome-python
Which will just install gnome-python-2.28.1-x86_64-1gsb. I did have to reboot after all of this to get Orca to run. There was probably something else that could be done but I took the quick and easy route for that part.
Next there is a gconf2 setting needed that I found on the Orca mailing list:
gconftool-2 --set /desktop/gnome/interface/accessibility --type boolean true
Once that is set you should be able to run Orca from a terminal to go through its setup. After that Orca should run just fine if you are running KDE (as I am) due to the dbus dependency. But you can just run Orca with dbus-launch if you are running something like Fluxbox (I am currently testing it in Fluxbox as I type this).
There is one final issue. Orca is relatively useless without applications that provide it the necessary information. Firefox normally would do this but Pat's SlackBuild script configures it with the --disable-accessibility option. So you either need to alter the SlackBuild script to enable accessibility and rebuild the package or just download Firefox from its site (this is what I did as I didn't want to wait for the build) and you will be set.
I don't have much experience at all with using screen readers so I cannot comment on how well Orca works compared to others, but it is reading Firefox for me and should be good enough to validate accessibility techniques for me.
On a side note, I did try Orca on a couple of other distros just in case I wanted to switch for this reason or at least dual boot. I was happy that I got it working on Slackware though. But Orca Ubuntu 11.04 worked great out of the box for me in both fallback and Unity (once again, I don't have experience with screen readers so my assessment may not reflect reality for someone that has to depend on this technology). It worked relatively well on Fedora 15 as well with Gnome 3 but I did have to set the gconf setting manually there.
So I consider this a success for my purposes (a sighted developer looking to learn more about accessibility).
Subscribe to:
Posts (Atom)