I'm now on 16.04 and the problem still persists. It even got worse, as
now, the short dropout happens exactly every 2 minutes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452004
Title:
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
Bugs, which is
Same problem here. Everything worked fine in 15.10, but I have had the problem
before. Unfortunately I don't remember exactly when it disappeared. It might
have been after the update to 15.10.
Acer Aspire VN7-571G
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Workaround from comment #40 in bug #1510970 works for me, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510998
Title:
Xorg crashes with segfault on 15.10
To manage notifications about this
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
Bugs,
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I use pulseaudio to stream music over wifi to a Rasberry Pi 2 at 192kb. Exactly
every 5 minutes there is a short dropout in the stream. This is always followed
by the following warning in plamashell:
networkmanager-qt: void
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
Bugs, which is subscribed to
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
Bugs, 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)
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172094
Title:
xorg synaptic
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
Same problem occurs for me when I run
ubuntu-bug xorg
I'm also running on (fully updated) Utopic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437214
Title:
ubuntu-bug crashes on
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172094
Title:
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
The patch from #57 is implemented in today's kernel update for Utopic
(3.16.0-33-generic #44-Ubuntu).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384342
Title:
kernel messages
The patch from #52 is implemented in today's new kernel 3.16.0-31.41!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393079
Title:
Touchpad not working after suspend/resume
To manage notifications
what about changing
+ } else if (IS_IVYBRIDGE(dev) || IS_HASWELL(dev)) {
in the patch file (#57) to
+ } else if (IS_IVYBRIDGE(dev) || IS_HASWELL(dev) || IS_IRONLAKE_M(dev))
{
It's a naive guess but maybe it works.
--
You received this bug notification because you are a member of
I compiled the current kernel (3.16.0-30-generic) from utopic with the
commit mentioned in #55 more than a week ago. Never ran into the problem
again, so the commit seems to solve the problem at least for me.
I have attached a patch file which works for the 3.16.0-30 kernel. The easy way
to
Here is the new bug report for utopic:
https://bugs.launchpad.net/compiz/+bug/1418516
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/763148
Title:
Adding/Removing an external monitor causes open
I'm on utopic with
compiz-core 1:0.9.12+14.10.20140918-0ubuntu1
and still experience the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/763148
Title:
Adding/Removing an external monitor causes
Bernhard, sorry, my bad. I left out one important step. Before compiling you
should also edit the file linux-3.16.0/debian.master/changelog and change the
version number in the first line to, e.g., 3.16.0-30.40+hidfix
Without this, the updater tries to update the newly compiled kernel, even
Then your touchpad uses a differrent driver. The patch is specifically
for the i2c-hid driver and so it is of no use for you, sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393079
Title:
Great that it works.
Concerning 14.04, I think the bug was not present there, but I'm not sure (see
bug description above).
Kernel versions =3.17 do include the patch, so with Ubuntu 15.04 latest, the
bug will be gone. But hopefully, the patch will be included already in updates
for 14.10.
@Orco: did you try the workarounds in #7 and #44? If they do not work
for you, the patch is most probably not applying to your case anyway...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393079
Hi Bernhard,
yes, this is how it should be done. You can store the patch-file in the
linux-3.16.0 directory. Then your point 4 is exactly what you have to execute.
But why do you want to compile the kernel? You said that Odie's
workaround worked for you. It should also work with your new install
Forgot one thing, you need:
sudo apt-get build-dep linux-image-$(uname -r)
before building the kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393079
Title:
Touchpad not working after
So here is the complete fix:
build a new kernel with the patch (see #36). Don't worry, it's very easy! Got
it from here:
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
Tested for the current kernel in 14.10
Get the source:
apt-get source linux-image-$(uname -r)
cd linux-3.16.0
replace the
Instead of replacing the file you should apply the attached patch:
patch drivers/hid/i2c-hid/i2c-hid.c i2c-hid.c.patch
** Patch added: i2c-hid.c.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1393079/+attachment/4308734/+files/i2c-hid.c.patch
--
You received this bug
The mainline kernel does not get security updates and is only intended
for debugging...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393079
Title:
Touchpad not working after suspend/resume
To
I just installed the 3.17.8 kernel. You can get the deb's from here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17.8-vivid/
For a 64-bit system you need
linux-headers-3.17.8-031708-generic_3.17.8-031708.201501081837_amd64.deb
linux-headers-3.17.8-031708_3.17.8-031708.201501081837_all.deb
odie, thanks for the try. Unfortunately it doesn't help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393079
Title:
Touchpad not working after suspend/resume
To manage notifications about this
@ tbreustedt: did you also remove the driver first (rmmod hid_multitouch)?
Also, you could try the same with i2c-hid:
sudo rmmod i2c-hid
sudo modprobe i2c-hid
Instead of odie's script you can also try the following for a permanent
solution:
sudo touch /etc/pm/config.d/00sleep_module
sudo chmod
Unfortunately. at least for KDE with customized settings for the
touchpad, it is not a satisfactory fix (see #36). As long as I don't
find a way to reload KDE settings via konsole I have to click through
the menue to properly restore the touchpad...
--
You received this bug notification because
Executing xinput on my laptop (Acer Aspire V Nitro) gives:
SYN1B7F:01 06CB:2970 UNKNOWN id=14 [slave pointer (2)]
for my touchpad.
From
http://www.adamdrew.net/?tag=kernel
I found a potential kernel patch which might solve the problem:
Public bug reported:
Streaming to an airport express box with AirTunes (pulseaudio-module-
raop) worked fine from 11.04 till 13.10. Since the upgrade to 14.04
streaming is unusable because of stuttering (the streaming breaks down
for fractions of a second or longer many times during a song). My
For me the streaming to the airport express box worked fine from 11.04
till 13.10. Since the upgrade to 14.04 streaming is unusable because of
the stuttering. My setup: Kubuntu, phonon-backend-gstreamer, amarok.
With phonon-backend-vlc the stuttering is even worse.
I downgraded
Public bug reported:
I have configured cups to use a printserver in ~/.cups/client.conf:
ServerName 141.xxx.xxx.xxx
Everything worked fine in Precise with cups 1.5. Since my upgrade to Quantal
with cups 1.6.1, I am unable to print. I get
dirk@gondor:~ lpstat
lpstat: Bad Request
** Affects:
I have the same problem as fejes. When I use the python interactive
shell I get:
Python 2.7.3 (default, Sep 26 2012, 21:51:14)
[GCC 4.7.2] on linux2
Type help, copyright, credits or license for more information.
import compizconfig
ctx = compizconfig.Context()
compizconfig - Info: Backend
Hi,
I was using the version from the PPA with no problems at all. Unfortunately,
compiz was updated yesterday (e.g. compiz-core:amd64 from
0.9.7.8-0ubuntu1vvpreproposed2 to 0.9.7.8-0ubuntu1.2). And now the flicker is
there again!?!?!
Could you please have a look at that.
--
You received this
Public bug reported:
After pausing a song, when resumed the volume is set to the maximum value
regardless of the previous setting.
This behavior started after the upgrade to Precise and only appears with the
phonon-backend-vlc and does not happen with phonon-backend-gstreamer.
As my volume is
There is some explanation here:
http://blogs.kde.org/node/4503
In my case it was not enough to delete $HOME/.local/share/akonadi, I
also had to delete $HOME/.config/akonadi and then restart akonadi and
update the akonadi configuration. Everything is fine again now.
If this happens to a newcomer
I ran into this problem this morning. Everything was fine on the first
boot. Then I did a hard switch off of my computer (this was not related
to akonadi). After starting it again akonadi now fills up the memory
very quickly.
Unfortunately disabling akonadi permanently is no option for me as I
After a compiz updates today I tried to run ccsm again. Unfortunately it still
does not work, but something changed. In addition to the output stated in the
initial bug report, I get lot's of
(ccsm:27947): GLib-GObject-CRITICAL **: g_object_set_qdata: assertion
`G_IS_OBJECT (object)' failed
Public bug reported:
I have installed NIS on our servers (Ubuntu Server 10.04.3, all updates
installed). Everything is working fine, except for one thing.
I added nis in /etc/pam.d/common-password:
password [success=1 default=ignore] pam_unix.so obscure sha512 nis
Users can now change their
Public bug reported:
When I start ccsm from the console I get:
Backend : kconfig4
Integration : true
Profile : unity
Adding plugins
Skipping upgrade com.canonical.unity.unity.01.upgrade
Skipping upgrade com.canonical.unity.unity.02.upgrade
Initializing core options...done
Segmentation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/898451
Title:
Unable to start ccsm (segmentation fault)
To manage notifications about this bug go to:
Unfortunately there is neither a compizconfig-settings-manager-dbg nor a
compizconfig-settings-manager-dbgsym package available. After following
instructions on https://wiki.ubuntu.com/DebuggingProgramCrash *-dbgsym
packages are available for many compiz components, but not for the ccsm
and
60 matches
Mail list logo