I switched back to Windows because it got worse. The touchpad didn't
work for hours, reboot didn't help. This means I can't provide more
information if needed.
The Sony Vaio VGN-CS31S is not usable with Linux for someone with few know-how
like me.
This is very sad. My PC runs with (X)ubuntu for 7
(In reply to Comment #59)
Hi Christopher,
I don't have access to this computer for 2 more weeks.
I will perform the testing you want me to do when I get back.
Regards,
fpgahardwareengineer
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserv
Public bug reported:
I have two identical spec NP900X4C laptops. On one I installed 12.10,
on the other 12.04.
On 12.10 the touchpad works fine, including right-click.
On 12.04 the touchpad works fine, EXCEPT for right-click. The standard
settings options do not correct this problem.
I tried
Still persists on 12.04
--
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/702090
Title:
i965gm GPU lockup if vesafb is left loaded (EIR: 0x0010 PGTBL_ER:
0x0100) - *E
** Also affects: xserver-xorg-driver-ati
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/994203
Title:
Xorg freeze with Nouveau
I've been having similar experiences on 64 bit systems, both with an ATI
RADEON 4650 in my Desktop, and Intel HD (on chip i5 3210m) graphics. As
it affects Noveau, NVidia, ATI and Intel, it really does not seem to be
related to graphics drivers.
I suspect this is a much more frequent problem than
** Attachment added: "crash-kern.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/994203/+attachment/3470341/+files/crash-kern.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubu
NB: Ubuntu 12.10 Desktop, intel HD graphics, i5 3210m HP pavilion
laptop. Dual booting with Windows (on a separate partition)
** Attachment added: "crash-xorg.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/994203/+attachment/3470343/+files/crash-xorg.log
** Sum
** Attachment added: "crash-syslog.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/994203/+attachment/3470342/+files/crash-syslog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in
*** This bug is a duplicate of bug 1015297 ***
https://bugs.launchpad.net/bugs/1015297
** This bug has been marked a duplicate of bug 1015297
Screen partially darkened after suspend and resume in Xubuntu
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Also affects: xserver-xorg-video-intel via
https://bugs.freedesktop.org/show_bug.cgi?id=56042
Importance: Unknown
Status: Unknown
--
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.lau
*** This bug is a duplicate of bug 1015297 ***
https://bugs.launchpad.net/bugs/1015297
Can you check bug #1015297 and see if that describes your issue? This
might be a duplicate...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xor
Very strange bug. I don't get this at all using Unity and it's always
bright on that DM. I followed Martins instructions and was unable to
reproduce the effect in XFCE 4.10. However when I let the computer go
idle by itself and allowed the xfce4-power-manager turn the screen off I
noticed slight
** Attachment added: "pm-suspend.log"
https://bugs.launchpad.net/xfce4-power-manager/+bug/1015297/+attachment/3470451/+files/pm-suspend.log
--
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/
Same problem here with Quantal and a NVIDIA card.
I kludged around it by building an equivs package for opencl-icd.
This is the second issue I have had with OpenCL on NVIDIA cards. I even
provided a patch for my last issue yet nothing happened. You people
really need to get someone to test this s
This looks suspiciously similar to bug 1039341(which is marked fix
released - but because the reporter couldn't reproduce) .
Melchiaros: Can you reproduce this every time ? How is the monitor
connected - VGA?DVI?HDMI?
--
You received this bug notification because you are a member of Ubuntu-X,
*** This bug is a duplicate of bug 1070150 ***
https://bugs.launchpad.net/bugs/1070150
** This bug has been marked a duplicate of bug 1070150
Intermittent low graphics mode with Intel HD graphics
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscrib
I found a fix for the 'failed to get size of gamma for output default'
which was causing the problems keeping the higher resolutions from being
used.
In using xrandr according to the https://wiki.ubuntu.com/X/Config/Resolution
guide to add higher resolutions and xrandr returns the gamma error, I
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
Hi Adrien,
This can be rather difficult to find the cause of; I've seen it once on one
of my machine, and it turned out to be an application I was using that was
doing a lot to the X server for no good reason. (It was animating a little
icon but was trying to be too clever).
Run top and wa
Running a suspend with pm_trace set, I get:
aer :00:03.0:pcie02: hash matches
I don't know what magic might be needed here, though. As I said before - it
worked a few days ago under Lucid.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Update: Booting with noapic seems to work!
As before, it worked under Lucid, without the noapic flag, so it's still
a bug IMO.
--
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/109
Best guess:
Booting with 'noapic', I see the "irq 5: nobody cared" message on
resume, along with 1 IRQ5 counts in /proc/interrupts (the devices
claiming that IRQ are quiescent).
Without 'noapic' that must be triggering something else to go haywire,
perhaps the AER logic (though that is all MS
23 matches
Mail list logo
