A victim of some other fix. This regression can be prevented by adding
amdgpu.dc=0 to the kernel command line.
--
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/1762818
Title:
Regression: Upgradin
** Attachment added: "Xorg log when booting with 18.04 kernel"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762818/+attachment/5109717/+files/newkernel.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.l
Public bug reported:
Symptom: booting 18.04 kernel reduces resolution available while 17.10
kernel (on 18.04) does not
I have a 3 identical monitor setup - all at 2560x1600 native resolution.
If I boot the current 18.04 kernel 4.15.0-13-generic then the third
monitor does not have the native reso
All I know is that whatever the cause was, it was fixed in 3.12 even in
the rcs. I have no idea what the actual fix was.
Kernel 3.11 end of lifed November last year. I also use btrfs for which
there have been maintenance patches in 3.12.
I followed the "Kernel Build and Installation" section at
You do know that no one knows what the fix is, only that it is in 3.12?
You can see that Timo gave up trying to find it in mid-November. If
Ubuntu is actually going to figure out the fix and backport it, then go
for it. However I am extremely sceptical and had to devise my own
workaround.
--
Yo
If Ubuntu would actually backport the 3.12 kernel to Saucy then go for
it. The kernel team PPA does not do 3.12 for saucy. At a minimum
3.12.6 is needed due to lots of btrfs fixes.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-vi
It isn't invalid. This is a very real issue affecting the existing
Ubuntu release.
I have been personally compiling 3.12 kernels from kernel.org as a
workaround that works for me, so I don't need anything.
I'd suggest closing as Won't Fix since Ubuntu won't provide a fix.
--
You received this
Kernel 3.12 even in the prereleases fixed this.
--
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/1242180
Title:
saucy regression - three monitors no longer work
To manage noti
Can you point me to other builds you want me to try, ideally as ppa
links like the above?
--
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/1242180
Title:
saucy regression - thr
This didn't work:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.7-saucy/
This did:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/
It would be ideal if you gave me a list of urls like above in preferred
testing order
--
You received this bug notification because you are a
I'm confused as to what the goal is. The drm-intel-nightly works.
--
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/1242180
Title:
saucy regression - three monitors no longer w
The drm-nightly from previous comment works
--
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/1242180
Title:
saucy regression - three monitors no longer work
To manage notifica
I installed 3.12 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.12-saucy/
It failed to boot. With normal boot there was no further progress after
ramdisk loading. In recovery mode the kernel said it failed to execute
/init but gave no further details.
I am now trying http://kernel.ubunt
Booting the raring kernel (3.8.0-33) under saucy results in all 3
monitors working correctly.
--
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/1242180
Title:
saucy regression -
@RichardNeill - already did all that as mentioned in comment 4 which
also has the advantage of working on the livecd.
--
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/1242180
Ti
xrandr output running command line from comment 2. Raring:
crtc 0:1920x1200 60.0 +1920+0 "DP2"
crtc 1:1920x1080 60.0 +3840+0 "HDMI1"
crtc 2:1920x1080 60.0 +0+0 "HDMI3"
Saucy livecd:
xrandr: Configure crtc 2 failed
crtc 0:1920x1080 60.0 +3840+0 "HDMI1"
crtc 1:1920x108
Which driver did you get working in the end? My experience was having 3
monitors work fine in raring 13.04, until the driver that is in Saucy
13.10 at which point it started pulling the "only two monitors at a
time" stunt. Bug 1242180
--
You received this bug notification because you are a memb
I also ran xorg-edgers-live-test as described in
https://wiki.ubuntu.com/XorgOnTheEdge and that didn't help. Restored
from my backup and everything works fine.
(xorg-edgers-live-test also needs updating - it tries to restart gdm
when it should be restarting lightdm)
** Attachment added: "xrandr
** Attachment added: "xorg log from raring where everything works fine"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+attachment/3884309/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xser
** Attachment added: "xorg log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+attachment/3884152/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://
Public bug reported:
I've just upgraded from raring. There I had 3 monitors attached to my
Intel HD Graphics 4000 (i7 3770 cpu) where it all works perfectly. (Two
monitors are identical flanking my centre displayport monitor.)
In saucy I can get any two monitors working, and any attempt to get
The failures to set occur using the graphical tool from system settings,
as well as the xrandr command line
xrandr --output DP2 --primary --auto --output HDMI3 --auto --left-of DP2
--output HDMI1 --auto --right-of DP2
** Attachment added: "xrandr output"
https://bugs.launchpad.net/ubuntu/+sou
I'm another user affected by this with an 8800GT that has been rock
solid stable in prior Ubuntu releases. I'm running the gnome shell
fallback mode. The current, current-updates and x-swat repository
versions all resulted in random crashes back to the login screen.
I've tried using the noveau d
I've just had it happen on a new machine that does not have a SSD. It
is a fast Core i7 with two striped hard disks (Seagate Barracuda XT) and
an Nvidia 450 video card. The gnome-settings-daemon autostart sleep fix
did the trick.
--
You received this bug notification because you are a member of
My machines affected were also i7. For my main machine the OS is on the
SSD while /home is on striped spinning media (similar throughput to SSD,
higher latency).
The sleep from comment #68 fixed it for me too. Looks like some sort of
race condition when loading things.
--
Meerkat (10.10) does
I just did a fresh install and hit this problem. I did the fresh
install due to a new SSD disk and did not experience the problem with my
spinning disks with the prior install. (Yes I also have an Nvidia
card.)
Something similar happened at work where a guy did a fresh install on a
machine and g
@Tim Thomas: Comment #83
The F key stuff you are seeing is normal functionality of the keyboard.
Look for the "F Lock" key above backspace and the light to the rightmost
of Caps/Num lock. When F lock is on (light is on) the functions keys
generate F1 through 12. When the light is off they genera
Just for the record the udev quirks file in comment #24 does not
fix/workaround the problem in any way.
--
Keyboard special keys interfere with mouse
https://bugs.launchpad.net/bugs/636311
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xor
For what it is worth I am yet another person affected. It has even
happened when not pressing the special keyboard keys. From a fresh
graphical boot it is usually under a minute before I get the left button
locked problem.
To fix it I do "modprobe -r usbhid ; modprobe usbhid" from an SSH
connect
29 matches
Mail list logo
