I don't think it's a problem with compiz nor nvidia-comon.
The same happened to me this morning with upgrade.
In the morning I was still on 10.10.
from apt/history.log (I removed some packages like thunderbird from the list) :
Upgrade:
linux-image-2.6.35-30-generic:amd64 (2.6.35-30.60,
Public bug reported:
Binary package hint: xorg
https://bugs.launchpad.net/ubuntu/+bug/516827
https://bugs.launchpad.net/ubuntu/+bug/516827/comments/8
If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/48447454/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/48447455/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/48447456/Dependencies.txt
**
T4210 Fujitsu Siemens
Same problem on full upgraded Lucid 10 minutes ago.
--
Fujitsu T4310: screen rotation doesn't rotate wacom pen/mouse axes
https://bugs.launchpad.net/bugs/516827
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
@Jakob:
yes,
the limit is 2048x2048
But 2048 is the maximum size of a texture. that means that texture CAN BE 2048.
2049 is 1px over the maximum.
Anyone with 945 can test it with intrepid live CD. Compiz WILL WORK on
2048x786 dual screen.
This bug is not about disabling compiz at 2048,
but about
oh no no no no no
this is wrong
The texture size is not exceeded.
for 1half years i was daily working on 2048 with compiz.
:'(
--
[i945gm] dual screen not working with virtual resolution enabled: just a blank
screen with a mouse pointer
https://bugs.launchpad.net/bugs/383345
You received this
yes
still here :)
up-to-date lucid
(upgrade from karmic)
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Tags added: apport-collected
** Description changed:
Jul 10 10:33:55 jxt4210i2 kernel: [ 8136.876360] input input18: event field
not found
Jul 10 10:33:55 jxt4210i2 kernel: [ 8136.876367] input input18: event field
not found
This message is flooding my kern.log,
apport information
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/43157331/ArecordDevices.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/43157333/BootDmesg.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/43157339/Card0.Amixer.values.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Card0.Codecs.codec.0.txt
http://launchpadlibrarian.net/43157340/Card0.Codecs.codec.0.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: Card0.Codecs.codec.1.txt
http://launchpadlibrarian.net/43157343/Card0.Codecs.codec.1.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/43157396/CurrentDmesg.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: IwConfig.txt
http://launchpadlibrarian.net/43157397/IwConfig.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/43157398/Lspci.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
apport information
** Attachment added: Lsusb.txt
http://launchpadlibrarian.net/43157400/Lsusb.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/43157403/ProcCpuinfo.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/43157404/ProcInterrupts.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/43157405/ProcModules.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: RfKill.txt
http://launchpadlibrarian.net/43157407/RfKill.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/43157429/UdevDb.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
apport information
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/43157401/PciMultimedia.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/43157434/UdevLog.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: WifiSyslog.txt
http://launchpadlibrarian.net/43157437/WifiSyslog.txt
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Laurens
my comments 42-43
compiz works even on that 1px.
In jaunty I was on my daily work on 1024+1024 with compiz.
Since Karmic I use 1024+1280 without compiz.
The switch from compiz to metacity on changed resolution is without
problems (gnome always starts with black screen 2048, I have
confirming on lucid
Fujitsu siemens T4210
On karmic worked without problems.
On lucid stylus/eraser don't rotate with screen.
as workaround:
$ ls /usr/local/bin/wacom*
/usr/local/bin/wacom-ccw.sh /usr/local/bin/wacom-cw.sh
/usr/local/bin/wacom-half.sh /usr/local/bin/wacom-none.sh
$ cat
last night upgrade 9.10 to 10.04:
Confirming Bug in 10.04.
No change.
--
[i945gm] dual screen not working with virtual resolution enabled: just a blank
screen with a mouse pointer
https://bugs.launchpad.net/bugs/383345
You received this bug notification because you are a member of Ubuntu
Bugs,
@Laurens
on the left side,
you have 1px visible or more?
(that white left border)
I had always 1px.
But on your screens it looks like more. (But probably just an illusion after
img resize)
--
[i945gm] dual screen not working with virtual resolution enabled: just a blank
screen with a mouse
@milos
your problem is unrelated.
i8xx HW cannot display framebuffer larger then 2048x2048.
It's a hardware limitation, not a system BUG.
@Radomirs
Please, at which combined resolution you get the black screen?
@Andcor
Please, what is your hardware?
Ubuntu does not automatically change
@Radomirs:
Please, before setting dual screen, disable desktop effects (compiz).
Compiz cannot work at resolution higher that 2048x2048 (yet) on i915/945
hardware, limitation of HW 2048x2048 max texture size.
Without Desktop effects your dual screen configuration should work. (it is then
limited
sorry, there was a typo. Correct is 2048.
And it is NOT a BUG.
It is Hardware limitation of i915/i945 graphics cards.
i965 works with compiz (desktop effects) until 4096x4096
--
[i945GM] dual screen not working with virtual resolution enabled: just a blank
screen with a mouse pointer
@ vincenzo
Interesting comment of yours.
Attached VGA cable is regretfully not a solution, I nearly always start
system with attached VGA cable.
And could you please provide lspci -vvn
and information if you are realy running on full karmic system and/or
xorg-edgers repository?
--
[i945GM]
A college just updated to karmic.
he has i965GM
Compiz working perfectly on 2048x768 and 2304x1024
So this is only i915/i945 chipset problem.
@Viktor
If I'm not mistaken, Virtual line is in KMS mode (default in karmic)
irrelevant.
Kernel is now managing resolutions, not xserver, and according
sorry for spam, but that was a terrible misspell :)
A colleague just updated to karmic. is correct :)
--
[i945GM] dual screen not working with virtual resolution enabled: just a blank
screen with a mouse pointer
https://bugs.launchpad.net/bugs/383345
You received this bug notification because
As the release of Karmic nears, this bug gets spookier :) (imagine the
number of forum questions :) )
So I prepared for you 2 videos:
http://launchpad.jay.cz/intel-compiz-pixel3.avi
http://launchpad.jay.cz/intel-compiz-pixel4-zoom.avi
(1280x720, xvid, 60MB and 40MB)
(because of the size, I left
I had an idea :)
Do desktop effects work in that garbaged state?
Yes they work.
In that one pixel I could see, changes of opacity, wobbly windows ...
That means that bug is somewhere, in manipulation with 3D texture and sending
it to display.
And if I take into consideration, that even older
Shortcuts I use for easier testing:
$ cat /usr/local/bin/compiz-start.sh
#!/bin/bash
compiz --replace
$ cat /usr/local/bin/compiz-kill.sh
#!/bin/bash
killall compiz.real
metacity --replace
Menu - preferences - Keyboard shortcuts
compiz-start.sh - Ctrl+Alt+1
compiz-kill.sh - Ctrl+Alt+5
:)
I'm unable to reproduce this bug anymore.
running up-to-date xorg-edgers
https://launchpad.net/~xorg-edgers/+archive/ppa
mesa 7.6
xserver 1.6.2
xserver-xorg-video-intel 2.8.0
kernel 2.6.30-10 - KMS
performance on i945 is poor ( ~ -40% than I remember on XAA - now around 20fps)
But no crashes or
Today I found a very interesting situation.
To describe it I attach fotos.
This one is :
xrandr --output LVDS --mode 1024x768 --primary --output VGA --mode 1024x768
--right-of LVDS
** Attachment added: dual_screen_compiz.jpg
http://launchpadlibrarian.net/29324361/dual_screen_compiz.jpg
--
dual_screen_compiz_virtualbox.jpg
is the same configuration
But before activating compiz, i had full-screen virtualbox on right display.
As you can see it's unharmed. I'm able to normally work in it.
As I pressed ctrl+f, to leave full-screen, virtualbox disappeared behind the
wall :) .
I hope
I'm unable to find any working configuration.
I tryed lots of combinations of driver, xserver, kernel, mesa7.6 and mesa7.5.
Either black screen or white screen (frustrating).
even thou I reported a month ago that xserver-xorg-video-intel -
2:2.7.1-0ubuntu1~xup~1 works...
It doesn't any more ...
all tests with all other packages up-to-date to from xorg-edgers.
xserver-common_1.6.1.901+git20090523+server-1.6-branch.5cd5a012-0ubuntu0sarvatt5_all
xserver-xfbdev_1.6.1.901+git20090523+server-1.6-branch.5cd5a012-0ubuntu0sarvatt5_i386
Most probably NOT a bug in intel drivers!
I found old .dsc files on xorg-edgers. And compiled many of them.
Right now I'm running on
xserver-xorg-video-intel_2.6.99.1+git20090416.b9716b83-0ubuntu0tormod_i386
and kernel 2.6.30-8
And I can reproduce this bug.
In the evening I'll try to go further
I forgot to mention a very important thing.
When there is a black screen with mouse on resolution 2048x768 (on compiz)
there is a *first pixel coulumn* which is the real living first pixel.
I do see moving of windows in that first pixel.
For me it looks like a typo in texture transformation (or
that fix works in kernel works.
right now I running on sarvatts kernel
linux-source-2.6.31-rc3-sarvatt_20090715, which he kindly gave me for testing,
until xorg-edgers have a kernel update
--
[i945GM] dual screen not working with virtual resolution enabled: just a blank
screen with a mouse
@Lucian
... or do you have autologin enabled?
--
[i945GM] dual screen not working with virtual resolution enabled: just a blank
screen with a mouse pointer
https://bugs.launchpad.net/bugs/383345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Lucian
Please for clarification.
You have destroyed screen before login on login screen, or after login in
gnome.
It never happened to me before login. On login screen I have Always cloned
outputs.
After Login, only with compiz enabled, I have the bug you described.
--
[i945GM] dual screen
@Lucian
Try also to disable Desktop Effects (compiz).
You can find the setting on tle last tab of Appearance setings.
Without Desktop effects 2048x1065 should work.
--
[i945GM] dual screen not working with virtual resolution enabled: just a blank
screen with a mouse pointer
https://bugs.freedesktop.org/show_bug.cgi?id=21190#c7
--- Comment #7 From Keith Packard 2009-07-11 09:33:45 PST ---
I've pushed driver fixes for this to master in patch:
d655a3ff423e69c19a5dc07140cbf3caaa32cb86 Remove NoAccel support.
There's an associated fix necessary in the
@Lucian
Please write if it's fixed for you.
It's not fixed for me, and even it's worse (xorg doesn't start with
virtual in xorg.conf).
So It's possible I have different bug.
--
[i945GM] dual screen not working with virtual resolution enabled: just a blank
screen with a mouse pointer
Confirming repaired.
xorg-edgers on jaunty
Thank you.
--
xrandr: Configure crtc 0 invalid time
https://bugs.launchpad.net/bugs/394490
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
@Tomrod Volden
With the link you provided I activated KMS on 2.6.30-10 (xorg-edgers on jaunty).
With full update from xorg-edgers ... the performance is ... breath-taking
wow.. (with compiz)
(2.6.30-10 doesn't like virtual size setting in xorg.conf, Xserver crashes on
startup.)
About this
Activated KMS on 2.6.30-10
still the same.
With the new kernel, Virtual setting in xorg.conf crashes xserver on startup.
$ xrandr
Screen 0: minimum 320 x 200, current 1360 x 1536, maximum 2048 x 2048
Unable to set resolutions beyond 2048.
With compiz on 2048x768, black/white/or garbage screen
you are incredible :)
reverted to xserver-xorg-video-intel_2%3a2.7.99.901+git20090611
.6d062e9e-0ubuntu0sarvatt~jaunty_i386.deb
$ xrandr --verbose --output LVDS1 --auto
crtc 1: 1024x768 60.0 +0+768 LVDS1
xrandr: Configure crtc 1 invalid time
crtc 0: disable
crtc 1: disable
screen 0: revert
test of xserver-xrg-core:
intel driver back to 20090709
xserver-xorg-core reverted to:
xserver-xorg-core_2%3a1.6.1.902~git20090629+server-1.6-branch.5b49aff4-0ubuntu0sarvatt~jaunty_i386.deb
bug still present
xserver-xorg-core reverted to:
xserver-xorg-core (2:1.6.1.901-2ubuntu2)
http://packages.ubuntu.com/en/karmic/xserver-xorg-core
works
(tested on jaunty)
--
xrandr: Configure crtc 0 invalid time
https://bugs.launchpad.net/bugs/394490
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Jul 10 10:33:55 jxt4210i2 kernel: [ 8136.876360] input input18: event field not
found
Jul 10 10:33:55 jxt4210i2 kernel: [ 8136.876367] input input18: event field not
found
This message is flooding my kern.log, messages and syslog
Reason for this message is USB mouse
** Attachment added: lspci-vnvn.log
http://launchpadlibrarian.net/28871100/lspci-vnvn.log
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: version.log
http://launchpadlibrarian.net/28871110/version.log
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: dmesg.log
http://launchpadlibrarian.net/28871105/dmesg.log
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: uname-a.log
http://launchpadlibrarian.net/28871138/uname-a.log
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: kern.log
http://launchpadlibrarian.net/28871144/kern.log
--
mouse : input : event field not found
https://bugs.launchpad.net/bugs/397750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
A plead to package maintainer:
Please confirm what is the root of the problem.
intel drivers? -then why does ubuntu display settings work.
xrandr code?
For it looks like, the developers made some big change in driver, and xrandr
didn't count with that.
Also I believe that grandr and ubuntu
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/28875869/Xorg.0.log
--
xrandr: Configure crtc 0 invalid time
https://bugs.launchpad.net/bugs/394490
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I really cannot tell definitely if I'm using KMS :)
https://launchpad.net/~xorg-edgers
kernel 2.6.30-9 (when I reboot it wil be 2.6.30-10)
xorg-server - 2:1.6.2~git20090708
xserver-xorg-video-intel - 2:2.7.99.901+git20090708 (after reboot 20090709)
(can not reboot now, I'm in work :) )
Default
2.6.30-10
X didnt start, so back on 2.6.30-9 .
With new 20090709 intel driver
xrandr is the same.
--
xrandr: Configure crtc 0 invalid time
https://bugs.launchpad.net/bugs/394490
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
todays update :
xorg-server -
2:1.6.2~git20090708+server-1.6-branch.6f1aff5a-0ubuntu0sarvatt~jaunty
xserver-xorg-video-intel -
2:2.7.99.901+git20090708.r1.40e7c950-0ubuntu0sarvatt~jaunty
xrandr --output LVDS --mode 1024x768 --primary --output VGA --mode 1360x768
--above LVDS
works with or
Please, is here anyone able and willing to create .deb for us mortals :)
I'd like to check the fix reported:
https://bugs.freedesktop.org/show_bug.cgi?id=22328
(acording to : Comment #10 From Keith Packard 2009-07-07 15:25:53 PST
https://bugs.freedesktop.org/show_bug.cgi?id=22076#c10 )
** Bug
Fabio:
I tryed your suggestion
xrandr --verbose --output LVDS --off
xrandr --verbose --output VGA --off
(before the line to change resolution.)
but I cannot confirm it to work.
Disabled my displays and because setting resolutioon after disabling displays
wasnt accepted. So configuration
Fabio:
heh, I didn't understand you post like that :)
updated xserver-xorg-video-intel to version
2:2.7.99.901+git20090702.74227141-0ubuntu0sarvatt~jaunty
no change
--
xrandr: Configure crtc 0 invalid time
https://bugs.launchpad.net/bugs/394490
You received this bug notification because you are
Public bug reported:
Binary package hint: xrandr
$ xrandr --verbose --output LVDS --mode 1024x768 --primary --output VGA
--mode 1024x768 --same-as LVDS
crtc 0: 1024x768 60.0 +0+0 VGA
xrandr: Configure crtc 0 invalid time
crtc 0: disable
crtc 1: disable
screen 0: revert
crtc 0: revert
** Attachment added: lspci-vvnn
http://launchpadlibrarian.net/28608268/lspci-vvnn
--
xrandr: Configure crtc 0 invalid time
https://bugs.launchpad.net/bugs/394490
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Hi,
Confirming this bug.
Running on
https://launchpad.net/~xorg-edgers/+archive/ppa
(newest xorg, intel driver and kernel)
(so only UXA and DRI2)
I have some xrandr configurations bind to keyboard shortcuts, so it's
easy for me to test without restarts.
Without compiz, everything works
xserver-xorg-video-intel - 2:2.7.1-0ubuntu1~xup~1
from
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates
xrandr --output LVDS --mode 1024x768 --primary --output VGA --mode 1024x768
--right-of LVDS
WORKS with compiz enabled
with loose bindings, problem with window textures not updating
I'm sorry it took so long, lets explain.
After jaunty upgrade NonSteam CS dropped to 4 FPS and Steam CS didn't
even care to start. (with EXA. XAA didn't start X, and UXA was crashing
few minutes after desktop start)
Today I found xorg-edgers https://launchpad.net/~xorg-edgers/+archive/ppa
I was able to ssh and kill wine.
System returned to normal.
So it is the same bug as the wine one from pauli.
But, exactly the same freeze happens on all graphic cards (intel, ati,
nvidia), so it must by kernel/mesa based bug.
I'm availiable for testing.
Just write what to do, and I'll freeze
** Attachment added: xorg.conf
http://launchpadlibrarian.net/19568091/xorg.conf
--
xserver lockup, mouse movable, sound in loop, SysRq unusable
https://bugs.launchpad.net/bugs/296825
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Proppably usefull information:
crash is independend of wine graphic settings vertex shader and pixel
shader. Still freezes.
Game did not crash in map without wall textures. There were just single
color walls. After switching to a map with full textures. Lockup was
inevitable.
So bug is possibly
** Description changed:
Short description:
xserver freeze. Total. Mouse is movable, but anything with keyboard (change
to VT1, Ctrl-Alt-Backspace, Ctrl-Alt-Del, Alt-SysRq-B, or anything) is dead.
Sound is in a short (0.5-1 sec) loop. CPU is on max (I hear the fan on max).
Absolutely sure
** Attachment added: lspci-vvnn
http://launchpadlibrarian.net/19568068/lspci-vvnn.txt
--
xserver lockup, mouse movable, sound in loop, SysRq unusable
https://bugs.launchpad.net/bugs/296825
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: var log dir after crash
http://launchpadlibrarian.net/19568047/log_08_crash.tar.gz
--
xserver lockup, mouse movable, sound in loop, SysRq unusable
https://bugs.launchpad.net/bugs/296825
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Short description:
xserver freeze. Total. Mouse is movable, but anything with keyboard (change to
VT1, Ctrl-Alt-Backspace, Ctrl-Alt-Del, Alt-SysRq-B, or anything) is dead. Sound
is in a short (0.5-1 sec) loop. CPU is on max (I hear the fan on max).
Absolutely sure way to
Public bug reported:
Binary package hint: xrandr
I have installed xrandr 1.2 but
$ xrandr -v
Server reports RandR version 1.1
/var/log/Xorg.0.log
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(--) RandR disabled
(II) Initializing built-in extension MIT-SHM
(II)
84 matches
Mail list logo
