Inkscape

Opacity indicator not initialized correctly - known bug?

Asked by Hachmann

Hi,

I've never thought of reporting this, because I thought it was so obvious that it *must* already have been reported / noticed.
Now I've finally searched, and couldn't find it, but still think it might be known:

1. Open a new document
2. Use any tool to draw a shape, with a fully opaque fill (as per default tool setting)
3. Check opacity indicator at the bottom left, it's always zero, but only the 'down' arrow is active.
4. Clicking on the down arrow makes the opacity go down to zero, and the indicator starts working as expected

The indicator will also start to show the correct value when the slider in the Fill&Stroke dialog is used.
(0.91, LM 64bit, as always ;) )

Does this need a bug report?

Kind regards,
 Maren

Question information

Language:
English Edit question
Status:
Solved
For:
Inkscape Edit question
Assignee:
No assignee Edit question
Solved by:
su_v
Solved:
Last query:
Last reply:
Revision history for this message
Best su_v (suv-lp) said : 		#1

AFAICT this is not directly an inkscape bug (at least no one directly related to changes in Inkscape's code) - it depends on the versions of certain dependencies (probably gtk2/gtkmm or glib/glibmm) installed on the local system.

Details (on OS X 10.7.5):
- not reproduced with Inkscape 0.48.5, 0.91, 0.91+devel r14194 with these (runtime) deps:
glib2 2.32.4, glibmm 2.32.1, gtk2 2.24.13, gtkmm 2.24.2, libsigcxx2 2.2.10
glib2 2.34.3, glibmm 2.34.1, gtk2 2.24.17, gtkmm 2.24.2, libsigcxx2 2.2.10

- reproduced with Inkscape 0.48.5, 0.91, 0.91+devel r14194 with these (runtime) deps:
glib2 2.44.1, glibmm 2.44.0, gtk2 2.24.28, gtkmm 2.24.4, libsigcxx2 2.4.1

Related:
Experimental GTK3 builds failed to launch with more recent GTK3 versions, and surprisingly (to me) the workaround for that crash also "fixed" the opacity spinbutton in the status bar (for GTK3 builds only):
* Bug #1375085 “GTK3: fails to launch GUI with GTK+ 3.14”
  https://bugs.launchpad.net/inkscape/+bug/1375085

AFAICT no one filed a bug report for Inkscape (with default GTK2) so far - would you mind converting the question into a bug report (use the link 'Create bug report' on the question's page: https://answers.launchpad.net/inkscape/+question/267870 )? I'll gladly confirm the bug report (even if it seems to be triggered by an external lib).

Revision history for this message
su_v (suv-lp) said : 		#2

Possibly related to changes in glib2 >= 2.38 - from old irc logs:
2013-10-10.log:17:16 su_v : ScislaC: just curious: when you launch inkscape (stable or trunk) on Saucy, what's the initial value (insensitive) in the 'Opacity' spinbox, in the status bar?
2013-10-10.log-17:16 su_v : 100 or 0 ?
2013-10-10.log-17:17 * su_v is trying to narrow down a regression seen with local builds (GTK+ 2.24.21, glib 2.38.0 - but could have changed before the latest upgrades)

Revision history for this message
Hachmann (marenhachmann) said : 		#3

Thank you, ~suv!

Just in case this can help:

libglib2.0-0: 2.40.2-0ubuntu1
libglibmm-2.4-1c2a: 2.39.93-0ubuntu1
libgtk2.0-0: 2.24.23-0ubuntu1.2 0
libgtkmm-2.4-1c2a: 1:2.24.4-1ubuntu1
libgtkmm-3.0-1: 3.10.1-0ubuntu2
libsigc++-2.0-0c2a: 2.2.10-0.2ubuntu2

Revision history for this message
Hachmann (marenhachmann) said : 		#4

Thanks ~suv, that solved my question.