when it happen in fullscreen mode I get this error message in the
terminal:
libva info: VA-API version 0.39.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openD
By using MPPE encryption in NetworkManager, PAP CHAP and EAP are automatically
grayed out leaving only MSCHAP and MSCHAPv2 active.
This configuration does not work returning the error message PPTP service has
stopped that everyone here is facing.
A workaround that works for me is to deactivate M
Public bug reported:
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename: xenial
Kernel: 4.4.0-57-generic(x86_64)
network-manager-gnome v. 1.2.0
network-manager v. 1.2.2
I have just installed Ubuntu 16.04 and I have noticed that virtual interfa
Same for me on Ubuntu 16.0.1. I get a black screen by using DRI_PRIME=1
glxgears but the frame is highen the Intel card.
Is it normal that xrandr --listproviders returns 2 providers for the
AMD/ATI card?
Providers: number : 3
Provider 0: id: 0x6b cap: 0x9, Source Output, Sink Offload crtcs: 3 out
*** This bug is a duplicate of bug 1507167 ***
https://bugs.launchpad.net/bugs/1507167
same problem on ubuntu 14.04 going in fullscreen mode under chrome. The
screen becomes white and then I get a crash. Kerner 3.13.0-86-generic
and driver i915.
--
You received this bug notification because
I cleaned everything up:
sudo sh /usr/share/ati/fglrx-uninstall.sh
sudo apt-get remove --purge fglrx fglrx-core fglrx-amdcccle fglrx-dev
sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
sudo apt-get remove --purge xserver-xorg-video-intel
sudo apt-get install xserver-xo
Public bug reported:
Description:Ubuntu 14.04.2 LTS
Release:14.04
Kernel: 3.13.0-53-generic
fglrx:
Installato: 2:14.501-0ubuntu1
Candidato: 2:15.200-0ubuntu0.3
Tabella versione:
2:15.200-0ubuntu0.3 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/restricted a
I have upgraded the Catalyst driver to the version 14.12 installing
directly the deb packages taken from the official amd website.
I have applied the workaround suggested here:
http://askubuntu.com/questions/540780/14-10-wine-and-fglrx-conflict
to solve the conflict fglrx/wine on Ubuntu 14.04
I have the same problem. I have noticed it using Skype 4.3.0.37 on
Ubuntu 14.04 using the official kernel 3.13.0-37-generic. If I do not
activate my cam everything is working fine but as soon as I switch on my
cam the audio start to be unstable and the video freeze.
In my case it does not affect c
Tested 0.9.3.2-1 on ubuntu 14.04 and it is working. Will the fix be
committed in Trusty?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1327539
Title:
Yagf package cor
Thanks Tehnick! Could you tell me in what consists your bug fixing? What
is the policy? should 64bit applications write or not in /usr/lib64?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.
** Also affects: yagf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1327539
Title:
Yagf package corrupts fglrx mo
HP DV6 same problem. I do not think the bug is due to gnome-screenshot
but it a problem of the keyboard map. STAMP is not recognized at all.
First I noticed I was not able to use altgr+STAMP REISUB anymore, now
the screenshot.
I have changed the shortcut for the screenshot to alt+h for instance an
Public bug reported:
On 64bit machine the fglrx installer assume that you /usr/lib64
directory is linked to /usr/lib. I believe this is a bit risky
expecially for those package that are still writing in /usr/lib64.
Last week I have installed yagf from the repository, which I guess
overwrote the /
** Attachment added: "kernel.log"
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1310071/+attachment/4123339/+files/kernel.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer-updates in Ubuntu.
I get the same error by typing:
glxinfo | grep rendering
libGL error: dlopen /usr/lib/fglrx/dri/i965_dri.so failed
(/usr/lib/fglrx/dri/i965_dri.so: cannot open shared object file: No such file
or directory)
direct rendering: Yes
--
You received this bug notification because you are a member of
Any news? The workaround does not work for me
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1310071
Title:
Low graphics mode on logout
Status in “fglrx-installer-upd
*** This bug is a duplicate of bug 1304434 ***
https://bugs.launchpad.net/bugs/1304434
Duplicate of Bug #1304434
** This bug has been marked a duplicate of bug 1304434
indicator-printers not working on ubuntu 14.04 beta
--
You received this bug notification because you are a member of De
I had the problem in Ubuntu 13.04 but not anymore in Ubuntu 14.04. I
believe it could related to the way how you mount it. I will check the
fstab as soon as I will be back at home.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus
HP Pavillion 6030el: Ubuntu 14.04 (clean installation) + fglrx-update
I'm able to use both discrete and integrated cards but when switching to
the integrated one I get a low graphic mode logging out and SysRq REISUB
does not work.
--
You received this bug notification because you are a member of
I can confirm what reported by EliCoten, If we click on the drive icon
we get the last window minimized although there is no pointer on it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bug
Sorry I have just realized that the error message in the terminal was
different. Sorry! Shoul I open another bug?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/666238
Title:
Fil
Please re-open this bug. It has not been fixed. I have exactly the same
problem on ubuntu 13.04.
This is the error message from the terminal:
** (file-roller:16278): WARNING **: Errore nel creare il collegamento
simbolico: File già esistente
Dear Marco why I can find just 13.8beta on amd website? Where can I get
13.9? I would like to test them. Thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
L
Thanks Rafael!!!. Usually I do not have any xorg.conf or xorg.conf.d.
xorg.conf is the one that comes from aticonfig. Should I put those lines
in the xorg.conf created by the catalyst driver?
ps: I have tried to install the beta version 13.6 using the user
interface but the installation does not s
How to disable SNA, please?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx
upgrade
Stat
Thanks, just one question: is your fglrx based on the catalyst 12.10 or
lower? Before 12.10 my card was not supported and maybe also the package
on x-edgers is based on an older driver.
Mine was just a test for Nick to verify if the package xorg-intel coming
from this ppa was able to run both fglr
PS: Thanks to all of you for your efforts :-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Low graphics mode in muxless hybrid ATI/Intel GPU systems after fgl
Clean installation (everything from quantal repository) + x-edgers
packages which include kernel 3.7 and xorg-intel + fglrx-updates = low
graphics mode.
Instead by using fglrx my graphics card is not recognized by aticonfig.
Too many reboot recently...I went back to the default configuration
(i91
@Nick:
I will test both the raring and x edgers sources this evening and I will let
you know.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Low graphics mod
I have removed everything and started from scratch but using this time
fglrx-updates instead of the beta version from the amd website to see if
I can get rid of the segmentation fault. I will let you know after some
test.
What I did so far:
sudo apt-get remove --purge fglrx fglrx-amdcccle
sudo ap
By installing the catalyst driver with the default xserver-xorg-driver-
intel I have the problem mentioned on this bug. Instead using your patch
will solve the problem concerning the fglrx but if the user would like
to remove the proprietary driver and restore the previous one, he needs
to remove a
Yes, your package works with fglrx (catalyst 12.11) but as soon as I
removed everything to perform a clean installation of the driver
following the steps on the unofficial forum :
sudo sh /usr/share/ati/fglrx-uninstall.sh
sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev*
If you
Please remind that the workaround proposed in #1 by installing xserver-
xorg-video-intel from ppa:andrikos/ppa causes again low graphic mode
when fglrx is removed and i915/xserver-xorg-video-ati will be used.
Configuration:
Hp Pavillion dv6 6030el
VGA compatible controller: Advanced Micro Devices
This bug is still affecting quantal as reported by Sebastien. The
workaround #5 works for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/963106
Title:
NetworkManager cause
35 matches
Mail list logo