*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
That sounds more like a window manager bug; in any case wouldn't likely
be related to a gpu lockup.
Ok, thanks, it looks like this is in fact a dupe of the false gpu lockup
bug; I'll dupe it.
** This bug has
It is possible. I had updated the system then update requested a restart
because a kernel update. And the message popped up after the restart.
--
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.launch
No, I don't have a lockup and mouse still usable.
The only thing I notice, is that some windows are not movable/minimizable until
I select them again via left unity menubar. But I am not sure if that
misbehaviour is a result of the error or if it is a different bug/problem.
--
You received this
** Package changed: plymouth (Ubuntu) => xorg-server (Ubuntu)
--
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/691526
Title:
plymouth fails to mount, crashes xsystem
To manage notification
You have been subscribed to a public bug:
Binary package hint: plymouth
If I remove xorg.conf I can restart into gnome, poor res.
Nvidia reinstall doesn't fix the issue or reconfigure of xorg.conf
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: plymouth 0.8.2-2ubuntu5.1
ProcVersionSignatu
TsFox, please perform at the Terminal:
apport-collect 853598
As well, please follow the steps noted at
https://wiki.ubuntu.com/X/Reporting
** Package changed: libreoffice (Ubuntu) => xorg (Ubuntu)
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug notificat
Alright, thanks! I'm not sure how to subscribe to it on there. Is it the
CC list? I'll keep checking on it to see if they need me, as well as
post a comment, advertising my presence.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-vi
You have been subscribed to a public bug:
I'm using Classic desktop - 11.04 64 bit.
2.6.38-11-generic #48-Ubuntu SMP Fri Jul 29 19:02:55 UTC 2011 x86_64 x86_64
x86_64 GNU/Linux
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 2.6.38-1
[Expired for xserver-xorg-input-keyboard (Ubuntu) because there has been
no activity for 60 days.]
** Changed in: xserver-xorg-input-keyboard (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-x
Ok, so that wasn't too useful. Please install 'xdiagnose' first, then
run apport-collect..
--
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/854985
Title:
Freezes computer using a lot CPU
To manag
You can select which libGL is used by running ‘sudo update-alternatives
--config x86_64-linux-gnu_gl_conf’ (on amd64) or ‘sudo
update-alternatives --config i386-linux-gnu_gl_conf’ (on i386).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
Michael - I've forwarded this bug upstream to
http://bugs.freedesktop.org/show_bug.cgi?id=41103 - please subscribe
yourself to this bug, in case they need further information or wish you
to test something. Thanks ahead of time!
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incom
Thanks Michael. I think in terms of logs we have everything necessary.
Upstream may wish to have you test some alternative kernels or patched
X. Stay tuned for that.
** Bug watch added: freedesktop.org Bugzilla #41103
http://bugs.freedesktop.org/show_bug.cgi?id=41103
** Also affects: xserve
Jiri Techet - I've forwarded this bug upstream to
http://bugs.freedesktop.org/show_bug.cgi?id=41102 - please subscribe
yourself to this bug, in case they need further information or wish you
to test something. Thanks ahead of time!
** Bug watch added: freedesktop.org Bugzilla #41102
http://bug
Was this while running under KDE? Was kwin running?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Incomplete
--
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
Jorge Godoy - I've forwarded this bug upstream to
http://bugs.freedesktop.org/show_bug.cgi?id=41101 - please subscribe
yourself to this bug, in case they need further information or wish you
to test something. Thanks ahead of time!
** Bug watch added: freedesktop.org Bugzilla #41101
http://bug
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug has been marked a duplicate of bug 828684
[i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
--
You received this bug notification because you are a member of Ubuntu-X,
which is s
Hi Bryce,
Yes, my system did lock-up. The computer appeared to be unresponsive to
anything but powering it down and the video signal to the screen appeared to
completely cease. Please let me know if there is any testing that you need
from me to help resolve the issue.
Thanks,
Michael
On Wed,
Hi Paulo, can you provide a more elaborated description of the problem
as you saw it?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided => High
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu
** Changed in: xserver-xorg-video-intel
Status: Unknown => Confirmed
** Changed in: xserver-xorg-video-intel
Importance: Unknown => High
--
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.l
** Changed in: xserver-xorg-video-intel
Status: Unknown => Confirmed
** Changed in: xserver-xorg-video-intel
Importance: Unknown => High
--
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.l
Corbin - I've forwarded this bug upstream to
http://bugs.freedesktop.org/show_bug.cgi?id=41099 - please subscribe
yourself to this bug, in case they need further information or wish you
to test something. Thanks ahead of time!
** Bug watch added: freedesktop.org Bugzilla #41099
http://bugs.fre
** Changed in: xserver-xorg-video-intel
Status: Unknown => Confirmed
** Changed in: xserver-xorg-video-intel
Importance: Unknown => High
--
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.l
** Changed in: xserver-xorg-video-intel
Status: Unknown => Confirmed
** Changed in: xserver-xorg-video-intel
Importance: Unknown => Medium
--
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
To answer your question, the bug is that your video card GPU locks up
for some reason, probably due to an error in either the mesa gl driver
for Intel, or the linux kernel drm intel graphics driver. IPEHR 0x7XXX
type errors _typically_ are mesa bugs.
It is actually very good to hear you're able t
** Tags added: gnome-shell
--
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/848598
Title:
[sandybridge-m-gt2] GPU lockup render.IPEHR: 0x7a02
To manage notifications abou
PSN - I've forwarded this bug upstream to
http://bugs.freedesktop.org/show_bug.cgi?id=41098 - please subscribe
yourself to this bug, in case they need further information or wish you
to test something. Thanks ahead of time!
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Co
Hi Rems,
Please let me know when this bug happens for a second time, then we'll
notify upstream about it.
(So far, it looks like a generic gpu lockup; hard to pinpoint cause in
this case.)
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Incomplete
--
You received this bu
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Invalid
--
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/848092
Title:
[i915gm] GPU lockup
To manage not
Jon Arnold - I've forwarded this bug upstream to
http://bugs.freedesktop.org/show_bug.cgi?id=41097 - please subscribe
yourself to this bug, in case they need further information or wish you
to test something. Thanks ahead of time!
** Bug watch added: freedesktop.org Bugzilla #41097
http://bugs
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Invalid
--
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/844956
Title:
[i915gm] GPU lockup
To manage not
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Invalid
--
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/855717
Title:
[sandybridge-m-gt2] GPU lockup
To
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Incomplete
--
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/839338
Title:
[arrandale] False GPU lockup r
Hi Szilard, the timestamp associated with the crash message in the log
appears to suggest the lockup occurred after the system had been up for
a long time. Is it possible that your system had locked up in a
previous session, and after restarting the computer the error message
popped up?
** Descri
nvucinic - I've forwarded this bug upstream to
http://bugs.freedesktop.org/show_bug.cgi?id=41096 - please subscribe
yourself to this bug, in case they need further information or wish you
to test something. Thanks ahead of time!
** Bug watch added: freedesktop.org Bugzilla #41096
http://bugs.f
** Also affects: gnome-desktop (Ubuntu P-series)
Importance: Undecided
Status: New
** Also affects: xserver-xorg-video-intel (Ubuntu P-series)
Importance: Undecided
Status: New
** Tags removed: rls-mgr-o-tracking
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug has been marked a duplicate of bug 828684
[i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
--
You received this bug notification because you are a member of Ubuntu-X,
which is s
** Changed in: xserver-xorg-video-intel
Status: Unknown => Confirmed
** Changed in: xserver-xorg-video-intel
Importance: Unknown => High
--
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.l
2011.09.21 and still having the same driver issue. I'd gladly supply
traces and/or error documents.
Lenovo - Thinkpad X201
Ubuntu 11.04
2.6.38-11-generic-pae #50-Ubuntu SMP Mon Sep 12 22:21:04 UTC 2011 i686 i686
i386 GNU/Linux
Everything's up-to-date.
GDM/KDM/Gnome/Kde/Compiz/metacity/kwin does
Okay, thanks for letting us know. It may have been solved via a kernel
update earlier. Please re-report if you reproduce the lockup.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubun
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug is no longer a duplicate of bug 814450
[gm45] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0003
** This bug has been marked a duplicate of bug 828684
[i965gm] False GPU lockup EIR: 0x0010
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug has been marked a duplicate of bug 828684
[i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
--
You received this bug notification because you are a member of Ubuntu-X,
which is s
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => Triaged
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in U
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided => High
--
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/850939
Title:
[i965gm] GPU lockup EIR:0x0
Hi Martin,
Just to be clear - does your system actually lock up at that point?
I.e. screen unresponsive but mouse cursor may still move.
If there are no symptoms whatsoever apart from the error dialog, this is
probably a dupe of bug 828684 which we're trying to investigate.
** Changed in: xserve
** Description changed:
- From a dupe:
+ [Problem]
+ The Intel driver experiences a GPU hang, but is able to recover from it
automatically. The user does not see any sort of bug/crash/lockup symptom,
however the error handler does detect the GPU hang and triggers the crash
report dialog.
+
+
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
Yeah, sorry about that. We're still not sure what causes these errors,
or whether it's an upstream bug or something peculiar to the Ubuntu
kernel's module loading. We will be shutting off the error prompts o
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug is no longer a duplicate of bug 849107
[i945gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0102
** This bug has been marked a duplicate of bug 828684
[i965gm] False GPU lockup EIR: 0x
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug is no longer a duplicate of bug 849107
[i945gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0102
** This bug has been marked a duplicate of bug 828684
[i965gm] False GPU lockup EIR: 0x
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug has been marked a duplicate of bug 828684
[i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
--
You received this bug notification because you are a member of Ubuntu-X,
which is s
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug is no longer a duplicate of bug 849594
[i915gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
render.IPEHR: 0x7d8e0001
** This bug has been marked a duplicate of bug 828684
[i965gm]
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug has been marked a duplicate of bug 828684
[i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
--
You received this bug notification because you are a member of Ubuntu-X,
which is s
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug has been marked a duplicate of bug 828684
[i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
--
You received this bug notification because you are a member of Ubuntu-X,
which is s
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug is no longer a duplicate of bug 849594
[i915gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
render.IPEHR: 0x7d8e0001
** This bug has been marked a duplicate of bug 828684
[i965gm]
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug has been marked a duplicate of bug 828684
[i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
--
You received this bug notification because you are a member of Ubuntu-X,
which is s
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug is no longer a duplicate of bug 850755
[i915gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
render.IPEHR: 0x0100
** This bug has been marked a duplicate of bug 828684
[i965gm]
Huh, this is weird. You got an intel GPU hang/recover, and the i915
driver is loaded, but you don't seem to have any intel graphics chips in
your pci list, but rather a radeon card. And you have some sort of
virtualbox thing going.
Having both i915 and radeon kernel modules is probably not going
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug is no longer a duplicate of bug 850755
[i915gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
render.IPEHR: 0x0100
** This bug has been marked a duplicate of bug 828684
[i965gm]
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug is no longer a duplicate of bug 850755
[i915gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
render.IPEHR: 0x0100
** This bug has been marked a duplicate of bug 828684
[i965gm]
*** This bug is a duplicate of bug 828684 ***
https://bugs.launchpad.net/bugs/828684
** This bug is no longer a duplicate of bug 850755
[i915gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
render.IPEHR: 0x0100
** This bug has been marked a duplicate of bug 828684
[i965gm]
** Description changed:
I got this just after booting
+
+ [ 22.303517] [drm] radeon defaulting to kernel modesetting.
+ [ 22.303525] [drm] radeon kernel modesetting enabled.
+ [ 22.303647] radeon :02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
+ [ 22.303659] radeon :02:00.0
Damian Christey - I've forwarded this bug upstream to
http://bugs.freedesktop.org/show_bug.cgi?id=41092 - please subscribe
yourself to this bug, in case they need further information or wish you
to test something. Thanks ahead of time!
** Bug watch added: freedesktop.org Bugzilla #41092
http:/
Ok i will try it... I also found an other way to make it work:
I plug it , I launch a virtual windows in Virtualbox and i redirect the
pad to the windows... and then there is no mouse problem
-Message d'origine-
De : boun...@canonical.com [mailto:boun...@canonical.com] De la part de Timo
** Changed in: xserver-xorg-video-intel
Importance: Medium => High
--
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/854986
Title:
[eDP1] 5 second delay between Xorg starting
Seth Forshee's patched driver version 0.2 work as expected with my sony VPC EB
4X8E
(previously I have to use the proto=imps module option)
thank you Seth
I attached alps reg dump from my computer and these are my maximum X and Y:
ABS_X=1827
ABS_Y=1329
how about a multitouch version?
** Attac
Public bug reported:
I was attempting to test this bug:
https://bugs.launchpad.net/bugs/781384 by installing FGLRX via jockey-
gtk. After I found that there were no fixes (still), I went back to
jockey and uninstalled FGLRX. However, upon rebooting, I found that
Unity would not load. Applications
The bug occurred again twice, so I'm attaching my dmesg output from the
first time. Hope you can work with that.
** Attachment added: "dmesg_not-working.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550625/+attachment/2438005/+files/dmesg_not-working.txt
--
You received this bug
The nvidia binary driver doesn't detect external monitors, you need to
configure it by using nvidia-settings.
** 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
the issue is not a lightdm one, it's xorg doing and not new (gdm was
doing that previous cycles as well)
--
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/850906
Title:
Login screen displaye
This problem no longer occurs after the latest batch of updates.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/848280
Title:
Dash in Unity-2D doesn'tdisplay properly.
To mana
Sorry, Bryce, of course!
--
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/852918
Title:
[sandybridge-m-gt2] False GPU lockup render.IPEHR: 0x0204
To manage notifications
I experience a similar bug.
I run VirtualBox with a Microsoft XP guest under Ubuntu 10.04 (Gnome). When I
leave the machine idle, the screensaver will appear (no problem) then the
monitor shuts off (as expected). Then inexplicably I get a dialogue "Ubuntu is
in low graphic mode". The dialogue (r
Seems to happen only running VirtualBox with Microsoft XP guest.
I run dual monitors (Dell Latitude D820 and a Dell external monitor. Machine
will crash no matter which display VirtualBox is running on.
I made a similar report on Bug 577487.
Workaround: Do not leave computer idle with VirtualBox
** Changed in: xserver-xorg-video-intel
Status: Unknown => Confirmed
** Changed in: xserver-xorg-video-intel
Importance: Unknown => Medium
--
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
I have just found the "master" bug of the Firefox performance issue (with link
to Mozilla upstream bug):
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/605567
Kind regards,
Jan
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-grap
** Branch linked: lp:indicator-datetime
--
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/730476
Title:
Part of the time appears cut off when displaying the day of the week
an
Hi Bruce,
I cannot confirm that. The system did not show any sign of error exept
for the "Report the Bug" popup. I did not hang and I had not powered
down or rebooted the system by hard until that time.
Unfortunately I can't login any more since todays upgrades. I'm hoping
that that bug be fix
** Changed in: unity-foundations
Status: In Progress => Fix Committed
** Changed in: indicator-datetime
Status: In Progress => Fix Committed
** Changed in: indicator-datetime
Milestone: None => 0.2.96
--
You received this bug notification because you are a member of Ubuntu-X,
** Description changed:
First time I've seen this one.
+
+ [14585.553826] PM: resume of drv:sd dev:2:0:0:0 complete after 485.400 msecs
+ [14585.553863] PM: resume of drv:scsi_disk dev:2:0:0:0 complete after 141.803
msecs
+ [14585.554026] PM: resume of drv:scsi_device dev:2:0:0:0 complete afte
** Changed in: unity-foundations
Milestone: oneiric-beta-2 => oneiric-final
--
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/730476
Title:
Part of the time appears cut off
** Changed in: unity-foundations
Milestone: oneiric-beta-2 => oneiric-final
--
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/832624
Title:
cursor jumping to screen border
To manage not
I had to test Oneiric Beta 2 20110921.1 image
(http://cdimage.ubuntu.com/daily-live/20110921.1/oneiric-desktop-amd64.iso) and
I discovered that this crash does not occur any more, while with 20110920 image
it happened everytime I used to start the persistent USB key.
Do I still have to try to do
Mark Bidewell - I've forwarded this bug upstream to
http://bugs.freedesktop.org/show_bug.cgi?id=41091 - please subscribe
yourself to this bug, in case they need further information or wish you
to test something. Thanks ahead of time!
** Bug watch added: freedesktop.org Bugzilla #41091
http://b
maybe its for Xorg?
** Package changed: ubuntu => xorg (Ubuntu)
--
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/854227
Title:
external monitor not detected in 11.10
To manage notifications abou
Actually, the error occurred during your previous session, but the crash
handler only popped up after rebooting. It looks like the system
recovered from the crash so you probably saw no symptoms.
** Description changed:
Error seems to occur on login
+
+ [ 1285.312032] wlan0: no IPv6 routers p
** Summary changed:
- [RV250] Screen artifacts
+ [RV250] Screen artifacts on X
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/766693
Title:
[RV250] Screen artifacts on X
To m
You have been subscribed to a public bug:
I would like to extend my desktop to an exteral monitor plugged in via
DVI.
My system:
Nvidia 7300 Card
Driver: Nvidia 173
Ubuntu 11.10 beta 1 (installed 18.09.2011)
Directly after installtion I was able to use the laptop and external monitor as
desired
Hi Michael,
Just to confirm - on your previous boot before this crash dialog
appeared, did your system lockup, or did it shutdown cleanly?
Looking at your dmesg, there is a GPU Hung error at the end of the log,
which suggests to me your system really did crash and burn, and it looks
like you had
Hi mholzapfel,
Looking at your dmesg I notice that the GPU hung error is the last entry
in your log, which makes me wonder if your machine hung during shutdown
of your previous session? Near as I can tell this is not a dupe of bug
#828684 (the general False GPU lockup), so this may be worth furth
Hi David,
Could you elaborate your problem description further?
The logs that were collected simply indicate this lockup was a false alarm (so
just a dupe of #828684), but perhaps you have an actual issue you're trying to
report?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: N
I had a look at the Krita sources, as pointed out by Jussi, and the
problem does not come from the kis_canvas_controller code, but seems to
come from kis_canvas_widget_base.cpp.
There, we have the following code:
void KisCanvasWidgetBase::processTabletEvent(QTabletEvent *e)
{
widget()->setFoc
The most trustworthy source for Ubuntu kernels is
http://kernel.ubuntu.com/~kernel-ppa/mainline/
--
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/763688
Title:
[915GM] S-video
** Changed in: unity
Status: New => Confirmed
** Tags added: nvidia
--
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/855414
Title:
Unity dash becomes very slow/laggy whe
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
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/b
Seeing this as well. But the slowness of the dash reveal is disregarding
whether I use mouse or keyboard to reveal the dash.
** Also affects: unity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity (Ubuntu)
Status: New => Confirmed
--
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/bug
1 - 100 of 160 matches
Mail list logo
