Can't turn the "Candy bar" off

what do you call "candy bar"?

> what do you call "candy bar"?

Well, that's how the author of Clearlooks decided to refer to the "animated"
progress bar, as you can see in the gtkrc file :

"progressbarstyle = 0 # 0 = candy bar, 1 = flat"

As you can see, when you have a progress bar (for example when downloading files
from the internet, Synaptic or web browser or whatever), the progress bar is
"animated", there are little "stripes" accross it that make the progress bar
look like it's "moving". A long bar... with many regularly spaced stripes all
accross it... does inded remind one of a "candy bar", hence the name !! :o)))
Problem is that as I said, when I set this option to "1", it is supposed to get
rid of the candy bar and display a "normal"/flat (no animation, and no stripes)
progress bar..... but it doesn't work, candy bar won't go away :-/

I've talked with upstream, this feature is not supposed to work for the moment,
you have to rebuild a package and change this configure option. They will fix
that for the next version though

> I've talked with upstream, this feature is not supposed to work for the moment,
> you have to rebuild a package and change this configure option. They will fix
> that for the next version though

There have been several updates to the clearlooks engine, new features have been
introduced, not to mention the cairo rewrite, but that bug is still there in
Dapper... did upstream give up on fixing it ?

My candy disappeared ! Please give a way to reactivate it. Don't force me to use a dull non-animated theme again for dapper, please! Even on my 7 years old laptop, the theme does look very good and does not lag / hog performances at all !

fancy candy bar is now the default (edgy).

is this still an issue?

Yes, the bug is still there, disabling the candy bar in the gtkrc file doesn't do anything, the candy bar won't go away.

Maybe we should get in touch with upstream about that.

Reassigning.

This bug is being tracked upstream by the software developers as http://bugzilla.gnome.org/show_bug.cgi?id=351943

Do you still get the bug? May you try to reproduce it with Gutsy?

Yes, the bug is still there.
Well, maybe no in fact. That is, in Feisty, I have just had a look at the gtkrc file for the Clearlooks theme, and the option to use or not the Candy bar for progress bars, is not even present anymore !!!
So this means that upstream "solved" the problem by making the candy bar mandatory, a "feature", I guess... arf arf.

This bug clearly isn't going to be investigated, so you can close it if you wish (one less bug in Malone can't be bad ;-), I will unsubscribe from it anyway, I give up....

Do you still get the bug? May you try to reproduce it with Intrepid?

Those annoying moving stripes are still there, and I cannot find an option to turn them off, so I guess the bug still persists.

a new bug needs to be open upstream then, may someone facing this could open it there? thanks.

Thank you for reporting this bug.

Does this occur in Lucid?

hi
I did it for the lucid

folder:
"gtk-engines-2.20.0/engines/clearlooks/src/"

files:
clearlooks_draw.c
clearlooks_draw_glossy.c
clearlooks_draw_gummy.c
clearlooks_draw_inverted.c

comment this block of code:

/* Draw the Strokes */
while (stroke_width > 0 && tile_pos <= width+x_step)
{
 cairo_move_to (cr, stroke_width/2-x_step, 0);
 cairo_line_to (cr, stroke_width-x_step, 0);
 cairo_line_to (cr, stroke_width/2-x_step, height);
 cairo_line_to (cr, -x_step, height);

 cairo_translate (cr, stroke_width, 0);
 tile_pos += stroke_width;
}

go to "gtk-engines-2.20.0/" and build it:
./configure
make

after that go to "gtk-engines-2.20.0/engines/clearlooks/.libs/" and replace "libclearlooks.so" in "/usr/lib/gtk-2.0/2.10.0/engines/" with your new file:
strip libclearlooks.so
sudo cp libclearlooks.so /usr/lib/gtk-2.0/2.10.0/engines/

and restart your gnome session

This is fixed now, if not with Oneiric for you please file a new bug.