and just now : A crash while I was trying to get a new tab on chrome...
( not with keyboard as David but by clicking on the icon)
--
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/
About an hour or two after resuming from suspend, pressing Control-N in
Firefox caused this to reoccur. Trying the key combo again now is fine;
opening 5 more windows without an Xorg crash. Not sure if it's a cause,
as Xavier says, by number of windows, but my Firefox typically has 5 or
more wind
For me, it'appear when I click on launcher. may be 5 or 6 times a day.
Mainly when there more than one window for an app.
--
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/1501468
AMD Radeon 6650M
It's this kind of bug that make you lose confidence in Ubuntu/Canonical.
--
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 kernel
Alberto --
This is the second time I have been involved in a major disaster
affecting the fglrx driver. It took quite some time to fix the one
that I reported a few months ago.
I asked that that bug be raised to "critical" as it affected an entire
class of users.
I understand that the heat is
Hello Christopher,
I tried the patch, it seemed to fix the problem for now, thank you
assisting with this.
Cheers
MWJ
--
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/1502520
Title:
My screen b
Public bug reported:
Message on booting up. See attached.
Came up in 1920x1080 expected 1366x768
Screen flashed a couple times, once in 1366x768, then back to max resolution
hard to read on this monitor.
Systems settings to get desired resolution.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Pa
@rich-ayotte I don't think it's fair to "blame AMD". They suck, but the
question is what does Canonical do about the non-working AMD drivers?
Canonical should detect the fact that the drivers don't work and do one
of 2 things:
1) Postpone the release, or
2) When doing an upgrade - prompt a human
The patch also works for me!
AMD A8-3870 Radeon HD 6550D GPU and kernel 4.2.0-16-lowlatency
--
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 kern
Hi,
>From your XorgConf.txt file: the Driver in use is VESA! How can you ask
for the driver not loaded to boost the Matrox card? It's mga which
should be loaded.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-mga in Ubuntu.
h
Unfortunately I'm experiencing laggy interface with open-source drivers
and about 15-20FPS when Firefox is opened and I'm moving some windows on
the screen. And it's gone away with fglrx :\ My videocard is strong
enough (R9 280X, 3GB GDDR5)
--
You received this bug notification because you are a
Personally I 've been using the open source drivers and I'm surprised of
how good they are. All my games run at the same FPS than catalyst. Plus
they will not break your computer.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in
For me, this has happened twice when typing Control-N within Firefox,
causing Xorg to crash. Both times were days apart, and both had
occurred shortly after a resume from suspend on my MacbookPro10,2. I
can't replicate specific circumstances to trigger this bug today mind
you.
--
You received t
*** This bug is a duplicate of bug 1501468 ***
https://bugs.launchpad.net/bugs/1501468
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Well then hopefully you can get it so this change to modesetting can be
reverted & one isn't forced to get screen to sleep then awake.
My whole point was that this report is claiming that the switch from Intel to
Nvidia fails which is not true is any respect.
It's purely a matter of no visible
Ohh, of course you should sudo dpkg -i *.deb, sorry for my mistake :(
--
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 kernel 4.2
To manage notif
cd /tmp/
apt-get source fglrx-updates
sudo apt-get build-dep fglrx-core
cd fglrx-installer-updates-15.201/
wget -O fix.patch
https://launchpadlibrarian.net/219738583/fglrx-installer-15.201_force-gcc_4.9.patch
patch -p1 < fix.patch
dpkg-buildpackage -us -uc
cd ../
mkdir fglrx-driver
mv *.deb fglrx-
Could someone please write how to apply the patch? Thank you!
--
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 kernel 4.2
To manage notifications
On 24-10-15 18:37:06, Nerdknight wrote:
> The patch in #29 also works for me, with a 6700M card. If you install
> fglrx you must uninstall radeon drivers
>
That is already dealt with by the package. I imagine gpu-manager
disabled fglrx when it failed.
--
You received this bug notification becaus
Issue solved by re installing (in English language this time instead of
French)
--
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/1509697
Title:
Black screen with mouse under 15.10
To manage notif
*** This bug is a duplicate of bug 1493888 ***
https://bugs.launchpad.net/bugs/1493888
The patch also works for me!.
@Paolo, to build the driver do the following:
1. Download fglrx-installer-15.201_force-gcc_4.9.patch
2. Get the sources: apt-get source fglrx
2. cd fglrx-installer-15.201
3. pat
The patch in #29 also works for me, with a 6700M card. If you install
fglrx you must uninstall radeon drivers
--
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 incom
Public bug reported:
Whatver I use gdm or lightgdm and xfce, Unity, gnome, I always get a
blackscreen after login under my user.
Nothing to do then :-(
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: User Name 4.2.0-16.19-generic 4.2.3
Uname: Linux
*** This bug is a duplicate of bug 1493888 ***
https://bugs.launchpad.net/bugs/1493888
@Sergey, How did you build it? Debuild binary doesn't work for me
(Ubuntu 15.10).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubunt
Why you had to blacklist the radeon module?
--
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 kernel 4.2
To manage notifications about this bug go
I was able to successfully apply the patch in #29, and I can confirm it working
on kernel 4.2.0-16-generic, 7950 card.
After applying the patch I manually had to:
1. blacklist the radeon module.
2. execute aticonfig --initial.
3. freeze the installed packages.
--
You received this bug notificati
there is a workaround to this.
install the nvidia-prime package and type
"sudo prime-select intel" this will force the intel GPU.
--
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/
Rich Schneider, have you had a chance to backup your information yet?
To advise, one should be backing up their data, regardless if they
intend to test a kernel or not so in the event of a disaster (ex. HW
failure) they aren't wiped out.
--
You received this bug notification because you are a me
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bumblebee (Ubuntu)
Status: New => Confirmed
--
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.ne
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
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/
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1242572
Title:
xkeyboard-config, console-setup, and ubiquity should use Super+Space
for switching keyboard layout
11) Did a reboot because graphics performance had dropped. Reboot through XFCE
desktop would make the screen go black, pstree showed that the desktop still
lived. reboot command from console would work, but boot into a black screen
(after a brief display of a background and something that might
I'm sorry, John, but bug exists in Ubuntu 15.10 final.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1242572
Title:
xkeyboard-config, console-setup, and ubiquity should use Super+Sp
Thank you Alberto, I know it's not easy trying to get AMD to budge. We
appreciate your efforts, looking forward to being able to use Catalyst
on Ubuntu 15.10 soon :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https
I am going to test the workaround here, and request an SRU for it. I
will also involve AMD to see if we can get an actual fix for it.
--
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/14938
Compiling the fglrx-installer with gcc 4.9 fixed this problem, but it's a
workaround and not the fix. (I guess).
You can get the patch here:
https://launchpadlibrarian.net/219738583/fglrx-installer-15.201_force-gcc_4.9.patch
Don't forget to freeze the fglrx-* packages after installing the fixed d
The "who" command verified to me all my tty consoles are fully
functional, only their displays are blacked out.
--
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/1470862
Title:
W
*** This bug is a duplicate of bug 1493888 ***
https://bugs.launchpad.net/bugs/1493888
** This bug has been marked a duplicate of bug 1493888
FGLRX incompatible with kernel 4.2
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-install
@so1dieroffortune Blame AMD, it's their closed source drivers that don't
work. AMD does not support kernels greater than 3.19 as shown in their
15.9 release notes here http://support.amd.com/en-
us/download/desktop?os=Linux+x86. The 4.0 kernel was released on April
12th, 2015 which is plenty of tim
Public bug reported:
Description:Ubuntu 14.04.3 LTS
Release:14.04
toor@android-a4-b1-e9-d8-8d-83:/$ apt-cache policy ocl-icd-opencl-dev
ocl-icd-opencl-dev:
Installed: (none)
Candidate: 2.1.3-4
Version table:
2.1.3-4 0
500 http://au.archive.ubuntu.com/ubuntu/ trusty/
@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
sanket, please do not mark yourself assigned unless you are going to be
release code very soon (e.g. later today) to fix this problem.
** Changed in: xorg (Ubuntu)
Assignee: sanket (sanketjn210) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu-X,
whic
*** This bug is a duplicate of bug 1501468 ***
https://bugs.launchpad.net/bugs/1501468
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1501468, so is being marked as such.
R270X
none of my installed kernels worked:
4.2.0-16
3.19.0-31
3.16.0-34
purge fglrx has resolved issue for now
--
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 i
*** This bug is a duplicate of bug 1509611 ***
https://bugs.launchpad.net/bugs/1509611
** This bug has been marked a duplicate of bug 1509611
Google Chrome froze
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs
Public bug reported:
This is the full apport data from the crash reported as bug #1507461.
It occurred whilst watching a full-screen Flash video in Google Chrome.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname
*** This bug is a duplicate of bug 1509622 ***
https://bugs.launchpad.net/bugs/1509622
Reproduced the bug and gathered full apport data in bug #1509622.
Marking this a duplicate.
** This bug has been marked a duplicate of bug 1509622
Xorg crash
--
You received this bug notification becau
48 matches
Mail list logo