I have the same problem on Natty. The root cause seems to be this line:
setting up libgl1-mesa-glx (7.10.2-0ubuntu2.1) ...
update-alternatives: error: alternative link /usr/lib/xorg/extra-modules is
already managed by i386-linux-gnu_gl_conf.
dpkg: error processing libgl1-mesa-glx (--configure):
*** This bug is a duplicate of bug 833841 ***
https://bugs.launchpad.net/bugs/833841
** This bug has been marked a duplicate of bug 833841
libgl1-mesa-glx alternative link
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Update: I'm not using the standard Nvidia driver because I of a bug in
the r8169 driver (see bug 821454). To fix that, I installed kernel 3.0.1
(see comment #3).
After that, I needed the Nvidia driver from xorg edgers (nvidia-
current_285.03-0ubuntu1~edgers~natty1_amd64.deb)
A workaround to fix
Thanks for your (new) report. The old one seems to have been forgotten and
died. The issue here is clear: The monitor is reporting bad data in the EDID.
From the xrandr output you posted in the other report:
1280x1024 (0x3d) 599.5MHz +HSync +VSync *current
which is also seen in your ddcprobe
** Changed in: mesa (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/833841
Title:
libgl1-mesa-glx alternative link
To manage notifications about
This looks very much like you've installed packages from the xorg-edgers
PPA which have been multiarched and then downgraded; that's
(unfortunately) not supported.
Alternatively, you might be mixing versions - the nvidia packages in
xorg-edgers are multiarched, and they won't install with mesa
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) = Chris Halse Rogers (raof)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/833841
Title:
libgl1-mesa-glx alternative link
To manage
status invalid
Your system has a lot of non-standard packages installed, and this has
caused this problem.
In particular the problem is caused because you have a multiarch version
of the nvidia driver installed (which has created the
x86_64-linux-gnu_gl_conf alternative), but the Natty mesa
Yes, exactly, it's not a bug on the driver; I think fglrx does it well just
ignoring the wrong EDID data and forcing the refresh rate he thinks can work.
I marked the old report as a duplicate of this: I did have only this computer
and no secondary pc nor monitor to test this bug, so I had to
I experienced this bug in Natty, but the situation changed in Oneiric. The
desktop now shows corruption after a suspend/resume cycle : the Unity Launcher
and Panel are not pixelated, but the desktop is.
If I open a new window, the window seems to appear behind the pixelated layer.
If I use the
I have this bug on Asus k43sj.
Description:Ubuntu oneiric (development branch)
Release:11.10
nvidia-current:
Installed: 280.13-0ubuntu1
Candidate: 280.13-0ubuntu1
Version table:
*** 280.13-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ oneiric/restricted amd64
** Attachment added: output from xorg edid-decode app
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/835945/+attachment/2329494/+files/edid-decode.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Changed in: pixman (Debian)
Status: Unknown = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to pixman in Ubuntu.
https://bugs.launchpad.net/bugs/756237
Title:
wxRuby crashes with segmentation fault in
** Changed in: xorg-server
Status: In Progress = 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/bugs/137234
Title:
[i945] Second display not enabled with intel
I nave nvidia-current 280.13-natty~ppa1 from Philip Johnsson's PPA and
had the same problem.
The fix was to remove nvidia-current, run updates and install nvidia-
current again.
I did not dare doing it before I read comment #3 here as I did not want
to get stuck without nvidia driver, but it all
Hi Kevin,
Interesting - I've just tried this in an Oneiric vm and it's not done a
straight truncation - it seems to have done a bit of a round though, which
makes me wonder if your original bug is present or not;
dg@kdedev:~$ xrandr --newmode 640x480_75.00 30.75 640 664 728 816 480 483 487
@Lars: as I said, nvidia-96 is a very old legacy driver which is not
expected to work with Unity 3D. You should use unity 2D instead.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-173 in Ubuntu.
Public bug reported:
I believe this might have been post-unhibernate, although I can't be
sure.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
--
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/836713
Title:
[i965gm] GPU lockup
To manage notifications about this bug go to:
** Attachment added: Xorg log file
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/815978/+attachment/2330140/+files/Xorg.0.log
--
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/815978
I can confirm I'm still getting this error on resume from hibernate with a
HD4850
2.6.38-11-generic-pae #48-Ubuntu SMP Fri Jul 29 20:51:21 UTC 2011 i686 i686
i386 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Sorry for the long response time. Below the information you asked for:
dmesg from the relevant timespan:
[13855.540177] usb 6-1: USB disconnect, device number 2
[13856.234508] Monitor-Mwait will be used to enter C-3 state
[13856.239367] thinkpad_acpi: EC reports that Thermal Table has changed
I'm installing 11.04 AMD 64 Desktop on a Satellite A305-S6898, and am
experiencing the same bug. If I specify nomodeset in the boot options in
GRUB, it seems to boot fine.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Public bug reported:
Description:Ubuntu 11.04
Release:11.04
I have Skype 2.2.0.35-0natty1 installed. I tried to close it by right-
clicking on Skype's menu and selecting Exit but then I saw login
screen.
What you expected to happen:
Skype exits
What happened instead:
Login screen
XorgLogOld contains Caught signal 11 (Segmentation fault). Server
aborting
--
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/836794
Title:
Xorg crash
To manage notifications about this bug go to:
For anyone interested, I have found a solution for my Acer Aspire 5100 in
UBUNTU 11.04 (64bit version)
The flashing screen is caused by the kernel modesetting feature (KMS) that
doesn't work good on the ATI radeon xpress 1100 graphic chip, so I disabled
this feature by editing the file
Okay. Here is an update. Currently running: Linux AccessDenied
3.0.0-0300rc7-generic #201107120911 SMP Tue Jul 12 10:15:32 UTC 2011
i686 i686 i386 GNU/Linux
I had a freeze half an hour ago. I ran compiz --replace --display :0,
Segmentation fault occurred like stated in unity.log (unity launches
*** This bug is a duplicate of bug 318325 ***
https://bugs.launchpad.net/bugs/318325
For anyone interested, I have found a solution for my Acer Aspire 5100 in
UBUNTU 11.04 (64bit version)
The flashing screen is caused by the kernel modesetting feature (KMS) that
doesn't work good on the ATI
*** This bug is a duplicate of bug 825177 ***
https://bugs.launchpad.net/bugs/825177
Public bug reported:
I can usually reproduce this bug by waking up my computer from sleep
mode/standby. However, this time the GPU crashed much later after the
computer had been started up from standby.
*** This bug is a duplicate of bug 825177 ***
https://bugs.launchpad.net/bugs/825177
--
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/836817
Title:
[arrandale] False GPU
Ah, cool.
Can you SSH in when this happens and do a `top`? See if it uses up 100%
of CPU, if so, I might have this same issue (freeky).
In the meantime, I'm also pushing this on compiz. Thanks!
** Package changed: xserver-xorg-video-intel (Ubuntu) = compiz (Ubuntu)
** Also affects: compiz
*** This bug is a duplicate of bug 825177 ***
https://bugs.launchpad.net/bugs/825177
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #825177, so is being marked as such. Please
--
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/836794
Title:
Xorg crash
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/836794/+subscriptions
** Changed in: xorg-server (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/835483
Title:
X11 crashes with Signal 11 if xemacs (or other) is
Public bug reported:
Hello, im not sure if its a bug in Ubuntu package, or in original xorg-
xserver source code, or if this even is a bug, but still
Generally no one should face this, but i did.
As an error, i deleted /tmp folder. When i recreated it, i didnt realize
to switch back rights
Like I said its fixed upstream, so naturally it should work correctly with
Oneiric. The refresh rate it correct at 74.8 (really 74.77). This modeline
should give you exactly 75:
640x480x75.00 30.906000 640 664 728 816 480 484 488 505 -HSync +VSync
when the bug is not present.
This bug
** Changed in: xserver-xorg-input-synaptics
Status: Unknown = Confirmed
** Changed in: xserver-xorg-input-synaptics
Importance: Unknown = Low
--
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:
Even though my screen saver settings say to Turn off after: 1 hour, my
screens always go blank after 10 minutes of inactivity. This is
entirely reproducible. I am using the free glx driver with my Radeon HD
4670 card, dual-headed.
ProblemType: Bug
DistroRelease: Ubuntu
--
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/836945
Title:
Screen always goes blank after 10 minutes
To manage notifications about this bug go to:
@Alberto: I think your point would be very valid if the hardware that
was very old too. But in Lucid, I got full 3D effects using the
nvidia-173 driver, in Maverick, I had to downgrade to nvidia-96, and in
Natty, there's seems to be no way to get 3D neither in Ubuntu Classic or
Unity. Maybe I'm
Public bug reported:
I've observed two position bugs running a dual monitor setup under
11.04:
1) libnotify popups appear in the upper right corner of the 2nd monitor, way
out of my area of visual focus.
2) Some apps (Libre Office) pop up their splash screen in a weird spot on the
1st monitor
--
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/836974
Title:
Dual monitor setup causes positioning issues
To manage notifications about this bug go to:
Timo,
Please generate device recordings by following the instructions at
https://wiki.ubuntu.com/Multitouch/Testing/uTouchEvEmu#Debugging. Then
attach the device.record and device.prop file to the bug.
Thanks!
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Closing since this sounds like a usage / installation error.
If you can come up with specific steps to reproduce the problem on a
clean system feel free to reopen the bug with the added clarification.
** Changed in: fglrx-installer (Ubuntu)
Status: Incomplete = New
** Changed in:
Thanks
** Changed in: fglrx-installer (Ubuntu)
Status: Incomplete = Fix Released
--
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/814382
Title:
amdcccle assert failure:
** Description changed:
+ Unpacking dkms (from .../dkms_2.2.0.2-1_all.deb) ...
+ Selecting previously deselected package fglrx.
+ Unpacking fglrx (from .../fglrx_2%3a8.881-0ubuntu1_i386.deb) ...
+ /usr/share/ati/fglrx-uninstall.sh: 32: cannot create
/etc/ati/fglrx-uninstall.log: Directory
** Changed in: fglrx-installer (Ubuntu)
Status: New = Confirmed
--
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/835265
Title:
package fglrx 2:8.881-0ubuntu1 failed to
*** This bug is a duplicate of bug 835265 ***
https://bugs.launchpad.net/bugs/835265
** This bug has been marked a duplicate of bug 835265
package fglrx 2:8.881-0ubuntu1 failed to install/upgrade: cannot create
/etc/ati/fglrx-uninstall.log: Directory nonexistent
--
You received this bug
Looks like a script needs to ensure /etc/ati exists before writing to
it. (Or, race condition?)
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided = High
** Changed in: fglrx-installer (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you
Hi cpatrick,
Thanks for that; sadly the retracer is not giving us any further
information than was originally posted.
Would you be willing to try again and collect a manual full backtrace
using gdb? Directions for doing this are available at
http://wiki.ubuntu.com/X/Backtracing (skip down past
Thanks! It's too late now to include this for oneiric (see bug
#834438). I've added a task to work on this for Ubuntu P, and am
closing the O task as wontfix. Thanks again for the contribution, we'll
look forward to seeing it in once the next development release opens.
** Also affects: libxmu
Thanks! The patch looks good. However, it's too late now to include
this for oneiric:
slangasek bryceh: yes, the patch looks correct to me provided that the
package builds with it applied; bear in mind that this gets entangled with the
freeze however
slangasek (feature freeze)
bryceh
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/798868
Title:
unity very slow to move
Thanks. Looks like the module is building ok, but perhaps isn't
installing where it's supposed to. Assigning to alberto to see what's
going on.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Incomplete = Triaged
** Changed in: nvidia-graphics-drivers (Ubuntu)
Assignee:
I also reported a pretty much duplicate issue with this in #836349 ...
looks like this has been ongoing for a while and is stuck on kernel API
call changes... I was trying to upgrade to Ubuntu's kernel 2.6.38-10
(really need 2.6.39 as that is known to have USB 3.0 **HUB** support
38-10 might have
Postponing this bug to the next release; we have an adequate workaround
for Oneiric, and it's not worth the regression risk to fix these in
-nvidia just yet.
** Also affects: fglrx-installer (Ubuntu Oneiric)
Importance: Low
Assignee: Alberto Milone (albertomilone)
Status: Fix
[I gather xcompmgr actually has nothing to do with this bug; feel free
to reopen with explanation if it does.]
** Changed in: xcompmgr (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xcompmgr in Ubuntu.
[As per Tim's comment, not an X driver issue.]
** Changed in: xf86-input-wacom (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/832189
Title:
Excellent, thanks for following up. Bet it was a kernel bug of some
sort.
** Changed in: xf86-input-wacom (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
** Changed in: xkeyboard-config (Ubuntu)
Status: New = Triaged
** Changed in: xkeyboard-config (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
Can you explain why you filed this against xcompmgr? Are you running a
customized installation using this (non-standard) compositor? Or is it
just filed against xcompmgr in error?
** Changed in: xcompmgr (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because
Hmm, thanks, however neither of that data shows a TV being connected.
Try enabling debug for the kernel drm. Launch 'sudo xdiagnose', it'll
be the first checkbox; then reboot, reproduce the bug, and capture your
full 'dmesg' output and add it as an attachment to this bug report.
This is likely
Hi Barry,
It sounds sort of like gnome-settings-daemon is not capturing the
settings properly, so your system is defaulting to 10 minutes. I notice
this in your dmesg which hints perhaps gsd is dying (coincidentally in
some power module):
[22483.782153] gnome-settings-[2178] trap divide error
Your patience is appreciated. A fix is ready and waiting, but it has
been waiting for review by other developers for about 2 months.
Also note, doing a distribution upgrade to Ubuntu 11.04 or later will
also resolve this bug.
--
You received this bug notification because you are a member of
** Also affects: qt4-x11 (Ubuntu Oneiric)
Importance: Undecided
Status: Confirmed
** Also affects: unity-2d (Ubuntu Oneiric)
Importance: Medium
Assignee: Florian Boucault (fboucault)
Status: Triaged
** Also affects: xserver-xorg-video-cirrus (Ubuntu Oneiric)
Hi Jay,
Sorry you're having trouble, however we no longer provide development
support in the distro for the i845 GPU. I looked at your crash dump
anyway, but it was not clear to me why it was failing; it appears to be
invalid memory being accessed.
Fortunately, upstream still maintains the 8xx
** Description changed:
As of relatively recently in onieric, if I run xterm, my X session ends
abruptly.
tested with gnome-shell's alt+f2 runner as well as running from within a
gnome-terminal command line.
+
+ #0 0x7faac7cf529b in ?? () from /lib/x86_64-linux-gnu/libc.so.6
+ No
Hmm, the code is failing on this line in exa_migration_mixed.c in the
server:
pExaPixmap-sys_ptr = malloc(pExaPixmap-sys_pitch *
pPixmap-drawable.height);
However the backtrace doesn't indicate what the values are for sys_pitch
or
Yeah this is due to the aspect ratio and scaling behavior of the mouse.
This is a known bug.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I'm not able to reproduce this bug on my oneiric box, and unfortunately
the stacktrace that was automatically included lacks most of the
symbols.
Please collect a full backtrace manually using gdb - see
http://wiki.ubuntu.com/X/Backtracing for directions (skip down past all
the apport directions
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed = Triaged
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Hmm, weird, this doesn't occur for me. Are you able to reproduce this
behavior after updating to latest bits?
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Hi Joe,
Are you still reproducing this problem with the latest oneiric bits?
Not sure what might be causing it; I'm thinking this issue should be
forwarded upstream.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because
status invalid
Ok; marking as invalid. We can't prevent PPAs from breaking upgrades :/
** Changed in: mesa (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
74 matches
Mail list logo
