** Information type changed from Private to Public
--
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/1249551
Title:
Xorg crashed with SIGABRT in RRSetChanged() with nvidia-prime
I've a very similar stack trace in #1249551 on Trusty, after enabling
nvidia-prime.
--
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/1161797
Title:
Xorg crashed with SIGABRT in
Doing the same thing like Goalie Fight wrote (#46). My system is now
running without freezing. At the first login, something crashed. I think
it was compiz or X? I don't know anymore.
nouveau was not installed in my fresh Ubuntu 13.10 system. Should this
package be in a fresh installed system?
I
Okay, I'm working under the assumption that this is a HDMI handshake
issue. I was looking for solutions to this and I found this wiki...
It talks about manually specifying the path to a raw EDID dump file from
my TV. I got as far as adding the debug line in my xorg.conf file and I
can see the
I confirm this too, though I'm gentoo user. Hope this info will be of some use:
Samsung 900X4c, kernel 3.11.6, xf86-input-evdev-2.8.2,
xf86-input-synaptics-1.7.1
Behaviour: Internal keyboard and touchpad freeze after random period of use,
external (usb) keyboard and mouse work fine. I suppose
AnGus, could you please confirm this issue exists with the latest
development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
please just make a comment to this.
** This bug is no longer a duplicate of bug 1103164
062a:0201
As was to expect this bug still exists in 13.10. Please continue to
ignore it.
--
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/772873
Title:
Vino does not work with compositing
To
Hi,
I'm looking for the bug, because I have the same symptoms in my PC (not
MacBook).
I have found this other bug
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1200962
with very similar symptons, in other platforms.
It seems common points in XOrg server and nvidia.
--
You received
Oops, so gcc is broken here after all, look at this..
3860 nouveau_pushbuf_reloc:
3860: 53 push %rbx
3861: 48 8b 5f 30 mov0x30(%rdi),%rbx
3865: 48 8d 43 04 lea0x4(%rbx),%rax
3869: 48 89 47
Well, pedantically gcc-4.7 behavior is this:
u32 *ptr = push-cur;
*ptr = func();
push-cur++;
But since func only reads push-cur it's the same.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
Compiled code with this patch:
15b0 nouveau_pushbuf_reloc:
15b0: 55 push %rbp
15b1: 48 8b 6f 30 mov0x30(%rdi),%rbp
15b5: 53 push %rbx
15b6: 48 89 fbmov%rdi,%rbx
So, we have nv34, nv43 and nv44 affected by this. I updated the
bugreport title so hopefully more people will stumble on it earlier
(hope that is okay).
- nv44: GCC thread: During normal operation.
- nv43: Resuming from suspend-to-mem
- nv34: Resuming from suspend-to-disk
--
You received this
Wow this is definitely a weird interesting bug.
It affects suspend-to-mem on my pci-e nv43 too.
after resume from suspend to memory
[ 40.107810] nouveau E[ PGRAPH][:01:00.0] ERROR nsource: DATA_ERROR
nstatus: BAD_ARGUMENT
[ 40.108059] nouveau E[ PGRAPH][:01:00.0] ch 3 [0x000f7000
while gcc-4.7 evaluates it as:
void
nouveau_pushbuf_reloc(struct nouveau_pushbuf *push, struct nouveau_bo *bo,
uint32_t data, uint32_t flags, uint32_t vor, uint32_t tor)
{
*push-cur = pushbuf_krel(push, bo, data, flags, vor, tor);
push-cur++;
}
--
You
Because the function also increments the push-cur pointer, it's a
subtle but real difference:
gcc-4.7:
u32 ret = func(); // May change push-cur ptr
*push-cur = ret;
push-cur++;
gcc-4.8:
u32 *ptr = push-cur;
push-cur++;
*ptr = func(); // Already sees the push-cur ptr
I'm not a language
http://cgit.freedesktop.org/mesa/drm/commit/?id=482abbfafb56cbceaf5355c026434e638cddd0f1
--
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/1247607
Title:
Libdrm compiled with gcc 4.8 makes card
Created attachment 88817
hack to force defined behavior
As I feared, recompiling only pushbuf.c with gcc-4.7 fixes this bug. So
something in pushbuf.c is miscompiled. Unfortunately it's also the
biggest abuser of post increment ops.
A simple workaround seems to be this patch.
--
You received
I am pretty sure the order of execution is considered undefined behavior
here in C, thus the nouveau code is wrong (it is a side effect). Check
out chapter 2.12 in The C Programming Language if you have it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Changed in: nouveau
Status: Confirmed = Fix Released
--
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/1247607
Title:
Libdrm compiled with gcc 4.8 makes card hang on resume from s2disk
Public bug reported:
Transitions and other graphics do not flow smoothly on my AMD RS880 chipset, I
also experience the same thing with other AMD chipsets as well. I have tried
everything from installing the official graphics drivers, which made things
worse, to installing Compiz which wasn't
** Changed in: fglrx-installer (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: fglrx-installer (Ubuntu Quantal)
Status: Confirmed = Fix Released
** Changed in: fglrx-installer (Ubuntu Raring)
Status: Confirmed = Fix Released
** Changed in: ubuntu-release-upgrader
I guess this is a duplicate of bug #1066464.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-sis in Ubuntu.
https://bugs.launchpad.net/bugs/1072148
Title:
Segfault on SiS 65x/M650/740 card when acceleration is on
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-sis-lts-raring (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
Public bug reported:
Mathematica 9, on 13.10 with Gnome3, crashes X when launched (blanks
screen; returns to login), whether or not -mesa or -opengl is provided.
Mathematica 9 was working in 13.04 and started doing this right after
upgrade to 13.10 (and Mathematica not changed)
Xorg logs show
I can confirm with problem with an ASUS Degatto and Ubuntu 13.10. The
mediahacks driver solves the crash. It seems there are still very small
graphical glitches from time to time though.
The chip in my case is: SiS650 revision ID 90 (M650 A1 AA)
--
You received this bug notification because you
** Bug watch added: Debian Bug tracker #729200
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729200
** Also affects: xserver-xorg-input-synaptics (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729200
Importance: Unknown
Status: Unknown
--
You received this bug
I'm hitting this bug, and I can't get any of the workarounds to work.
I'm on Kubuntu Saucy, and I've tried fglrx, fglrx-updates, fglrx from
x-edgers (https://launchpad.net/~xorg-
edgers/+archive/ppa?field.series_filter=saucy), and three versions of
the AMD binary driver (13.4, 13.9, and 13.11
Public bug reported:
error
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu6
Uname: Linux 3.12.0-031200-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.12.6-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for
28 matches
Mail list logo
