[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-vi
Launchpad has imported 2 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=66366.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
On Wed, Jun 26, 2013 at 11:04:43PM +, bugzilla-dae...@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=64073
>
> --- Comment #18 from Ben Widawsky ---
> If someone can reproduce this, can they read back register 0x20f4?
>
Would that not be in the error state dump I atta
(In reply to comment #17)
> I can confirm that I did see strange white corruption when playing the
> game, but I thought it was unrelated or an application error.
>
> Unfortunately, I don't have access to the hardware anymore so I cannot
> further test anything. However, given that the hangs happ
I can confirm that I did see strange white corruption when playing the
game, but I thought it was unrelated or an application error.
Unfortunately, I don't have access to the hardware anymore so I cannot
further test anything. However, given that the hangs happened on two
different OSes, with the
Is there any input or assistance I can give to help move this along?
Thanks!
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b16000
** Tags added: lucid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/896922
Title:
Lenovo L520 - "psmouse.c: touchpad at isa0060/serio4/input0 lost sync"
and stops worki
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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1194478
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
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/1194478
Title:
*** This bug is a duplicate of bug 1195618 ***
https://bugs.launchpad.net/bugs/1195618
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1195618, so it is being marked as such. Please look
I can confirm this seems to be a v3.8 bug. I get the same symptoms on
amd64 3.8.0-25.37 (current raring kernel), and
3.8.0-27.39~pre201306280400 (current raring kernel-ppa pre-proposed.)
When I installed a v3.9 kernel (I used 3.9.0-030900.201304291257 from
http://kernel.ubuntu.com/~kernel-ppa/main
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
This should be the Xorg.log from my attempt to boot 3.10.0-1.8 with the
broken nvidia kernel module. There was nothing listed in either
kern.log nor syslog indicating why or what happened.
** Attachment added: "Xorg.1.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-310-
Public bug reported:
I was humming along and appeared to be fine, then the system froze
completely and forced me to power-cycle to get it to come back to life.
On doing so, booting into the current 3.10 (3.10.0-1.8) kernel for
Saucy, there was no nvidia driver, and an error in the xorg logs sayin
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xf86-input-wacom (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net
Not seeing anything obvious from the logs, first things first lets try a
newer fglrx driver in case its a reoccurance of
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1105171
I pushed saucy's fglrx with lts-quantal|lts-raring support to this ppa
https://launchpad.net/~sarvatt/+ar
** Package changed: linux (Ubuntu) => fglrx-installer-experimental-12
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-experimental-12 in Ubuntu.
https://bugs.launchpad.net/bugs/1190883
Title:
Black screen after resume
You have been subscribed to a public bug:
CID: 201206-11418 Dell Inspiron N5425 (12.04.2 Precise - 3.5.0-32)
This system could be suspended successfully, but the screen is totally black
after resume from suspend.
The externel output (HDMI) works fine, just no internal display.
This system needs
*** This bug is a duplicate of bug 1195965 ***
https://bugs.launchpad.net/bugs/1195965
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1195965, so it is being marked as such. Please look
I think the "xdiagnose" icon is useless for the end user, since its
usage appears to be very uncommon. Nearly any bug in X appears to be
capable of being reported successfully without using this tool.
On the other hand, I have the same behaviour here as Anatoly under
Ubuntu 13.04: xdiagnose only r
*** This bug is a duplicate of bug 1033533 ***
https://bugs.launchpad.net/bugs/1033533
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1033533, so is being marked as such.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fglrx-installer (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
Between about 90 and 95% of the time after I login the screen corrupts
and the system freezes. It freezes so much that I can't even Alt-F1 to
get to a terminal session, control-all-backspace to reset X or even SSH
in from another machine. All I can do is switch if off and on
Does not work on my installation of Ubuntu 13.04.
Does the file /usr/share/applications/xdiagnose.desktop correspond to the dash
entry for xdiagnose? If so, then xdiagnose is launched via [pkexec xdiagnose]
command which does not work with dash for me:
* When I launch xdiagnose using dash icon not
That package was slightly older than one patch I had in mind. I can be
optimistic!
Do the errors continue to take the same form?
--
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/
akukuq's comment works on sony vaio v410 ubuntu 12.04,
which was simply "dconf write
/org/gnome/settings-daemon/peripherals/touchpad/touchpad-enabled true"
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launc
Not working on my raring box. And even if it runs, I still feel that it
is useless to end users.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/1183771
Title:
xdiagnose's shortcut launched
This bug seems to have been fixed. When I run xdiagnose from the dash, I
get an authentication dialog asking for my password. I enter it, and
xdiagnose is run.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.laun
Frustrated with this, I switched to the proprietary drivers, but then I still
had the same problems.
Day later, I get garbled output even at the BIOS post screen before the drivers
are loaded.
So it is my graphics card that has died (Gainward brand FYI).
So I guess just my hardware, not the dri
I started to use this Laptop on Lucid (11.10) therefore filed the bug
against Lucid kernel. As this was an issue in every kernel from update
to update (11.10 -> 12.04 -> 12.10 -> 13.04), the issue is now also in
13.04 and also still mainline [1]
[1] https://bugzilla.kernel.org/show_bug.cgi?id=8740
I wonder if the issue is the lock screen triggering constant damage
then...
--
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/1194004
Title:
[regression] Compiz wakes up 200Hz w
Sounds like a Won't Fix, or Opinion then. Which is troublesome for
Compiz.
--
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/1194004
Title:
[regression] Compiz wakes up 200Hz wh
That has never been policy.
** 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/1194004
Title:
[reg
sorry for choosing the Package "xf86-video-omap", that was an incorrect
handling of the bug submitting form.
** Package changed: xf86-video-omap (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-video-omap in Ubuntu.
https:
Public bug reported:
choosing a kernel 3.9. when booting -> resolution of monitor is o.k. xrandr -q
gives correct values.
when choosing a 3.10 kernel, the monitor resolution is too less.
and: xrandr -q does not show the possible monitor resolution, but gives an
error message showing problems wi
35 matches
Mail list logo
