[Expired for compiz (Ubuntu) because there has been no activity for 60
days.]
** Changed in: compiz (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/194638
I no longer have the computer that experienced this issue, and my new
one has tons more video RAM so I can't determine whether this issue
still exists or not. I'll leave it as Incomplete in case someone else is
still experiencing it and can provide the info.
--
You received this bug notification
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
I found solution that works for me.
I deleted whole ~/.config/compiz and ~/.gconf/apps/compiz directories,
and compiz is behaving properly afterwards - no more xv issues.
YMMV.
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
I see this on my AGP 7600GT (256M); as well as stopping video going full
screen, it makes mythtv frontend with the opengl drawing engine
unbelievably slow and cpu hungry (presumably it falls back to software
3d rendering or something). Would this be caused by texture memory
fragmentation or
It happens to me as well, Ubuntu 9.10, nvidia drivers
185.18.36-0ubuntu9.
Mplayer issue can be easily resolved with setting video output to x11,
but tvtime application can't change it's output and it doesn't work.
Also, screensavers are extremely slow with 100% CPU usage.
It makes compiz
It also happens to me. Jaunty with a Nividia 8400GS video card 512MB, 4
gig of system ram and a 1670X1050 resolution. Only does it when I run
emerald.
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received
Hmm, I'm also using Emerald. Maybe this only occurs when using Compiz
_and_ Emerald?
Has anyone seen this when not using Emerald?
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug notification
I'm using gtk-window-decorator..
NVnews topic: http://www.nvnews.net/vbulletin/showthread.php?t=124410
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug notification because you are a member of
I'm using Fedora 11, this is my problem too on my GeForce 7600 GS (256Mb
of RAM). It's not Ubuntu specific.
Current versions:
Xorg 1.6.1.901
Nvidia driver 185.18.14 / 180.51
Kernel 2.6.29.4
Compiz 0.7.8
i686
My previous Fedora 9 _working well_ on the same hardware, there's:
Xorg 1.5.2
Nvidia
Still occurs in Jaunty Jackalope.
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I've seen this as well. It seems to be related to the number of windows
I have open at the time. If I close a few of them the problem goes
away.
This is on Intrepid on a 8Gig 64bit Intel box with a GeForce 7600 GT
(256MB Memory) and 2 1920x1200 monitors running in twinview.
Is there a good way
FYI, I hadn't seen this for a while, but then today it happened a lot
when I was trying to play a 1080p video. So it's probably more likely
with larger video resolutions. Which of course would make sense.
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
I'm having the same problem using Sabayon 32/64 bit.
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have the same problem. My card is a nVidia 660GT with 128MB. I'm using
Ubuntu Hardy and I tried with the Nvidia restricted drivers 169.12,
173.14.12 (envyng) and the latest 177.80 (from the nvidia web).
I can reproduce the problem whenever I want, I think it's related with
the amount of texture
Yay, finally some confirmation. :)
** Changed in: compiz (Ubuntu)
Status: New = Confirmed
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug notification because you are a member of Ubuntu
Happened again today, except this time the bug occurred whenever the
video WASN'T in fullscreen mode. I got backtraces for both Totem and
MPlayer; they are attached. They don't really say much though, basically
just that the program gave a frame to the X server and got back this
error.
At the
** Attachment added: gdb-totem.txt
http://launchpadlibrarian.net/15507382/gdb-totem.txt
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug notification because you are a member of Ubuntu
Bugs,
Please create a backtrace and attach it here as a non-compressed text
file. Instructions are available at
https://wiki.ubuntu.com/DebuggingProgramCrash and
https://wiki.ubuntu.com/Backtrace
Relevant debug package may include xserver-xorg-core-dbgsym, compiz-
core-dbgsym. libx11-6-dbgsym,
This bug is not a crash, it is just an error that makes the program
exit. How can you get a backtrace for that?
** Changed in: compiz (Ubuntu)
Status: Incomplete = New
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
ahh.. my fault for forgetting to mention setting breakpoint. Could you
try to break at exit. Interrupt gdb by ctrl-c and type 'break exit'
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug
Gotcha. I will do this the next time this bug happens. (Could be a while
though.)
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Perhaps related to Bug #216322?
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Seems unlikely to me. The description is very different.
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I take it back, this happened again today. Definitely less common than
it used to be, though. Note that I am using pure up-to-date Hardy now.
** Changed in: compiz (Ubuntu)
Status: Invalid = New
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
I haven't seen this in ages. Changing to Invalid.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug notification because you are a
Anything I can do to help debug this? This is the last bug preventing me
from using Compiz. I'm a computer engineer so you can feel free to ask
me to use gdb and stuff.
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
Yes, this still occurs today, even with the Compiz/X/NVIDIA packages
from Hardy Heron. Attaching logs taken with the Hardy packages and
changing back to New.
These logs were taken with me using SMPlayer and the 'xv' output module.
** Attachment added: .xsession-errors against Hardy packages
** Attachment added: Xorg.0.log against Hardy packages
http://launchpadlibrarian.net/13387119/Xorg.0.log
** Changed in: compiz (Ubuntu)
Status: Incomplete = New
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
Hi Tristan
you report this issue some time ago and hasn't been any activity in a while, i
was wondering if this is still an issue for you with the latest upgrades in
Hardy Heron.
Thanks in advance
** Changed in: compiz (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) =
** Attachment added: lspci-vvnn-output.txt
http://launchpadlibrarian.net/12160796/lspci-vvnn-output.txt
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug notification because you are a member
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/12160784/Xorg.0.log
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug notification because you are a member of Ubuntu
Bugs, which
Oh, I should probably also mentions that I am using TwinView.
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: .xsession-errors
http://launchpadlibrarian.net/12160783/.xsession-errors
--
Compiz gets into a state where going fullscreen in apps causes an X11 BadAlloc
error
https://bugs.launchpad.net/bugs/194638
You received this bug notification because you are a member of Ubuntu
I've now tried changing the Legacy Fullscreen Support and Unredirect
Fullscreen Windows options while experiencing this problem, but that
had no effect. I also checked my memory usage when this happened and it
was only at around 50%. Not sure what else to check.
--
Compiz gets into a state where
35 matches
Mail list logo
