On Mon, 28 Mar 2011, Ajay Jain wrote:
A -maximized option was added in patch #240, in early 2009.
A quick check here shows it working.
Xterm -version shows XTerm(215). I am using Red Hat Enterprise Linux
Client release 5.5 (Tikanga). I can only guess .. it's not the latest
!
right (215
I'm having what appears to be a common problem but not of
the solutions I've found on various forums and threads have
worked for me.
I noticed this issue after I configured my system to use
the en_US.utf8 locale but it's possible that this issue
existed before that change. Note that in
Ajay Jain ajay...@gmail.com writes:
Hm, if your xterm doesn't support -maximized and if your WM (what's
your WM?) hasn't means to maximize xterm on start, you could try
'devilspie':
I use Gnome. Could you/anybody help on how can WM maximize it? I mean
what command. Meanwhile, I shall look
Hi,
I just ran in a couple of bugs because my code assumes sizeof(XID)==4
on all platforms which doesn't seem to hold on AMD64.
Whats the reason for XID to be 8bytes (unsigned long) on AMD64, I
thought an x-id (in protocol sence) is defined as 4 bytes anyway?
Will Xlib/xcb ever return values
On Mon, Mar 28, 2011 at 04:11:35PM +0200, Clemens Eisserer wrote:
Hi,
I just ran in a couple of bugs because my code assumes sizeof(XID)==4
on all platforms which doesn't seem to hold on AMD64.
Whats the reason for XID to be 8bytes (unsigned long) on AMD64, I
thought an x-id (in protocol
Hi Matthieu,
Thanks for your explanation =)
This is a mistake done 25 years ago or so. It's hard to justify it,
but it is so. A number of things that are 32 bits on the wire
are represented as 64 bits long at the API level on LP64 machines.
Is it considered more or less safe to store those
On Mon, Mar 28, 2011 at 04:47:18PM +0200, Clemens Eisserer wrote:
Hi Matthieu,
Thanks for your explanation =)
This is a mistake done 25 years ago or so. It's hard to justify it,
but it is so. A number of things that are 32 bits on the wire
are represented as 64 bits long at the API
On 3/26/11 9:06 AM, Felix Miata wrote:
On 2011/03/26 17:29 (GMT+0530) Suresh.M composed:
we having a supermicro motherboard X8DTL-IF which has Matrox G200eW
vga chip and we are using RHEL 3 U8 AS version OS.
This is old version from 2007? Why don't you try newer version? Newer
version figure
On 3/27/11 11:50 PM, Matthew Monaco wrote:
So, I don't mean for this to be a lesson in gdb. I was able to build
Xorg with debugging symbols easily. When I start gdb and run 'continue'
before Xorg crashes, nothing happens. It doesn't even bring me back to a
(gdb) prompt. When I try to exit out
On 03/28/11 07:35 AM, Matthieu Herrb wrote:
Changing the APIs now would break too many things, an no one as ever
considered doing a new major revisition of all those APIs.
In some sense, libxcb is the major revision of the X client API,
which hopefully has fewer mistakes we won't realize for
I'm having this really bizarre and annoying problem lately with my X
install (running KDE4.6 on top). I'll be using my computer without
problems, and then I will be unable to open any new windows. If I go
into an already-open terminal and attempt to run xeyes (or anything
else), I get this
On 3/28/11 2:40 PM, tsuraan wrote:
I'm having this really bizarre and annoying problem lately with my X
install (running KDE4.6 on top). I'll be using my computer without
problems, and then I will be unable to open any new windows. If I go
into an already-open terminal and attempt to run xeyes
Almost certainly what's happened is:
- your sole authentication method to the server is xauth cookies
- your xauth cookie record contains the hostname
- your hostname changed
Comparing the output of 'xauth list' and 'hostname' when this happens would
be enlightening.
xauth list had
On 03/28/2011 11:12 AM, Adam Jackson wrote:
On 3/27/11 11:50 PM, Matthew Monaco wrote:
So, I don't mean for this to be a lesson in gdb. I was able to build
Xorg with debugging symbols easily. When I start gdb and run 'continue'
before Xorg crashes, nothing happens. It doesn't even bring me
14 matches
Mail list logo
