On Mon, 2010-02-22 at 22:44 +0100, Tom Cowell wrote:
Well, that's good news (unless your email has triggered the problem again!).
Not yet. ;)
Just out of curiosity, has another auto-generated .xmodmaprc appeared?
No new .xmodmaprc file has appeared. I'm thinking that may have been
something
On Mon, 2010-01-18 at 22:48 +0100, Tom Cowell wrote:
Well, according to my primitive understanding, xmodmap is normally
used for a little bit of tweaking of the keyboard layout (fiddling
with delete and backspace, for instance, or swapping CapsLock and
Ctrl).
Your file looks odd to me
On 01/11/2010 09:16 AM, Tom Cowell wrote:
Yes, that's what I meant. I suppose the action of strace (and
valgrind, probably) will slow things down, so maybe the timeout
messages can be taken at face value, and maybe there is a timeout that
can be increased so that the strace/valgrind of startx
On 01/18/2010 03:17 PM, Ryan Daly wrote:
I was able to start Xorg w/ 'startx' as root. I'm writing trace files
out, so as soon as I get it to exit on me, I'll look through and see
what's left.
One bad thing... The strace files started taking up so much room that I
needed to stop
On 01/18/2010 04:23 PM, Tom Cowell wrote:
What was/is in the .xmodmaprc?
248 lines of things like this:
keycode 61 = slash question slash question slash question
keycode 62 = Shift_R NoSymbol Shift_R NoSymbol Shift_R
keycode 63 = KP_Multiply XF86_ClearGrab KP_Multiply XF86_ClearGrab
On 01/08/2010 04:13 PM, Justin P. Mattock wrote:
On 01/08/10 13:05, Ryan Daly wrote:
On 01/08/2010 03:56 PM, Justin P. Mattock wrote:
gripes!! valgrind breaks with
libc 2.11.90(I'll see later on this),
In your case what does valgrind
output's say when the crash occurs?
Did you use any
On 01/11/2010 08:47 AM, Tom Cowell wrote:
Ah yes. My strace suggestion would have the same problem.
On my machine (and presumably yours) the Xorg binary is setuid-root -
it acquires elevated permissions when you run it, and this breaks the
process tracing (and it seems odd to me (though I
On 01/11/2010 09:02 AM, Justin P. Mattock wrote:
On 01/11/10 05:53, Ryan Daly wrote:
On 01/11/2010 08:47 AM, Tom Cowell wrote:
Ah yes. My strace suggestion would have the same problem.
On my machine (and presumably yours) the Xorg binary is setuid-root -
it acquires elevated permissions when
On 01/11/2010 09:00 AM, Tom Cowell wrote:
Does it work as root if you run it without strace or valgrind?
Can you tell I'm getting out of my depth?
startx works as root if that's what you mean...
This message and any files
On 01/07/2010 06:07 PM, Justin P. Mattock wrote:
not sure what might be the next step for you at this point.
I've an old machine over here, I can throw in ubuntu
to see if I hit this as well(you said typing triggers this).
with that, you are using gdb to
debug, out of curiosity maybe
On 01/08/2010 08:38 AM, Ryan Daly wrote:
On 01/07/2010 06:07 PM, Justin P. Mattock wrote:
Yes, typing seems to be the trigger...but there are times when it stays
up for hours, if not a day or two before exiting on me. Then, once it
does it seems to do it frequently if I log in again
On 01/07/2010 06:11 PM, Dan Nicholson wrote:
Not sure this will work, but if it's a symbol resolving problem, you
can try to get it to crash faster by using LD_BIND_NOW.
LD_BIND_NOW=1 startx `which xterm`
X will not start with LD_BIND_NOW set to 1. It's unable to load
On 01/08/2010 03:50 AM, Tom Cowell wrote:
I'm a novice here - excuse me butting int, and ignore me if this isn't useful.
If I understand correctly, you have:
a) The X Server receives SIGTERM and exits.
b) The source of the SIGTERM is unknown (but perhaps one of the
clients of the X
On 01/08/2010 08:59 AM, Pat Kane wrote:
On Fri, Jan 8, 2010 at 7:38 AM, Ryan Daly d...@ctc.com wrote:
Could hardware problems trigger this?
Yes, have you run memcheck on the flakey system? If the first
pass is okay, let it run all night.
No, I have not. I'm not familiar with that tool
On 01/08/2010 10:11 AM, Tom Cowell wrote:
I was responding to this remark from Peter Hutterer:
uhm. SIGTERM is the termination signal. Something's shutting down your
server.
If SIGTERM is coming from another process, then the debugger won't
provide any information about _which_ process.
On 01/08/2010 10:19 AM, Pat Kane wrote:
See: http://www.memtest.org/
Many boot/live CDs have memtest as an option when booting from them.
I know that my Fedora and Ubuntu install CDs let me boot into memtest.
Ahh, OK. I have used that tool before.
I'll run the 'strace' as suggested
On 01/08/2010 10:30 AM, Justin P. Mattock wrote:
well looking at your debug log you provided
on launchpad It seems
to be doing something with nss
before crapping out as well as something with
libc and tls.
The screen left some output that may be of interest, too. (I transposed
this
On 01/08/2010 03:56 PM, Justin P. Mattock wrote:
gripes!! valgrind breaks with
libc 2.11.90(I'll see later on this),
In your case what does valgrind
output's say when the crash occurs?
Did you use any options with valgrind or just 'valgrind startx'?
On 01/06/2010 10:34 PM, Ryan Daly wrote:
On 01/06/2010 10:26 PM, Justin P. Mattock wrote:
the module should work.. hopefully their the same arch's
as for the next step:
try starting the server from a TTY instead of through gdm
(as stated by peter hutterer from the other post try
On 01/07/2010 01:25 PM, Justin P. Mattock wrote:
I know it says these errors aren't fatal to the X server, but could they
be causing me problems?
as for xkbcomp doing a quick google
gave me this:
http://bugs.gentoo.org/269931
but still don't see that this is the
culprit.
I read
On 01/07/2010 05:30 PM, Peter Hutterer wrote:
waiting for X server to shut down ddxSigGiveUp: Closing log
/Xorg.out
I know it says these errors aren't fatal to the X server, but could they
be causing me problems?
as for xkbcomp doing a quick google
gave me this:
not sure whats going on, but by
looking at the log I see some userspace tools
erroring out(which should not keep the screen from
going forward), but I also see something about
fglrx not found.. could either mean that you
haven't the xorg module, as well as the kernel module,
or the fglrx
On 01/06/2010 10:53 AM, Jeremy Huddleston wrote:
On Jan 6, 2010, at 10:50, Ryan Daly wrote:
not sure whats going on, but by
looking at the log I see some userspace tools
erroring out(which should not keep the screen from
going forward), but I also see something about
fglrx not found
On 01/06/2010 01:31 PM, Justin P. Mattock wrote:
fglrx is the closed-source ATI driver
OK. That rules that out then...
The backtrace is pretty consistent with the following few lines:
Program received signal SIGTERM, Terminated.
0x7f146bab8110 in __close_nocancel () from
On 01/06/2010 02:28 PM, Justin P. Mattock wrote:
alright.. so at least you can switch
modules i.g. from nvidia to vesa and such.
From what it seems your hitting something
maybe with evdev, or mouse/kbd(but could be wrong).
over here I've noticed something like that
with using fluxbox
On 01/06/2010 02:49 PM, Tim McConnell wrote:
Thanks,
Tim McConnell
timothy.mcconn...@comcast.net mailto:timothy.mcconn...@comcast.net
On Wed, 2010-01-06 at 11:27 -0800, xorg-requ...@lists.freedesktop.org wrote:
What is the model of the Nvidia card? Also what do you have installed as
On 01/06/2010 08:04 PM, Peter Hutterer wrote:
The backtrace is pretty consistent with the following few lines:
Program received signal SIGTERM, Terminated.
0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0
(gdb) backtrace r full
#0 0x7f146bab8110 in __close_nocancel ()
On 01/06/2010 03:59 PM, Justin P. Mattock wrote:
over here my xorg modules live in:
/usr/lib/xorg/modules/*
ubuntu might be the same(but can't remember).
as for uninstalling, synaptic I think
might let you uninstall a module
individually, but you never know might
want to uninstall a whole
On 01/06/2010 08:47 PM, Peter Hutterer wrote:
Right, but it's nothing I'm doing. That's the problem. I'm not
initiating an exit, nor am I hitting ctrl-backspace (I don't think
that's enabled by default any longer anyway).
I'm looking for suggestions as to WHAT may be causing the SIGTERM.
On 01/06/2010 09:39 PM, Justin P. Mattock wrote:
you need a newer version of xmacros
(everything is at cgit.freedesktop.org)
Got'em and installed in /usr/local.
hopefully ubuntu is up-to-date
i.g. hopefully it doesn't take
much to use the latest version.
(you can also grab the tar ball
Would anyone be able to take a look at a bug report I filed with Ubuntu?
My Xorg server keeps terminating on me and sends me back to the login
screen. I have obtained a number of backtraces, all of which are logged
in the bug report. The link to the bug report is below.
31 matches
Mail list logo
