Opacity indicator not initialized correctly (0 instead of 100%)

Bug #1463078 reported by Hachmann on 2015-06-08
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Inkscape
Low
Unassigned

Bug Description

Steps to reproduce:

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 ;) )

Please find additional info in the original question: https://answers.launchpad.net/inkscape/+question/267870

Tags: ui Edit Tag help
Hachmann (marenhachmann) on 2015-06-08
description: updated
su_v (suv-lp) wrote :

Testing in different build and runtime setups on OS X 10.7.5:
- not reproduced with Inkscape 0.48.5, 0.91, 0.91+devel r14194 using
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 using
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 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

Based on related questions found in the irc logs, this could be related to changes in glib >= 2.38 (released in Sept 2013).

Changed in inkscape:
importance: Undecided → Low
status: New → Confirmed
tags: added: ui
su_v (suv-lp) on 2015-12-14
Changed in inkscape:
milestone: none → 0.92
jazzynico (jazzynico) wrote :

Bug reproduced on Xubuntu 16.04, Inkscape 0.91 and lp:inkscape/0.92.x rev. 15059 (gtk2).
Not reproduced with lp:inkscape rev. 15095 (gtk3).

Since the trunk has switched to gtk3, the bug can be considered fixed in Inkscape 0.93.

Changed in inkscape:
milestone: 0.92 → 0.93
status: Confirmed → Fix Committed
prkos (prkos) wrote :

I can still observe this in Inkscape 0.92+devel 15229 on Ubuntu 14.04LTS.

su_v (suv-lp) wrote :

prkos wrote:
> I can still observe this in Inkscape 0.92+devel 15229 on Ubuntu 14.04LTS.

Confirmed with lp:inkscape r15505 on Ubuntu 14.04:
$ apt-cache policy libglib2.0-0 | grep Installed
  Installed: 2.40.2-0ubuntu1
$ apt-cache policy libglibmm-2.4-1c2a | grep Installed
  Installed: 2.39.93-0ubuntu1
$ apt-cache policy libgtk-3-0 | grep Installed
  Installed: 3.10.8-0ubuntu1.6
$ apt-cache policy libgtkmm-3.0-1 | grep Installed
  Installed: 3.10.1-0ubuntu2
$ apt-cache policy libsigc++-2.0-0c2a | grep Installed
  Installed: 2.2.10-0.2ubuntu2

Seems still likely an Inkscape issue related to certain versions of upstream libs or C++ bindings?

Hachmann (marenhachmann) wrote :

FWIW, I also still get it on Ubuntu 16.04 base (0.92.x branch).

libglib2.0-0:
  Installiert: 2.48.2-0ubuntu1

libglibmm-2.4-1v5:
  Installiert: 2.46.3-1

libgtk-3-0:
  Installiert: 3.18.9-1ubuntu3.1

libgtkmm-3.0-1v5:
  Installiert: 3.18.0-1

libsigc++-2.0-0v5:
  Installiert: 2.6.2-1

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers