*** This bug is a duplicate of bug 956071 ***
https://bugs.launchpad.net/bugs/956071
Just confirming that there have been no crashes for me after reverting
the xserver-xorg-input-synaptics version and locking it in synaptic
package manager as well (advice from other bug #32 linked to above).
I think, the probnlem is this packege: xserver-xorg-input-synaptics.
This issue persists since version 1.6.2-1ubuntu1~precise1. So i forced version
1.5.99.902-0ubuntu5.
After that, i had not issue anymore with lid open/close..
--
You received this bug notification because you are a member of
Proposed workaround offered in posts #31 and #32 from here:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/956071
I have followed the suggestion from #31 and have not had any crashes
since.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
I should cross reference that it seems there are a few additional
related bugs which seem to be very simliar, if not identical:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/956071
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1030535
--
You received this
Finally got the /etc/X11/core created on recent crash yesterday.
Trying the gdb command, I was first presented with an error, after which
I ran the bt full command (inside gdb). Maybe I have a problem and gdb
is not running well? I'll post the reply when starting gdb, and then
the results of the
Same here.
[242145.761286] Xorg[1287]: segfault at 9 ip b76d2b28 sp bf896790 error 4 in
Xorg[b75b2000+1f3000]
[242145.761524] Core dump to |/usr/share/apport/apport 1287 11 0 pipe failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
This might be a duplicate of bug 956071.
** Also affects: xorg-server (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681796
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
didi_X8, I am not sure your crash is the same issue, it seems yours
bombed out in BasicComputeAcceleration() while in this report it is
XIGetDeviceProperty().
The original poster had XIChangeDeviceProperty+40, whereas I got
XIChangeDeviceProperty+440 which is also seen in http://bugs.debian.org
/c
Update:
I found a file "_usr_bin_Xorg.0.crash" in /var/crash which contains a lot of
useful information, including a core dump (so I think).
Trying to get that info reported, I used apport to report an additional bug:
1032612
However the most valuable information (stack trace) seems to be missing
Having the same problem on a Thinkpad T410s, also Intel graphics (Core i5).
I just tried to create a core dump, following the instructions of Lasse.
However when trying to reproduce the crash, I had a total lockup, with hard
reset needed. No /etc/X11/core was generated.
--
You received this bu
Hmm Interesting... The same thing actually happened to me. First
crash after going through the above didn't produce a core dump. A couple
of days later though, crash + core dump. Don't know why it wouldn't
work the first time but maybe trying again will get you a core, like it
did for me.
The
Lasse,
I followed the above steps, but am not getting a /etc/X11/core created
after a crash. I did install the dbg versions of core and video-intel.
One minor adjustment to the above instructions is that lightdm.conf is
in /etc/lightdm/lightdm.conf (just forgot the lightdm folder)
--
You recei
Those of you who are seeing similar problems; could you try to get a
core dump and a full stack trace?
Here's how I managed to do it:
1. Prevent X from trapping SIGSEGV by putting the following in
/usr/share/X11/xorg.conf.d/00-no-trap-signals.conf:
Section "ServerFlags"
Option "NoTrapSi
I finally managed to get a core dump and a better stacktrace:
(gdb) bt full
#0 XIGetDeviceProperty (dev=0x7f962cfb5760, property=,
value=0x7fff8ba11458) at ../../Xi/xiproperty.c:852
handler =
prop = 0x7f962cfba920
rc =
#1 0x7f962b69f422 in get_property (dev=, proper
This issue affects me as well. I have a ThinkPad T410. Though I haven't tried
the successive sleep-wakeup experiment, I suspect the crash occurs as described
by comment #18 above.
Here's my lspci output:
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
00:02.0
I should note that the machine I am having issues with is running 32
bit, so is not just 64bit related.
I just tried from a live CD on a stick (12.04 32 bit), and couldn't
reproduce the problem (not 100% sure it wouldn't crop up, but it
successfully woke from suspend 10 times in a row without kic
probably it is related to one of these xorg updates:
xserver-xorg-core:amd64 (1.11.4-0ubuntu10.3, 1.11.4-0ubuntu10.5)
xserver-xorg-core:amd64 (1.11.4-0ubuntu10.5, 1.11.4-0ubuntu10.6)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
anyone tried a fresh install/start from live system yet? where 12.04
live system should be ok as this bug was first reported in july
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026777
Title:
Xorg
News at 11: Just restored from Hibernate: 33 seconds (I make it) after
restore, I was logged out. Xorg error as anticipated.
I've snaffled what looks to me to be the kern.log lines during
hibernation and restore. They, plus the Xorg Seg fault line, re
attached.
** Attachment added: "Xorg.log"
Addendum to the above. I have upped the swap to 4GB and enabled
Hibernate (it's disabled by default in 12.04).
First impression is that it simply makes the sleep/wake cycle take a
hell of a lot longer, but I don't have the flashing power LED which will
probably be an advantage if I take the machin
Just checked the exact details - I suspend the machine when I shut the
lid. Looking on the Power control panel, "hibernate" is greyed out. ISTR
I need more swap than I have core in order to hibernate?? - that wasn't
deliberate, I simply used the settings 12.04 applied when I installed
clean.
So no
Andy Holyer, are you indicating this bug happens when hibernating as
well? If you are "suspending" and that is fully shutting down your
computer, starting again and logging in back to the place you were
before it seems like you are referring to "hibernating".
Regardless, it does seem like the sam
I think this is the bug I have noticed since some point in July.
As a distinction, this is not on a Thinkpad - it's a Samsung NC10 Netbook. I've
been using this as you would a netbook - suspend by shutting the lid, then
start up, get the login prompt and back to where you were before the suspens
i also confirmed that the bug doesn't appear switching on and off the wifi by
hardware switch..
still, last time the bug appeared for me, i was waiting for the wifi connection
due to bad signal; as soon as it got connected, i was kicked to the login.
strange bug...
--
You received this bug not
I have confirmed that the "kick out to login" still is a problem even
with wifi disabled (via hardware switch).
Stephen, I have the machine set to not suspend (due to inactivity) when
plugged in. So, we are shutting it down overnight, but keeping it
active during the day. Windows just isn't an o
I wonder if anyone who actually works on X is reading any of this?
Sadly, I am now using Windows... can't use ubuntu when it crashes five
times a day.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026
I should note that I have seen the issue in 2 ways:
1. The manual 3 times suspend / wake leads me to the type of hang that
smwilsonau reports: nameile the "half-moon light keeps blinking" when
the lid is closed and it is attempting to suspend. Then, when opening
the lid, I am already back to the
Re #15, for me this is NOT when the crash happens. For me, the crash
happens while trying to suspend. I can tell this because the half-moon
light keeps blinking, which means that the computer never actually goes
properly into suspend (at which time that light would normally become
solid).
It is pr
FYI, I am using KDE as my desktop and have experienced this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026777
Title:
Xorg segfault: kicks out to login screen
To manage notifications ab
this bug seems to be related to gnome network manager; the x session
terminates in the moment when wifi connection is re-established after
wakeup. i wonder if it is related to suspend at all...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
bfrancom,
Any chance you have the time to try 3-4 successive "lid close, wait for
full suspend, lid open, wait until all settled" sequences? I can
consistently re-create the problem doing this and wonder if anyone can
confirm.
--
You received this bug notification because you are a member of Ub
I was getting these Xorg crashes after an upgrade yesterday. It also caused
some connectivity/network issues. The network issues seemed to revolve around
my "vpnc" being active (not sure if that was upgraded yesterday too), but after
reconfiguring the VPN, all is fine. No more Xorg crashes.
Do other people get a crash report with this title:
Xorg crashed with SIGABRT in XIChangeDeviceProperty()
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026777
Title:
Xorg segfault: kicks out to
** 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/1026777
Title:
Xorg segfault: kicks out to login screen
To manage notifications about this bu
Good idea. I'm going to paste the two descriptions from 1027619 here
too:
OP:
I am running xubuntu 12.04 on a Thinkpad X301. Since I first installed
12.04 a few months ago, everything worked fine for a couple of months.
But a few weeks ago (i.e. early July 2012), I started getting xorg
crashes.
Bug 1027619 does seem identical. I will mark the other as a duplicate
as we have a bit more testing in the comments listed here, but good
summary of problem in the other listing as well.
Again, I am happy to install the debug versions for xserver-xorg but
would appreciate any help on how to best
This bug affects me. I have a Lenovo X301 with Intel graphics. The
description just above from iveand (#8) is identical to my symptoms.
I have reported what I think is the same bug here:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1027619
Output from lspci:
00:00.0 Host bridge: Intel Co
** Summary changed:
- Xorg segfault
+ Xorg segfault: kicks out to login screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026777
Title:
Xorg segfault: kicks out to login screen
To manage notif
38 matches
Mail list logo
