** Changed in: unity
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740972
Title:
running compiz in Xephyr kills compiz
To manage notifications about this bug go
[Expired for unity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: unity (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/740972
Ti
[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/740972
actually i don't get any crash. can you start unity with unity
--advanced-debug from tty1 to start it in gdb, and then run xephyr so it
crashes unity on :0, can you provide the trace?
** Changed in: unity (Ubuntu)
Status: New => Incomplete
** Changed in: compiz (Ubuntu)
Status: New
** Changed in: unity
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740972
Title:
running compiz in Xephyr kills compiz
--
ubuntu-bugs mailing list
ubuntu-bugs@list
I'm personally not aware what portion of compiz or unity failed. i would
suggest you try to reproduce the bug and see for yourself. To give you some
bit of information, I did:
$ Xephyr :8
$ ps axww | sort > /tmp/out.1
$ DISPLAY=:8 compiz
$ ps axww | sort > /tmp/out.2
$ diff /tmp/out.1 /tmp/out.
apport information
** Tags added: apport-collected ubuntu unity-2d
** Description changed:
Binary package hint: unity
I was using Xephyr and caused my external-to-xephyr compiz-decorator to
crash. This is 100% reproducible
1.) log into unity deskop
2.) run: Xephyr :8 &
3.) ru
** Changed in: compiz (Ubuntu)
Status: New => Incomplete
** Changed in: unity (Ubuntu)
Importance: Undecided => Low
** Changed in: unity
Importance: Undecided => Low
** Changed in: compiz (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you ar
** Changed in: unity
Status: New => Incomplete
** Changed in: unity (Ubuntu)
Status: New => Incomplete
** Also affects: compiz (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
does it make the decorator crash or compiz crash? if that's only the
decorator the title is misleading and that seems similar to bug #730495
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740972
Title:
If you try to run compiz on DISPLAY=:0 while one is already running, it gives a
message like:
$ compiz
compiz (core) - Error: Screen 0 on display ":0" already has a window manager;
try using the --replace option to replace the current window manager.
That makes sense.
However, if you launch Xep
This bug is (at least for me) trivial to recreate. Have you tried ?
I quickly tried to get a backtrace, but didn't get one. It seems that
the compiz process doesn't crash.
Basically, there are 2 compiz process in play, one with DISPLAY=:0,
then, later, one with DISPLAY=:8.
The second one makes
12 matches
Mail list logo
