The workaround is to disable sna.
Create the file
/etc/X11/xorg.conf.d/20-intel.conf
with the following content:
Section "Device"
Identifier "Card0"
Driver "Intel"
Option "AccelMethod" "uxa"
EndSection
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Workaround from comment #40 in bug #1510970 works for me, too.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1510998
Title:
Xorg crashes with segfault on 15.10
To manage notifications about
According to comment #32 in bug #1510970 it might help to upgrade to kernel
4.3. I just tested this but unfortunately got a segfault again after only a few
minutes...
Kernel: Linux 4.3.0-040300-generic #201511020949
--
You received this bug notification because you are a member of Ubuntu-X,
Why is the importance changed from Critical to High? I am experiencing
3-5 crashes per day and am not aware of any workaround. This is more or
less an unusable system and I am seriously thinking of downgrading
again.
Johan Tol, have you tried to get a backtrace like I mentioned in #8?
That way it
Yes. All are dated after the update to 15.10.
_usr_bin_akonadi_akonotes_resource.1000.crash,
_usr_bin_akonadi_archivemail_agent.1000.crash,
_usr_bin_akonadi_archivemail_agent.1000.upload,
_usr_bin_akonadi_archivemail_agent.1000.uploaded,
_usr_bin_akonadi_ical_resource.1000.crash,
I'm not sure what you mean with "kernel call trace".
The first entry in syslog which is related to the crash mentioned in #13 is
Nov 1 12:53:06 gondor org.a11y.atspi.Registry[4315]: XIO: fatal IO error 11
(Resource temporarily unavailable) on X server
":0"
But this is not always the same.
I already had two crashes today, but no specific xorg file. One of the crashes
happened at 12:53:06 according to syslog. Only one file in /var/crash, namely
_usr_bin_akonadi_maildispatcher_agent.1000.crash is related to that crash and
occurred at 12:53:08 according to the crash file.
Sorry, now I know what you mean: log messages from #3.
These appear at completely different times, so probably they are unrelated to
the crashes (see again syslog in #2). I mentioned them because they also
involve the intel graphics, so who knows...
--
You received this bug notification
Ok, it worked when logging into my machine from another computer and then
starting gdb.
The backtrace is attached.
** Attachment added: "gdb-Xorg.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1510998/+attachment/4509542/+files/gdb-Xorg.log
--
You received this bug notification
I tried to get a backtrace according to "Already running programs" for X from
https://wiki.ubuntu.com/Backtrace
I started gdb on the first virtual console (Ctrl+Alt+F1). After
executing "continue" in gdb, I can still switch between the different
consoles, but after typing Ctrl+Alt+F7 to get back
I don't know if this is related, but my syslog is full of messages like
this:
Oct 28 12:08:46 gondor kernel: [3.426755] [ cut here
]
Oct 28 12:08:46 gondor kernel: [3.426766] WARNING: CPU: 1 PID: 192 at
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1510998/+attachment/4507632/+files/syslog
** Description changed:
I updated my system from 15.04 to 15.10 yesterday. Since then the X
server has already crashed 5 times, which renders the system close to
Public bug reported:
I updated my system from 15.04 to 15.10 yesterday. Since then the X
server has already crashed 5 times, which renders the system close to
unusable for me.
The corresponding messages in Xorg.0.log.old are:
[ 12125.023] (EE)
[ 12125.023] (EE) Backtrace:
[ 12125.023] (EE) 0:
Here is the bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=90493
** Bug watch added: freedesktop.org Bugzilla #90493
https://bugs.freedesktop.org/show_bug.cgi?id=90493
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
There doesn't seem to be an usage issue in Vivid, but after an uptime
of only three days the filesize of Xorg.0.log is already 116MB due to
those error messages...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
The behaviour usually worsens after using the system for a longer time.
As I cannot run on a live system for a longer period, this is hard to
say. I will report after the upgrade to Vivid.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
Errors are still produced in Vivid Daily Build, though it seems that the
two/three finger taps and the jumping of the mouse pointer gets better.
** Changed in: xorg (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I updated the BIOS:
gondor:/etc# dmidecode -s bios-version dmidecode -s bios-release-date
V1.14
01/08/2015
Unfortunately it has no influence on the touchpad behaviour. The errors
showing up are still like the ones logged in
XorgLog.txt/xserver.errors.txt
** Changed in: xorg (Ubuntu)
Public bug reported:
My touchpad is behaving strangely (As far as I remember it only appeared after
some update in Utopic).
Using a two or three finger click, it needs several tries till it actually
accepts the click. Sometimes the mouse pointer jumps to a different location
on the screen when
I used 'apport-cli -f -p xorg' to report the bug. Here it is:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437867
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
Unfortunately I am running into this bug when trying to file a new bug:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1437214
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
I'm running Kubuntu 14.10 and I am still experiencing the bug.
For me it does not seem to be related to suspend/resume, at least it happens
long after a resume. Also, there was never a particular high load on the
machine. In my case it seems to get triggered by clicking on a link which then
After about 5MB of similar messages in Xorg.0.log.old here is the end of
the file which actually contains the xorg crash:
(EE) [dix] SYN1B7F:01 06CB:2970 UNKNOWN: unable to find touch point 0
(EE) [dix] SYN1B7F:01 06CB:2970 UNKNOWN: unable to find touch point 0
(EE) [dix] SYN1B7F:01 06CB:2970
23 matches
Mail list logo
