Inkscape color chooser widget's maximum limited to 245 instead of 255

Bug #257685 reported by mahfiaz
60
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
High
Unassigned
inkscape (Mandriva)
Unknown
High
inkscape (Ubuntu)
Fix Released
High
Bryce Harrington

Bug Description

Binary package hint: inkscape

Ubuntu Intrepid, inkscape-0.46-2ubuntu1

This makes hard to get white objects (hex input helps), as RGBA value becomes f5f5f5f5.

It may be related to usa of new GTK+ 2.13 library

Related branches

Revision history for this message
Markus Vuori (lite-deactivatedaccount) wrote :

I'm having the same problem. Makes the application almost totally unusable and needs to be fixed!!

Revision history for this message
mahfiaz (mahfiaz) wrote :

I should have marked this one duplicate, as the following bug report is more descriptive, sorry for drmad.
But the problem really seems to be caused by new GTK+ 2.13, when it happens in 0.46 source-built version (see referred link).

https://bugs.launchpad.net/inkscape/+bug/262681

Revision history for this message
mahfiaz (mahfiaz) wrote :

Marking this as confirmed because of two other confirming comments.

Changed in inkscape:
status: New → Confirmed
Revision history for this message
mahfiaz (mahfiaz) wrote :

Maybe ahead of time, but I reported it to gnome bugzilla:

http://bugzilla.gnome.org/show_bug.cgi?id=549832

Revision history for this message
covox (covox) wrote :

Confirmed. This is ultra irritating as you can't do things like use the colour white from the HSV palette (unless you count "typing the RGBA value in hex every single time" a workaround). The worst side-effect is that every colour you touch is given an alpha value of 245/255, which means going around and editing all the colours back to full opacity by hand.

Revision history for this message
mahfiaz (mahfiaz) wrote :

Copied from gnome bugzilla:

------- Comment #1 from Matthias Clasen 2008-09-04 00:47 UTC -------
GTK+ is simply enforcing documented behaviour now. The fix is to set page_size
to 0 when using adjustments for simple scalar values, such as in a slider.

>From the release notes:

* GtkAdjustment now enforces that values are restricted to the
  range [lower, upper - page_size]. This has always been the documented
  behaviour, and the recommended practice is to set page_size to 0
  when using adjustments for simple scalar values, like in a slider
  or spin button.

Revision history for this message
Oliver Etchebarne (drmad) wrote :

Is there a _easy_ way to correct that GtkAdjustment problem? Perhaps somebody can write a patch? IMHO that seems to be simple to fix.

Revision history for this message
ScislaC (scislac) wrote :

This is a must fix before 0.47 is released.

Changed in inkscape:
importance: Undecided → High
milestone: none → 0.47
status: New → Confirmed
Revision history for this message
ishmal (ishmalius) wrote :

In src/widgets/sp-color-slider.cpp, line 332, this little modification seems to fix the problem:

 if (!adjustment) {
  adjustment = (GtkAdjustment *) gtk_adjustment_new (0.0, 0.0, 1.0, 0.01, 0.0, 0.0);
 }
 //in case of existing adjustment
    gtk_adjustment_set_page_increment(adjustment, 0.0);
    gtk_adjustment_set_page_size(adjustment, 0.0);

Maybe someone with knowledge of the older SP-vintage widgets can decide if this is a valid fix or is merely fixing the symptom.

Posting this to the maillist.

Revision history for this message
ScislaC (scislac) wrote :

Bob committed fix to SVN.

Changed in inkscape:
assignee: nobody → ishmalius
status: Confirmed → Fix Released
status: Confirmed → Fix Released
Revision history for this message
Artem Popov (artfwo) wrote :

Reopening for Ubuntu, this bug is still present in Inkscape 0.46-5ubuntu1 (jaunty)

$ inkscape --version
Inkscape 0.46 (Jan 27 2009)

Changed in inkscape:
status: Fix Released → New
Revision history for this message
Jon A. Cruz (jon-joncruz) wrote :

This is fixed in what will be 0.47, not back in 0.46.

There is a fix in. It is just that a release has not yet been made and pushed downstream

Revision history for this message
Artem Popov (artfwo) wrote :

This is why it's reopened for Ubuntu. The fix is not present in Ubuntu yet. Also, setting status to Confirmed (from Duplicate). As Jaunty has passed the feature freeze, a patch for fixing this particular problem would be most welcome!

Changed in inkscape:
status: New → Confirmed
Revision history for this message
Nate Wiebe (natew) wrote :

is this going to be released for ubuntu soon? or when is 0.47 being released?
this also seems to be happening in every new ubuntu alpha. It happened in hardy, intrepid, and now jaunty [when they were still in alpha stage]. Is there any way that it could be permanently fixed?

Revision history for this message
Timothy Waters (timothy-waters) wrote :

This issue is FINALLY fixed in the current svn. The Ubuntu packages for this work and the problem is not present. They are here:
https://launchpad.net/~towolf/+archive/ppa

Revision history for this message
Bryce Harrington (bryce) wrote :
Revision history for this message
Bryce Harrington (bryce) wrote :

Presumably this is the patch needing to be pulled.

Changed in inkscape (Ubuntu):
assignee: ishmalius → bryceharrington
importance: Undecided → High
status: Confirmed → In Progress
Revision history for this message
Artem Popov (artfwo) wrote :
Revision history for this message
Bryce Harrington (bryce) wrote :

artfwo, could you attach a patch here with what exactly should be pulled for Ubuntu Jaunty?

Revision history for this message
Artem Popov (artfwo) wrote :

Okay, but in this case I will do a deeper examination of what is to be pulled for this bug and produce a patch, but only in the evening.

Revision history for this message
Artem Popov (artfwo) wrote :

It is done.

Attaching the debdiff with cherry picks, which fix both this bug and bug 338196 - they are related in a way, so there is a single patch for both. Needs a sponsor to upload! :)

A test build is available from my PPA as well:
https://launchpad.net/~artfwo/+archive/ppa

Everything works okay here. Inkscape is usable again, yay!

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package inkscape - 0.46-5ubuntu4

---------------
inkscape (0.46-5ubuntu4) jaunty; urgency=low

  * Add 104_gtk_zero_pagesize.dpatch:
    - Cherry pick from 0.47 SVN for the "color value limited to 245" bug
      (LP: #257685)
    - Cherry pick from 0.47 SVN for other GtkAdjustment related warnings
      (LP: #338196)

 -- Aerteieem PEopeove <email address hidden> Wed, 08 Apr 2009 20:04:08 +0700

Changed in inkscape (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Bryce Harrington (bryce) wrote :

Артём, good work; I've sponsored the upload.

Changed in inkscape (Ubuntu):
status: Fix Released → Fix Committed
Revision history for this message
Bryce Harrington (bryce) wrote :

[oops]

Changed in inkscape (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Tim Schofield (tim-scoffer) wrote :

Confirmed now working in Jaunty inkscape 0.46-5ubuntu4

Revision history for this message
Guillermo Espertino (Gez) (gespertino-gmail) wrote :

Tim, it's fixed in SVN. The fix will be included in Inkscape 0.47, which will be released in june.
Meanwhile, you can try a development version (Tobias Wolf has a PPA in launchpad with a recent build for Jaunty).

Revision history for this message
Toon Verstraelen (toon-verstraelen) wrote :

I'm running jaunty with inkscape 0.46-5ubuntu4. The same problem is still present.

Revision history for this message
brtkr (brtkr-deactivatedaccount) wrote :

Right now I've compiled and made a package from 0.47pre2 to RPM.
It has no problem. I compiled and run on Mandriva. If you have time to download and try it, why not?
Check this site:
brtkr[point]extra[point]hu/downloads.php?cat_id=5

Changed in inkscape (Mandriva):
status: Unknown → Confirmed
Changed in inkscape (Mandriva):
importance: Unknown → High
Changed in inkscape (Mandriva):
status: Confirmed → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.