I made a new trusty desktop VM. This issue still exists there also. Setting
back to "Triaged".
It remains unclear to me as to why these were set to "Fix Released".
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to compiz-plugins-main in Ubuntu.
The issue persists. I set status back to triaged. It is not clear to me
why it was set to "Fix Released".
** Changed in: compiz (Ubuntu Xenial)
Status: Fix Released => Triaged
** Changed in: compiz-plugins-main (Ubuntu Xenial)
Status: Fix Released => Triaged
--
You received this
I can still create this issue on two different installations (one is a
VM and one is an actual HP Laptop) of xenial-desktop-amd64.iso of
2015.12.20.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to compiz-plugins-main in Ubuntu.
Matching subscr
> Anyone can provide a valid (and recent) stacktrace for this?
attached is my attempt.
** Attachment added: "Trace file that was asked for."
https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/815996/+attachment/4525035/+files/compiz-hang.txt
--
You received this bug notific
Public bug reported:
Just to separate the variables, use a different "Turn screen off when
inactive for" time and "Lock screen after" time under "Brightness and
Lock" under "System Setting".
Leave the system inactive.
The screen goes blank after the appropriate inactive period.
After the additio
In my case this was a new 14.10 installation from the daily ISO of
2014.09.16. It was todays updates that created this issue, but the last
update I did was September 30th.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matchi
Behavior for me is still identical to what I posted in #10 above.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1292041
Title:
Lockscreen doesn't turn of
This was on our task list spreadsheet since late in the 13.10 cycle, I
think.
For my part of it, I had every intention of getting to it this cycle,
and it could have been done early in the cycle.
Reference:
https://docs.google.com/spreadsheet/ccc?key=0AsSw0cKYcffNdFlFakF5M0VjR002UEVvakVPZGpydHc#g
I use a different screen blank time and lock time. The screen does go
blank at the correct time, but then it come on again at the additional
"lock" time, and stays on thereafter. For me this started a couple of
days ago (~2014.03.12).
--
You received this bug notification because you are a member
With the limited information on this one, I think it is a duplicate of
previously mentioned bug reports, and it is fixed.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchp
Yes, this has fixed my problem for one of my 14.04 Desktop VM running on my
12.04 server host.
I have several other scenarios to check, it'll take me awhile. (I came here
from bug 1282342 , which started 2104.02.17)
--
You received this bug notification because you are a member of DX
Packages,
Stephen: No that is a different problem, or so I think. I have been
updating and testing every day.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1283671
T
It is extremely likely that this bug is a duplicate of bug 1284536 , which mine
( bug 1282342 ) was determined to be.
See also my posting number 4 above.
And yes, this bug is driving me crazy. Everything broke on February 17th.
--
You received this bug notification because you are a member of DX
Have a look at bug 1284536
Mine ( bug 1282342 ) has been determined to be the same.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1283671
Title:
14.04 da
*** This bug is a duplicate of bug 1284536 ***
https://bugs.launchpad.net/bugs/1284536
This time including the entire file, while still a large file it is much
smaller than the last one with the core dump included.
** Attachment added: "This is the one that resulted while filing the previous
** Attachment added: "Another crash report, hopefully with better more useful
information"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1282342/+attachment/3996556/+files/_usr_bin_compiz.1000.crash.002
--
You received this bug notification because you are a member of DX
Packages, whi
Well thanks very much for looking. I actually have several of those files from
about 4 different VM's.
For whatever reason those files do not get generated for every occurrence of
the issue.
Since posting the full file earlier, I have been learning about how to use
apport-retrace (and gdb) to ex
This is the entire file, and I assume contains what you want. Otherwise
just let me know, I'll to anything to help with this.
** Attachment added: "Crash file from VM from daily ISO of yesterday"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1282342/+attachment/3996361/+files/_usr_bin_c
The bug 1283671 is for a 32 bit installation. My 32 bit trusty VM has
this issue also.
I have also tried: One CPU instead of four; Less memory, down to 2
gigabytes; The cirrus video driver instead of vmvga.
--
You received this bug notification because you are a member of DX
Packages, which is s
These are the commands I used to create and install new VM's today:
1.) Using daily iso from 2014.02.15 (works fine)
sudo virt-install -n desk_tt2 -r 8192 --disk
path=/media/newhd/desk_tt2.img,bus=virtio,size=50 -c trusty-desktop-
amd64-20140215.iso --network bridge=br0,model=virtio --video=vmvga
I had the trusty daily iso from 2014.02.15. It installs and runs fine.
I'm saying that this issue was introduced on approximately 2014.02.16 or
2014.02.17
The bug 1283671 referred to above says 2014.02.21, but I think it was a few
days prior.
--
You received this bug notification because you ar
** Attachment added: "all occurances in kern.log files"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1282342/+attachment/3987808/+files/logkern
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions
** Attachment added: "a file from /var/crash with the core dump removed"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1282342/+attachment/3987809/+files/_usr_bin_compiz.1000.crash
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to uni
** Attachment added: "All occurances in syslog files"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1282342/+attachment/3987807/+files/logsys
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: d
Just a screen shot I captured one time.
** Attachment added: "Screen shot of error window"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1282342/+attachment/3987560/+files/compiz_crash.png
--
You received this bug notification because you are a member of DX
Packages, which is subscrib
Public bug reported:
My Ubuntu Desktop 14.04 VM became unusable (unity shell) a few days ago, and
after some significant updates.
Things are fine after I log in and until I try to do something. Then compiz
will crash and my system becomes unusable. I do have sshd running and can
connect via ssh
26 matches
Mail list logo
