| Proyecto: | Trisquel |
| Versión: | 6.0 |
| Componente: | Programs |
| Categoría: | informe de fallo |
| Prioridad: | normal |
| Asignado: | No asignado |
| Estado: | closed |
Occasionally, after booting into Trisquel 6.0 gnome-panel will be invisible. Pressing ALT+F1 will cause the Applications Menu to appear above the invisible panel.
The issue never occurred for me in Trisquel 5.5 when I was using Metacity. I am currently using Compiz on Trisquel 6.0 (it uses Compiz by default).
I will try using Metacity and see if the problem occurs at all over the next few weeks.
This issue could be related to the following upstream bug report:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/147943
There are a number of duplicate bug reports that suggest that this issue is still present in recent versions of Ubuntu.
I haven't had this issue since updates came in 1-2 weeks ago (I think). If nobody else is having this issue, I will close this in a few days.
After first boot the gnome-panel was visible. But after installing different software tools (eg. xfe, abiword, gnumeric) the panel was permanently grey (see screenshots) I installed xfce and lxde as workaround.
sg.germany, see http://trisquel.info/en/forum/taskbar-clears-after-updating-60#comment-31868
working links to the attachments are
http://trisquel.info/files/issues/Bildschirmfoto%20vom%202013-03-15%2016:05:54.jpg and http://trisquel.info/files/issues/Bildschirmfoto%20vom%202013-03-15%2016:06:00.jpg
I'm still getting this bug - I got it on startup this morning.
I can't test if it is Compiz-related because of this bug: https://trisquel.info/en/issues/7862
I'm still getting this bug as well...
I never updated this bug report, but a few months ago I tried using Metacity and it fixed the issue.
(I've reverted back to Compiz though, for other reasons.)
Also: I marked #9725: gnome-panel dissapears as a duplicate of this bug.
I can't remember the last time I saw this issue, but it's been a while. According to my dpkg log I got a compiz-gnome update in August. Could that have fixed the issue? Has anyone else experienced this issue recently?
I can't reproduce this bug any more so I am closing it.