Same problem/issue on my Acer 5750G with a GT 520M nVidia, discrete gpu.
Marco
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2017212
Title:
ASUS N56VM fails to load GUI
Public bug reported:
Relatar erro na execução Linux
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
Uname: Linux 4.15.0-96-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.14
Public bug reported:
Hi.After i installed my video card i did some display changes like Scale
and Refresh Rate.After i changed Refresh Rate from 30 to 50 & 59 it
crush .I reinstalled 3 times ubuntu because my monitor was no signal
receive from I use Samsung Led TV with 60 Hz Refresh
Yes, to get both screen working... I need to boot with only the Display Port
connected!
If I boot with both ports connected only the DVI one gets detected.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Public bug reported:
I had a problem where my monitor connected to the Display Port didn't
work but the monitor at the DVI Port was working fine.
The only way I manage to get the Display Monitor working was to boot
with only this monitor connected and after the Desktop was loaded I
could connect
After some further investigation, I learned, that there are two APIs for this.
1. VA-API: for Intel with the tool: vainfo
2. VDPAU-API: for others with the tool: vdpauinfo
and there is the libvdpau-va-gl which translates VDPAU-API to VA-API.
Setting VDPAU_DRIVER uses this library and this
In xenial after upgrade to hwe-16.04 the missing library is showing up
in kaffein.
Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file:
No such file or directory
vo_vdpau: Can't create vdp device : No vdpau implementation.
Setting VDPAU_DRIVER to va_gl removes the
A correction to #34
$ vdpauinfo
display: :0 screen: 0
Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file:
No such file or directory
Error creating VDPAU device: 1
$ xine
Questo è xine (X11 gui) - un riproduttore video libero v0.99.9.
(c) 2000-2014 The xine Team.
Same problem here after a fresh install of Ubuntu 16.04.3 on a Thinkpad
T460
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated
Graphics (rev 07)
$ vdpauinfo
display: :0 screen: 0
Failed to open VDPAU backend libvdpau_.so: cannot open shared object
Could this be related to https://bugs.launchpad.net/ubuntu/+source/oem-
config/+bug/1638473
--
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/1714140
Title:
Fresh OEM install, xorg failed to start
Tested and resolved on both 32-bit and 64-bit Kubuntu ZZ Beta 1 Images
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Fix Released
** Changed in: xorg (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of
This may be resolved with Kubuntu ZZ Beta 1.
--
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/1625595
Title:
Libre Office Writer Icons unreadability on YY and ZZ with Intel
With nvidia-driver 304 134 taken from PPA https://launchpad.net
/~graphics-drivers/+archive/ubuntu/ppa the problem seems to be solved in
my case.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
Changing the title of the bug report as Libre Office Calc icons are
readable, and tested on ZZ also.
** Summary changed:
- Libre Office Icons unreadability on YY with Intel Drivers
+ Libre Office Writer Icons unreadability on YY with Intel Drivers
** Summary changed:
- Libre Office Writer
** Tags added: kubuntu
--
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/1625595
Title:
Libre Office Icons unreadability on YY with Intel Drivers
To manage notifications about
Public bug reported:
I expect a web browser on the ISO.
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Tags: kubuntu
** Package changed: xorg (Ubuntu) => firefox (Ubuntu)
** Tags added: kubuntu
--
You received this bug notification because you are a member
I can confirm this bug, and that changing the video output to "OpenGL
GLX video output(XCB)" as per comment #15 appears to work around the
issue (thanks epoxy!).
My system:
Ubuntu 16.04
Kernel 4.4.0-31-generic
Acer Aspire F15 laptop
CPU Intel i7-6500U (Skylake)
Nvidia GeForce 940M (probably not
Public bug reported:
After upgrading from 14.04 to 16.04 on a Lenovo x230, the mouse pointer
speed is way too high even if set at minimum. It's so bad it's almost
unusable.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic
-suspend
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1573760
I you require additional information please let me know.
Best regards
Marco
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
I still get many people asking me how to fix this behavior in Linux.
Since this bug is now nine years old and there seems to be no interest
in providing a "proper" fix, I've created a small shell script that
should configure your system to generate a cedilla c on '+c:
Public bug reported:
Aftet add Proprietary GPU Drivers https://launchpad.net/~graphics-
drivers/+archive/ubuntu/ppa i have this issue and when i login i have
wrong screen resolution (low resolution)
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-304 304.125-0ubuntu0.0.2
Ok just for clarify my point: I usually do bug reports not just for me but
hoping that my problems help someonelse solve him/hers. I am perfectly well
keeping the old kernel and frankly I do not think to have security problems in
this way. To sum up: I have no needs, but I am here if You want
Having al least had occasion to test the PC with 15.04, that kernel
(3.19) ... it seems to work!
Dmesg report a series of bugs like this (of the top of my head):
noveau E[PBUS] [...] MMIO write of 0x0101 FAULT at 0x000
repeated perhaps 10 times...
Hope this helps...
--
You
Tested with an hardware like this... 15:04 works!
--
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/1389732
Title:
The computer freeze randomly
To manage notifications about this bug go to:
Really strange though. The 15.04 live CD seems to work but if I try to
install linux-image-generic-lts-vivid (3.19) on a 14.04, it hangs...
--
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/1456184
Sorry I do not understand your question.
I have resolved keeping the old 12.04 kernel when updating to 14.04.
Thanks to [...] that update program keeps the old kernel. If I tried a new
install of 14.04 on that hardware it would result a mission impossible. I am
afraid it could not be the only
Thanks for the advise but according to this:
https://wiki.ubuntu.com/Releases and if I understand correctly the end
of life of 12.04 LTS is far from expired.
Anyway a backport is really the solution since if someone want to
install a 14.04 from scratch instead of upgrading from a 12.04 he/she
*** This bug is a security vulnerability ***
Public security bug reported:
I am not sure I thought I just run a debugger.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
Uname: Linux
Output of sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date:
1804
08/23/2010
** Changed in: xorg (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Perhaps there is a misunderstand here: the PC was already updated to the
last available BIOS version. If there is a but in the BIOS, than that
bug is not going away. BTW I have a friend of mine with a laptop with
AMD CPU and more or less the same NVidia card that had similar problems
resolved in
I re-read my message, sorry for being rude.
So your suggestion is to leave this bug report to the (missing?)
willingness of his author and continue with my report?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Sorry I missed this:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
...Instead, if you are the original reporter, ensuring the report has
all the requested testing information performed would be the fastest way
to ensure your bug is resolved as soon as possible. If you are
I know that the BIOS is updated to last version available: 1804.
I actually am writing from my laptop and that is a desktop PC.
As soon as I reach that PC I'll do what I was asked to do and I will
post the results...
Thanks for your patience.
--
You received this bug notification because you
Please if you set a bug as incomplete, ask for what it needs to fill in
the gaps of information... what is missing from this bug report I
wonder...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Tested even with 3.19 backported vivid kernel hangs a few seconds
after X boot... :-((
--
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/1389732
Title:
The computer freeze randomly
To
this workaround works: http://askubuntu.com/questions/588538/whats-the-
correct-driver-to-use-with-a-geforce-6150se-nforce-430-on-lubuntu-14
but IMHO it is not acceptable for two reasons:
1) it is an all proprietary solution
2) it works bad (noveau under kernel 3.2.0 worked better)
--
You
Sorry I got a working xorg adding nomodeset to boot but the screen
resolution is wrong (1024x768 instead of FHD 1920x1080). Hope this
helps...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
I managed to create an apport report just before screen freeze (changing
console to ctrl+alt+f1) and saved to file this time. See attached
report.
** Attachment added: Apport report
I do not know how to do it. I mean: when the computer freezes it is
impossible to file any bug report. And I think that filing a bug report
for a working (with the old kernel) system is useless...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
This is the content of Xorg.1.log:
[ 12693.660].
X.Org X Server 1.11.3
Release Date: 2011-12-16
[ 12693.660] X Protocol Version 11, Revision 0
[ 12693.660] Build Operating System: Linux 2.6.42-37-generic x86_64 Ubuntu
[ 12693.660] Current Operating System: Linux babi-desk 3.2.0-68-generic
Public bug reported:
VGA compatible controller: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a]
(rev a2)
Freeze when used with new kernels (3.13 or 3.16) and works with 3.2.0 (from
12.04 precise) or 3.13 (trusty) with nomodesed option (but wrong resolution)
lsb_release -rd
Description:
Filed bug report here:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1456184
--
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/1389732
Title:
The computer freeze randomly
To manage
** Changed in: xorg (Ubuntu)
Status: Expired = Confirmed
--
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/1389732
Title:
The computer freeze randomly
To manage notifications about this
Please re-open this bug.
I own the same motherboard: http://www.asus.com/Motherboards/M2N68AM_PLUS/ with
last bios version 1804.
I recently upgraded from 12.04 to 14.04. 12.04 was working flawlessly. Luckily
I retained the old 3.2.0-83-generic-64 kernel from 12.04. It seems that it is a
kernel
To be clearer 14.04 works without problems with 12.04 3.2.0 kernel.
--
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/1389732
Title:
The computer freeze randomly
To manage notifications about
Why this bug is still (three years now!!!) marked incomplete? What is
missing? Please convert it in open or commit the suggested patch and
close it!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
Public bug reported:
Upon opening of the game War Thunder, there is a crash realted to
outdated intel drivers. The intel drivers on this computer are Intel
Sandybridge Mobile, and it gives error 8111000B. I updated and upgraded,
but there seems to be no difference.
ProblemType: Bug
Public bug reported:
no more infomation about the crash
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: xserver-xorg-core 2:1.16.2.901-1ubuntu3
ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
Uname: Linux 3.18.0-11-generic x86_64
NonfreeKernelModules: nvidia
This problem hit me hard today. Problems like this definitely diminish
the user trust in the Ubuntu upgrade process.
The solution was a painful manual rollback, using the output of dpkg
--get-selections from before the upgrade (this old habit has saved me
in more than one occasion). Getting my
Just a comment on this issue, that I reported some months ago for Ubuntu
13.10. After installing Ubuntu 14.04, this issue is not occurring again,
at least in my system.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
I use Ubuntu amd catalyst installer application
Il 22/apr/2014 20:09 Daniel Letzeisen 1310...@bugs.launchpad.net ha
scritto:
You're trying to use an old version (13.251). Where are you getting it?
You should be using https://launchpad.net/ubuntu/+source/fglrx-
installer/2:13.350.1-0ubuntu2
I have the same issue by Danny in #65
Workaround suggested in #6 worked for me until I upgraded linux imag
3.11.0-17
Then compiz returned requiring too much resources to the system (cpu and
ram)
I tried to fix with a intel graphic workaround but without benefits.
For me solution suggested in #
Exactly the same problem for me. I own an HP Elitebook Folio 9470m with
the Intel HD 4000. I'm running Ubuntu 13.10 and I have recently updated
the Intel drivers using their installer.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
The touchpad works in way live, but already installed ubuntu 13.10 does
not recognize the touchpad in a laptop acer aspire one, in ubuntu 13.04
the touchpad was working without problem
** Affects: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided
The result is
Description:Ubuntu 12.10
Release:12.10
xorg-driver-fglrx:
Installato: (nessuno)
Candidato: (nessuno)
Tabella versione:
fglrx-kernel-source:
Installato: (nessuno)
Candidato: (nessuno)
Tabella versione:
fglrx-amdcccle-updates:
Installato: (nessuno)
In case someone was wondering, no regressions on the 13.12 drivers
(version 2:13.251-0ubuntu1) either.
--
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
Thanks to Vince, #14 resolved my problems. Dave Turvene's driver works
flawlessly.
My touchpad now works as it should...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
No regressions on the 13.11 beta V9.4 drivers (version
2:13.250-0ubuntu1) as well.
--
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
@naught101:I would suggest using the default intel drivers and mesa version
with the default kernel as well, I think the new drivers should be used with
the new kernel you were using, this is why I recommended them in the first
place.
If you still have this bug with all the packages from the
@naught101: this bug report originally was referring to Ubuntu 12.10 and
was later extended to Ubuntu 13.04, however I don't think it has yet
been extended to Ubuntu 13.10 (it is not mentioned in the table above).
Anyway, the bug is similar to the one I reported, but by watching the
Xorg log file,
Same with XMG A503 and Ubuntu 13.10:
- CPU: Intel Core i7-4700MQ
- GRAPHICS: intel HD 4600 + NVIDIA GeForce GTX 765M 2048MB GDDR5
- RAM: 16GB (2x8192) SO-DIMM DDR3 RAM 1600MHz Crucial
- HDD: 1000GB SATA-III 7200rpm HGST Travelstar 7K1000
- WIFI CARD: Intel Dual Band Wireless-AC 7260
No problem
@niniendowarrior:if you want to try the new dynamic power management on the
open source drivers you should add
radeon.dpm=1
to the
GRUB_CMDLINE_LINUX_DEFAULT
line on the /etc/default/grub file and then run
sudo update-grub
as specified on https://help.ubuntu.com/community/RadeonDriver
You should
@kpijarski: The bug niniendowarrior talked about is this
http://ati.cchtml.com/show_bug.cgi?id=848
I don't know how to solve your problem. I'm using the fglrx drivers version
13.11 beta version 6 (2:13.250-0ubuntu1 on Ubuntu 12.10 64 bit) and only the
secondary monitor to have its full
Public bug reported:
Description:Ubuntu 13.10
Release:13.10
Codename: saucy
I was trying Mir with Josm (Java Open Street Map) editor
Please read http://josm.openstreetmap.de/ticket/9184
Sounds like a problem of Mir or java with Mir.
Thank...
** Affects: xorg-server
No significant regression also with the 13.11 beta drivers (version
2:13.200-0ubuntu1), as expected.
--
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
@Romano Giannetti:The bug treated here is related to the binary Catalyst
drivers, if you have the bug you mentioned with the open source drivers
of the Ubuntu repositories you can file a new bug here on Launchpad, you
can also report bugs about open source drivers on
https://bugs.freedesktop.org/.
You can find them using this link:
http://www2.ati.com/drivers/linux/amd-catalyst-13.9-linux-x86.x86_64.zip
Sometimes AMD allows downloading their drivers before the official page is up.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug
If you have the dual head bug with the drivers provided by the fglrx or the
fglrx-updates package, the command to file a new bug should be
ubuntu-bug fglrx
(or fglrx-updates)
but if you are experiencing this bug only with the drivers downloaded from
AMD's site then I think you should not file a
Filing on AMD's bug tracker is the right thing to do, if you want you
can also file here on Launchpad (try using Apport/ubuntu-bug).
--
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:
Is there a bug regarding this dual head problem on Ubuntu 13.04? If not,
it could be useful to file a new bug so that Ubuntu developers (and
hopefully also AMD's ones) are correctly informed about this issue.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
As expected, these new drivers (whose version is the same:
2:13.200-0ubuntu1) show no significant regressions regarding the solved
bugs I talked about. Is the dual head situation the same on Ubuntu
13.04?
--
You received this bug notification because you are a member of Ubuntu-X,
which is
With the 13.8 beta drivers (version 2:13.200-0ubuntu1) there isn't any
apparent regression regarding the aforementioned three bugs on Ubuntu
Desktop 12.10 64-bit. What is the situation with Ubuntu 13.04?
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I would like to point out that, since the bug was originally found on
Ubuntu Desktop 12.10 64 bit edition, I am still using this version of
Ubuntu to verify if it has been solved, so my report is about the state
of the bugs on Ubuntu Desktop 12.10. Users of Ubuntu 13.04 may still
find that some of
With the latest OpenGL 4.3 beta drivers (version 2:13.150-0ubuntu1)
there isn't any apparent regression regarding the three bugs I mentioned
in my previous posts.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
Basically the bug treated here (#1068404), the one similar to bug
#1088220 and the problem with XvBA reported as bug 789 on the unofficial
ATI Linux Driver Bugzilla are not present in the OpenGL 4.3 beta
drivers.
--
You received this bug notification because you are a member of Ubuntu-X,
which
Public bug reported:
After a clean install of Ubuntu, my system does not recognise more than
two low resolutions.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
Uname: Linux 3.8.0-23-generic x86_64
With Catalyst 13.6 beta drivers (version 2:13.101-0ubuntu1) again this
bug seems to be solved (as in previous versions), but also the two other
bugs I mentioned (the one similar to bug #1088220 and the one reported
as bug 789 on the unofficial ATI Bugzilla) are apparently corrected
too. Now, if
Apparently with Catalyst 13.6 beta drivers (version 2:13.101-0ubuntu1)
this bug is solved, could the other people experiencing this bug (except
for Nick) confirm this?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in
@gunnarhj When libglib will be updated on the main PPA, no one will use
skype anymore? :) Maybe it's better to fix it. I'm not sure if it's a
skype issue or a libglib issue...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
I don't know exactly to reproduce this crash, but it often happens when
using unity, after a long uptime, after some suspend/wake up cycles,
when dragging Firefox window to the right edge of the screen (to semi
maximize it).
kern.log:
[drm:i915_hangcheck_hung] *ERROR*
Additional info: I can't run unity again without a reboot (I get a
intel_do_flush_locked failed: Input/output error), but I can execute
metacity without any problem.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
+1 to #97.
Skype don't run with libglib 2.37.0 from the ricotz testing PPA
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1155327
Title:
skype crashed with SIGSEGV in
This is correct. Regarding the crash when iGPU is selected, since it is similar
to Bug #1088220 I didn't report a new bug, but I can if you think it is useful,
regarding the bug with XvBA, I reported it as bug 789 on the unofficial ATI
Bugzilla, since the new drivers are apparently not
Here is the lsmod output, dmesg log and Xorg log for the XvBa crash
(modules, dmesgXvBAcrash and Xorglogcrash respectively) and the lsmod
output, dmesg log, syslog and Xorg log for the crash while restarting Xorg
with iGPU selected (modulesintel, dmesgintelcrash, syslogintelcrash and
With the new 13.4 drivers (version 2:12.104-0ubuntu1) the situtaion is
the same as reported in my previous post about the 13.2 beta 7 drivers.
P.S.: @Nick Andrik: Even if late, I would like to thank you again for
your precious aid in solving this bug!
--
You received this bug notification
P. P. S.: my message is late, your help was fast!
--
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 systems after fglrx
upgrade
This is happening frequently in my computer. It usually happens after a
long uptime, after some suspends/wake ups cycles, when I try to maximize
or half-maximize windows in unity by dragging them.
It requires a hard reboot to get the system working again (trying to
start unity or to restart the
Public bug reported:
Description:Ubuntu Raring Ringtail (development branch)
Release:13.04
xserver-xorg-video-intel:
Installato: 2:2.21.5-0ubuntu1
Candidato: 2:2.21.5-0ubuntu1
Tabella versione:
*** 2:2.21.5-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ raring/main
Nothing new with the 13.3 beta 3 drivers regarding this bug, as far as I
know (even the version is the same: 2:12:100ubuntu1).
--
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
I solved on a L850-1PD by installing Catalyst 13.2 beta6, now it's
beta7.
http://www2.ati.com/drivers/beta/amd-driver-installer-
catalyst-13.2-beta7-linux-x86.x86_64.zip
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in
Public bug reported:
Frequent freezing and grpahics problems.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
Uname: Linux 3.5.0-26-generic i686
.tmp.unity.support.test.0:
ApportVersion: 2.6.1-0ubuntu10
Public bug reported:
Description:Ubuntu Raring Ringtail (development branch)
Release:13.04
xorg:
Installato: 1:7.7+1ubuntu4
Candidato: 1:7.7+1ubuntu4
Tabella versione:
*** 1:7.7+1ubuntu4 0
500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
100
The new 13.3 beta 2 drivers (still 2:12.100-0ubuntu1 !) behave more or
less the same as I written in the previous post about the 13.2 beta 7
drivers.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
P.S.: since I reported this bug with Ubuntu 12.10 I think I'm going to
use it until this bug is solved, so unfortunately I cannot help those
who have Ubuntu 13.04 and are having issues with the X server different
from those I reported.
--
You received this bug notification because you are a
Same here:
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07)
The system seem also set/detect wrong screen size as you
Rebooting with kernel
Linux ubuntu 3.8.0-12-generic #21-Ubuntu SMP Thu Mar 7 17:17:00 UTC 2013
i686 i686 i686 GNU/Linux
instead of
linux-image:
Installato: (nessuno)
Candidato: 3.8.0.13.27
Tabella versione:
3.8.0.13.27 0
500 http://archive.ubuntu.com/ubuntu/ raring/main i386
With Catalyst 13.2 beta7 (2:12.100-0ubuntu1) not much has changed (not even the
version number!), so to sum it up:
-2D and 3D acceleration is mostly fine with both the iGPU and dGPU (at least
Unity and some OpenGL appplications such as glxgears work correctly)
-XvBA seems to be broken (or the
Yes, this is what I was trying to explain.
--
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 systems after fglrx
upgrade
To
In the 13.2 beta 6 drivers (2:12.100-0ubuntu1) the situation is more or less
the same as that with the beta 3 drivers, the periodic crashes of the Xserver
when using the iGPU are there as well.
However, I noted that with the 13.2 beta drivers (both version 3 and 6) XvBA
seems to be broken:
On my system the driver works fine both with dgpu and the igpu, excpet
for a bug which should be the same as Bug #1088220. Basically, when
using the iGPU some periodic crashes of the X server with subsequent Low
Graphics Mode are experienced. However, the main bug reported here seems
to be solved.
1 - 100 of 371 matches
Mail list logo
