Public bug reported:
After updating to the newest version of the fglrx package
(15.201-0ubuntu0.14.04.1) I can no longer log in after a reboot. When I
type a password it takes a couple of seconds to throw me back into the
log in screen. Previous versions worked fine.
Removing fglrx to switch to
I'm in the same situation, with Ubuntu 14.04.3 and fglrx-updates.
Tried the instructions in comment #18 but did not change anything. The
log file is attached. Also tried removing and reinstalling fglrx, to no
effect.
Problems seemingly started when I booted without the GPU (using Intel
iGPU) to
Maybe this is a stupid question, but why is a DKMS failure not
considered fatal enough to prevent the kernel upgrade from taking
place, or at least updating grub?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apt-get also says:
dpkg: dependency problems prevent configuration of fglrx-amdcccle-updates:
fglrx-amdcccle-updates depends on fglrx-updates; however:
Package fglrx-updates is not configured yet.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Contrarily, if you already have fglrx installed, you can install the
14.04.2 LTS enablement stack without complaints... but it will not work
(very well). I got constant crashes.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in
Public bug reported:
With VirtualBox I get a weird-sized screen with corruption when booting
the utopic RC. Switching to Ctrl+Alt+F1 and back to Ctrl+Alt+F7 fixes
the issue. With trusty (and IIRC early utopic alphas) there is no such
issue.
I'm running VirtualBox 4.3.10 with Ubuntu Trusty as the
I no longer have the same hardware. Haven't seen this with new hardware
+ Ubuntu 13.04.
--
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/1013980
Title:
Windows stopped responding to mouse
To
*** This bug is a duplicate of bug 1080514 ***
https://bugs.launchpad.net/bugs/1080514
** This bug has been marked a duplicate of bug 1080514
Click-and-drag in eye of gnome crashes X
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
This is still reproducible with the latest fglrx in saucy –
2:13.101-0ubuntu3.
--
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/1080514
Title:
Click-and-drag in eye of gnome crashes X
** Bug watch added: freedesktop.org Bugzilla #66955
https://bugs.freedesktop.org/show_bug.cgi?id=66955
** Also affects: mesa via
https://bugs.freedesktop.org/show_bug.cgi?id=66955
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
I can confirm this on both Ubuntu 12.10 and 13.04, using both fglrx and
fglrx-updates.
** Changed in: fglrx-installer (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
I've got this in Chromium both dragging images and dragging selected
text. Maybe dup of bug 1080514?
I have a Radeon HD7770 and have seen it both with Ubuntu 12.10 and
13.04, my current fglrx is 2:9.012-0ubuntu1 (fglrx-updates).
An Apport window pops up after relogin, but it's never opened a
I'm seeing this since I changed from AMD HD 4850 with open drivers to
AMD HD 7770 with fglrx.
Syslog says:
Feb 13 22:46:44 HOSTNAME gnome-session[1705]: Gdk-WARNING: gnome-session: Fatal
IO
error 11 (Resource temporarily unavailable) on X server :0.#012
I'm running 12.10, and the non -updates
It happened again immediately after I posted the above. This time a drag
drop cursor (fist with +) was left behind. It stays above everything
else, even if I go Ctrl+Alt+F1.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
I got this again, this time with no part of the screen responding.
Restarting compiz with 'compiz --replace' fixed the issue.
** Description changed:
After logging in to the system after suspend or just a locked screen,
windows sometimes stop responding to mouse commands. At that point I'm
Just a note that
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
RV516 [Radeon X1300/X1550 Series]
also triggers this so it is not specific to R600+ drivers.
For these old GPUs FGLRX is not available so there is no workaround...
--
You received this bug notification
I get similar corruption with open radeon drivers and 4850. White or
grey shapes on top of the check email text and icon and sometimes
other icons. Intermittent.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
** Attachment added: Screenshot - this time by the expand button.
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/752157/+attachment/2074223/+files/unity-corruption.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I have not encountered the problem in Lucid, but the same problems still
happen with my two Karmic installs.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete = Fix Released
--
Display problems on boot
https://bugs.launchpad.net/bugs/507847
You received this bug
I noticed the fd0 error messages in CurrentDmesg.txt and tried turning
floppy support off from my motherboard BIOS. It defaulted to on, even
though I don't have a floppy drive. Now I can boot in 10s and the
messages don't appear.
--
[RV770] Boot hangs for 20s with mouse cursor visible over
Public bug reported:
Binary package hint: xorg
When booting Lucid, the screen first stays black for a while, then I see
the startup screen with Ubuntu logo and the red dots after about 10s
from Grub. However, those dots don't change color like on shutdown and
the mouse cursor is visible (and
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/41843053/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/41843054/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41843055/Dependencies.txt
**
Wall clock shows ~10s from Grub to seeing cursor and ~35s to seeing the
desktop.
** Attachment added: Bootchart
http://launchpadlibrarian.net/41845393/snotra-lucid-20100324-2.png
--
Boot hangs for 20s with mouse cursor visible over startup screen
https://bugs.launchpad.net/bugs/546087
You
Public bug reported:
Binary package hint: xorg
In the past few weeks or so I have had many display related regressions
from how Karmic worked for me in last October-early December.
First, every one boot in 2-3 or so (irregularly) no cursor appears,
though mouse works fine; i.e. I can click
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/37917007/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/37917008/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37917009/Dependencies.txt
**
25 matches
Mail list logo
