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 should I run under gdb : X ? and unfortunately I have not been developing for years, so using gdb as an expert in order to report valuable information, as stated by this paragraph, is clearly beyond my current abilities - and additionally, I am not sure it would actually help : what if X is not the true culprit ?
I don't know what you think about it. My initial intention, as I stated in my first post, was to follow the guidelines provided by
I saw in there many interesting suggestions, and my feeling was that these are general and broad enough, and they would be more useful in order to deal with a random and unknown problem.
What is your opinion ?
Currently, my best starting point is the backtrace from Xorg.0.log, also found in the kdm log or in the gdm log :
Other people posted the same backtrace, unfortunately it seems that this same backtrace is dumped for different issues - so what was good to them was no use to me.
Hello Leo,
About using https:/ /wiki.ubuntu. com/X/Troublesh ooting 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 should I run under gdb : X ? and unfortunately I have not been developing for years, so using gdb as an expert in order to report valuable information, as stated by this paragraph, is clearly beyond my current abilities - and additionally, I am not sure it would actually help : what if X is not the true culprit ?
I don't know what you think about it. My initial intention, as I stated in my first post, was to follow the guidelines provided by
https:/ /wiki.ubuntu. com/X/Backtraci ng
I saw in there many interesting suggestions, and my feeling was that these are general and broad enough, and they would be more useful in order to deal with a random and unknown problem.
What is your opinion ?
Currently, my best starting point is the backtrace from Xorg.0.log, also found in the kdm log or in the gdm log :
Backtrace: +0x28) [0x4a3258] .so.0 (0x7f025f381000 +0xf8f0) [0x7f025f3908f0] ng+0x1ba) [0x45f98a] start_main+ 0xfd) [0x7f025e078c4d]
0: /usr/bin/X (xorg_backtrace
1: /usr/bin/X (0x400000+0x655bd) [0x4655bd]
2: /lib/libpthread
3: /lib/libc.so.6 (__select+0x13) [0x7f025e138fc3]
4: /usr/bin/X (WaitForSomethi
5: /usr/bin/X (0x400000+0x30952) [0x430952]
6: /usr/bin/X (0x400000+0x261aa) [0x4261aa]
7: /lib/libc.so.6 (__libc_
8: /usr/bin/X (0x400000+0x25d59) [0x425d59]
Caught signal 3 (Quit). Server aborting
Other people posted the same backtrace, unfortunately it seems that this same backtrace is dumped for different issues - so what was good to them was no use to me.
Best regards
R. Grasso