MY BAD !
it was not my tv card, but my WEBCAM : I was trying to run mplayer on
the webcam by mistake, but previously it would output a bunch of errors,
not just freeze the OS !
kamoso and cheese froze as well
actually, the webcam was plugged onto another device, and it seems that
this messed up
ah, not good ! now even kernel v3.4.0-5-generic trigger the issue : so
it's related to today's reboot : I have downloaded the lastest updates.
However, I cannot watch TV any more ! great !
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
Public bug reported:
Once again, the kernel fails to properly drive my TV card HVR-1300; I
just upgraded to kernel 3.5.0-30-generic; when I wanted to watch tv
using
mplayer tv:// -tv driver=v4l2:input=1:device=/dev/video0:norm=PAL-DK
the command just stalled, the process cannot be killed (kill -
I made some progress : actually, in my previous xorg.conf, I was loading
the module "v4l" (I am not sure why I loaded it - must have been a test
a long time ago) - as soon as I commented it, I got my display back !
Actually, I have an Hauppauge HVR-1300 TV card, which always had some
troubles with
mmh, must be a typo; here
ftp://download.nvidia.com/XFree86/Linux-
x86_64/270.41.19/README/README.txt
the 8600 GT is mentioned
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/815705
Title:
I have a suggestion : I looked at the supported hardware on NVidia pages
: for driver 195.36 (with Ubuntu 10.04) my graphic card 8600 GT was
mentioned :
http://www.nvidia.com/object/linux-display-ia32-195.36.24.html
However, for driver 270.41 (Ubuntu 11.04), my card is NOT mentioned :
http://www
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 0x
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 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
Question : can somebody modify the page
https://wiki.ubuntu.com/X/Backtracing
and replace, in paragraph "Backtrace with gdb" :
sudo gdb /usr/bin/Xorg 2>&1 | tee gdb-Xorg.txt
with
sudo gdb /usr/bin/X 2>&1 | tee gdb-X.txt
which should be correct i our Debian/Ubuntu world ?
--
random Xorg cras
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
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. Now
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
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-X,
whi
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 ? An
(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 giv
** Attachment added: "output from : gdb /usr/bin/Xorg 2>&1 | 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 me
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 freezin
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.
--
r
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 proc
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
to
This patch fixed two similar issues to me :
- from v10.04 on x86_64, connected into an xterm in ssh onto a v10.04 on
i686 : changing to *some* directories, or moving *some* files on the
i686 computer lead to an X crash on the x86_64 box;
- running konqueror on the x86_64 box, I wanted to rename a
23 matches
Mail list logo
