Unfortunately, after a recent restart, the problem has returned, and my
prior trick of changing the Refresh Rate no longer fixes the problem.
--
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/1880347
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchp
Public bug reported:
After an update (kernel?), I have begun to receive the message "Running
in Low Graphics Mode" at boot. I can tell it to use Default setting from
the options it offers, and get by it, after which things look and work
normally until a reboot, which may or may not occur correctly
I can't follow the above instruction, since before that date (6/5/18) I
have turned off all options in X-Diagnose, and the system boots every
time now.
BUT :
1) The boot process is now verbose, despite turning off all options, and I
can't change this back to quiet, which could produce the problem
Today, with Xdiagnose unused, I again had an error message "Running in
Low Graphics Mode", after about a dozen starts with no problem.
I again engaged Xdiagnose, checked the top 3 boxes about functions, and
also engaged "Disable bootloader graphics".
Back to checking results...
--
You received
ent).
If you want to demonstrate what kernel is being using currently type:
uname -a
roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17
12:56:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
roger@roger-desktop:~$
B) Regarding your comment:
>&quo
r
To: rogerdavis
Sent: Sun, Jun 3, 2018 11:50 pm
Subject: [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups
- not all
Roger Davis:
a) You are responding multiple times to the same comment, causing confusion.
Hence, it is best if you looked at the bug report (not email inbo
A) roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17
12:56:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
roger@roger-desktop:~$
B) Will be checking for several days to confirm if I've just been lucky, or ???
- I'll hold off on filin
In response to Christopher M. Penalver
1) same as 3 above
2) roger@roger-desktop:~$ ls -la /var/crash
total 8
drwxrwsrwt 2 root whoopsie 4096 May 29 03:46 .
drwxr-xr-x 15 root root 4096 Dec 17 2016 ..
roger@roger-desktop:~$
3) "To confirm, is there a reason you are using the non-de
1) I cannot tell which update caused this.
2) Not sure how to boot to previous kernels, especially not wanting to
fowl up my settings.
3) roger@roger-desktop:~$ sudo apt-get install --install-recommends
linux-generic-hwe-16.04 xserver-xorg-hwe-16.04
[sudo] password for roger:
Reading package
1) roger@roger-desktop:~$ sudo apt-get install --install-recommends
linux-generic-hwe-16.04 xserver-xorg-hwe-16.04
[sudo] password for roger:
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-generic-hwe-16.04 is already the newest version
1) I cannot tell which update caused this.
2) Not sure how to boot to previous kernels
3) roger@roger-desktop:~$ sudo apt-get install --install-recommends
linux-generic-hwe-16.04 xserver-xorg-hwe-16.04
[sudo] password for roger:
Reading package lists... Done
Building dependency tree
Public bug reported:
Supplement to 1772...@bugs.launchpad.net,
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-43-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubu
. This problem shows up no matter which of the above I'm using, or
Unity.
roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
roger@roger-desktop:~$ free -m
total used free shared buff/cache available
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
I have raised this bug at
https://bugzilla.kernel.org/show_bug.cgi?id=198669
** Bug watch added: Linux Kernel Bug Tracker #198669
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-
The file name above should read radeon_ring.c. I thought you used to be
able to edit comments on here!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1746232
Title:
driver loop
This crash looks very similar to #1301649. However is does not require
the system to go into power save.
The crash is in radeon_ring_backup which is in
linux/drivers/gpu/drm/radeon/radeon_device.c and part of the linux
(kernel) package.
I have added that package to this bug.
--
You received thi
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1746232
Title:
driver looping then crashing
To manag
Public bug reported:
Running driver on Artful with the xwayland compositor. At random times
the GPU stalls with.
Jan 30 11:22:28 dragon kernel: [ 487.046219] radeon :02:00.0: ring 0
stalled for more than 29200msec
Jan 30 11:22:28 dragon kernel: [ 487.046224] radeon :02:00.0: GPU lockup
opher.m.penal...@gmail.com> wrote:
> Roger Merritt:
> >"successfully installed the mainline kernel 4.6-rc6"
>
> Did you test 4.7-rc6, or 4.6-rc6?
>
> >"Apparently the problem is not in the kernel."
>
> The test you did wasn't enough to conclude t
Oh, boy. I did it again. That should have been ...040700*r*c6-generic.
On Thu, Jul 7, 2016 at 6:14 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Roger Merritt:
> >"successfully installed the mainline kernel 4.6-rc6"
>
> D
at 6:15 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Roger Merritt, to further narrow this down, could you please test the
> latest mainline kernel (4.7-rc6) following
> https://wiki.ubuntu.com/Kernel/MainlineBuilds and advise to the results?
>
> --
>
thing
sits quietly. At least with 16.04 there was some visible activity after the
grub menu until it went black. Thanks for the effort, though.
On Mon, Jul 4, 2016 at 10:28 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Roger merritt, to see if this is already resolve
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695186/+files/Lsusb.txt
--
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/1584284
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695185/+files/Lspci.txt
--
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/1584284
Title:
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695194/+files/XorgLog.txt
--
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/1584284
Tit
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695193/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "xserver.outputs.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695198/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695196/+files/Xrandr.txt
--
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/1584284
Title:
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695197/+files/xdpyinfo.txt
--
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/1584284
T
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695195/+files/XorgLogOld.txt
--
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/158428
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695192/+files/UdevDb.txt
--
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/1584284
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695191/+files/ProcModules.txt
--
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/1584
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695190/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695187/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695189/+files/ProcEnviron.txt
--
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/1584
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695188/+files/ProcCpuinfo.txt
--
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/1584
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695184/+files/LightdmLog.txt
--
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/158428
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695180/+files/JournalErrors.txt
--
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/
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695182/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695179/+files/GconfCompiz.txt
--
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/1584
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695181/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "LightdmGreeterLogOld.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695183/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695178/+files/DpkgLog.txt
--
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/1584284
Tit
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1584284/+attachment/4695177/+files/Dependencies.txt
--
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/15
apport information
** Tags added: apport-collected compiz-0.9 ubuntu wily
** Description changed:
- I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD
- A10-5800K AGP, Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no
- graphics card -- the Radeon HD 7660D graphics are d
Public bug reported:
Lenovo 50-70 avec ubuntu 16.04 LTS.
Mon écran externe HP est détecté mais ne reste noir (en veille).
Merci
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
.
This is happening: "... the screen goes blank after the splash screen
(about the time the login screen should come up), report the bug against
xorg."
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xo
*** This bug is a duplicate of bug 1510970 ***
https://bugs.launchpad.net/bugs/1510970
This occurs mainly using libreoffice, but lately also using chrome, I
attach a crash file...
** Attachment added: "_opt_google_chrome_chrome.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+b
usr_lib_chromium-browser_chromium-browser.1000.crash
** Attachment added: "usr_lib_chromium-browser_chromium-browser.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535454/+files/_usr_lib_chromium-browser_chromium-browser.1000.crash
--
You received this b
also other crash-files are to be found:
** Attachment added: "usr_bin_gnome-panel crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535450/+files/_usr_bin_gnome-panel.1000.crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Here is my metacity crush log, i experience this bug since upgrading
from 14.04 to 15.10!
** Attachment added: "metacity crash file"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535449/+files/_usr_bin_metacity.1000.crash
--
You received this bug notification becau
_usr_bin_pidgin.1000.crash
** Attachment added: "_usr_bin_pidgin.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535451/+files/_usr_bin_pidgin.1000.crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xo
_usr_bin_vlc.1000.crash
** Attachment added: "_usr_bin_vlc.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535452/+files/_usr_bin_vlc.1000.crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubu
@Duncan
I don't have odd artifacts; I meant that there is just a desktop
background, no other screen items visible at all. But that is when I try
to use the driver selection utility to revert to the Open Source driver,
not when I'm trying to use the AMD binary driver, which works fine.
I think th
Do you remember to reverse the whole process when going from fglrx ->
open source ?
I can now switch from radeon to fglrx, but then it seems to prevent the
open source radeon driver from loading when I switch back.
See bug 1493888 Post #203 for details.
--
You received this bug notification bec
@Duncan
I think it's still being tested, so its probably only in Wily-proposed
at the moment.
--
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/bugs/1493888
Title:
FGLRX incompatible with gc
@Mathew Hodson.
OK, so when switching from AMD to Open Source drivers in the additional
drivers tab, the fglrx-updates-core and fglrx-updates-dev are left
installed. This means that on reboot, dmesg contains the following
[2.470360] fglrx: module license 'Proprietary. (C) 2002 - ATI Technolog
@Mathew Hodson.
I removed the amdgpu blacklist entry I had manually added and used the
"Additional Drivers" tab of Software and Updates to switch to the Open
Source drivers.
This resulted in a fallback Unity desktop without GPU acceleration (
glxinfo reported gallium using llvmpipe, which is mesa
@Philip Gemmell
Not sure if the open source driver blacklist has made it into the fix
yet - this caused my screen to be blank after updating.
See previous comments #114 #119 and #120.
I didn't need to change nomodeset, but I did need to add "blacklist
amdgpu" to the end of /etc/modprobe.d/blackl
>>On 27-10-15 17:47:55, Roger Barrett wrote:
>> It both works and doesn't work for me.
>>
>> The kernel module is fine, the X Server loads and seems to open the device
>> correctly, but the screens stay blank, then turn off.
>> The attached tar file has
It both works and doesn't work for me.
The kernel module is fine, the X Server loads and seems to open the device
correctly, but the screens stay blank, then turn off.
The attached tar file has dmesg output and the Xorg and gpu-manager log files.
The only thing I can see is the gpu-manager log c
@northar: The general view seems to be that open source drivers must
work, but not necessarily the closed source, except for LTS releases.
Personally I think the closed-source graphics card drivers are important
enough that they should be fixed before release; it seems that every
second release ha
Public bug reported:
Release 15.10 Wily Beta 2.
GPU R9 290. Hawaii Core.
When switching to fglrx from radeon, I get no graphics.
Scenario 1: Use the "Additional Drivers" push-button to change to fglrx
; do not create xorg.conf.
Result: On reboot, both the Displayport and DVI screens turn off (
*** This bug is a duplicate of bug 1292830 ***
https://bugs.launchpad.net/bugs/1292830
Constantly Black borders and overlays no matter how I reset or reinstall
on my Dell E7440 Laptop. Let me know if I can provide logs that will
help. I installed the xorg edgers to try to get multiple monitors
I'm confused by this. The fix was a setting problem, and I was informed
a long time ago. Moribius1 nailed it on July 21st, in the page
http://ubuntuforums.org/showthread.php?t=2235440&p=13078735#post13078735
, also referencing
https://bugs.launchpad.net/ubuntu/+source/xfe/+bug/1029256 . Fixed by :
Public bug reported:
Bug report??
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory:
Public bug reported:
I select "new folder", window appears, but cannot enter name in text box
to create new folder.
It seems that some users have this problem, some not. XFE has no
variants, so I'm guessing the problem arises within Ubuntu and
variations in Ubuntu setup.
Please see
http://ubunt
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
Public bug reported:
safeboot mode necessary
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
.tmp.unity.support.test.1:
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
C
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 am suffering from the same bug using a P502 also named Sager NP9150 (P150EM
Barebone)
with an AMD 7970m and an Intel igpu.
As I workaround i use a small script I have attached. Placed in /etc/pm/sleep.d
it seems to work for the moment.
Dont forget to make it executable.
I have no problems wit
** Branch linked: lp:ubuntu/raring/xorg
** Branch linked: lp:xorg-server
** Branch linked: lp:fontconfig
** Branch linked: lp:aptfs
** Branch linked: lp:dtdparser
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.la
** Changed in: libxres (Ubuntu)
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxres in Ubuntu.
https://bugs.launchpad.net/bugs/1188410
Title:
branch fix
To manage notifications about this bug go to:
h
Arnold
Why i can do to link libxres?
Merci
** Changed in: libxres (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxres in Ubuntu.
https://bugs.launchpad.net/bugs/1188410
Title:
branch fi
the ubuntu desktop is unstable after loading,no typing can take place
and the outer edge disappears along with the desktop when another action
is selected
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
Upgraded to 12.10 from 12.04.Various problems since,Ubuntu desktop is
now dropping out after logging in and using say firefox when go back to
desktop it does not function and machine has to be closed down manually
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7
20:07:16 Precision-M4600-JRYQKQ1 kernel: [ 646.449954] [drm] nouveau
:01:00.0: nouveau_connector_detect:249 - DDC not detected!
Nov 7 20:07:16 Precision-M4600-JRYQKQ1 kernel: [ 646.449955]
[drm:output_poll_execute], [CONNECTOR:20:VGA-1] status updated from 2 to 2
Roger R. Cruz
--
Yo
When this error ocorr normally I just reboot the machine.
Is there a way to see a log of what was running prior to my reboot (the freeze
moment)?
--
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/107
Public bug reported:
I couldn't determine yet what is causing the problem or how to reproduce it.
But my Dell Latitude E5430 with 12.04 just freeze from time to time (normally
once in two days).
The screen, mouse and keyboard just freeze( I can't turn the caps-lock light)
If some want me to run
1 - 100 of 174 matches
Mail list logo
