[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
nierce, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/
Updating from 13.04 to 13.10 I get a segfault when executing Xephyr as
following :
Xephyr :3 -screen 1440x900x16 &
DISPLAY=:3 metacity
The segfault message :
(EE)
(EE) Backtrace:
Avertissement du gestionnaire de fenêtres : Erreur fatale d'E/S 11 (Ressource
temporairement non disponible) sur le
With the latest packages on Saucy (13.10) my problem with Xephyr disappear!
Now, works fine: Xephyr :100
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740785
Title:
Caught signal 11 (Segmentation fa
Trying to run sugar-emulator or xephyr :100
ignacio@ignacio:/usr/bin$ Xephyr :100
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTE
[51.033] (EE)
[51.034] (EE) Backtrace:
[51.035] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb772bc79]
[51.035] (EE) 1: /usr/bin/X (0xb7584000+0x1abb66) [0xb772fb66]
[51.035] (EE) 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb756140c]
[51.035] (EE) 3: /usr/lib/xorg/modules/drive
Seeing the same thing on a fresh install of 12.10 (64-bit) with NVidia
driver, GT240 graphics card.
>From Xorg.0.log:
[ 9613.796] (EE) Backtrace:
[ 9613.796] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f4138301b76]
[ 9613.796] (EE) 1: /usr/bin/X (0x7f4138159000+0x1ac9a9) [0x7f41383059a9]
[ 9
** No longer affects: unity (Ubuntu)
** No longer affects: lightdm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740785
Title:
Caught signal 11 (Segmentation fault). Server aborting
To ma
In my case this problem randomly appears on boot before greetings screen
and i receive message "The system is running in low-graphics mode"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740785
Title:
Its happens randomly with me too on 32bit Ubuntu 12.04 ThinkPad R500
with Intel 4500MHD video card
Xorg.0.log:
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x37) [0xb76b8647]
1: /usr/bin/X (0xb753+0x18c3ca) [0xb76bc3ca]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb750d40c]
3: /usr/lib/i386-linux-gnu/
I use Kubuntu 12.04 with fglrx driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740785
Title:
Caught signal 11 (Segmentation fault). Server aborting
To manage notifications about this bug go t
I think I got some similar bug on Kubuntu 12.04.
It happens randomly.
I found this in /var/kdm.log
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x37) [0xb7749627]
1: /usr/bin/X (0xb75c1000+0x18c3aa) [0xb774d3aa]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb759e40c]
3: /usr/lib/dri/fglrx_dri.so (0xb19e00
Gotcha. Will do. After doing that, should I mark this bug as a
duplicate?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740785
Title:
Caught signal 11 (Segmentation fault). Server aborting
To manag
Closing the lightdm, unity, etc component the issue affect those but
it's not in their code. The bug seems to mix several issues, could you
get a stacktrace and an Xorg.0.log from a config having the issue, on
precise would be better. It might be best to open a new bug report that
to keep a confusi
** Changed in: lightdm (Ubuntu)
Status: New => Invalid
** Changed in: unity (Ubuntu)
Status: New => Invalid
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
If the bug still exists in oneiric and it is not fixed, realize that the
bug will become more prevalent in precise since 12.04 will be a LTS
release and many users will be upgrading.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Can confirm that the bug still exists. This is a problem for xorg in
general, and therefore raises issues with both lightdm and unity. It may
also affect gdm and kdm.
** Changed in: xorg-server (Ubuntu)
Status: Expired => Confirmed
** Also affects: xorg (Ubuntu)
Importance: Undecided
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I'm using xine-ui to connect to vdr(mpeg2,x264 videos) .This logout
happens once from 5-10 times when closing xine fullscreen by remote
control or keyboard. After logging in compiz is using 100% cpu.
GT9600 Driver Version: 270.41.19 on natty x64 . This also happened with
older drivers I think.
Ho
It's incomplete because we still need someone to collect a full
backtrace on this crash - see http://wiki.ubuntu.com/X/Backtracing for
guidance.
Alternately, if you can specify steps to reproduce the crash I can try
on my end (I haven't seen any crashes like this, and I hit Enter many
times during
Today again. This time without compiz and two monitors.
Pidgin, Thunderbird, Chromium only was opened and again logout happened just
after hit Enter in pidgin sending icq message.
Why is this bug still Incomplete? What else to attach?
I have tried this https://wiki.ubuntu.com/X/Backtracing but a
My 64-bit Maverick runs without a crash for 9 days now on 270.41.06
nVidia binary drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740785
Title:
Caught signal 11 (Segmentation fault). Server a
I don't believe this was fixed in natty. If anything, it is more
widespread now.
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/778490.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740785
Titl
Please ignore my comment #14 for now, as this seems to be a completely
different bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740785
Title:
Caught signal 11 (Segmentation fault). Server aborti
** Attachment removed: "Xorg.crash3.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/2124357/+files/Xorg.crash3.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/7
Unfortunately, my Xorg on the new nVidia drivers crashed, but this time
on another account with compiz enabled and during non-3D work (just a
terminal and a browser, no VMware). The backtrace was this time quite
different.
** Attachment added: "Xorg.crash3.log"
https://bugs.launchpad.net/ubunt
I was getting the same error as Ian, JPM ( #775705) and qwazi on my
64-bit Maverick with nVidia binary drivers (260.19.06). No compiz here,
but extensively using VMware Player with 3D acceleration.
According to a hint by Paul de Vries
(http://vimeo.com/groups/cinelerra/forumthread:236340), I have
Same dealy here on Maverick 64-bit running with Compiz:
[ 50342.253] (II) XKB: reuse xkmfile
/var/lib/xkb/server-81EC4871279DB1D73113D19E789F270C19322F52.xkm
[ 85236.715] (II) XKB: reuse xkmfile
/var/lib/xkb/server-81EC4871279DB1D73113D19E789F270C19322F52.xkm
[102302.968]
Backtrace:
[102303.066
I've seen the exact same stack trace as the first comment in this bug
report.
Dell Latitude D630.
Ubuntu 11.04
Classic Desktop (with effects)
I've attached the Xorg log file containing the error. Is there anything
else you would like me to do?
I *think* the crash happens when Chrome is loading/r
It happens to me again today. Still on maverick. I found out that probably it
happens only if acceleration (compiz) is on.
Attaching ubuntu-bug xorg
** Attachment added: "result file from ubuntu-bug xorg"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/2108392/+
Backtrace:
[ 29851.244] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80eab1b]
[ 29851.244] 1: /usr/bin/X (0x8048000+0x5fac8) [0x80a7ac8]
[ 29851.244] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x69340c]
[ 29851.245] 3: /usr/bin/X (_CallCallbacks+0x3e) [0x8074e1e]
[ 29851.245] 4: /usr/bin/X (WriteToClient+0x2
Architecture: i386
DistroCodename: natty
DistroRelease: Ubuntu 11.04
DistroVariant: ubuntu
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
Package: xorg-server (not installed)
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersi
I don't have natty yet. Perhaps in this week.
This bug hasn't appear for longer time but this makes it even subtle.
I will update this bug if it will continue in natty.
Thanks for info
On 28.4.2011 06:17, bugbot wrote:
> Hey nierce,
>
>
> Hi, have you had a chance to test if this bug is still pres
Hey nierce,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
I'm getting this on 11.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740785
Title:
Caught signal 11 (Segmentation fault). Server aborting
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
getting this too - will add additional files
[36.899] 9: /usr/bin/X (mieqProcessInputEvents+0x199) [0x459c39]
[36.899] 10: /usr/bin/X (ProcessInputEvents+0x9) [0x46d9e9]
[36.899] 11: /usr/bin/X (0x40+0x40f23) [0x440f23]
[36.899] 12: /usr/bin/X (0x40+0x21a7e) [0x421a7e]
[
If you need any files, let me know and I'll do a dump and attach them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740785
Title:
Caught signal 11 (Segmentation fault). Server aborting
--
ubuntu-
This seems to be happening to me of late. Symptoms as previous poster.
Get a seg fault in /var/log/Xorg.0.log.old
Backtrace:
[ 7808.923] 0: /usr/bin/X (xorg_backtrace+0x28) [0x45c5a8]
[ 7808.924] 1: /usr/bin/X (0x40+0x5a87d) [0x45a87d]
[ 7808.924] 2: /lib/libpthread.so.0 (0x7f9f6a38a000+0xf
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740785
Title:
Caught signal 11 (Segmentation fault). Server aborting
--
ubuntu-bugs mailing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740785
Title:
Caught signal 11 (Segmentation fault). Server aborting
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/
40 matches
Mail list logo
