Verified with 3.5.0-36 and 3.10-saucy kernel.
None of them could get it work.
** Tags added: blocks-hwcert
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel-lts-quantal in Ubuntu.
https://bugs.launchpad.net/bugs/1197608
Information from Ara,
there is a possibility that the HDMI output of this system is directly wired to
the nVidia video card,
consequently,no HDMI output with Intel UMA
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
For 201201-10339 that I mentioned in #3, there is a possibility that the
HDMI output of this system is directly wired to the nVidia video card,
consequently,no HDMI output with Intel UMA
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** No longer affects: oem-priority
--
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/1114872
Title:
[hsw backport] kernel oops, Xorg freeze
To manage notifications about this
** Changed in: xserver-xorg-video-intel-lts-quantal (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-lts-quantal in Ubuntu.
https://bugs.launchpad.net/bugs/1197608
Title:
I may be having this same problem but currently unsure as it seems to be
tied to Skype use for me, although this might just be a coincidence - my
computer is rarely heavily loaded. It was the fact that the other
terminals still work that's made me this this is the same issue that I'm
having.
*
Public bug reported:
NVIDIA GTX645 should already been supported by current NVIDIA drivers,
we need to verify the supported ones and add the PCI ID to them.
** Affects: nvidia-graphics-drivers-304 (Ubuntu)
Importance: Medium
Assignee: Gavin Guo (mimi0213kimo)
Status: New
**
** Changed in: oem-priority/precise
Status: New = Invalid
** No longer affects: oem-priority/precise
--
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/1114872
Title:
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
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.
Not so bad, just less than ideal. Though since that hw doesn't support
runtime suspend, there isn't anything that can be done. It is certainly
not the cause of the spontaneous slowdown. (At least that what's I
think, a mere driver author!)
--
You received this bug notification because you are a
Noticed it was Fix Released for Raring, but problem appears to remain,
attached is screen shot showing corrupt image on right, and photo
showing different type of corruption that fixes itself if you take a
screen shot, below is my version information (13.04 64-bit after apt-get
Workaround that I put in for raring was presumed to be sufficient. Since
then we have identified and fixed the root cause, but that fix has yet
to even land in saucy.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
Hi All,
This bug has just started to affect me i have some details that might
help diagnose this though i am surprised that a bug like this has been
open since 2006?
Right my hardware spec has been the same for some time and i never
received this bug. I have recently due to motherboard
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
Public bug reported:
The system become unresponsive. Mouse freeze; num lock responded after 10-15
seconds...
I had to reboot: Alt+Sysrq+B
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-core 2:1.14.1-0ubuntu0.8
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Uname:
Public bug reported:
Today's saucy update with reboot and X crashes when trying to display
the greeter. I see continual flashes from purple screen to black
console.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu5
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Public bug reported:
Hello all,
What I expected to happen:
I expected a normal picture on all of my monitors.
What happened instead:
I have a problem with xrandr, or at least with my video cards, now I'm using
the ubuntu 13.04 live DVD, but if I use an up-to-date ubuntu server 13.10
Public bug reported:
this is the /var/log/installer/dm with the traceback:
X.Org X Server 1.14.1
Release Date: 2013-04-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-37-generic i686 Ubuntu
Current Operating System: Linux ubuntu 3.10.0-2-generic #10-Ubuntu SMP Fri Jul
5
I have the same problem with ubuntu-studio 13.04. System just randomly
logs out, most common when starting up/shutting down a program.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
Public bug reported:
After login Unity does not start (for all users: first user, an
additional user, guest session). Right-click menu of desktop background
works. Log out only by stopping and restarting lightdm, after another
login this crash report, still on a Unity-less desktop.
ProblemType:
Public bug reported:
Vanilla Lubuntu 13.04. Steps to reproduce:
1) open LXTerminal
2) in the opened terminal run sudo xterm, enter password
3) in the opened xterm run xterm -e su nobody
4) try to close the new opened xterm with the X button in the window title
Result: this xterm won't close. To
The missing Unity was caused by an update which uninstalled Unity. After
installing Unity again I have a correct desktop again. I do not know
whether the crash was caused by missing Unity (but then X should error
and not crash).
--
You received this bug notification because you are a member of
Public bug reported:
Vanilla Lubuntu 13.04. Steps to reproduce:
1) run LXTerminal
2) in the opened terminal run xterm -e su nobody -c su -, enter password
Result: in the opened xterm you will see Job control is off. It is
possible to terminate this buggy xterm with just Ctrl+C.
This worked
Hi Jens
That sounds very strange. Could you please try the modesetting driver instead
of vesa or fbdev. It has hardware cursor support (the others don't). Also make
sure you're using the gma500_gfx kernel module.
-Patrik
--
You received this bug notification because you are a member of
I have the same problem with a Logitech Performance MX mouse.
I am on Ubuntu 13.04 (uprgade from 12.10).
The mouse used to work on 12.10 and also worked on 13.04, then after a couple
of upgrades this behavior appeared.
I also connected a Logitec Anywhere MX, and this does not seem to have the
Patrick,
your are right, it is very strange. I updated my system to saucy but the
problem remains.
I tried as suggested by you the modesetting driver without success.
First I had to remove psb_gfx and gma500_gfx from
/etc/modprobe.d/blacklist.conf where I added it at 12.04 times to avoid
the
On Tue, Jul 09, 2013 at 05:29:52PM -, DmitryKX wrote:
Public bug reported:
Vanilla Lubuntu 13.04. Steps to reproduce:
1) open LXTerminal
2) in the opened terminal run sudo xterm, enter password
3) in the opened xterm run xterm -e su nobody
4) try to close the new opened xterm with
On Tue, Jul 09, 2013 at 05:35:59PM -, DmitryKX wrote:
Public bug reported:
Vanilla Lubuntu 13.04. Steps to reproduce:
1) run LXTerminal
2) in the opened terminal run xterm -e su nobody -c su -, enter password
Result: in the opened xterm you will see Job control is off. It is
I've given up and switched away. There's been no response from anyone
about anything related to this bug in months and it's far too painful
for me to deal with any longer. If/when someone posts a fix or
workaround or something, I'll try it.
--
You received this bug notification because you
** Changed in: xorg (Ubuntu)
Importance: Undecided = Low
--
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/1199129
Title:
Closing my laptop lid will also close up my additional display
To
This affects me to. I'm running a new install of 12.04 with gnome-
session-fallback on an AMD computer with a nvidia GT240 graphics card.
I have not yet established if specific applications are causing this
bug.
Syslog output from the point of the crash untill power off:
Jul 10 05:57:17
31 matches
Mail list logo
