Public bug reported:
On my ACER Extensa 5635ZG with NVidia G105M graphics onboard and Ubuntu 12.10
OS there is a problem with nvidia-current driver. It's similar to the problem
described here:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/483857
but I have only
I tried the new 13.2 beta driver from AMD (2:12.100-0ubuntu1) and they work
correctly with the Intel driver from 12.10 repository (2:2.20.9-0ubuntu2)!
I think it is important to verify whether this problem is finally solved by the
new 13.2 beta driver also for other users.
--
You received this
Same issue on Ultrabook: Samsung Series 5 535UC3 A03DE.
--
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/1093788
Title:
X doesn't load after fglrx install
To manage notifications
Please someone with nvidia also test the updated version in precise. The
jockey update got into -updates already, so that part should be ok.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-173 in Ubuntu.
I think the following test should work:
1. Enable precise-proposed, apt-get update
2. Via jockey, install the updated 173 series driver, and check that the
correct version 173.14.36-0ubuntu0.0.1 was installed
3. Reboot, test that it works
4. Update to 12.04.2 stack with sudo apt-get install
As a side note: with the 13.2 beta driver the integrated GPU too works fine
without having to apply the patch for direct rendering.
It must be verified, however, if this is true also for systems where the patch
was never applied.
--
You received this bug notification because you are a member
Addition to 4. above: install also xserver-xorg-lts-quantal
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-173 in Ubuntu.
https://bugs.launchpad.net/bugs/1064192
Title:
[update request] nvidia-173.14.36 adds support
One possible answer to my own question is, that AMD's ATI Catalyst
driver disables the Xorg RandR extension and enables it's own RandR
extention:
from /var/log/Xorg.0.log:
[...]
[68.714] (II) fglrx(0): RandR 1.2 support is enabled!
[68.714] (II) fglrx(0): RandR 1.2 rotation support is
Works for me, too - thank you, Marco!
Haven't checked the intel GPU for now, but for me it was critical to be able to
use the proprietary driver (OpenCL). Finally AMD reacted...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
I don't think this can be a Terminator bug, we aren't doing anything special
when we are maximised. It might be worth checking your terminator preferences
to see what the background setting is - perhaps it's set to be transparent and
that is placing a high burden on your X server?
Seems kinda
*** Bug 32814 has been marked as a duplicate of this bug. ***
--
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/626321
Title:
X.org server should keep track of and restore its initial
*** This bug is a duplicate of bug 1064192 ***
https://bugs.launchpad.net/bugs/1064192
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-settings (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1064192 ***
https://bugs.launchpad.net/bugs/1064192
** Summary changed:
- The quantal version of nvidia-settings didn't support legacy nvidia driver
(173)
+ The quantal version of nvidia-settings doesn't support legacy nvidia driver
(173)
--
You
.The package should really be getting a correlating nvidia-
settings-173 !
nvidia-settings-295.33 should be taken as EOL as the ancient driver is.
see also bug1100994 (associated to here)
It may sound rude, but I've asked for it in the first place, as it is
the common way other distros deal
I can confirm I have not experienced the bug with drm-intel-next after
several days of testing. What's the procedure next? Are the patches
going to be backported to 3.7.x?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel
(In reply to comment #146)
I can confirm I have not experienced the bug with drm-intel-next after
several days of testing. What's the procedure next? Are the patches going to
be backported to 3.7.x?
The band-aid is backported already afaik, the real fix should show up in
the next 3.7.x point
Ah, thanks, great! Now I see that the two patches from Comment #144 and
Comment #145 are included in 3.7.3. So I guess the real fix you're
talking about it the one from Comment #143.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Adding 'acpi_backlight=vendor' to the GRUB_CMDLINE_LINUX_DEFAULT options
in /etc/default/grub (comment #71) also worked for me. 'quiet splash'
and 'pcie_aspm=force' options shouldn't be necessary in this situation
(though 'quiet splash' is added by default). Also, as a general rule,
you should
(In reply to comment #148)
Ah, thanks, great! Now I see that the two patches from Comment #144 and
Comment #145 are included in 3.7.3. So I guess the real fix you're talking
about it the one from Comment #143.
Yep, that's right.
--
You received this bug notification because you are a member
Public bug reported:
After updating the fglrx driver (2:9.000-0ubuntu0.1) in 12.04, xorg
started crashing.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-36.57-generic-pae 3.2.35
Uname: Linux 3.2.0-36-generic-pae i686
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1110512/+attachment/3507597/+files/Xorg.0.log.old
--
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/1110512
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Your bug report is more likely to get attention if it is made in
English, since this is the language understood by the majority of Ubuntu
developers. Additionally, please only mark a bug as security if it
shows
One possible answer to my own question is, that AMD's ATI Catalyst
driver disables the Xorg RandR extension and enables it's own RandR
extention:
from /var/log/Xorg.0.log:
[...]
[68.714] (II) fglrx(0): RandR 1.2 support is enabled!
[68.714] (II) fglrx(0): RandR 1.2 rotation support is
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Bah, ubuntu-bug is not able to find out root-protected crashes, neither
it gives any message that one should look into /var/crashes/. Attached
is the real crash file. I cannot uploaded because of yet another bug
?field.comment=Bah, ubuntu-bug is not able to find out root-protected
crashes, neither
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see
Could you recheck on raring? It seems there have been some touch related
fixes in xorg-server since the quantal xserver release.
--
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/1015183
Been trying to run Unity with the nvidia-current-updates driver
(304.43). Doesn't work!
Hardware:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G72M
[GeForce Go 7400] [10de:01d8] (rev a1)
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Changed in: linux
Status: Unknown = Fix Released
** Changed in: linux
Importance: Unknown = Medium
--
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/657990
Title:
The update-notifier part of this bug is being tracked in LP: #1098235.
** No longer affects: update-notifier (Ubuntu Raring)
** No longer affects: update-notifier (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
Jeff or Greg, can you try 12.10 and see if this is still an issue
(12.04.2 would be good as well).
--
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/877686
Title:
[Latitude
*** This bug is a duplicate of bug 877682 ***
https://bugs.launchpad.net/bugs/877682
Marked as dupe of the Oneiric version of this bug as Natty is dead and
it was fixed in Oneiric.
** This bug has been marked a duplicate of bug 877682
[Latitude E6510 / Thinkpad W510/T510] External Video
It seems related to screen power settings, since it only triggers after
some time of inactivity.
--
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/1110512
Title:
xorg started crashing after driver
resolved by update.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Expired = Invalid
--
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/863459
Title:
Really
Over a year with no action, closing.,
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New = Invalid
--
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/877719
Title:
No one bothered to look at this, system was certified.
** Changed in: xorg-server (Ubuntu)
Status: New = Invalid
--
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/876581
Title:
Public bug reported:
Ubuntu 10.12 inestable se queda congelado
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.6.1-0ubuntu10
[ 6043.229] (EE)
[ 6043.229] (EE) Backtrace:
[ 6043.229] (EE)
[ 6043.229] (EE) Segmentation fault at address 0x0
[ 6043.230]
Fatal server error:
[ 6043.230] Caught signal 11 (Segmentation fault). Server aborting
[ 6043.230]
[ 6043.230] (EE)
Now there's a backtrace!
--
You received
The onboard icon works for me. Got anything else?
** 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/1108861
Title:
xorg core dumped
Please explain the steps to reproduce the crash in further detail.
** Description changed:
X-server crashes while using multiple master cursors with xinput (both
gnome3 and unity).
+
+ #7 OsSigHandler (signo=11, sip=optimized out, unused=optimized out) at
../../os/osinit.c:107
+ No
Was this being run under virtualbox?
** Description changed:
- Xorg crashed with SIGABRT in OsAbort()
+ #4 0x7f4ddcfde3ed in FatalError (f=f@entry=0x7f4ddcfe5d08 Cannot run in
framebuffer mode. Please specify busIDsfor all framebuffer devices\n)
at ../../os/log.c:793
+
** Summary changed:
- Xorg crashed with SIGABRT in memcpy()
+ Xorg crashed with SIGABRT in sna_video_copy_data()
** Description changed:
Xorg crashed with SIGABRT in XvdiPutImage()
+
+ #12 0xb6f43f40 in memcpy (__len=optimized out, __src=0xb3e24000,
__dest=optimized out) at
No. Native install on my T430s.
30 jan 2013 kl. 22:32 skrev Bryce Harrington:
Was this being run under virtualbox?
** Description changed:
- Xorg crashed with SIGABRT in OsAbort()
+ #4 0x7f4ddcfde3ed in FatalError (f=f@entry=0x7f4ddcfe5d08 Cannot run
in framebuffer mode. Please
** Description changed:
To reproduce:
Use ubuntu desktop
Shut laptop lid (screen turns off)
Shortly afterwards I hear the login noise and when I open the lid I've been
logged out
+ I don't have gnome-screensaver installed as I thought it might be part
+ of the problem.
- I don't
blank screen with 13.2 beta for me, but the problem is now elsewhere.
Xorg.log:
[25.961] (II) LoadModule: fglrx
[25.961] (II) Loading
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so
[26.712] (II) Module fglrx: vendor=FireGL - AMD
** Description changed:
Fast-user switching results in a black screen, X crash.
+
+ #8 signal handler called
+ No locals.
+ #9 __memcpy_sse2 () at ../sysdeps/x86_64/multiarch/../memcpy.S:272
+ No locals.
+ #10 0x7f402c498737 in memcpy (__len=7680, __src=optimized out,
** Description changed:
After upgrade to raring and reboot, I'm seeing frequent Freezes in
normal usage of X. The mouse cursor moves but cannot interact with
windows.
ctrl-alt-f1 will work, and I can login there.
Running 'sudo restart lightdm' from the console ends up with multiple
** Summary changed:
- [sandybridge-gt1] False GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001
+ [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001
** Description changed:
- apport showed up for no reason
+ apport showed up because I had a hung system
ProblemType: Crash
Please collect a full backtrace on this crash - see
http://wiki.ubuntu.com/X/Backtracing for guidance.
** Summary changed:
- Xorg crashes when playing a video
+ Xorg crashes when playing an mkv video with SNA
** Description changed:
- chrashes when watching video
+ crashes when watching video
Alright well even if the issue is still happening, we'd need log files
for the 3.8 kernel. I'll close this report out and if it occurs again
hopefully there'll be a new report.
I think IPEHR: 0x0200 may be a generic error code, so it's possible
Brian and Neven are seeing unrelated issues.
This change was made by a bot.
** Changed in: linux (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/bugs/1097315
Title:
Xorg hangs in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
I have the same problem, and yet no solution...
--
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/1108144
Title:
thinkpad w530 quadro k1000m cannot use second monitor
To manage
** Changed in: xdiagnose (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/1101958
Title:
package xdiagnose 3.4.2 failed to install/upgrade:
Public bug reported:
Recently installed 12.10 from both desktop / and alternate. Neither one
had working video support. In 12.04 the support works with
1:2.3.3-1ubuntu1. In 12.10 the version that is not working is
1:2.3.6-0ubuntu. Video doesn't work at all.
The relevant urls are
Seeing the same thing on a fresh install of 12.10 (64-bit) with NVidia
driver, GT240 graphics card.
From Xorg.0.log:
[ 9613.796] (EE) Backtrace:
[ 9613.796] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f4138301b76]
[ 9613.796] (EE) 1: /usr/bin/X (0x7f4138159000+0x1ac9a9) [0x7f41383059a9]
[
Public bug reported:
On my Lenovo IdeaPad Y550 with GeForce GT240M I can't get nvidia
proprietary drivers to work. On kernel 2.6 everything works fine. On 3.x
- it doesn't work. Google says nothing, askubuntu and #ubuntu on irc
says nothing. I don't have an Optimus.
ProblemType: Bug
Public bug reported:
look i have sent yall notice that ubuntu is not working right on my
machine. lots of errors and it preforms rerally slow like super slow .
It is rediculous how long it takes for the keyboard entries to show on
the screen. any ways i dont know much about compouters that is why
[Expired for xserver-xorg-video-nouveau (Ubuntu) because there has been
no activity for 60 days.]
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-video-intel 2:2.20.19-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
Uname: Linux 3.8.0-2-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.8-0ubuntu3
Architecture: amd64
Make sure you have your BIOS set to allocate as much memory (looks like
8MB max) to video as possible. If glxinfo still gives you BadAlloc
(insufficient resources for operation), then consider forcing 16bit
color depth in xorg.conf.
--
You received this bug notification because you are a member
Addition to bug info:
Without a fix, users cannot reliably use a rotated touchscreen.
Without fix users unable to use serveral screens one or more of which
are touchscreens, on systems or drivers which do not support separate
coordinate systems for each physical screen, e.g. ATI FireGL or
*** This bug is a duplicate of bug 1041790 ***
https://bugs.launchpad.net/bugs/1041790
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
64 matches
Mail list logo
