Re: xlib problem

2002-04-03 Thread Sean 'Shaleh' Perry

On 03-Apr-2002 Marcelo Chiapparini wrote:
> Hello!
> 
> sometimes I get the message "locale 'en_US.ISO-8859-1' not supported by Xlib"
> 
> how can I fix it?
> 
> Thanks!
> 

edit /etc/locale.gen and add 'en_US ISO-8859-1' then run locale-gen as root.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



xlib problem

2002-04-03 Thread Marcelo Chiapparini
Hello!

sometimes I get the message "locale 'en_US.ISO-8859-1' not supported by Xlib"

how can I fix it?

Thanks!

Marcelo
-- 
Marcelo Chiapparini
DFT-IF/UERJ
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: xlib problem

2001-09-26 Thread Branden Robinson
On Wed, Sep 26, 2001 at 04:25:49AM -0500, Colin Watson wrote:
> On Tue, Sep 25, 2001 at 10:04:45PM -0400, Brian Schramm wrote:
> > Unpacking replacement xlibs ...
> > dpkg: error processing /var/cache/apt/archives/xlibs_4.1.0-6_i386.deb
> > (--unpack):
> >  trying to overwrite `/usr/X11R6/include/X11/pixmaps/mouse.xpm', which is
> > also in package qcad
> > dpkg-deb: subprocess paste killed by signal (Broken pipe)
> 
> This bug was already fixed in qcad 1.4.6-1, so once you upgrade to that
> version you should be fine - but perhaps xlibs should replace qcad (<<
> 1.4.6-1) to make this easier? Cc'd to debian-x for comments.

Will be taken care of in 4.1.0-7.

-- 
G. Branden Robinson|  We either learn from history or,
Debian GNU/Linux   |  uh, well, something bad will
[EMAIL PROTECTED] |  happen.
http://people.debian.org/~branden/ |  -- Bob Church


pgpsve5qGWZXo.pgp
Description: PGP signature


Re: xlib problem

2001-09-26 Thread Colin Watson
On Tue, Sep 25, 2001 at 10:04:45PM -0400, Brian Schramm wrote:
> I am still trying to upgrade from potato to woody.  With a modem this is a
> panfull process at best.  Here it is 4 days latter and now I cannot get
> anywhere with it.  Here is the error message that I get.
> 
> Moving old app-defaults file XmAddressBook to
> /etc/X11/app-defaults/XmAddressBook.xlibs-old.
> Moving old app-defaults file XRn to /etc/X11/app-defaults/XRn.xlibs-old.
> Moving old app-defaults file Atmidi to
> /etc/X11/app-defaults/Atmidi.xlibs-old.
> Unpacking replacement xlibs ...
> dpkg: error processing /var/cache/apt/archives/xlibs_4.1.0-6_i386.deb
> (--unpack):
>  trying to overwrite `/usr/X11R6/include/X11/pixmaps/mouse.xpm', which is
> also in package qcad
> dpkg-deb: subprocess paste killed by signal (Broken pipe)

This bug was already fixed in qcad 1.4.6-1, so once you upgrade to that
version you should be fine - but perhaps xlibs should replace qcad (<<
1.4.6-1) to make this easier? Cc'd to debian-x for comments.

-- 
Colin Watson  [EMAIL PROTECTED]



Re: xlib problem

2001-09-25 Thread Jason Boxman
On Tuesday 25 September 2001 10:04 pm, Brian Schramm wrote:
> I am still trying to upgrade from potato to woody.  With a modem this is a
> panfull process at best.  Here it is 4 days latter and now I cannot get
> anywhere with it.  Here is the error message that I get.
>

> Unpacking replacement xlibs ...
> dpkg: error processing /var/cache/apt/archives/xlibs_4.1.0-6_i386.deb
> (--unpack):
>  trying to overwrite `/usr/X11R6/include/X11/pixmaps/mouse.xpm', which is
> also in package qcad
> dpkg-deb: subprocess paste killed by signal (Broken pipe)
> Errors were encountered while processing:
>  /var/cache/apt/archives/xlibs_4.1.0-6_i386.deb
> Sub-process /usr/bin/dpkg returned an error code (1)
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> schserv:~#
>
> Please help.

I know your pain.  Dial up installations are a trip.

As someone else suggested you might try removing qcad.

Then you could bust out a

dpkg --pending --configure

and see if dpkg resumes.

Good luck!

(I had a similar problem with kde 2.2.1 in Sid and did an apt-get -f install 
and then a dpkg --pending --configure and it seemed to resolve itself, even 
though I didn't remove either package that had the offending file.  I don't 
know why it worked.)

> Brian
>
> Brian Schramm
> [EMAIL PROTECTED]ICQ 104442754  AIM schrammbrian
> www.linuxexpert.org



Re: xlib problem

2001-09-25 Thread dman
On Tue, Sep 25, 2001 at 10:04:45PM -0400, Brian Schramm wrote:
| I am still trying to upgrade from potato to woody.  With a modem this is a
| panfull process at best.  Here it is 4 days latter and now I cannot get
| anywhere with it.  Here is the error message that I get.
| 
| Moving old app-defaults file XmAddressBook to
| /etc/X11/app-defaults/XmAddressBook.xlibs-old.
| Moving old app-defaults file XRn to /etc/X11/app-defaults/XRn.xlibs-old.
| Moving old app-defaults file Atmidi to
| /etc/X11/app-defaults/Atmidi.xlibs-old.
| Unpacking replacement xlibs ...
| dpkg: error processing /var/cache/apt/archives/xlibs_4.1.0-6_i386.deb
| (--unpack):



|  trying to overwrite `/usr/X11R6/include/X11/pixmaps/mouse.xpm', which is
| also in package qcad



| dpkg-deb: subprocess paste killed by signal (Broken pipe)
| Errors were encountered while processing:
|  /var/cache/apt/archives/xlibs_4.1.0-6_i386.deb
| Sub-process /usr/bin/dpkg returned an error code (1)
| E: Sub-process /usr/bin/dpkg returned an error code (1)
| schserv:~#
| 
| Please help.

I have highlighted the most significant message above.  The problem is
the file that the new package is trying to install is also owned by
another package.  It would be pretty nasty for packages to stomp on
each other's feet like that so dpkg stops and warns you instead.  The
only solution that I know of is to remove one package (qcad) and
install the other (xlibs) then reinstall the first.

I have this same problem with a 3rd party package ('sos') putting it's
binary in /usr/X11/bin and then trying to upgrade xfree86-common.
Say ... I could fix that myself, couldn't I?

HTH,
-D



xlib problem

2001-09-25 Thread Brian Schramm
I am still trying to upgrade from potato to woody.  With a modem this is a
panfull process at best.  Here it is 4 days latter and now I cannot get
anywhere with it.  Here is the error message that I get.

Moving old app-defaults file XmAddressBook to
/etc/X11/app-defaults/XmAddressBook.xlibs-old.
Moving old app-defaults file XRn to /etc/X11/app-defaults/XRn.xlibs-old.
Moving old app-defaults file Atmidi to
/etc/X11/app-defaults/Atmidi.xlibs-old.
Unpacking replacement xlibs ...
dpkg: error processing /var/cache/apt/archives/xlibs_4.1.0-6_i386.deb
(--unpack):
 trying to overwrite `/usr/X11R6/include/X11/pixmaps/mouse.xpm', which is
also in package qcad
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/xlibs_4.1.0-6_i386.deb
Sub-process /usr/bin/dpkg returned an error code (1)
E: Sub-process /usr/bin/dpkg returned an error code (1)
schserv:~#

Please help.

Brian

Brian Schramm
[EMAIL PROTECTED]ICQ 104442754  AIM schrammbrian
www.linuxexpert.org

   



Re: xemacs-19.15p4 segfault on new frame -- xlib problem?

1997-05-26 Thread Carey Evans
stephen farrell <[EMAIL PROTECTED]> writes:

> I recently upgraded to debian from redhat, and an interesting new
> problem has surfaced with xemacs.  I use a scrpt with gnudoit to
> create new frames frequently.  now when I run this script xemacs
> coredumps frequently, especially after it's been running for a while.
> When I look at the back-trace, the last instructions are in Xt stuff.

[snip]

> #0  0x402669b9 in __kill ()
> #1  0x806f4dd in fatal_error_signal (sig=11) at emacs.c:202
> #2  0xbfffe54c in ?? ()
> #3  0x400b84c0 in XtInitializeWidgetClass ()
> #4  0x400b8c72 in _XtCreatePopupShell ()
> #5  0x400b8caf in XtCreatePopupShell ()

[snip]

I had (still have, in a way) a bug in XEmacs 19.14 (xemacs_19.14-1)
that looked very similar, although it was reported fixed in 19.15.
(make-frame) always crashed with a stack trace like yours after
displaying an XFace in Gnus (or elsewhere).  I have a small script
that demonstrates this bug, if you'd like to test your XEmacs.

I "fixed" it myself by a (setq features (delq 'xface features)).

-- 
Carey Evans  <*>  [EMAIL PROTECTED]

"Lies, damn lies, and computer documentation."


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


xemacs-19.15p4 segfault on new frame -- xlib problem?

1997-05-26 Thread stephen farrell

I recently upgraded to debian from redhat, and an interesting new
problem has surfaced with xemacs.  I use a scrpt with gnudoit to
create new frames frequently.  now when I run this script xemacs
coredumps frequently, especially after it's been running for a while.
When I look at the back-trace, the last instructions are in Xt stuff.

Similarly I noticed a little hack I did of xcpustate to run without
the label started coredumping.  I hacked that a little more and it
seems to be ok.

However, it seems that the xlibs that come with debian are more
sensitive to problems in the code and more likely to cause a
segfault (?). 

The libs on my redhat system... well, geez.  I don't know what they
were.  I switched them so many times--part of the reason I reinstalled
was to get a clean system since I had mucked around so much with my
old setup.

One thing I'm noticing now is that I have a hodgepodge of R6.1 libs
and R6.0 libs... e.g., libXt is 6.0, libX11 is 6.1... odd.

I installed debian off the ftp site, which, iirc, means I should have
the latest "stable" packages.

I compiled xemacs-19.15p4 on my own.  It is otherwise stable.

Thoughts??

--sf


(here is a snippet from the backtrace:)

#0  0x402669b9 in __kill ()
#1  0x806f4dd in fatal_error_signal (sig=11) at emacs.c:202
#2  0xbfffe54c in ?? ()
#3  0x400b84c0 in XtInitializeWidgetClass ()
#4  0x400b8c72 in _XtCreatePopupShell ()
#5  0x400b8caf in XtCreatePopupShell ()
#6  0x80fa550 in x_create_widgets (f=0x890b600, lisp_window_id=404799492, 
parent=404799492) at frame-x.c:1697
#7  0x80fa8d9 in x_init_frame_1 (f=0x890b600, props=404799492)
at frame-x.c:1928
#8  0x809b440 in Fmake_frame (props=404799492, device=405350656) at frame.c:424
[...]


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .