I'm trying to build tigerVNC which uses xserver from source under ubuntu
11.10 32bit.
I'm following instructions from
http://tigervnc.svn.sourceforge.net/...79view=markuphttp://tigervnc.svn.sourceforge.net/viewvc/tigervnc/trunk/BUILDING.txt?revision=4879view=markup
In the configure step I'm
I've been getting SIGSEGVs in mieqEnqueue while valgrinding the server
hoping to find the source of an Ubuntu crash bug (which doesn't appear
to affect the upstream server).
Upon inspection, it was dying when trying to print the EQ overflowing
message. Digging down, ErrorF appears to end up
On 2012-03-31 13:05, Julien Cristau wrote:
On Thu, Mar 22, 2012 at 16:36:27 +0100, Pander wrote:
James, Julien, did you receive enough compelling arguments to resolve
this conflict so that o apostrophe results in ó. Then we can finally
close the book on gtk+/GNOME conflicts.
OK. Can you
On 04/03/2012 11:57 PM, Christopher James Halse Rogers wrote:
I've been getting SIGSEGVs in mieqEnqueue while valgrinding the server
hoping to find the source of an Ubuntu crash bug (which doesn't appear
to affect the upstream server).
Upon inspection, it was dying when trying to print the
On 03/04/2012 22:25, Chase Douglas wrote:
This option specifies a file descriptor in the launching process. X
will scan for an available display number and write that number back to
the launching process, at the same time as SIGUSR1 generation. This
means display managers don't need to guess
In OsInit(), we check if fd 2 is writeable, and if not, assume stderr has
been closed, and open /usr/adm/X0msgs for writing, and dup it on to fd 2.
Unfortunately, this happens after CreateWellknownSockets() has opened the
listener sockets, and that may use fd 2
Specifically, this can easily
On 4 April 2012 18:21, Jon TURNEY jon.tur...@dronecode.org.uk wrote:
In OsInit(), we check if fd 2 is writeable, and if not, assume stderr has
been closed, and open /usr/adm/X0msgs for writing, and dup it on to fd 2.
Unfortunately, this happens after CreateWellknownSockets() has opened the
On 12-04-03 07:43 PM, Yaakov (Cygwin/X) wrote:
From: Yaakov Selkowitz yselkow...@users.sourceforge.net
Signed-off-by: Yaakov Selkowitz yselkow...@users.sourceforge.net
---
xorg-macros.m4.in |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/xorg-macros.m4.in
Core events aren't generated for slave devices, so this is just wrong.
On top of that, the mask being checked in the removed hunk is wrong as
well. It is dereferencing a pointer of type OtherClients as though it
were a pointer to type InputClients.
Signed-off-by: Chase Douglas
The current code returns a reference to memory that may not actually be
an XI2 mask. Instead, only return a value when an XI2 client has
selected for events.
Signed-off-by: Chase Douglas chase.doug...@canonical.com
---
Xi/exevents.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
The current code checks the core event mask as though it were an XI2
mask. This change fixes the checks so the proper client and event masks
are used.
Signed-off-by: Chase Douglas chase.doug...@canonical.com
---
Xi/exevents.c | 18 --
1 files changed, 12 insertions(+), 6
On 03/23/2012 02:44 AM, Jeremy Huddleston wrote:
Is there a way we can tweak indent to not mess up blocks like this:
Blocks like this can be surrounded with /* *INDENT-OFF* */ and /*
*INDENT-ON* */ to disable (and re-enable) automatic indentation.
} known_numeric_keys[] = {
-{65,
This option specifies a file descriptor in the launching process. X
will scan for an available display number and write that number back to
the launching process, at the same time as SIGUSR1 generation. This
means display managers don't need to guess at available display numbers.
As a
On 04/ 4/12 03:29 PM, Chase Douglas wrote:
This option specifies a file descriptor in the launching process. X
will scan for an available display number and write that number back to
the launching process, at the same time as SIGUSR1 generation. This
means display managers don't need to
On 04/04/2012 07:18 PM, Alan Coopersmith wrote:
On 04/ 4/12 03:29 PM, Chase Douglas wrote:
This option specifies a file descriptor in the launching process. X
will scan for an available display number and write that number back to
the launching process, at the same time as SIGUSR1 generation.
https://bugs.freedesktop.org/show_bug.cgi?id=48244
--- Comment #6 from Michel Dänzer mic...@daenzer.net 2012-04-03 23:58:58 PDT
---
(In reply to comment #5)
Note 1: The file dmesg and Xorg.0.log files i got them when the graphic was
ok,
I had to take them when the graphic was bad?
That
Hello Mike, I am looking for the implementation details. Could you please
let m know where can I find them. My understanding on suspend is that all
the ongoing I/O request needs to be stopped and new I/O request should not
be processed. Correct me if I am wrong.
Thanks, -Bala S
2012/4/3 Michel
https://bugs.freedesktop.org/show_bug.cgi?id=48244
--- Comment #7 from basic dos...@gmail.com 2012-04-04 04:31:41 PDT ---
Created attachment 59469
-- https://bugs.freedesktop.org/attachment.cgi?id=59469
dmesg when the graphics are bad
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=48244
--- Comment #8 from basic dos...@gmail.com 2012-04-04 04:32:09 PDT ---
Created attachment 59470
-- https://bugs.freedesktop.org/attachment.cgi?id=59470
Xorg.0.log when the graphics are bad
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=43191
Alex Deucher ag...@yahoo.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=48310
Alex Deucher ag...@yahoo.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=34486
Alex Deucher ag...@yahoo.com changed:
What|Removed |Added
CC||freedesk...@slated.org
Hello Alex and Mike, I will look into this and get back to you.
Thank you for the prompt reply,
-Bala S
On Wed, Apr 4, 2012 at 6:31 PM, Alex Deucher alexdeuc...@gmail.com wrote:
2012/4/4 Balasubramanian S spar...@gmail.com:
Hello Mike, I am looking for the implementation details. Could you
Hi Elmar,
Elmar Haneke el...@haneke.de (04/04/2012):
[…]
Fatal server error:
[ 1304.253] Caught signal 11 (Segmentation fault). Server aborting
[…]
thanks for the report.
Bonus points if:
- you can get us a full backtrace. Some hints available at:
http://x.debian.net/howto/use-gdb.html
24 matches
Mail list logo
