RSION="20.04.5 LTS (Focal Fossa)"
nick@Precision-3541:~$ sudo lshw -C display
[sudo] password for nick:
*-display
description: 3D controller
product: GP107GLM [Quadro P620]
vendor: NVIDIA Corporation
physical id: 0
bus info: p
** Package changed: ubuntu-release-upgrader (Ubuntu) => mesa (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1998639
Title:
MESA-INTEL: warning:
To manage notifications about this bug
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1926860
Title:
XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
To
** Patch added: "apport-lp-1952947-impish.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+attachment/5561447/+files/apport-lp-1952947-impish.debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-utils in Ubuntu.
** Description changed:
+ [Impact]
+
+ This bug makes it more difficult for Wayland users to report bugs with
+ apport. When a Wayland user tries to use the -w,--window option, apport
+ fails silently. We do not want users to face a high barrier to
+ submitting bug reports.
+
+ The patch for
** Attachment added: "prevboot log"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917806/+attachment/5473726/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
Public bug reported:
Freezes after submitting the login password. If I shutdown the system
it usually works afterwards on the first boot, but not subsequent
reboots.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-66.74-lowlatency
Hello, here is the log as requested
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1890863/+attachment/5400918/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
After coming out of suspend the display is not receiving any data and
stays in power saving mode. Only power cycling the system brings it
back. Unsure whether this is related to amdgpu or something else.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg
Also FWIW it also happens with amdgpu so I think it's probably mutter
and not nvidia
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1827428
Title:
Mouse cursor left
Been experiencing this on multiple distributions but haven't been able
to find an upstream bug report
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1827428
Title:
Mouse
I am going to disagree with #62. I am running Lubuntu 18.04 fully
updated as of the date of this message.
My system is a Dell Optiplex 9020. I have tested with a Logitech M325
wireless mouse, a Dell usb mouse and an old hp PS/2 mouse (the Optiplex
9020 is a modern system but does indeed have PS/2
This issue (which did not occur with a fresh install of 16.04) appears
to be related to the contents of file:
/usr/share/themes/Ambiance/gtk-2.0/gtkrc
At line 346 (at present) there is the following:
style "menu" = "dark" {
Changing it to:
style "menu" {
... resolves this particular
** Package changed: xorg (Ubuntu) => ubuntu-meta (Ubuntu)
--
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/1734794
Title:
Install of ubuntu-desktop login loop
To manage notifications about this
Public bug reported:
Tested on clean VM. To repro install ubuntu-17.10 server edition
> sudo apt update
> sudo apt upgrade
> sudo apt install ubuntu-desktop --no-install-recommends
> sudo reboot
# Reboots to graphical login screen. After entering username password returns
to graphical login for
This bug happens again after I've done a fresh install.
** Attachment added: "Xorg.0.log.problem_wait"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664979/+attachment/4947065/+files/Xorg.0.log.problem_wait
--
You received this bug notification because you are a member of Ubuntu-X,
It happened when I unlock the screen.
--
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/1664979
Title:
EQ overflowing. Additional events will be discarded until existing
events are processed.
After another reboot, EQ overflowing occurs again, it seems random to me
now.
** Summary changed:
- Xorg freeze EQ overflow...
+ EQ overflowing. Additional events will be discarded until existing events are
processed.
--
You received this bug notification because you are a member of Ubuntu-X,
Public bug reported:
I was on 14.04 and had no problem, but I started to have EQ overflow after
upgrading to 14.04.3.
Then I did fresh install of 16.04 on the same PC, but still EQ overflow occurs
after closing SMPlayer.
[640410.566] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0x4078)
I'm possibly experiencing this bug, but I'm using the Nvidia proprietary
driver, particularly the 367.57 version.
I tried to switch the clocksource to acpi_pm, as suggested in some forums, but
it doesn't help.
While that's EQ overflowing, I couldn't check anything but reboot.
Attached is the
P.S. mine is also GT710 and Xubuntu 16.04, with kernel 4.4.0-59-generic.
--
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/1587730
Title:
graphic system freezes after a while, can still ssh into
Public bug reported:
i was running sudo apt-get install mesa-utils for working with my amd
driver
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libxatracker2:amd64 11.2.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
Just hit this and judging from various comments online lots of other
people have to. You might want to withdraw version 304.132...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
I was just including my example as another plus point for fake modes ("scale"
in this case didn't mean "output scaling".
If we had the fake modes then output scaling wouldn't really be required in
this case, as we would have a set of mutually inclusive modes to chose from.
--
You received this
This is also an issue when we have cloned displays.
We need to be able to scale down to a fake mode. My laptop screen only runs at
1080p and if I have an external monitor plugged in with a lower resolution (eg
720), the only valid resolution will be the lower one.
--
You received this bug
Public bug reported:
The system for this bug is running Trusty with xvfb 2:1.15.1-0ubuntu2.7
Xvfb fails to launch after being used for a couple days and I can't see
any reason to why it wont launch.
We have inetd.conf setup to run an x11vnc script with the following
command whenever a
Public bug reported:
Slows boot time in Ubuntu to over 1 minute 40 seconds. The system
appears to hang when loading Apport.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
I was able to fix this problem on a MacBook Pro 4,1 with a GeForce 8600M GT by
following these instructions:
https://ubuntuforums.org/showthread.php?t=2209602
In this case, installing the current version of Ubuntu (16.04.1) via USB
with a GUID partition table was not a problem.
--
You received
That's correct. And it hadn't happened for a while now but just
happened again yesterday.
--
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/1576546
Title:
random letters don't
I just switched to Ubuntu from Debian (using xfce not gnome). .Xmodmap
has worked on Debian since ... forever. I can't do without it. I thought
Ubuntu was based on Debian?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
I worked with Zebra on this and was able to get the scanner working by
reducing the USB polling interval on the scanner to 8msec, the default
is to poll every 3msec. I still believe this is a bug in how xterm
accepts input because of the following:
A) This issue does not occur when accepting
Thanks for the response Thomas. The DS4208 has multiple cables that it
can be plugged in with, the xterm issues are when it is plugged in over
USB. RS232 is not used for doing direct-text input.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
I have a symbol DS4208 Wired USB barcode scanner hooked up to a machine
running Ubuntu 14.04 via a USB connector. When using xterm and
attempting to scan a 1D or 2D barcode the xterm window will accept in a
couple characters from the USB scanner not in the correct order, and
Thanks, I'll try running with -k8 and other settings to see if I can't
get it to respond differently!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xterm in Ubuntu.
https://bugs.launchpad.net/bugs/1499416
Title:
xterm freeze when accepting
Thomas,
The characters being sent/received are normal ASCII characters, we're doing
Vin code scanning so it's even in the domain A-Z 0-9 like I said, it was
working fine on an older version of xterm.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Thomas: This issue is reproducible simply by attempting to scan a
barcode into the xterm window NOT a child process, I was simply
indicating that it happened in both places. The USB scanner is acting
as a basic character-input device when used like this. There's no
special application running
Here's what xterm is apparently seeing when I scan a barcode and use the
-l option to log the output.
^[]0;isisup@LUBE151: ~^Gisisup@LUBE151:~$ 1G
The 1G is the first 2 printed characters of the barcode in this case,
but there are 15 more it should have kept reading instead locking up.
Using
I have exactly the same issue with Kubuntu 15.04 (clean install, all
updates).
lspci:
00:00.0 Host bridge: Intel Corporation 82X38/X48 Express DRAM Controller (rev
01)
00:01.0 PCI bridge: Intel Corporation 82X38/X48 Express Host-Primary PCI
Express Bridge (rev 01)
00:1a.0 USB controller: Intel
Could you guys fix this already? Using an excuse that it's not broken in
15.04 is total BS. 14.04.2 is supposed to be a LONG TERM SUPPORT version
and one of the most important parts of a desktop system has been unable
to be installed for like 2-3 months now. This is pathetic.
--
You received
Jessie installed. I'll notify here if it
reaapears in Debian, too.
Best wishes,
Nick Dowson
--
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/1435587
Title:
System slows down to almost unusable
Public bug reported:
Hi, after an update about a month and a half / two months ago my system
started freezing after a period of usage. This tends to happen about
once a day... so generally after the laptop's been on for a few hours
(not necessarily constantly), sometimes probably up to 8 or ten
Public bug reported:
for 3 days ran this and it worked after ,no idea if this fixed it or
coincidence but thanks have a grat weekend i love ubuntu just wish
someone could send me in the right direction to learn it
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
Issue persists in Xubuntu 14.04; opening http://google.com/chrome/ in
either Chrome or Firefox triggers the bug. The issue can be worked
around by either disabling hardware acceleration in Chrome or switching
the acceleration method to UXA in Xorg.conf.
--
You received this bug notification
Thank you Infektedpc it is work for me too.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1424263
Title:
Broken dependencies
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1300914 ***
https://bugs.launchpad.net/bugs/1300914
Edgar I have the same problem only _after_ upgrading to
3.13.0-44-generic. Can you test if the problem goes away for you too
when you boot with an earlier version of kernel?
--
You received this bug
*** This bug is a duplicate of bug 1300914 ***
https://bugs.launchpad.net/bugs/1300914
oops! I've missed the duplicate bug warning - will re-post to bug
#1300914
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
I'm also seeing this after both an upgrade, then a purge reinstall.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1370270
Title:
package fglrx-updates-core
Public bug reported:
Upgrading fglrx (13.350.1-0ubuntu3 = 14.201-0ubuntu1)
Unpacking fglrx-core (2:14.201-0ubuntu1) ...
dpkg: error processing archive
/var/cache/apt/archives/fglrx-core_2%3a14.201-0ubuntu1_amd64.deb (--unpack):
trying to overwrite '/lib/fglrx/modprobe.conf', which is also in
** Attachment removed: xserver.devices.txt
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1369307/+attachment/4203893/+files/xserver.devices.txt
** Attachment removed: xserver.outputs.txt
Old, likely will not fix.
** Changed in: fglrx-installer (Ubuntu)
Status: New = Invalid
** Attachment removed: BootDmesg.txt
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714073/+files/BootDmesg.txt
** Attachment removed: xserver.outputs.txt
Thanks Straximus, that worked for me too.
--
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/1308105
Title:
Xfce resets TV mode to NULL when power cycled
To manage notifications
^No AMD owns ATI, the other major graphics card provider.
I am also experiencing this problem on integrated Intel graphics on
Xubuntu 14.04 when using HDMI. It's the first distro I have used on this
system but I never had the problem on Xubuntu 12.04 on my previous sytem
(which was VGA/D-sub).
I
Public bug reported:
Left click on an app icon in the launcher bar works fine on first use.
After closing the app, it is impossible to open the app again by left
click. The only way to open the same app is to right click and select
the open option from the menu. Software updater would not launch
Good news that the code to enable this has finaly landed in Linux.
Unfortunately, I don't have access to the hardware where this bug was initially
reported against, so I cannot test this new functionality
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I no longer see the problem on Ubuntu 13.10. Both monitors show as DVI
connected and both work fine.
--
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/890061
Title:
Nouveau
Public bug reported:
I am somewhat used to having GPU lockups hang X for me maybe once a
week. I've followed a few vague bugs on the problem, but over the past
weekend this has grown to every couple of hours.
Easy ways to trigger it: changing workspaces too quickly while there is
disk activity,
This bug also exists in fglrx-13 from xorg-edgers @
https://launchpad.net/~xorg-edgers/+archive/ppa
Not entirely sure where fglrx bugs go. I've also reported at:
http://ati.cchtml.com/show_bug.cgi?id=847
** Bug watch added: ATi Linux Platform Bugs #847
Public bug reported:
Running a new ASUS EAH6670 on Raring, seems to have frozen w/ kernel
spinning in X during logoff.
htop shows an unkillable spinning thread (100% CPU, all in kernel) of:
/usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[11139.483689] AMD
Thanks for the advice, Chris! The --newmode/--addmode arguments will be
very useful. I do want to use that mode quite badly, as the display
represents all other resolutions I tried (of which there were many on
the older kernels) very badly.
I presently cannot remember on what basis I concluded
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658592/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Graphics worked in Precise. After upgrading, lightdm does not load, but
the safe graphics mode dialog is displayed, instead This dialog fails
to accomplish anything other than allowing me to exit to a terminal and
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658605/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658596/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658598/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658599/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658606/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658597/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658595/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658601/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658594/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658591/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658604/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658600/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658603/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: xserver.outputs.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658607/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658593/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
You are correct Chris, the original logs were indeed from a working
session. I did not consider that they might only cover one session - my
apologies, I hope I have not wasted anyone's time!
As you can see by the spam :S it looks like I successfully ran apport-
collect from the VT... I had to
An interesting thing I noticed is that, upon login into the VT, ubuntu
tells me that there is a new release available (13.04) and that I
sould use do-release-upgrade to upgrade to it. Perhaps something went
wrong in the upgrade process.
Actually trying to run do-release-upgrade tells me that
Ahhh, given what you just mentioned, I remembered that I had added a
line to /etc/lightdm/lightdm.conf, in order to force light-dm to use the
native resoltution of the display:
display-setup-script=xrandr --output HDMI2 --primary --mode 1440x900
This was returning a failure code, causing
Thanks Timo,
Unfortunately, the kernel you linked does not appear to work any better.
--
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/1173491
Title:
Boot to Safe Graphics
Public bug reported:
Graphics worked in Precise. After upgrading, lightdm does not load, but
the safe graphics mode dialog is displayed, instead This dialog fails
to accomplish anything other than allowing me to exit to a terminal and
I thus cannot use the system in graphical mode at all (even
Please let me know if I can provide further helpful information. (Or if
imdoinitwrong.)
--
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/1173491
Title:
Boot to Safe Graphics after upgrade to
Wait how do I go about installing the fixed stuff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1068994
Title:
button1 gets stuck after a while
To manage notifications about this bug
For anyone wanting to work on this issue, you might want to take a look
on these bugs:
https://bugs.launchpad.net/ubuntu/+bug/1068404
This was about the initial X-server crash and it was an incompatibility of the
fglrx driver with the intel one.
The solution is to install fglrx 13.1+ which
Guys just a small remark.
I have changed laptop and I don't have my intel/ati system any more.
So, I won't be able to troubleshoot any more :(
Nick
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs
I would try but i've just broken my system. added trim command in bootup
and disabled writing reports to make my SSD last longer however I now
have no desktop, blank screen. I've undone these changes but ctrl-alt-f7
(still with random curruptions but no desktop). seen another post
somewhere
Yes, you are probably right, I'm hiding my comment on the other bug
Thanks for pointing it out!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1068404
Title:
Low graphics mode in muxless
Try to install this version 2:12.100.3-0~andrik1 (for both
fglrx-updates and fglrx-amdcccle-updates) and remove the updated intel
driver.
Just the updated fglrx driver should work
--
=Do-
N.AND
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Marco, I think the periodic crashes refer to the Bug #1088220 which still
remains.
At least the new (13.1+) drivers seem to solve the initial segmentation fault,
is that right?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
I think the intel driver is out of this bug and should be marked as
invalid.
The solution relies in the fglrx driver. I have tried the 13.2beta3
driver and it solves the problem.
If we don't want to go for this version, a Suse user on the
corresponding attached bug, reported that also 13.1 is ok.
** Branch linked: lp:~andrikos/ubuntu/quantal/fglrx-installer-updates
/fix-fglrx-intel-hybrid
** Branch unlinked: lp:~andrikos/ubuntu/quantal/fglrx-installer/fix-
switch-to-igpu
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1068404
Title:
Low graphics mode in muxless hybrid ATI/Intel GPU
And this is the new merge request of 13.2beta3 for quantal-proposed:
https://code.launchpad.net/~andrikos/ubuntu/quantal/fglrx-installer-updates/fix-fglrx-intel-hybrid/+merge/148950
** Branch unlinked: lp:~andrikos/ubuntu/quantal/xserver-xorg-video-intel
/fix-ati-hybrid
--
You received this bug
And this is the new merge request of 13.2beta3 for quantal-proposed:
https://code.launchpad.net/~andrikos/ubuntu/quantal/fglrx-installer-updates/fglrx-13.2-beta3/+merge/148950
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
fault and the low
graphics mode is activated.
WORKAROUND: Follow carefully the instructions here:
https://help.ubuntu.com/community/BinaryDriverHowto/ATI#WORKAROUND
As per Nick Andrik, this is a version regression of xserver-xorg-video-
intel from 2.20.2 (working and in below
It seems that the fglrx 12.3-beta3 driver solves this issus without any
patch needed for the intel driver.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1068404
Title:
Low graphics mode in
Yes, I menat the 13.2, not 12.3, sorry.
I packaged and tried that version for ubuntu and it seems to resolve the
problem.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1068404
Title:
Low
).
Could anyone please test the packages in your systems in order to see if
it is a proper fix and if any regressions appear?
Thanks,
Nick
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1068404
).
Could anyone please test these packages in your systems in order to see
if this is a proper fix and if any regressions appear?
Thanks,
Nick
--
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
workaround not working:
the message is:Error: Key DDX,PX_GPUDOWN not found in PCS database
Do you still get the crash if you reboot after you get this error?
Nick
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu
1 - 100 of 460 matches
Mail list logo
