[Expired for Compiz because there has been no activity for 60 days.]
** Changed in: compiz
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/1470097
Title:
Unity do
[Expired for Unity because there has been no activity for 60 days.]
** Changed in: unity
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/1470097
Title:
Unity does
[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/1470097
[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/1470097
T
Ok, so...
I've prepared a SRU for getting these ddebs built, the branch is
building at https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-027/+packages then if you use this PPA
(packages should be ready in few minutes), you should be able to get the
*-dbgsym packages installed (e
ok, will you report when they are available on the debs? then i'll redo
the backtrace with compiz debug symbols.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470097
Title:
Unity does not support c
ddebs are on http://ddebs.ubuntu.com/pool/main/c/compiz/ but it seems
the vivid ones are missing, the infrastructure has sometime issues
(though it got recent improvements) in which case we need no change
uploads to generate new imports...
--
You received this bug notification because you are a m
Oh, that's weird!
Actually these should be in main, but I see no trace either on the
main's Packages or in the pool, so it seems that something weird is
happening on wily. I'll look into that (or maybe seb128 knows more :)).
--
You received this bug notification because you are a member of Ubunt
hmm. sorry. no debug symbols for compiz
1:0.9.12.1+15.04.20150410.1-0ubuntu1 available for vivid.
since recompiling compiz on the affected machine will remove the illegal
instruction i cannot help you on this any further.
--
You received this bug notification because you are a member of Ubuntu
B
sorry, I forgot to look at the pool. none of them is in the ddebs sorted
to dist vivid.
fyi the only compiz debug symbol in the debs is
compizconfig-backend-kconfig-dbgsym
from http://ddebs.ubuntu.com/dists/vivid/universe/binary-amd64/Packages
--
You received this bug notification because you
** Changed in: compiz
Status: New => Incomplete
** Changed in: compiz (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470097
Title:
Unity does not su
The only we need are compiz-core-dbgsym compiz-plugins-default-dbgsym
compiz-gnome-dbgsym libcompizconfig0-dbgsym
They should all be on ddebs repos.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/14700
ok, found and installed the unity-dbgsym and libnux-4.0-0-dbgsym
but that does not change the backtrace, so I assume it's a compiz bug.
I followed https://wiki.ubuntu.com/DebuggingCompiz.
There they say to install compiz-core-dbgsym compiz-plugins-dbgsym
compiz-fusion-plugins-main-dbgsym compiz-
> hmm, I'll try again with installed unity-dbgsym.
Please install dbg symbols also for compiz and nux.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470097
Title:
Unity does not support cpu
>From the added backtrace we get that pextrd is the illegal instruction
and therefore schouldnt be used.
hmm, I'll try again with installed unity-dbgsym.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Thank you for your bug report. The stacktrace lacks symbols though,
could you get one with debug packages. Do you know what instruction is
used and shouldn't?
** Changed in: unity (Ubuntu)
Importance: Undecided => High
** Changed in: unity (Ubuntu)
Status: New => Incomplete
** Changed
** Also affects: compiz
Importance: Undecided
Status: New
** 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 Ubuntu.
https://bugs.launchpad.net/bugs/1470097
Bbacktrace of unity crashing due to illegal instruction.
** Attachment added: "Corresponding unity backtrace"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1470097/+attachment/4422445/+files/unity_backtrace.txt
--
You received this bug notification because you are a member of Ubuntu
B
18 matches
Mail list logo
