https://bugzilla.novell.com/show_bug.cgi?id=659886
https://bugzilla.novell.com/show_bug.cgi?id=659886#c7
--- Comment #7 from Martin Seidler 2010-12-17 13:57:23 UTC ---
I was a bit puzzled my self.
Today I am even more:
I tried the workaround again on my installed system (after I had downgraded all
compiz pagages to the factory-tested versions):
[CODE]
rm ~/.config/compiz/enable-compiz
rm: cannot remove `/home/username/.config/compiz/enable-compiz': No such file
or director:
[/CODE]
So it seems to be a bit more coherent. But I thought my factory tested system
would be nearly the same as a fresh installed Milestone 5. But it took quit a
time to install all the debug-info packages. Maybe I could use them to corner
the problem a bit.
How do I use them for a program that is stared with the log in and does not
crash but is only not quit behaving in the wanted way?
I read http://live.gnome.org/GettingTraces/Details but this seems to appeal
directly only to programs that crash or could forced to crash and I do not
really now how to start gdb and log in GNOME after that (if that is a/the way
to get the information).
http://en.opensuse.org/Report_bugs provides only a red link to
"How to report a GNOME bug" and no specific compiz information.
The page linked from the red link (
http://old-en.opensuse.org/openSUSE:Bugreport_GNOME ) is empty, too.
And I am not quite sure about the page
http://old-en.opensuse.org/GNOME/Submitting_Bugs
"The contents are currently being evaluated " since ;)...28 January 2010 and
last edit really appealing to the content on the 11 November 2008.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.