Public bug reported:
Binary package hint: linux-image-2.6.27-1-generic
Description:Ubuntu intrepid (development branch)
Release:8.10
After upgrading from linux-image-2.6.26-5-generic to linux-
image-2.6.27-1-generic, the CPUs are running in throttling state T7
(12%). I have both kern
** Attachment added: "Xorg.0.log after crash"
http://launchpadlibrarian.net/21804127/Xorg.0.log.crash
--
Xorg server segfaults in cwGetBackingPicture
https://bugs.launchpad.net/bugs/319402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Attachment added: "xorg.conf used to reproduce the crash"
http://launchpadlibrarian.net/21804177/xorg.conf.crash
--
Xorg server segfaults in cwGetBackingPicture
https://bugs.launchpad.net/bugs/319402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Attachment added: "Output of lspci -vvnn"
http://launchpadlibrarian.net/21804184/lspci.vvnn
--
Xorg server segfaults in cwGetBackingPicture
https://bugs.launchpad.net/bugs/319402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Running Ubuntu 9.10 with kernel 2.6.30? I won't even ask how you got as
far as you did. ;) But here is what I think the problem is:
Looks like the drm kernel module is loaded. See this message in
BootDmesg.txt: "[drm] Initialized drm 1.1.0 20060810". Therefore the
fglrx kernel module fails to load
Public bug reported:
When moving the mouse pointer from screen 1 to screen 2, the pointer is
not disabled on screen 1. It remains visible at its last position on
screen 1 while a second cursor is now moving on screen 2. The same
happens when moving from screen 2 back to screen 1. The mouse pointer
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27179928/Dependencies.txt
** Attachment added: "LsHal.txt"
http://launchpadlibrarian.net/27179929/LsHal.txt
** Attachment added: "LsMod.txt"
http://launchpadlibrarian.net/27179930/LsMod.txt
** Attachment added: "LsPc
** Description changed:
When moving the mouse pointer from screen 1 to screen 2, the pointer is
not disabled on screen 1. It remains visible at its last position on
screen 1 while a second cursor is now moving on screen 2. The same
happens when moving from screen 2 back to screen 1. The mo
It's fixed for me with kernel 2.6.27-7 x86_64 on Compaq 6715b.
--
CPU throttled to 12% with kernel 2.6.27
https://bugs.launchpad.net/bugs/262066
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
This looks like the same problem as described in bug#262066.
--
kernel 2.6.27.x extremely slow (Turion + ATI board)
https://bugs.launchpad.net/bugs/274480
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
Public bug reported:
Description:Ubuntu 8.04.2
Release:8.04
xserver-xorg-core 2:1.4.1~git20080131-1ubuntu9.2
xserver-xorg-core-dbg 2:1.4.1~git20080131-1ubuntu9.2
How to reproduce the crash:
- log in to GNOME session
- make sure compiz is enabled
- open Firefox
- go to http://www.mogu
I downloaded the source and did some more debugging. I found that when
the crash happens pPixmap is NULL. Or in other words
(pWindow)->devPrivates[cwWindowIndex].ptr == NULL. See the debugging
session below. I had to jump through some hoops because the compiler
optimized away some local variables.
Is the fix going to be backported to Ubuntu 8.04 LTS?
--
Xorg server segfaults in cwGetBackingPicture
https://bugs.launchpad.net/bugs/319402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Sounds like the kernel module is not installed or loaded correctly.
Without the kernel module there is no hardware acceleration and the
software fallbacks are currently very slow.
--
slow redraw with fglrx
https://bugs.launchpad.net/bugs/355690
You received this bug notification because you are a
xrandr --output --scale or --transform works fine with Jaunty. The
segfault only happens when I omit the --output parameter. In a way it
makes sense, since --scale and --transform are output-specific. Would be
nice though, if xrandr could print an error message pointing out my
mistake instead of j
Still happens on Karmic with x11-xserver-utils 7.4+2. I ran xrandr
--scale 1x1 which resulted in a segfault.
--
xrandr --scale XxY crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/354715
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Public bug reported:
Binary package hint: evolution
Ubuntu Dapper, evolution 2.6.1-0ubuntu7
Locale: en_CA.UTF-8
When I reply to an email that was sent on e.g. May 24, 2005, evolution
inserts the following header in front of the quoted message:
On Tue, 2005-24-05 at 09:27 -0500, Joe Blow wrote:
Public bug reported:
evolution version 2.6.1-0ubuntu7
I have a mh mailbox that I used before with Breezy without problems.
After upgrading to Dapper I can't create new folders in that mailbox.
Instead I get this error message:
Error while Creating folder `Archiv'.
Store root /home/fkuehlin/Mai
The problem is no longer occurring in this form with the latest version
of the package (gnome-power-manager 2.21.92-0ubuntu1).
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete => Invalid
--
Status icon shows AC power and full battery when logging in while on battery
power
h
I just dist-upgraded to version 2.21.92-0ubuntu1. Now the symptoms are
different. In a way it's misbehaving more consistently, because
unplugging and replugging the AC power doesn't change the situation.
When the AC is plugged in it shows the battery icon without a power cord
and the tooltip says
Me too. Not sure what you mean with blacklisting. ohci_hcd depends on
ssb, so I can't really prevent ssb from being loaded if I want USB to
work. I added this line to /etc/modprobe.d/ndiswrapper to work around
the problem:
install ndiswrapper modprobe -r ohci_hcd ssb; modprobe --ignore-install
ndi
There was a bug in my workaround that resulted in broken USB. I
misspelled the ohci_hcd module name in the last modprobe command.
Replace the install-line I added to /etc/modprobe.d/ndiswrapper with
this one:
install ndiswrapper modprobe -r ohci_hcd ssb; modprobe --ignore-install
ndiswrapper $CMDL
Public bug reported:
System information: HP Compaq 6715b, running latest Hardy as at Feb 25.
gnome-power-manager version 2.21.1-0ubuntu1
If I'm running on battery power when I log into my Gnome session, the
power icon shows that I'm on AC power with a fully charged battery. If I
plug in the AC it
Not sure if I'm seeing the same issue, but after upgrading from
2.6.24-11 to 2.6.24-12 I have no sound and lots of these messages in my
kernel log, affecting virtually every single snd_* module that is loaded
at boot time:
[ 49.921905] snd: Unknown symbol unregister_sound_special
[ 49.922033]
Additionally, the new network configuration applet in Feisty allows you
to specify both a domain name and a search list. The result will be
unexpected and people will end up scratching their head about why their
search list is ignored. But I guess that's a new bug.
I actually did read the man page
I'm seeing the same with Eastern Time here. Even worse, calendar
invitations I receive are off by one hour. For example a meeting that
should have been from 4 to 5 PM was shown as 3 to 4 PM instead.
--
Evolution displays wrong time after new dst
https://launchpad.net/bugs/91637
--
ubuntu-bugs m
The Catalyst Control Center stores its configuration settings in
xorg.conf. If you've used the GNOME monitor applet in the past, it
applies its settings when you log in and overrides any settings stored
in xorg.conf.
Try deleting ~/.config/monitors.xml, log out and log back in. Does that
make sett
@mback: Your xorg.conf specifies the virtual size as 2048x2048. If you
set it to 3200x1200, it should work fine.
I guess this bug can be closed as Invalid.
--
xrandr reports incorrect maximum screen size
https://bugs.launchpad.net/bugs/449867
You received this bug notification because you are a
Radeon X1400 is not supported by current fglrx releases. Fglrx currently
supports Radeon HD 2xxx and later.
--
fglrx on Aspire 5672 (Radeon X1400) server freeze at startup
https://bugs.launchpad.net/bugs/355533
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
The fglrx driver saves all used video memory to system memory before
suspending. When you suspend to disk all that memory also has to be
swapped out to the swap partition. If you have a graphics card with lots
of memory and not a lot of available system memory, the saving of video
memory will cause
Current versions of fglrx don't support Radeon X700 hardware. Only
Radeond HD 2xxx and newer is supported. BTW, the same applied to Ubuntu
9.10 and 9.04.
You should continue using the Radeon driver. Do not install fglrx on
your system.
--
X will not start and crashes after upgrade from Karmic
ht
@icosena: make sure you don't have an old version of libGL laying around
in /usr/lib. In Ubuntu Lucid there should be no /usr/lib/libGL.so*. If
you have any version of libGL left there, try removing it (keep a backup
just in case) and see if the problem goes away.
--
Does not support current Luci
@Peter Cordes: I disagree with your assessment. I believe the kernel-
panic is specific to systems with switchable graphics. Your problem is
more generic and affects a completely different part of the driver. I'd
recommend opening a separate bug for this 64-bit packaging problem.
--
fglrx causes
Public bug reported:
Binary package hint: x11-xserver-utils
The problem was observed on both Karmic and Lucid (current as at March
2, 2010) using both the open-source radeon driver and the proprietary
fglrx driver on different ATI cards (at least RV730 and RV740).
Steps to reproduce (with a 1900
The problem persists with the new Radeon driver PPA. I strongly suspect
that this problem is not driver-specific.
xrandr --output VGA-0 --scale 0.5x0.5 works as expected
xrandr --scale 0.5x0.5 segfaults.
It should report an error message instead of just crashing.
--
xrandr --scale XxY crashed w
I just got this a few minutes after resuming from S4. The screen blanked
for a second and when it came back I saw the tray icon.
--
session active, not inhibited, screen idle message
https://bugs.launchpad.net/bugs/423694
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Thiago,
your hardware is not supported by the fglrx driver. Only R6xx and later
hardware is supported by the current driver version. The problem is that
you're using the radeon driver while fglrx is installed. The fglrx libGL
and libglx is incompatible with the radeon driver. Uninstall fglrx an
@Nils: You're still using the radeon driver, not fglrx. Run "aticonfig
--initial -f" and reboot to activate fglrx.
@Dann: You get this watermark if /etc/ati/signature is not installed
correctly. The fact that /etc/ati/control was missing as well indicates
that something went wrong during driver in
It would be helpful to see an Xorg.0.log file with fglrx active. Both
XorgLog.txt and XorgLogOld.txt attached to this bug are with RADEON
active.
--
fglrx fails to identify attached monitor, displays blank screen
https://bugs.launchpad.net/bugs/560570
You received this bug notification because yo
What you're describing is a feature, not a bug. You configured two
independent desktops.
Use "Multi-display desktop with display(s) X" to set up an extended
desktop that spans both monitors and allows you to drag windows from one
to the other.
--
unable to drag a windows from one monitor to anot
Looks like you're using an old driver version on a new Xserver. You need
the new fgrlx 8.721 or 8.723 packages for fglrx to work on Lucid.
--
fglrx driver fails to load
https://bugs.launchpad.net/bugs/560777
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
The latest Catalyst drivers don't support Lucid yet. But Lucid already
includes a driver version that does work on Lucid. The package name is
fglrx. The control center comes in a separate package fglrx-amdcccle.
You can install them using Synaptics or aptitude or whatever your
favourite package man
The log file just stops half way through the driver initialization.
There's no backtrace. There are two possibilities:
1. the Xserver is still spinning at 100% CPU load in the background
2. the system crashed hard and didn't have a chance to write the complete log
file to the disk
You could try
X700 is not supported by the current fglrx driver. Your Xorg log file
shows that you're actually still using the open-source Radeon driver.
Fglrx replaces libGL.so and libglx.so with incompatible versions, which
is causing your problems. If you uninstall fglrx the Radeon driver
should work without
Looks like normal behaviour to me. The CRT uses a lower resolution, so
you end up with dead space. You can change the resolution on the CRT to
match the vertical size of the DFP.
--
Unusable Area on main screen in 2 screen setup
https://bugs.launchpad.net/bugs/561982
You received this bug notifi
Did you reboot after uninstalling fglrx? I highly recommend you do that.
Either way, this is not a bug in fglrx. I recommend closing this bug.
If your problem persists, report a new bug against the radeon driver and
make sure you include log files generated without fglrx installed.
--
fglrx/glx
This bug was fixed in fglrx-8.723. Please update.
--
Random system freeze
https://bugs.launchpad.net/bugs/560364
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
Ok, let me restate the problem: "Monitors positioned incorrectly and
visual corruption in 2 monitor setup with monitors positioned side by
side"
Your xorg.conf clearly shows that CRT2 should be right of DFP4. But your
screenshot shows the opposite positioning. I'm assuming the original
screenshot
@Proxess: This shouldn't be necessary. The fglrx installation disables
KMS by blacklisting the radeon kernel module.
--
Lucid Lynx 64 bit nightly build hangs on boot
https://bugs.launchpad.net/bugs/552644
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Your Xorg.log file indicates that you're still using the Radeon driver
and DRI is disabled. That's why compiz is not starting. Sounds like
you're using your own session startup script. Try replacing compiz with
metacity, that way you'll at least be able to move your windows around
and get through y
> Felix, all your statements are correct. "xrandr --output CRT2 --left-of DFP4"
> used
> after login to get screen on left side. I can not find place in amdcccle to
> do this move.
You should be able to move the monitors around in CCC-LE by drag-and-
drop to change their relative positions.
--
> The second LCD is an analog TV connected to lower DVI connector with
an adapter.
Can you confirm what kind of display and connector this is? Is it a TV
with SVideo, Composite (1 RCA) or Component video (3 RCA) input? Or is
it an LCD monitor with VGA (15-pin D-Sub connector) input?
--
Unusable
Xorg.0.log from comment #12 shows that fglrx is not installed correctly:
(II) LoadModule: "fglrx"
(WW) Warning, couldn't open module fglrx
(II) UnloadModule: "fglrx"
(EE) Failed to load module "fglrx" (module does not exist, 0)
(EE) No drivers available.
Fatal server error:
no screens found
--
*** This bug is a duplicate of bug 501551 ***
https://bugs.launchpad.net/bugs/501551
According to the attached Xorg.0.log file the user was using the Radeon
driver, not fglrx. But the bug is marked as affecting fglrx-installer.
Whoever has the authority to fix this bug record, please do so.
-
The log file says that the fglrx driver module wasn't found. It should
have been installed in /usr/lib/xorg/extra-
modules/modules/drivers/fglrx_drv.so. If that file doesn't exist,
something went wrong during installation.
--
Lucid Lynx 64 bit nightly build hangs on boot
https://bugs.launchpad.ne
It could be a bug in Compiz too since the corruption only occurs when
compiz is used. If someone reproduces it with fglrx and fails to
reproduce it with radeon with the same set of monitors it would show
that the problem is likely in fglrx. That would require hardware with 3D
support in both fglrx
It's not fixed for me. I also saw bug#360208 which was closed as
Invalid. This one is in "Fix Released". Was there an actual fix or did
the problem just disappear for Daniel?
I got this problem after upgrading from Karmic. If the solution is to
delete my hamster.db, doesn't that mean I loose my en
I got the same problem after upgrading from Karmic to Lucid.
I think crashing like this due to "corrupted" configuration files is not
acceptable. If the solution is to delete the hamster.db, doesn't that
mean I loose all the history stored in the file? That too, is not
acceptable to anyone who was
Public bug reported:
Binary package hint: devicekit-disks
Detection of CD-ROM, DVD-ROM and blank CD-R and DVD-R media is broken
after updating or reinstalling devicekit-disks. I have observed this
problem after two recent updates of devicekit-disks on Karmic. I was
also able to reproduce the prob
** Attachment added: ".etc.fstab.txt"
http://launchpadlibrarian.net/42790474/.etc.fstab.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/42790476/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/42790477/CurrentDmesg.txt
** Attac
Bryce, Alberto clearly stated that he gets the same symptoms when using
NVidia graphics. This is clearly not a bug in fglrx.
--
Mounting a system from LG's HL-DT-ST DVD-ROM GDR-H30N makes Xorg to freeze
https://bugs.launchpad.net/bugs/567967
You received this bug notification because you are a me
@Alberto, Matthew: I don't think it's a problem with the kernel module.
Matthew's lsmod command actually shows that the kernel module is loaded.
The error messages are from the Xorg log. It's the user-space
fglrx_drv.so that can't be found. Maybe Xorg isn't looking in the right
place for some reaso
If this is a problem with the open-source drivers, it shouldn't be
reported against fglrx-installer.
--
Non-proprietary (Ubuntu's default) video driver eventually switches monitor to
a fuzzy mode (ATI/AMD video hardware)
https://bugs.launchpad.net/bugs/568591
You received this bug notification b
You're using Xserver 1.8. Version 1.8 is not supported by the driver
yet.
--
package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: subprocess
installed post-removal script returned error exit status 2
https://bugs.launchpad.net/bugs/568963
You received this bug notification because you are
Check your apt sources. Maybe you're using some non-standard apt
repository that already has Xserver 1.8.
--
package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: subprocess
installed post-removal script returned error exit status 2
https://bugs.launchpad.net/bugs/568963
You received this
Kernel version 2.6.33 is not supported by this driver. There are
unofficial patches floating around to make fglrx compile on kernel
2.6.33 and 2.6.34, if you're feeling adventurous.
--
package fglrx 2:8.723.1-0ubuntu3 failed to install/upgrade: fglrx kernel module
failed to build
https://bugs.la
Your xorg.conf looks like it wasn't generated by aticonfig. Try if
running this as root fixes the problem:
aticonfig --initial -f
--
No login screen at startup
https://bugs.launchpad.net/bugs/577906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Your Xorg.log.auto looks OK. Xorg.log.manu looks incomplete, like the
output of the Xserver on the console it was started from. Either way,
there is no more crash or segault.
The black screen when you start X without any clients connecting to the
Xserver is normal.
As far as I can tell, the Xserv
I don't see anything wrong with the log files. X starts, apparently in
the monitor's native resolution (1920x1080). Then there is a VT switch
and finally it looks like a clean shutdown. No evidence of a crash. What
exactly are the symptoms of the problem you're observing now?
The only unexpected t
Looks like a version mismatch between the kernel module and the user-
space X driver. The kernel module seems to come from Catalyst 10.4, the
user-space driver comes from the fglrx-package included in Ubuntu.
I'd recommend uninstalling all versions of fglrx that you have
installed, make sure that
At this point I see no evidence of a driver bug. Is the problem
reproducible after uninstalling fglrx? If yes, it's definitely not a bug
in fglrx.
--
No login screen at startup
https://bugs.launchpad.net/bugs/577906
You received this bug notification because you are a member of Ubuntu
Bugs, which
@SunnyDrake: When you install the Catalyst driver from amd.com, make
sure you uninstall the fglrx packages included in Ubuntu first.
--
Does not support current Lucid kernel (2.6.32) or xserver (1.7)
https://bugs.launchpad.net/bugs/494699
You received this bug notification because you are a membe
@Bryan Smith:
Uninstall fglrx, install dkms, reinstall fglrx.
# /usr/share/ati/fglrx-uninstall.sh
# apt-get install dkms
# ati-driver-installer-...run
DKMS will automatically rebuild the fglrx kernel module every time the
kernel gets updated. That should solve your problem.
HTH
--
fglrx fails
** Attachment added: "Xorg.0.log after reproducing the issue"
http://launchpadlibrarian.net/40092988/Xorg.0.log
--
Setting mode with xrandr fails after changing panning region
https://bugs.launchpad.net/bugs/531000
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Attachment added: "lspci -vvnn"
http://launchpadlibrarian.net/40092998/lspcivvnn
--
Setting mode with xrandr fails after changing panning region
https://bugs.launchpad.net/bugs/531000
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This system has two monitors and reproduces the problem as described.
Two other systems with only one monitor show slightly different symptoms
after the last xrandr --mode call: the screen freezes or stops updating
while the mouse pointer is still responsive. I can still move windows
around and by
Anyone experiencing this problem on Karmic, check if you're affected by
https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/501715
The "memory leak" occurs after system updates that trigger ureadahead to
reprofile. Rebooting fixes the problem. A workaround is to reboot the
system twice after
I have the same problem. I just discovered some useful keyboard
shortcuts for youtube:
: pause/play
/: skip forward/back
: fullscreen
: leave fullscreen
Hope this helps.
--
Youtube doesn't work on ubuntu 64 bits, prerelease 64 bits version works
https://bugs.launchpad.net/bugs/436126
You receiv
Public bug reported:
Binary package hint: nautilus
Steps to reproduce:
* insert CD into drive
-> CD is detected and nautilus opens a window as expected
* eject CD from the CD desktop icon's context menu
-> CD is ejected as expected
* remove CD from the tray and close CD drive
* Push eject-but
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/32996147/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/32996148/XsessionErrors.txt
** Attachment added: "usr_lib_nautilus.txt"
http://launchpadlibrarian.net/32996149/usr_lib_
Public bug reported:
Binary package hint: human-theme
Human theme in Karmic: in the bottom left and bottom right corners of
windows, there are opaque pixels that make the window corners appear
less rounded and more jagged. A modified screenshot is attached. The top
half shows what I see on the sc
** Attachment added: "human-border.png"
http://launchpadlibrarian.net/33248619/human-border.png
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33248620/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/33248622/XsessionErrors
I have an alternative patch (no PPA, sorry), that replaces the
backfilling of pixmaps with clearing them. Pixmaps with an alpha channel
will be initialized transparent. Pixmaps without an alpha channel will
be initialized black. That replaces temporary corruption observed with
KDE menus with tempor
The patch is against the Xserver source shipped with Karmic's xorg-
server 1.6.3-1ubuntu4. Do not apply the no-backfill patch at the same
time as my backclear patch, they are mutually exclusive.
--
[M76] [ubuntu 9.04] slow unminimizing with ati card and desktop effects enabled
https://bugs.launch
Public bug reported:
Binary package hint: indicator-session
All the entries in the "Set Status" submenu are greyed out. I can't
change the status. The icon of the applet indicated offline status. At
the same time I have Empathy running and my status in Empathy is
"Available".
I have tried removi
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/32333943/Dependencies.txt
--
Can't change status in indicator-applet-session
https://bugs.launchpad.net/bugs/435535
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The fglrx driver version included in current Karmic (8.660) works even
when i915 is loaded. This bug should no longer occur with current
Karmic. Note that the current Catalyst release (9.9 based on 8.65) is
still affected by this problem though.
--
initramfs scripts hard-coded to load i915; block
The XVBA libraries have silently removed the dependency on libstdc++5 in
driver version 8.63. The dependency of the libamdxvba1 package on
libstdc++5 can safely be removed for driver version 8.63 and newer.
--
removal of libstdc++5, please drop dependency in libamdxvba1
https://bugs.launchpad.net
Try this sequence of commands:
sudo apt-get build-dep xorg-server
apt-get source xorg-server
cd xorg-server-1.6.3
patch -p1 < /path/to/xserver-xorg-backclear.patch
debuild
cd ..
sudo dpkg --install xserver-xorg-core*.deb
--
[M76] [ubuntu 9.04] slow unminimizing with ati card and desktop effects
@svaens: Xorg 1.6.0 is fairly close to 1.6.3. You could try applying the
backclear patch to it. I'd say your chances are about 95% that it'll
work.
In my experience the latest drivers don't resolve this issue.
--
[M76] [ubuntu 9.04] slow unminimizing with ati card and desktop effects enabled
htt
I'm seeing the same on two different machines. The problem is
intermittent. Sometimes only one separator is at the bottom, sometimes
both. Sometimes there is only one separator instead of two. Example
screenshot attached.
** Attachment added: "Screenshot"
http://launchpadlibrarian.net/32897059/
I found a few forum threads that seem to be about the same problem but haven't
realized it's caused by ureadahead yet:
http://ubuntuforums.org/showthread.php?p=8641459
http://swiss.ubuntuforums.org/showthread.php?p=8643666
I'm observing the same thing at work (64-bit) and at home (32-bit). Even
w
I can confirm that this problem is no longer occurring.
--
Date format for quoted message header is misleading
https://bugs.launchpad.net/bugs/50390
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
The steps you take to recover your system (dpkg-reconfigure -phigh
xserver-xorg; aticonfig --initial -f) do much more than changing
xorg.conf. I have two possible suspicions.
1: Due to the age of the system I suspect that it's an AGP board,
correct? Maybe the sequence or timing of loading fglrx an
Public bug reported:
driconf doesn't work on Ubuntu 18.04. The reason is that xdriinfo fails
with "Screen 0: not direct rendering capable." There appears to be a fix
for this upstream:
https://cgit.freedesktop.org/xorg/app/xdriinfo/commit/?id=6273d9dacbf165331c21bcda5a8945c8931d87b8
Building my o
Public bug reported:
/var/log/syslog is flooded with messages of this kind (once per second),
making the log grow at a rate of > 4KB/s or about 350MB per day:
Aug 11 15:10:49 Dobby gnome-shell[1725]: message repeated 3 times: [ Object
Gio.Settings (0x559de3638920), has been already deallocated -
Some related info I found online:
Github bug report:
https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/issues/447
Patch linked by the above:
https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/commit/2efb9d1248e719474eab91d92d0905f5d3e1d25c
--
You received this
Public bug reported:
DKMS kernel build against linux-headers-4.4.0-63-generic fails. I see
that /usr/src/linux-headers-4.4.0-63-generic is full of broken symlinks:
$ ls -l /usr/src/linux-headers-4.4.0-63-generic
total 1252
drwxr-xr-x 3 root root4096 Feb 9 10:52 arch
lrwxrwxrwx 1 root root
Please attach /var/log/Xorg.0.log and /var/log/Xorg.0.log.old just after
the Xserver crashed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684171
Title:
[Amarok] docking all three "content" windows
Sorry, I had a typo in my request. I need the output of
ls -l /usr/lib/libGL*
Either way, if you uninstalled fglrx, the problem is gone and no one
else has this problem, I guess this bug report can be closed.
--
python2.6 crashed with SIGSEGV in XF86DRIQueryExtension()
https://bugs.launchpad.ne
1 - 100 of 180 matches
Mail list logo
