I also ran the i2c_hid module with debug enabled (`modprobe i2c_hid
debug=1`), which gives a bit of insight in what commands are sent to the
touch screen. On a suspend, it seems to send a sleep command. On a
resume, it sends a power on command, followed by a reset command (which
is properly acknowl
I dug around a bit, and found that the touchscreen can also be fixed by
reloading the ic2_hid module.
It also works to reinitialize just the hid driver for the touchscreen
(rather than reloading the entire module) by running:
echo 0018:06CB:77B2.000C > /sys/bus/hid/drivers/hid-multitouch/unbind
e
** Description changed:
I'm not entirely sure this bug belongs in package xinput, but I'm
- following the lead of #1275416, which describes the same symptoms (but
- on other hardware, so likely a different underlying problem).
+ following the lead of
+ https://bugs.launchpad.net/ubuntu/+source/x
Public bug reported:
I'm not entirely sure this bug belongs in package xinput, but I'm
following the lead of #1275416, which describes the same symptoms (but
on other hardware, so likely a different underlying problem).
On this notebook, the touchscreen works well out of the box. But as soon
as I
** Description changed:
After resuming from a suspend, almost all text on screen is not visible.
This includes menu items, text in all three boxes (list of folders, list
of e-mails, e-mail body) in Thunderbird (with the curious exception of
"ffl" in the File menu), top menu in Chromium (bu
In case any one else comes across this problem: I had exactly the same
symptoms and found out they were caused by xbindkeys that was started in
the background. Removing my .xbindkeysrc solved the problem for me.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I'm confused. I just got this error while trying to installing linux-
generic-lts-saucy on my 12.04.3 machine. The build for both nvidia-304
and nvidia-319 failed:
nvidia-304 304.88-0ubuntu0.0.3: nvidia-304 kernel module failed to build
nvidia-319 319.32-0ubuntu0.0.1: nvidia-319 kernel module fail
Also worth mentioning is that I'm also getting i915 related errors in
syslog which actually did not cause any problems in the UI. All entries
mentioned in the attached file for example - I just happened to see them
because I had the Log File Viewer open at that moment, but the machine
and UI just k
Just got a complete lock-up on kernel 3.7.4, I could not even ping the
machine anymore. Syslog shows this as the last entry before I shut down
the machine by pressing the power button for > 3 seconds (even the reset
button did not work anymore!):
Jan 28 11:28:39 simba kernel: [ 7659.927292] [drm:_
Then 6 seconds later, again (second file). The GUI is completely frozen
at that point, but I can still move the mouse cursor.
I should point out that only the GUI breaks down - I can still SSH into
the machine and do stuff from there.
In the mean time I've upgraded to kernel 3.7.4 to see if that
Here are two syslog snippets from the last time my machine crashed.
A lot of repeating stuff is going on at 14:11:41 (first file).
** Attachment added: "20130124 syslog at 14h11m41s crash.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/975083/+attachment/3498197/+
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Expired => New
** Changed in: linux (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad
This bug is still very much present, even with all the latest updates
installed. I just ran into it several times after re-installing my
system from scratch and trying again for a moment without the separate
videocard. It's even become worse since the system just drops (locks) to
a shell (see attac
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1011994
Title:
Connecting / disconnecting DisplayPort often causes crash
To manage notifications about this bug go to:
https://
Public bug reported:
As per http://askubuntu.com/questions/146716/connecting-disconnecting-
displayport-causes-crash :
When I connect or disconnect an external monitor to DisplayPort of my HP
ProBook 6550b, the system crashes most of time.
While the situation in Ubuntu 11.10 was still somewhat w
Latest news after two more weeks of using 12.04:
- Crashes became less frequent but were indeed not gone both with the 3.4 as
well as with the latest 3.2 kernel
- Apport no longer 'detected' any of the crashes so I was unable to send out
any reports about them (regression in Apport?)
- Since the
Sure thing. I've reserved today for extensively testing 12.04 so
hopefully by tomorrow I will have a fairly good picture of all the
issues that are still present.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Well this is interesting. I've just been working for about an hour and a
half with kernel 3.2.0-23 without experiencing a single lock up.
The load issue is still there though, but at least now I am able to get
some work done. Now let's see how well this kernel deals with
suspend/resume... I will k
Today I experienced a complete lock up of the machine with kernel
3.4rc2, only a few minutes after booting. The only program that was
running was Team Viewer 6.
After resetting the machine, the issue did not return and I also was not
prompted by Apport to file a bug.
So perhaps it was a one-time
Well after rebooting, the situation seems to be a lot better. With the
previous kernel (or perhaps before the updates were applied) I would
have experienced several lock ups by now, but right now it has not
failed even once. Of course this is after running for less than half an
hour, so I guess mor
Just filed bug 979367, bug 979368 and bug 979369 while running the
3.4rc22 kernel. However, over 200 megs in updates had not been applied
yet, so perhaps this was all in vain :-(
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-
Never mind about the Apport crash, this was already reported in bug
901675. Now applying over 200 megs in updates, so perhaps this entire
endeavor has been in vain
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ub
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/979368
Title:
[sandybridge-gt1] GPU lockup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
Public bug reported:
As part of the investigation for bug 975083, I'm filing this bug as I'm
now running the 3.4rc2 kernel. This is number two out of three, number
one is bug 979367.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
Uname: Linux 3.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/979369
Title:
[sandybridge-gt1] GPU lockup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
Public bug reported:
As part of the investigation for bug 975083, I'm filing this bug as I'm
now running the 3.4rc2 kernel. This is number three out of three, number
one is bug 979367 and number two is bug 979368.
Next up is the Apport crash, as mentioned in bug 979367 :-)
ProblemType: Crash
Dis
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/979367
Title:
[sandybridge-gt1] GPU lockup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
Public bug reported:
As part of the investigation for bug 975083, I'm filing this bug as I'm
now running the 3.4rc2 kernel. I was prompted for this right after
startup, after the system had failed to resume which forced me to cut
and restore the power to the machine. The first boot attempt after t
Running this kernel now and was greeted by another Apport popup. Since I
suspected this to be a leftover from the previous boot, I ignored it. I
will keep working with this kernel and report my findings here.
One thing that has not been solved with this kernel is the load - this
is still constantl
And here's a screenshot of what that particular 'crash' results into.
** Attachment added: "Screenshot from 2012-04-10 20:13:45.png"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/975083/+attachment/3041867/+files/Screenshot%20from%202012-04-10%2020%3A13%3A45.png
--
And here's a screenshot of what that particular 'crash' results into.
** Attachment added: "Screenshot from 2012-04-10 20:13:45.png"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/975083/+attachment/3041866/+files/Screenshot%20from%202012-04-10%2020%3A13%3A45.png
--
Oh and the bugreport for #12 is bug 978239.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/975083
Title:
[sandybridge-gt1] GPU lockup
To manage notifications about this bug
And right after posting the previous comment, my system went one step
further into the state of becoming fully unusable. This time it was the
'all-decorations-and-controls-gone' kind of crash. Luckily I still had
this browser window open with the terminal on top, so I was able to
'save' the i915_er
I just filed three more instances of this bug, one with the exact same
result as in this bug (bug 978219) and two bugs (one pair) which are
related to a single 'almost' crash: bug 978221 and bug 978222.
I hope these shed more light on the matter.
Also, I've attached the i915_error_state which is
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/978239
Title:
[sandybridge-gt1] False GPU lockup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
Public bug reported:
...and yet another 'false' lockup, this time as described here:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/975083/comments/12
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
ProcVersionSignature:
And the 'twin brother' of this bug report (they always come in pairs)
can be found in bug 978222.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/978221
Title:
[sandybridge-gt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/978221
Title:
[sandybridge-gt1] False GPU lockup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
Public bug reported:
Similar to bug 975083, but this GPU lockup actually only manifested itself as a
short black out, after which the system returned to 'normal' (and promptly
asked me to file this bug).
I will file the accompanying second report right after this one and provide the
number here
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/978219
Title:
[sandybridge-gt1] GPU lockup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
Public bug reported:
Very much the same as bug 975083, but filed once more in the hopes of
producing more useful debug data.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/978222
Title:
[sandybridge-gt1] False GPU lockup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
Public bug reported:
This is the 'twin-brother' of bug 978221.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
.tmp.unity.support.test.0:
ApportVersion
Well... it just happened again while browsing Youtube videos
(unfortunately I was not running GTKrecordmydesktop) and when looking at
the /sys/kernel/debug/dri/0/i915_error_state file via SSH, both EIR,
PGTBL_ER, and all of the IPEHR's where displaying 0x000.
However, before this particular lo
Oh and just as in bug 975444, the crash reports always come in pairs.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/975083
Title:
[sandybridge-gt1] GPU lockup
To manage not
It just happened again, after first blanking for a moment (which kicked
of apport, see bug 975444). SC was not even running, so I removed it
from the bug's description. Now using GTKrecordmydesktop as I'm typing
this (found a switch which enabled 'on the fly' encoding), so if it
happens again we wi
Oh and little extra piece of info - the crash reports always come in
pairs. I skipped the second one because it probably would not have added
any extra info.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
http
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/975444
Title:
[sandybridge-gt1] False GPU lockup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
Public bug reported:
Related to bug 975083 - sometimes my screen blanks for a second and then
I immediately get the apport crash 'wizard' kicking in (which is
awesome). However, a *real* lockup (as in bug 975083) occured right
after trying to report this very bug.
ProblemType: Crash
DistroRelease
Thanks Bryce for your swift response. I'll try to answer your questions
as best as possible:
1. The machine was running 11.10 before, but I completely wiped the root
partition (I always do this due to bad past experiences with
'upgrades'). I never had any use for sync in the past, so I never tried
Don't know if this helps, but bug 975315 was reported today and seems to
be similar.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/975083
Title:
[sandybridge-gt1] GPU lockup
...and again.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/975083
Title:
[sandybridge-gt1] GPU lockup
To manage notifications about this bug go to:
https://bugs.launchpad.
This just happened again.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/975083
Title:
[sandybridge-gt1] GPU lockup
To manage notifications about this bug go to:
https://bug
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/975083
Title:
[sandybridge-gt1] GPU lockup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
Public bug reported:
Might be similar to bug 902787, but I do have composite enabled so therefore
filing a new bug.
I just installed 12.04 beta 2 today (fresh install), updated it and after a
reboot I was just working with SC to re-install my apps using the nifty 'Sync
Between Computers' option
Same for HP Pavilion dm1 1020, touchpad not recognized.
--
[Karmic] Touchpad not recognised correctly, synaptics driver not in use
https://bugs.launchpad.net/bugs/380126
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in
Fixing from CLI isn't my favorite part. But the bug is driving me crazy
...
--
[multi screen] mouse position sometimes wrong
https://bugs.launchpad.net/bugs/363375
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in ubuntu
My search ended up here: https://launchpad.net/~xorg-
edgers/+archive/ppa/+build/1151959 Do i need all these debs / built
files below on the page? Or can i add some lines to the repo? I can't
find anywhere the right code to do this.
--
[multi screen] mouse position sometimes wrong
https://bugs.la
@Dustin: where can i get this package / what is a easy way to install
this?
--
[multi screen] mouse position sometimes wrong
https://bugs.launchpad.net/bugs/363375
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in ubuntu
59 matches
Mail list logo