That version is no more supported; please open a new bug report if the
actual archive found version also has the same issue.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620278
Title:
random Xorg crash
--
ubuntu-bugs mailing list
** Package changed: xorg-server (Ubuntu) = nvidia-graphics-drivers
(Ubuntu)
--
random Xorg crash
https://bugs.launchpad.net/bugs/620278
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
well, actually the previous backtrace happened when I had troubles with
my cx88_blackbird driver - I did not have any TV data at all, thus I
removed it with `modprobe -r cx88_blackbird', then I started it again;
it happened twice; the following one happened when I wanted to kill
xawtv with Ctrl-Q
I just had another problem; I was not interacting with the OS, I just
came back and saw X stopped : here is the backtrace :
Program received signal SIGPIPE, Broken pipe.
0x7f71a827e5e1 in ?? ()
(gdb) backtrace full
#0 0x7f71a827e5e1 in ?? ()
No symbol table info available.
#1
Hello,
I just had a X crash, so I immediately run 'backtrace full' in gdb :
here are the results :
(gdb) backtrace full
#0 0x7fc5339465e1 in ?? ()
No symbol table info available.
#1 0x02001160 in ?? ()
No symbol table info available.
#2 0x01fc96b0 in ?? ()
No symbol table
Your backtrace suggests that X is being killed with a SIGQUIT signal.
We had this problem earlier in the Lucid development cycle, and it was
caused by an interaction between X and plymouth.
I notice you've got a non-standard “console=tty1” option on your kernel
command line. Does this behaviour
Thanks for your post ! I just removed “console=tty1” and rebooted -
unfortunately I did not write down why I set this value.
I hope you don't care that I did not restore “quiet splash” : I hate
hiding the much valuable boot messages under the hood (I use to force
the text mode on RHEL as well)
I
Hello,
I did not read correctly the instructions at once, and did not start gdb
on my second desktop at first - this is why X froze. I understood two
days ago; thus I restored
ServerCmd=/usr/bin/X
in /etc/kde4/kdm/kdmrc, restarted kdm which now runs the normal X
wrapper
root 31084 31080 2
Question : can somebody modify the page
https://wiki.ubuntu.com/X/Backtracing
and replace, in paragraph Backtrace with gdb :
sudo gdb /usr/bin/Xorg 21 | tee gdb-Xorg.txt
with
sudo gdb /usr/bin/X 21 | tee gdb-X.txt
which should be correct i our Debian/Ubuntu world ?
--
random Xorg crash
Ok, at least I understood
man Xwrapper.config
(quite Debian specific, this X wrapper, I just discovered it !
RHEL/Fedora, which I know better, don't implement it - fixing things
helps you increase your knowledge !)
well, according to Debian policies, let's say that I have a dirty
workaround.
I did not shut down my desktops yesterday - Xorg keeps working, with kdm
in the background - my doomed command does not seem to be doomed any
more - these were today's news ...
--
random Xorg crash
https://bugs.launchpad.net/bugs/620278
You received this bug notification because you are a member
Hello,
So, here is my report - not exactly the one we assumed : however :
last friday evening, reading briefly the doc, I understood that
attaching gdb to X was dead simple, so I tried - and X froze -
completely - it was late, thus I dropped it, and resumed the debug
session now.
It kept
** Attachment added: output from : gdb /usr/bin/Xorg 21 | tee gdb-Xorg
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/620278/+attachment/1511276/+files/gdb-Xorg
--
random Xorg crash
https://bugs.launchpad.net/bugs/620278
You received this bug notification because you are a
(continuation)
Oh I am sorry ! I assumed I could attach a file independently from the
edit session ! apparently not ;-)
so, now, kdm started Xorg and not X (as it should be ? you tell me !)
I did not had any further luck with gdb : attaching it to Xorg, my
screen froze as well - I guess I am
Well, so far my doomed command did not kill X (I MUST say Xorg !!). It
s not sufficient. So I am going to keep doing my home things as usual,
running Xorg and not X, and we'll see.
I am sorry I could not report anything from gdb.
Anyway, did these tests already give any insights to anybody ? And
I would add : on CentOS 5.5, we actually have :
lrwxrwxrwx 1 root root 4 May 18 13:18 /usr/bin/X - Xorg
X is a LINK, and not some separate weird binary
--
random Xorg crash
https://bugs.launchpad.net/bugs/620278
You received this bug notification because you are a member of Ubuntu
Bugs,
** Package changed: xorg (Ubuntu) = xorg-server (Ubuntu)
--
random Xorg crash
https://bugs.launchpad.net/bugs/620278
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Tags added: kubuntu
--
random Xorg crash
https://bugs.launchpad.net/bugs/620278
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
Marking as incomplete until you provide the debugging information required to
find the cause of the issue.
Please look at https://wiki.ubuntu.com/X/Troubleshooting and follow the guide
that corresponds to your problem. Report back any useful findings and add as
separate attachments all the
Hello Leo,
About the missing package : I removed it on purpose. Well, according to
https:/ /wiki.ubuntu. com/Bugs/ FindRightPackage, should I understand
that you will use it as a pointer to begin the troubleshooting search ?
As a senior Unix sysadmin, I did not feel correct to state what seemed
Hello Leo,
About using https://wiki.ubuntu.com/X/Troubleshooting as a guidline for
adding meaningful informations : the only entry point in this document,
matching my case, is :
Problem results in X crash or exit
however, the only suggestion is to run gdb to get a backtrace : well,
what process
Hello Robert,
The bugs that are just assigned to Ubuntu are a lot, so we are always
trying to classify them. I don't really know if this is a problem on
xorg or kdm, and I could have made a mistake. But assigning the most
probable package is a good idea because it will call the attention to
Ok Leo, I understand.
I will review my gdb skills briefly :-) Good ol'days ;-)
It's getting late here in France (all this is happening at home ;-) - I
am not sure I am going to setup all this this evening. More probably
this week-end. I already started apport ;-) But the sooner the better.
--
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/620278/+attachment/1499372/+files/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/620278/+attachment/1499373/+files/CurrentDmesg.txt
** Attachment added: Dependencies.txt
26 matches
Mail list logo
