headers
Matthew Weier O'Phinney | 1 Jul 2002 17:53

truetype fonts

I'm using ROX-1.2.0 on a Debian (unstable) machine. I use Blackbox as my
window manager (currently 0.65 alpha8), and ROX as my desktop/file
manager. I've had some incarnation of this setup for a few months now,
and everything has run as I needed.

Over the weekend, I added xfstt to my setup -- the TrueType Font Server
for X11 (Debian package xfstt). I followed the instructions in the
mini-HOWTO for using TrueType with Debian, and added the following lines
to my XF86Config:

   Under the Modules section:
        Load "xtt"

   Under the Files section:
        FontPath   "unix/:7101"
        FontPath   "unix/:7100"

TrueType now works in all my applications.

However, I noticed something buggy with ROX: when I try to use the
"Enter Path" command (either via menu or using the "/" key), ROX dies. I
checked to make sure this was related to the TrueType fonts by disabling
the 2 FontPath statements in my XF86Config and discovered that ROX then
worked correctly.

Has anybody else noticed this? Is there a patch already available? Or
should I upgrade to the 1.3.0 development branch?

Thanks!
Matthew
(Continue reading)

Permalink | Reply | 11 comments |
headers
Matthew Weier O'Phinney | 1 Jul 2002 18:13

Re: truetype fonts

As a followup...
I have changed the XF86Config file to have the 
    FontPath "unix/:7101" 
line at the end of the FontPath list -- which means that if a match is
found in the Type1 fonts first, that's what an application will use
(reading some other howtos indicated that I did not need both unix/:710*
lines). 

Even with this change (i.e., ROX now uses the appropriate Type1 fonts),
ROX mis-behaves and crashes when I try to use the Enter Path command.

--Matthew

On Mon, 2002-07-01 at 11:53, Matthew Weier O'Phinney wrote:
> I'm using ROX-1.2.0 on a Debian (unstable) machine. I use Blackbox as my
> window manager (currently 0.65 alpha8), and ROX as my desktop/file
> manager. I've had some incarnation of this setup for a few months now,
> and everything has run as I needed.
> 
> Over the weekend, I added xfstt to my setup -- the TrueType Font Server
> for X11 (Debian package xfstt). I followed the instructions in the
> mini-HOWTO for using TrueType with Debian, and added the following lines
> to my XF86Config:
> 
>    Under the Modules section:
>         Load "xtt"
> 
>    Under the Files section:
>         FontPath   "unix/:7101"
>         FontPath   "unix/:7100"
(Continue reading)

Permalink | Reply | 10 comments |
headers
Thomas Leonard | 1 Jul 2002 22:13
Picon
Favicon

Re: truetype fonts

On Mon, Jul 01, 2002 at 12:13:57PM -0400, Matthew Weier O'Phinney wrote:
> As a followup...
> I have changed the XF86Config file to have the 
>     FontPath "unix/:7101" 
> line at the end of the FontPath list -- which means that if a match is
> found in the Type1 fonts first, that's what an application will use
> (reading some other howtos indicated that I did not need both unix/:710*
> lines). 
> 
> Even with this change (i.e., ROX now uses the appropriate Type1 fonts),
> ROX mis-behaves and crashes when I try to use the Enter Path command.

What happens if you run it as 'rox --debug' (see Developers section of
website for details)?

It's probably looking for the 'fixed' font, although why that should fail
I don't know...

The ROX-Filer 1.3.x series all have a completely different font system, so
you could try that instead...

--

-- 
Thomas Leonard			http://rox.sourceforge.net
tal00r <at> ecs.soton.ac.uk		tal197 <at> users.sourceforge.net
Permalink | Reply | 9 comments |
headers
Thomas Leonard | 3 Jul 2002 00:30
Picon
Favicon

ROX-Filer 1.2.1

I've put up the 1.2.1 release of the filer now:

http://rox.sourceforge.net/rox_download.php3

This has a security fix! If you're using the filer on a multi-user system
then you'll want to upgrade. The developer release is also affected (CVS
is fixed).

chmod go-x ~/Choices

might be a good workaround...

Backported fixes in this release:

- Set Run Action to a shell command would make the executable
  world-writeable (spotted by alexander).
- Short form of '--client-id' option didn't work (reported by Julio Hugo
  Toloza).
- Fixed compile problem with libxml's parser.h.
- More robust approach to SOAP errors.
- Drop Gtk+-2.0 support (didn't work with stable Gtk+ release anyway; use
  ROX-Filer 1.3.x instead).
- When copying directories, ignore an error caused by filesystems,
  such as Samba shares, that don't support chmod fully (reported by
  Andrew S Dixon).
- Using another window in between entering target mode and selecting
  the target printed a warning instead of performing the operation.

--

-- 
Thomas Leonard			http://rox.sourceforge.net
(Continue reading)

Permalink | Reply | 0 comments |
headers
Enno Lenze | 3 Jul 2002 01:56
Picon

Re: ROX-Filer 1.2.1

On Tue, Jul 02, 2002 at 11:30:05PM +0100, Thomas Leonard wrote:
> http://rox.sourceforge.net/rox_download.php3

thats really cool, but i'Ve git still the problem,that i've deletet my
./Choice and don't know how to get it back. a re-install didn'T work. So
waht can i do?

regards, enno
--

-- 
WWW: http://www.handverbrennung.de
ICQ: #126972554
Interessantes: http://www.y0ah.tk
Permalink | Reply | 0 comments |
headers
Thomas Leonard | 3 Jul 2002 13:46
Picon
Favicon

Re: Illegal instruction

On Sun, Jun 30, 2002 at 05:38:02PM +0200, Enno Lenze wrote:
> Hello!
> I'm using rox since a few days. After i intalled the debian package
> (via apt-get), and trying it, i tried to get the least version from the
> page. After the installation rox won't start because of a wrong
> ./Choices/rox/Options 
> so i tried to edit it, but i failed. after that i removed the whole
> ./Choices folder and uninstalled rox. Then i re-installed it, hopeing
> that it will set the right 'Options'. But it didn't.
> Now, if i want to start rox it says 'Illegal instruction'
> What did i wron, how can i fix it?

Well, it should never say that! Try running with --debug to see what's
causing the trouble.

Eg:

	$ rox --debug
	(gdb) run -n
	Starting program:...
	[crash!]
	(gdb) backtrace
	[useful information here]

Send us that and I'll take a look...

--

-- 
Thomas Leonard			http://rox.sourceforge.net
tal00r <at> ecs.soton.ac.uk		tal197 <at> users.sourceforge.net
(Continue reading)

Permalink | Reply | 1 comment |
headers
Enno Lenze | 3 Jul 2002 14:58
Picon

Re: Illegal instruction

On Wed, Jul 03, 2002 at 12:46:45PM +0100, Thomas Leonard wrote:
> > ./Choices/rox/Options 

thanks :-)

---
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-linux"...(no debugging symbols
found)...
(gdb) backtrace
No stack.
(gdb) 
---

regards, enno

--

-- 
WWW: http://www.handverbrennung.de
ICQ: #126972554
Interessantes: http://www.y0ah.tk
Permalink | Reply | 0 comments |
headers
Matthew Weier O'Phinney | 3 Jul 2002 15:11

Re: truetype fonts

On Mon, 2002-07-01 at 16:13, Thomas Leonard wrote:
> On Mon, Jul 01, 2002 at 12:13:57PM -0400, Matthew Weier O'Phinney wrote:
> > As a followup...
> > I have changed the XF86Config file to have the 
> >     FontPath "unix/:7101" 
> > line at the end of the FontPath list -- which means that if a match is
> > found in the Type1 fonts first, that's what an application will use
> > (reading some other howtos indicated that I did not need both unix/:710*
> > lines). 
> > 
> > Even with this change (i.e., ROX now uses the appropriate Type1 fonts),
> > ROX mis-behaves and crashes when I try to use the Enter Path command.
> 
> What happens if you run it as 'rox --debug' (see Developers section of
> website for details)?
I tried this this morning. Basically, ROX locks up, and then I have to
kill it (using the Blackbox window's "Kill Client" option). When I run a
backtrace, I get the message "No Stack".

> 
> It's probably looking for the 'fixed' font, although why that should fail
> I don't know...
> 
> The ROX-Filer 1.3.x series all have a completely different font system, so
> you could try that instead...
I'll try this later.

> 
> 
> --
(Continue reading)

Permalink | Reply | 8 comments |
headers
Matthew Weier O'Phinney | 4 Jul 2002 16:06

Re: truetype fonts -- Now keyboard shortcuts

I just tried 1.3, and the problem with Enter Path is solved.

However, something new to note: 
In 1.2, I could enter keyboard shortcuts for the menu items, and they
would stick for the current session; once I exited X and came back in,
however, they would be gone.

In 1.3, following the directions for creating keyboard shortcuts, they
simply do not take -- no shortcuts are registered...

--Matthew

On Wed, 2002-07-03 at 09:11, Matthew Weier O'Phinney wrote:
> On Mon, 2002-07-01 at 16:13, Thomas Leonard wrote:
> > On Mon, Jul 01, 2002 at 12:13:57PM -0400, Matthew Weier O'Phinney wrote:
> > > As a followup...
> > > I have changed the XF86Config file to have the 
> > >     FontPath "unix/:7101" 
> > > line at the end of the FontPath list -- which means that if a match is
> > > found in the Type1 fonts first, that's what an application will use
> > > (reading some other howtos indicated that I did not need both unix/:710*
> > > lines). 
> > > 
> > > Even with this change (i.e., ROX now uses the appropriate Type1 fonts),
> > > ROX mis-behaves and crashes when I try to use the Enter Path command.
> > 
> > What happens if you run it as 'rox --debug' (see Developers section of
> > website for details)?
> I tried this this morning. Basically, ROX locks up, and then I have to
> kill it (using the Blackbox window's "Kill Client" option). When I run a
(Continue reading)

Permalink | Reply | 7 comments |
headers
Panagiotis Vossos | 4 Jul 2002 18:09
Picon

problem compiling rox 1.2.1

I tried to compile rox 1.2.1 on my system and got the following error:

creating cache ./config.cache
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for xml2-config... xml2-config
checking that gtk-config runs... yes
checking for gdk-pixbuf library... yes - use '-L/usr/lib -lgdk_pixbuf -L/usr/lib -L/usr/X11R6/lib
-lgtk -lgdk -rdynamic -lgmodule -lglib -ldl -lXext -lX11 -lm'
checking that xml2-config runs... yes
checking whether file -b works... yes
checking for large file support... yes
checking how to run the C preprocessor... gcc -E
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for dirent.h that defines DIR... yes
checking for opendir in -ldir... no
checking for ANSI C header files... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for fcntl.h... yes
checking for sys/time.h... yes
checking for unistd.h... yes
checking for mntent.h... yes
checking for sys/ucred.h... no
checking for sys/mntent.h... no
checking for regex.h... yes
checking for iconv.h... yes
checking for working const... yes
(Continue reading)

Permalink | Reply | 2 comments |

Gmane