First, I installed the fix from your PPA first and then rebooted and still got
a crash
Then I disabled the vesafb kernel module using xdigagnose and rebooted and the
error did not pop up this time
Hope this helps
--
You received this bug notification because you are a member of Ubuntu-X,
Hi Reinhard,
It sounds like you have a clickpad trackpad. This is a known issue of
clickpad trackpads and X synaptics. The fix, as you noted, is to define
a bottom edge area. We probably want to do this for all clickpad
devices, which I believe we have information from the kernel for.
** Changed
This bug was fixed in the package xserver-xorg-video-savage -
1:2.3.1-2ubuntu2.1
---
xserver-xorg-video-savage (1:2.3.1-2ubuntu2.1) maverick-proposed; urgency=low
* 101_fix_use_of_privates.diff: From upstream, fixes crashes due to
use of uninitialized privates. LP: #635362
--
you need to enable the output from the display properties.
** Changed in: xorg (Ubuntu)
Status: New = Invalid
--
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/771458
Title:
S-video out
** Package changed: xserver-xorg-video-nv (Ubuntu) = nvidia-graphics-
drivers (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/763808
Title:
11.04 does not properly
how do i do that ?
--
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/771458
Title:
S-video out doesn't work
___
Mailing list:
Alright. On some other similar bugs to this one people are indicating
that the drm-intel-next-proposed kernel does indeed fix it. However,
we're far from narrowing down what specific patch is needed.
I am pretty sure your bug is the same as theirs. I will dupe these
together. If you have time
@AceLan Kao
I think I found the i915 patch, which would fix this bug (along with a
lot of other documented i915 fixes):
from (http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.39-rc1)
commit 36d527deadf7d0c302e3452dde39465e74a65a08
Author: Chris Wilson ch...@chris-wilson.co.uk
I can confirm similar behavior.
Installed Natty beta2 fresh (yesterday). AMD64. Applied all updates.
Using recommended Nvidia driver.
Not only do I experience a plain white screen when I maximize a window
(though the top menu appears to be intact), but I also have this problem
when I make the
There are a lot of them, including the most general bug #124406, so many
that I think we should be able to get priority on fixing this very
annoying bug. I also saw this bug sometimes in my old Asus EEE 1000.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Well, I ended up trying the other Nvidia driver sooner rather than
later because of this issue. Literally, the comp is nearly unusable
otherwise: the Nvidia configuration screen is too big, resulting in a
white out; the ubuntu system settings dialog is too big, resulting in a
white out. Neither
*** This bug is a duplicate of bug 745112 ***
https://bugs.launchpad.net/bugs/745112
Several other testers have found that drm-intel-next-proposed solves it.
There is a similar bug against sandybridge (#761065) which was isolated
down to 4 kernel patches recently, provided in this test
*** This bug is a duplicate of bug 745112 ***
https://bugs.launchpad.net/bugs/745112
** This bug is no longer a duplicate of bug 747205
[arrandale] Black screen on all outputs when external VGA is connected
** This bug has been marked a duplicate of bug 745112
[arrandale] desktop is
*** This bug is a duplicate of bug 745112 ***
https://bugs.launchpad.net/bugs/745112
** This bug is no longer a duplicate of bug 747205
[arrandale] Black screen on all outputs when external VGA is connected
** This bug has been marked a duplicate of bug 745112
[arrandale] desktop is
*** This bug is a duplicate of bug 745112 ***
https://bugs.launchpad.net/bugs/745112
** This bug is no longer a duplicate of bug 747205
[arrandale] Black screen on all outputs when external VGA is connected
** This bug has been marked a duplicate of bug 745112
[arrandale] desktop is
*** This bug is a duplicate of bug 745112 ***
https://bugs.launchpad.net/bugs/745112
** This bug has been marked a duplicate of bug 745112
[arrandale] desktop is messed up (goes black) when laptop is docked with two
external 1920x1200 monitors (x86_64)
* You can subscribe to bug 745112
*** This bug is a duplicate of bug 745112 ***
https://bugs.launchpad.net/bugs/745112
(Hmm, actually 737891 is a bit of a mess; I'll dupe to a more
appropriate one.)
** This bug has been marked a duplicate of bug 745112
[arrandale] desktop is messed up (goes black) when laptop is docked
*** This bug is a duplicate of bug 745112 ***
https://bugs.launchpad.net/bugs/745112
** This bug has been marked a duplicate of bug 745112
[arrandale] desktop is messed up (goes black) when laptop is docked with two
external 1920x1200 monitors (x86_64)
* You can subscribe to bug 745112
*** This bug is a duplicate of bug 745112 ***
https://bugs.launchpad.net/bugs/745112
** This bug is no longer a duplicate of bug 747205
[arrandale] Black screen on all outputs when external VGA is connected
** This bug has been marked a duplicate of bug 745112
[arrandale] desktop is
*** This bug is a duplicate of bug 745112 ***
https://bugs.launchpad.net/bugs/745112
** This bug is no longer a duplicate of bug 747205
[arrandale] Black screen on all outputs when external VGA is connected
** This bug has been marked a duplicate of bug 745112
[arrandale] desktop is
As a matter of facts, I have got the same problem.
I tried some tricks found here and there to configure properly my device but I
only got the eraser to work properly.
I bought this PenPartner years ago fot my old iMac, and I found it last Weekend
under a pile of olds CDs ...
So I can't say it
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
I have duped bugs #750259, #734756, and #747205 here.
Bug #737891 also exhibits this same issue but also conflates it with
another issue where creating a screen 4096 wide exceeds the max texture
width (as per the linked upstream bug), so I'm going to let that bug
focus on that particular issue
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
This kernel seem to have another regression that about one time in
three, when suspending, it will hang with the 'suspend' and capslock
lights flashing.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
*** This bug is a duplicate of bug 745112 ***
https://bugs.launchpad.net/bugs/745112
** This bug has been marked a duplicate of bug 745112
[arrandale] desktop is messed up (goes black) when laptop is docked with two
external 1920x1200 monitors (x86_64)
* You can subscribe to bug 745112
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
On lp #747205 we discovered by creating a new user account, that having
certain RANDR operations present in monitors.xml would trigger it,
presumably because gnome-settings-daemon would pick up those
configuration settings and try applying them, triggering an underlying
bug in RANDR. Perhaps
Bug #761236 is the broken-out portion of bug #737891 which is this
specific issue. On that report, it was found that kernel
2.6.39-0.4~20110419 resolved it, but the elderberry PPA with the -intel
workaround did not.
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Changed in: linux
That should capture all the background on the various instances of this
bug that I've been working with people on. Basically, there are some
variations in symptoms but all of the reports are particular to
Arrandale, occur in relationship with setting up external screens
(perhaps something
An alternative thing to investigate: There is another bug particular to
Sandybridge, with roughly similar symptoms to this one, which has
already been git bisected and found a candidate patch. The flagged
patch with the fix appears to also affect Arrandale, so I have a hunch
it *might* also
Right, and 761236 is looking like a dupe of a common Arrandale bug,
#745112. That in turn *might* be a sub-case of bug #761065 which
affects late-model cards and for which a kernel fix is being verified.
So, as to the disposition of this bug report: We've factored out the
single-monitor issue
Ok forget the post above. Seems to have nothing to do with this bug.
On Kernel 2.8.38: /sys/module/i915/parameters/semaphores is set to 0
On Kernel 2.8.39: /sys/module/i915/parameters/semaphores is set to 1
if i do the following:
sudo -i
echo 1 /sys/module/i915/parameters/semaphores
The Bug
Hmm, starting to sound like a bad modeline.
1. When did you first start noticing this? Were you running natty
previously and able to set this resolution without experiencing this
problem? Or was this the first time you tested it on natty? Carl, did
it happen on maverick for you as well, like
Daniel, again please do your testing using xrandr, not with the hotkey.
That is a more direct interface to the RANDR functionality, whereas
using the hotkey has dependencies/interactions with other non-X stuff
that could give false test results.
--
You received this bug notification because you
Looking at your dmesg anyway, this pops out as interesting:
[ 135.356761] [drm] GMBUS timed out, falling back to bit banging on pin
2 [i915 gmbus vga]
Can you do a fresh boot and look at dmesg before and then after
reproducing the problem. Does the printing of this line correlate to
the issue
Public bug reported:
Binary package hint: xorg
I have to constantly change my screen brightness because it never stays
to the brightness level I set it at. I'm NOT referring to the dim
display when idle option in power management. Even when I set the
brightness to max or min--it still changes
--
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/771561
Title:
Screen Brightness Settings Do Not Stick
___
Mailing list:
** Description changed:
Binary package hint: xorg
After a few months without any specific problems regarding my graphics
card I see screen artifacts in Gnome again (some time ago this problem
seemed to be solved, see bug 413259). It takes some time now after
booting up before the
** Changed in: xserver-xorg-video-intel
Status: Fix Released = Confirmed
--
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/727594
Title:
SRU: [i915gm] GPU lockup (ESR:
** Changed in: xserver-xorg-video-intel
Status: Fix Released = Confirmed
--
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/714719
Title:
[i915gm] GPU lockup (ESR:
The problem seems to persist in Natty – see bug 771370. Even though the
corruption looks quite different… it's the same graphics card with PCI
ID 1002:4c66.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
DBO on IRC thought they had an instance of this bug, but turned out in
their case to be caused by overlay-scrollbar, which appears to be
resulting in a lot of bugs with similar symptoms (white screens,
application-specificness, goes away after uninstalling overlay-
scrollbar). See bug #770304 as
(I suspect the original report predates overlay-scrollbar though. But
don't really have any ideas on diagnosing it.)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/752445
Hi FitzLT, can you elaborate on why you think this is an X bug?
Offhand sounds more like a power-management issue, but maybe you have
some additional rationale you omitted from the bug description?
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
You received this bug
** Description changed:
Binary package hint: xorg
X/GDM seemed to restart out of the blue resulting in the loss of
everything I had open. I was browsing with Chromium at that moment.
- 'm using a dual-monitor setup on a ATI Technologies Inc RV620 LE [Radeon
- HD 3450]. No changes made
If you could reproduce it I'd have you collect a full backtrace, but
since it appears to have been a one-time crash and has only a terse
Xorg.0.log crash log, it's unclear what happened.
I notice you have virtualbox-ose installed, which has it's own driver
modules. Perhaps it's doing something
*** This bug is a duplicate of bug 752940 ***
https://bugs.launchpad.net/bugs/752940
** This bug is no longer a duplicate of bug 753014
[i945gm] GPU lockup (ESR: 0x0010 PGTBL_ER: 0x0102)
** This bug has been marked a duplicate of bug 752940
GPU lockup (ESR: 0x0010 PGTBL_ER:
*** This bug is a duplicate of bug 752940 ***
https://bugs.launchpad.net/bugs/752940
Yeah that basically confirms it as the vesafb conflict, thanks.
** This bug has been marked a duplicate of bug 752940
GPU lockup (ESR: 0x0010 PGTBL_ER: 0x0010) - i915 unused but triggers
apport
*** This bug is a duplicate of bug 745112 ***
https://bugs.launchpad.net/bugs/745112
Alright, well it is an experimental kernel and likely has its own new
bugs it brings, but we should stay focused on the original black screen
issue. (If you feel motivated, upstream would probably like to
This sounds much like bug #745112 although the chipset is different.
Install and boot this kernel, and see if it fixes it:
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next-proposed/
If so, then install this kernel and see if it also fixes it or not:
This happens to me as well on my 1005HA on Natty beta2 with all updates.
--
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/745304
Title:
Graphics corruption after hibernate
Install xdiagnose, and then run 'sudo xdiagnose'. Turn on graphics
debug messages (the first checkbox).
Reboot, and then reproduce the issue changing your screen's backlight
setting. Now ssh into the machine while it is frozen, and run the
command 'dmesg ~/dmesg.txt' and 'cp
Hmm, bummer that didn't turn up anything useful. Well, one other
possible thing to try. There's another hangtimer check failed bug for
this hardware, bug #761065, which has a fix identified. Try booting
this kernel:
http://people.canonical.com/~acelan/bugs/lp753189/
If that doesn't fix it,
Probably a dupe of bug #727594. Test natty-proposed.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Thanks for confirming the ppa fixed it. I've posted an SRU for that fix
with bug #727594, and the fix is now available in natty-proposed.
Basically, this bug report should be marked a dupe of #727594 now.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Fix Committed
The fix is currently sitting in the queue for the next stable kernel
release and should be included in an update shortly after the natty
release.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
I was having a very similar issue with a thinkpad X201 (see
https://bugs.launchpad.net/bugs/771344 - which is now duped here)
However, booting with the monitors plugged in made no difference - I
would go to the black screen regardless when I logged in an existing
account.
However, a freshly
Stack Trace added, should be enough to debug or at least file upstream.
** Summary changed:
- xterm font corruption with unity and nouveau experimental 3d
+ xterm font corruption and X crash with nouveau experimental 3d (not just
Unity)
** Description changed:
Binary package hint: unity
Not sure how to remove Unity from the affects line. If someone would
do that, I'd appreciate it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/767970
Title:
xterm font corruption and X crash
, i686: installed
GraphicsCard:
nVidia Corporation C79 [GeForce 9300 / nForce 730i] [10de:086c] (rev b1)
(prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. Device [19da:0ae5]
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
JockeyStatus:
xorg:nvidia_173
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/771594
Title:
Nvidia-current don't work whit 9300 igp (zotac) 32/64 bit
___
Mailing
[Expired for xserver-xorg-video-mga (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: xserver-xorg-video-mga (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
Thank you for taking the time to report this bug and helping and helping
to make Ubuntu better. Unfortunately, the package installation log
attached to this bug report does not contain any useful information this
is likely because your root filesystem is full. This is probably why
the package
On Tue, Apr 26, 2011 at 03:32:31PM -, libihero wrote:
how would i be able to give you that?
ssh your machine
dmesg dmesg.txt
cp /var/log/Xorg.0.log ~
reboot
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to :
Same Problem on t43p on Maverick
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/92482
Title:
NumLock gets enabled unexpectedly on my laptop
I've got new news on my status. I noticed that my monitor does not blink
anymore. I speculate an update in this past week has fixed the issue.
However, this only bring me back to the better functionality I had with
Ubuntu 10.10. I still have the tiled screen as I posted pictures of from
my phone.
removed unity from affects as the issue is in other stack
** Project changed: unity = null
** Changed in: null
Status: Incomplete = Invalid
** Changed in: unity (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
I add the output of dmesg.
The command cp /sys/kernel/debug/dri/0/i915_error_state
i915_error_state.txt, just outputs no error state collected. So, I do
not think, it's necessary to attach this file
** Attachment added: dmesg.txt
Similar problem with lenovoT410. when I wake up or reboot my laptop the
X session doesn't start completely.
--
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/737891
Title:
201 - 290 of 290 matches
Mail list logo
