Ah, the first report from a non-Nvidia user! This effectively rules out
the possibility that the problem lies within the nvidia driver, it
definitely seems to be a problem with Compiz or X...
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug notific
As I mentioned above, I've had this crash when not running Compiz (only
one though), so it seems more likely to be a bug with X, but one that is
made much more common by Compiz (and usually by simultaneous intensive
disk IO and CPU).
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.ne
The same problem again with Kubutuntu Gutsy 7.10, Compiz Fusion and
intel driver.
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xe420]
2: /usr/bin/X [0x817e39d]
3: /usr/bin/X [0x817a9ef]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]
5: /usr/bin/X [0x8168f19]
6: /usr/bin/X [0
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Sourcepackagename: xorg => linux-restricted-modules-2.6.22
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for U
If anyone from cannonical/ubuntu is willing to acknowlegde this issue I
can reproduce it at will and provide strace logs of the crash.
I am using NVIDIA drivers and any GLX usage will cause a crash.
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug
I just got exactly the same thing, but this time while not running
Compiz or any OpenGL. It happened immediately after I entered my
password to unlock KDE, immediately after resuming from 'Suspend'. This
is a not a laptop, but I have got suspend and hibernate working fine on
it (until this hiccou
A "me too" under Kubuntu Gutsy with NVidia 100.14.19.
Same backtrace.
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Another me too, I had this error before in Gutsy (beta), I reinstalled
the final version and everything was working fine, then the last thing I
did was install some devel packages to compile kmediafactory (xorg-devel
included) ,and shutdown the computer. The next time I booted the
computer, X fail
Just a "me too" here. I'm also using Kubunto with Compiz, but didn't try
switching Compiz off yet.
I don't have a clue what's going on here, but it seems like it has
something to do with the CPU or I/O load. Currently I've got a RAID
resync running and a large rsync operation and I've encountered
I forgot to mention that i do use compiz-fusion
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
Another "Me too", with Gutsy and official NVIDIA drivers
Same Backtrace:
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xe420]
2: /usr/bin/X [0x817e39d]
3: /usr/bin/X [0x817a9ef]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]
5: /usr/bin/X [0x8168f19]
6: /usr/bin/X [0x8164315]
I also forgot to mention that I am not using compiz or beryl...
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
New Note 5
I can confirm a similar problem - I'm not sure if this is the same bug
as described here, but here goes - firefox has been completely crashing
my computer since I upgraded from Feisty to Gutsy a week or so ago (i.e.
I can't switch VTs to find out what's going on, can't reset Xorg using
I'm sorry, but at least two of us are still experiencing this issue on
Gutsy RC, so I'm marking this as confirmed again.
** Changed in: xorg (Ubuntu)
Status: Fix Released => Confirmed
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug notific
Another "me too" for Gutsy RC, with nvidia-glx-new
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xe420]
2: /usr/bin/X [0x817e39d]
3: /usr/bin/X [0x817a9ef]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]
5: /usr/bin/X [0x8168f19]
6: /usr/bin/X [0x8164315]
7: /usr/bin/X [0x8157
Well, in my case, everything works perfectly, including games, so it'd be
quite odd if it was a hardware issue.
On 10/12/07, Magnes <[EMAIL PROTECTED]> wrote:
>
> For me random crashes stopped when I replaced damaged capacitor on the
> main board and changed not working properly power supply! It l
For me random crashes stopped when I replaced damaged capacitor on the
main board and changed not working properly power supply! It looks it
had something to do with the hardware malfunction.
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug notific
Still happening on Gutsy Beta asof 11-oct, only when Compiz is on. I'm
not sure how many people have this problem, but it makes Compiz unusable
to me, so the composite-by-default spec is not really acomplished =/
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xe420]
2: /usr/bin
I have something like this:
Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x81) [0x80c5d91]
1: [0xe420]
2: /usr/lib/xorg/modules//libfb.so(fbComposite+0x57d) [0xb706df3d]
3: /usr/lib/xorg/modules/drivers//nvidia_drv.so(_nv000729X+0x498) [0xb71407b8]
Fatal server error:
Caught signal 11. Serv
In my case it only happened with Compiz or Beryl activated. I'll try
installing the Gutsy beta and see if it still happens.
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug cont
Just one more note: this wasn't a compiz problem, since I don't even
have it installed.
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mai
Thanks mlind. I'll go ahead and close the bug. If anyone spots this
behavior again on Gutsy, please enter a new bug report.
** Changed in: xorg (Ubuntu)
Status: Confirmed => Fix Released
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug no
Although my backtrace looks bit different in comment #14, xserver
stopped crashing for me too when I upgraded to gutsy.
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Compiz has received a LOT of attention for Gutsy, including many bug
fixes.
Can one other person confirm that this behavior stops happening when
upgrading to Gutsy? If so, we can close this bug as fixed.
Unfortunately it's not likely that this will be backported to Feisty,
however Gutsy's releas
I finally got tired of the crashing (three times a day isn't so nice...)
and upgraded to Gutsy last week. So far I haven't had a single crash, so
I guess my problem is fixed in Gutsy.
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug notification be
In my case it's definately not because of Beryl, since I don't have it.
(And I've never even tried it.) And since this crashing seems to happen
on different manufacturers graphics cards I don't think the problem is
in those driversl...
There are two upstream bugs having same kind of backtraces:
h
Just a comment: I've tried CompComm from the SVN packages build by
Evandro and the same thing happens. Since I've disabled Beryl it hasn't
happened anymore, so it's definitely related, at least in my case. If
anyone is following this bug, I think it should be marked in Gutsy
Milestones, considering
I tried commenting out the one font row from xorg.conf that Bryce
mentioned, but it didn't help.
This time X just hanged, but sshd was killed (gkrellmd was still running
though). Just before the hang I was trying to close one firefox window.I
was able to login from normal terminals (Ctrl-Alt-F1..)
I have the same problem now after I've upgraded to Feisty. Didn't have
stability problems with Edgy as the original poster. But then again, I'm
using Kubuntu.
More of my backtraces and other findings can be seen in bug #108829 but
here's my latest backtrace:
Backtrace:
0: /usr/bin/X(xf86SigHandle
Another "me too" here. Crashes are a little random, but AFAIK it only
happens with Beryl enabled. Using latest nvidia-glx-new. I'm not sure if
this happens with Compiz as I haven't used it much. I think this bug
should be marked as critical.
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c5d91
Another "me too" -- similar backtrace to 'mlind', but not identical.
I'm using Ubuntu Feisty with ubuntu's NVidia drivers and a GeForce 5200
FX card. The crashes happen randomly -- the only common thing I've
found is it tends to be when I'm using Yakuake (KDE terminal), or just
switching away from
I wonder if this is the same issue I'm having with feisty with both
opensource and proprietary ATI drivers. Happens only when the
screensaver has been active for some time though (random mode)
Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x81) [0x80c5d91]
1: [0xe420]
2: /usr/X11R6/bin/X(miSet
32 matches
Mail list logo
