Hi Bryce,
For GPU lockup bugs with Intel graphics, you need to collect the output
of 'dmesg' and your /sys/kernel/debug/dri/0/i915_error_state file.
The dmesg output is included in the other kernel bug report I mentioned
(bug #1117499). There was nothing relevant shown.
I didn't know to
Version 2:8.960-0ubuntu1.1 of fglrx-installer-updates has been
superseded on January 25 by a different version in precise-proposed. Is
this issue reproducible using the version 2:9.000-0ubuntu0.3
currently in precise-updates?
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided
On Mon, Feb 04, 2013 at 06:38:38PM -, Dave Lentz wrote:
@Steve: is that the Catalyst legacy driver branch or the main one? The
main one won't work with OP's GPU...
I have no idea, but whichever branch it is, it supersedes the version of the
package this bug was reported against; so if it's
Dave, you're right - sorry, I misread the report and thought this was
about the fglrx-installer-updates package rather than the fglrx-
installer one.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
This report shows that you have an unofficial version of the libdrm-
nouveau1a package installed from a ppa. You will need to downgrade to an
official version if this package first, then upgrade the system.
** Changed in: libdrm (Ubuntu)
Status: New = Invalid
--
You received this bug
** Tags removed: regression-update
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1113841
Title:
package libdrm-nouveau2 (not installed) failed to install/upgrade:
intentando sobreescribir
Per Bryce, having the updated versions of the driver packages in
-updates without the updated jockey introduces the possibility of wrong
drivers being presented that will break the system. So since this SRU
has been verified, I'm publishing the new jockey to precise-updates now
even though it's
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
On a ThinkPad E435 running 12.04, I updated to jockey 0.9.7-0ubuntu7.7.
I confirmed that the new version of jockey presents fglrx-experimental-9
and installs the package correctly.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
Hello Maarten, or anyone else affected,
Accepted jockey into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/jockey/0.9.7-0ubuntu7.7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Alberto, or anyone else affected,
Accepted jockey into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/jockey/0.9.7-0ubuntu7.7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
Hello Maarten, or anyone else affected,
Accepted fglrx-installer-updates into precise-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source/fglrx-
installer-updates/2:9.000-0ubuntu0.3 in a few hours, and then in the
-proposed repository.
Please help us by
Hello Alberto, or anyone else affected,
Accepted fglrx-installer-updates into precise-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source/fglrx-
installer-updates/2:9.000-0ubuntu0.3 in a few hours, and then in the
-proposed repository.
Please help us by
** Changed in: oem-priority/precise
Status: New = Fix Committed
** Changed in: oem-priority/precise
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
** Also affects: oem-priority/precise
Importance: Undecided
Status: New
** Changed in: oem-priority/precise
Importance: Undecided = High
** Changed in: oem-priority/precise
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
xserver-xorg 1:7.6+12ubuntu1.12 does not appear to be an official
version of this package for 12.04 (or for any other version of Ubuntu).
It looks like you have unofficial X packages installed locally, not only
of xserver-xorg but also of packages such as xserver-xorg-core, which
don't satisfy the
** Tags removed: regression-update
--
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/1095205
Title:
under scruitiny
To manage notifications about this bug go to:
Public bug reported:
freezes ecery time
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
Public bug reported:
Ubuntu 12.04 hangs once, twice a day.
xdiagnose
Shows error:
pci:00: ACPI_OSC request failed (AE_ERROR), returned control mask : 0x1d
Memory test shows no problem.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu
The fglrx-updates package in the queue addresses the dependencies like
so:
--- fglrx-installer-updates-9.000/debian/substvars 2012-10-16
15:04:48.0 +
+++ fglrx-installer-updates-9.000/debian/substvars 2012-11-21
13:48:00.0 +
@@ -1,2 +1,2 @@
BTW, Alberto, please note that fglrx-installer-updates (and probably
other packages here) is currently blocked from being accepted into
precise-proposed by an existing SRU which is still pending verification
(2:9.000-0ubuntu0.1). If you think this needs to be pushed to -proposed
before the
** Description changed:
- Nvidia and fglrx drivers need to be updated in order to build against
- Linux 3.7
+ [Impact]
+ Nvidia and fglrx drivers need to be updated in order to build against Linux
3.7
+
+ [Test case]
+ 1. Install the latest upstream kernel as described at
Looking at this, I don't think it makes sense for this to be in an SRU.
The justification seems to be that it will make things more convenient
for testing with tools that are not part of Ubuntu. Nothing in the
updated xdiagnose package makes use of this new python module. So this
isn't fixing a
** Changed in: x11proto-dri2 (Ubuntu)
Status: New = Invalid
** Changed in: x11proto-gl (Ubuntu)
Status: New = Invalid
** Changed in: x11proto-randr (Ubuntu)
Status: New = Invalid
** Changed in: x11proto-randr (Ubuntu Precise)
Assignee: (unassigned) = Maarten Lankhorst
Hello Maarten, or anyone else affected,
Accepted x11proto-randr into precise-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/x11proto-
randr/1.4.0+git20120101.is.really.1.4.0-0ubuntu1~precise1 in a few
hours, and then in the -proposed repository.
Hello Maarten, or anyone else affected,
Accepted x11proto-gl into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/x11proto-
gl/1.4.16-1~precise1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Maarten, or anyone else affected,
Accepted x11proto-dri2 into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/x11proto-
dri2/2.8-1~precise1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
This bug makes using a command-line shell from an xterm window extremely
annoying. So annoying that I'm considering switching distributions.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
The attached screen shot shows two views of the same window. The one in
the foreground shows the problems.
How to duplicate the problem.
1. Click on XTERM on the menu bar to open a new xterm window
2. Hold down the Enter key for 20 lines or so. That's what you see: the prompt
disappears and the
*** This bug is a duplicate of bug 1063969 ***
https://bugs.launchpad.net/bugs/1063969
** Package changed: plymouth (Ubuntu) = nvidia-graphics-drivers
(Ubuntu)
** This bug has been marked a duplicate of bug 1063969
NVIDIA does not work with framebuffer drivers
--
You received this bug
** Bug watch removed: freedesktop.org Bugzilla #18049h
https://bugs.freedesktop.org/show_bug.cgi?id=18049h
--
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/347587
Title:
) memory? I have seen a problem
like this in the past with animated xscreensaver patterns left running
for several days - then it seemed like the X server saved the frames in
backing store.
Steve Platt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
** Changed in: xorg (Ubuntu)
Importance: Undecided = Critical
--
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/1076787
Title:
GLX error: Can not get required symbols
To manage notifications
DkmsStatus:
fglrx, 9.000, 3.6.0-030600rc4-generic, x86_64: installed
ndiswrapper, 1.57: added
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
This looks inconsistent. Do you have wrong GL
*** This bug is a duplicate of bug 1063969 ***
https://bugs.launchpad.net/bugs/1063969
In 12.10, graphical boot splash is not supported when using nvidia
drivers, per request of nvidia upstream.
** Package changed: plymouth (Ubuntu) = nvidia-graphics-drivers
(Ubuntu)
** This bug has been
The upstream delta includes the following changes that don't have
referenced bugs in launchpad or test cases:
* Fix race condition in vblank
* Fix prime rendering with kwin
Why are these appropriate to include in SRU without test cases?
** Also affects: xorg-server (Ubuntu Quantal)
I sampled a few call stacks of the slowdown using gdb. It looks like the
system is spending a lot of time in the NVIDIA driver, called from
libpixman-1-0's fetch_and_convert_pixel. I've attached a representative
stack trace from GDB, with pixman debug symbols.
** Attachment added:
Re: comment #2, I sampled the xorg process - not the terminal or unity.
'top' showed that all of the CPU time was being spend in xorg.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
Public bug reported:
As xterm and uxterm are not used directly, but required for ALSA mixer
(IIRC) then it would be best if they didn't appear in the menu, under
System Tools. It does cause a bit of confusion for some users having
three terminal emulators in the menu.
ProblemType: Bug
Worked for me too.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1068165
Title:
package libdrm2 2.4.39-0ubuntu1 failed to install/upgrade: trying to
overwrite shared
Audrey,
It's probably best if you raise a separate bug against xserver-xorg
.-video-ati for this. Although I believe the cause is the same, the
removal of xaa support, The solution for each driver may not be the
same.
--
You received this bug notification because you are a member of Ubuntu-X,
That's to be expected as it's still a Series 315 chip.
The bug is with 315 series (SiS 315/E/PRO, 550, [M]650, 651, 740,
[M]661[FMG]X,[M]741[GX]) chips.
See
https://wiki.ubuntu.com/QuantalQuetzal/ReleaseNotes/CommonInfrastructure
at the bottom for a workaround.
--
You received this bug
Quax, you're correct, I miss-read it as 67.
As for blacklisting, I never tried it myself untill now and it really doesn't
seem to work with video drivers. although a friend seems to have managed with a
different OS.
I just uninstalled xserver-xorg-video-sis, this also removes
*** This bug is a duplicate of bug 1063969 ***
https://bugs.launchpad.net/bugs/1063969
** Package changed: plymouth (Ubuntu) = nvidia-graphics-drivers
(Ubuntu)
** This bug has been marked a duplicate of bug 1063969
No Plymouth Splash on Latitude E6420
--
You received this bug
From the descriptions, bug #1066883 does not look like the same bug.
comment #5 is working for me:
Comment 5:
Try disabling plymouth-splash
sudo mv /etc/init/plymouth-splash.conf /etc/init/plymouth-
splash.conf.disabled
plymouth unconditionally exits before the display manager is launched.
*** This bug is a duplicate of bug 1063969 ***
https://bugs.launchpad.net/bugs/1063969
This is not a bug in plymouth. The package for the nvidia binary
drivers has blacklisted the framebuffers, without which plymouth can't
work.
** Package changed: plymouth (Ubuntu) =
The plymouth splash doesn't display because according to the information
attached to your bug report, it has no framebuffer to display it on.
This is a direct result of a recent change to the nvidia-graphics-
drivers package. Reassigning.
** Package changed: plymouth (Ubuntu) =
This change has been applied in quantal and as a direct result has made
boot splash unusable for all users when the nvidia drivers are installed
(bug #1063969). This is not something that should have been changed
during freeze due to a vague concern that the driver does not interact
well.
--
*** This bug is a duplicate of bug 1063969 ***
https://bugs.launchpad.net/bugs/1063969
** Changed in: plymouth (Ubuntu)
Status: Confirmed = Invalid
** This bug has been marked a duplicate of bug 1063969
No Plymouth Splash on Latitude E6420
--
You received this bug notification
12.10 has been trouble-free for me. I have attempted to duplicate the
exact conditions that would reliably crash 12.04 on my T520, and so far,
the system has resolutely failed to fail :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
This is all I get when I try to get a full backtrace.
sudo gdb /usr/bin/Xorg /etc/X11/core
GNU gdb (GDB) 7.5-ubuntu
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and
Public bug reported:
See attached Xorg.0.log
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic i686
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
Date: Tue Oct 2 22:37:50 2012
** Attachment added: xorg.0.log.seg.fault
https://bugs.launchpad.net/bugs/1060492/+attachment/3366507/+files/xorg.0.log.seg.fault
--
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/1060492
Title:
Removing the 'regression-update' tag, which is for bugs in SRUs.
** Tags removed: regression-update
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1054689
Title:
unusable
Is that a personal opinion
No, this is the whole reason pam-xdg-support was written in the first
place.
Individual applications should not, in general, recommend specific pam
modules.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to weston in
I am not sure what good fallback location is.
Check the behavior of e.g., nautilus or dconf for comparison. I believe
they fall back to something under the user's homedir - that's not
guaranteed to be local, but it's guaranteed to exist and be writable.
--
You received this bug notification
Sorry, I disabled the edgers PPA but forgot I needed to purge it.
I've now got your version installed as you can see.
xserver-xorg-video-trident:
Installed: 1:1.3.6-0ubuntu1.1
Candidate: 1:1.3.6-0ubuntu1.1
Version table:
*** 1:1.3.6-0ubuntu1.1 0
500
Still the same :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-trident in Ubuntu.
https://bugs.launchpad.net/bugs/1044820
Title:
Failed to load module trident (loader failed, 7)
To manage notifications about this bug go
/var/log/Xorg.0.log
** Attachment added: /var/log/Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-trident/+bug/1044820/+attachment/3346353/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
As requested apt-cache policy xserver-xorg-video-trident
** Attachment added: xserver-xorg-video-trident
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-trident/+bug/1044820/+attachment/3346352/+files/trident.txt
--
You received this bug notification because you are a member
Looks like Didier incorporated this patch into his
mesa_9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1 upload,
closing this bug.
Thanks!
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2012-2864
** Changed in: mesa (Ubuntu)
Status: New = Fix Released
--
You
*** This bug is a security vulnerability ***
Public security bug reported:
Mesa allows remote attackers to possibly execute arbitrary code due to a
samplers array overflow in the glsl/linker.
References:
Here is a debdiff to address the issue. Confirmed to build with no
additional compilation warnings on amd64.
** Patch added: mesa_9.0~git20120821.c1114c61-0ubuntu3.debdiff
Do we know that anyone is using the oneiric-proposed X server at all?
Silence is not a very confidence-inspiring metric.
--
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/930936
Title:
Public bug reported:
MGA driver not loading. Section from xorg.log
[45.022] (II) LoadModule: mga
[45.028] (II) Loading /usr/lib/xorg/modules/drivers/mga_drv.so
[45.029] (EE) Failed to load /usr/lib/xorg/modules/drivers/mga_drv.so:
/usr/lib/xorg/modules/drivers/mga_drv.so: undefined
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-mga in Ubuntu.
https://bugs.launchpad.net/bugs/1044797
Title:
Failed to load module mga (loader failed, 7)
To manage notifications about this bug go to:
Public bug reported:
Trident driver not loading on boot
Relevant section from xorg.log:
[ 567.004] (II) LoadModule: trident
[ 567.006] (II) Loading /usr/lib/xorg/modules/drivers/trident_drv.so
[ 567.099] (EE) Failed to load /usr/lib/xorg/modules/drivers/trident_drv.so:
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-trident in Ubuntu.
https://bugs.launchpad.net/bugs/1044820
Title:
Failed to load module trident (loader failed, 7)
To manage notifications about this bug go to:
Works OK in 12.04
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-mga in Ubuntu.
https://bugs.launchpad.net/bugs/1044797
Title:
Failed to load module mga (loader failed, 7)
To manage notifications about this bug go to:
Works OK in 12.04
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-trident in Ubuntu.
https://bugs.launchpad.net/bugs/1044820
Title:
Failed to load module trident (loader failed, 7)
To manage notifications about this bug go
You haven't said anything here about what problem you're experiencing.
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
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/1041360
Title:
I would argue that this doesn't warrant a release note because this is
not a feature that we advertise anywhere as being usable (or if we do,
that's something we should correct!). If users are *lucky*, having an
alternate CD to hand for upgrading the desktop will save them a
CD's-worth of package
Cool, So it works.
Whats the best way of upgrading to these drivers ?
Thanks
On 15 August 2012 15:16, Jbyvosges j_lbar...@yahoo.fr wrote:
Finally!
After 4 months of waiting, it seems that this driver (304.37) works
properly.
Thanks to you.
--
You received this bug notification because
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
Hello nsg, or anyone else affected,
Accepted xserver-xorg-video-intel into precise-proposed. The package
will build now and be available at http://launchpad.net/ubuntu/+source
/xserver-xorg-video-intel/2:2.17.0-1ubuntu4.1 in a few hours, and then
in the -proposed repository.
Please help us by
#434 - Your bug is not this bug. You should create a new bug to describe
your issue, or look for one that already exists, such as bug 989566 or
bug 919815. The endless stream of Me too! from completely unrelated
configurations makes this bug impossible to accurately test and solve,
hence Won't Fix
Public bug reported:
Login screen just flicks on screen then screen goes blank before login
screen flickers back on and of for ever more. Can be a problem getting
to a TTY as well, this seems to be a matter of hitting Alt+Ctrl+Fn at
just the right time.
Hardware: VGA compatible controller:
Attach Xorg log
** Attachment added: Xorg log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1034812/+attachment/3254183/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-sis in
Attach Apport report
** Attachment added: Apport report
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1034812/+attachment/3254184/+files/apport.xserver-xorg-video-sis.2ne9vz.apport
--
You received this bug notification because you are a member of Ubuntu-X,
which is
*** This bug is a duplicate of bug 915265 ***
https://bugs.launchpad.net/bugs/915265
** This bug has been marked a duplicate of bug 915265
[regression] Unity launcher on-screen corruption on resume from suspend with
nVidia proprietary driver
--
You received this bug notification because
Public bug reported:
nvidia-current 304.32-0ubuntu1 is not installable because it Recommends:
a newer version of nvidia-settings than we have in the archive:
Recommends: nvidia-settings (= 304.32) but 302.17-0ubuntu2 is to be
installed
(workaround is to install with 'apt-get install
--
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/1034035
Title:
nvidia-current 304.32 requires newer nvidia-settings
To manage notifications about this bug go to:
** Also affects: fglrx-installer (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: fglrx-installer-updates (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: fglrx-installer-updates (Ubuntu Precise)
Status: New = In Progress
** Changed
Hello Martin, or anyone else affected,
Accepted fglrx-installer-updates into precise-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source/fglrx-
installer-updates/2:8.960-0ubuntu1.1 in a few hours, and then in the
-proposed repository.
Please help us by
Hello Alex, or anyone else affected,
Accepted fglrx-installer-updates into precise-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source/fglrx-
installer-updates/2:8.960-0ubuntu1.1 in a few hours, and then in the
-proposed repository.
Please help us by
Hello Martin, or anyone else affected,
Accepted fglrx-installer into precise-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/fglrx-
installer/2:8.960-0ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Alex, or anyone else affected,
Accepted fglrx-installer into precise-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/fglrx-
installer/2:8.960-0ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Manoj, or anyone else affected,
Accepted xorg-server into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/xorg-
server/2:1.11.4-0ubuntu10.7 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
If every program and service loaded into ram continued working until
they required hd acces [sic] then it is not related to this bug, which
is a hard freeze in which no program continues to function in relation
to the Ivy Bridge video.
--
You received this bug notification because you are a
** Tags removed: regression-update
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1030570
Title:
Radeon HD 6870 temperature is over 60 °C
To manage notifications about this
On 27/07/12 18:12, jondecker76 wrote:
I'm still having autologout problems constantly
[code]
Jul 27 12:55:57 main-desktop kernel: [11597.562389] Xorg[1443]: segfault at
b4f04000 ip b48453fe sp bfb634b0 error 7 in nvidia_drv.so[b4787000+706000]
[/code]
All I can say is try Unity 2D not 3D.
** Package changed: skype (Ubuntu) = xorg (Ubuntu)
** Package changed: xorg (Ubuntu) = xorg-server (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/1014384
Title:
Skype crashes X server
Public bug reported:
Hi,
Pretty randomly, I get display corruption with my Nvidia GeForce GTX560
Ti and the 295 drivers in use in Precise. Logs attached to this report.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nvidia-current 295.40-0ubuntu1
ProcVersionSignature: Ubuntu
--
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/1029765
Title:
Random display corruption with 295
To manage notifications about this bug go to:
This is not a bug. The halt command is not defined to power off the
system. For powering off, you need to call either 'poweroff' or 'halt
-p'.
** Changed in: xorg (Ubuntu)
Status: New = Invalid
** Tags removed: regression-update
--
You received this bug notification because you are a
Public bug reported:
Hello
Afetr a while I am using Firefox, if I quit the application I will not be able
to reopen unless I reboot
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic
501 - 600 of 1216 matches
Mail list logo
