gimp does not works with xscanimage anymore

Bug #157002 reported by Marco Ciampa
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gimp (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

xscanimage is working properly if launched stand-alone. With gimp (2.4.0-rc3) the xscanimage plug-in is detected (you can see the icon in the menu) but disabled.

Workaround: use xscanimage alone or install xsane.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Intrepid Ibex. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Changed in gimp:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gimp:
status: Incomplete → Invalid
Revision history for this message
sharmaine (sharmainequijada) wrote :

Xscanimage drop down dialog "Device dialog" is disabled thus, we cannot use xscanimage in gimp 2.6.6.
Not reproducible in gimp 2.4.5

Changed in gimp (Ubuntu):
status: Invalid → New
Revision history for this message
Ted (tedks) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Lucid Lynx. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

Changed in gimp (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gimp (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
clou (thorsten-becker) wrote :

The bug can be reproduced in Lucid Lynx beta 2 Live CD:

- Start the live CD
- enable universe Sources
- install "sane"
- open The Gimp
- Click on "Create" -> "xscanimage"

Expected behaviour: clicking on "Device dialog" starts xscanimage

Experienced behaviour: "Device dialog" is greyed out and disabled. xscanimage cannot be started from within gimp.

Changed in gimp (Ubuntu):
status: Invalid → New
Revision history for this message
clou (thorsten-becker) wrote :

The result of the following...:

user@ubuntu:~$ xscanimage -gimp
xscanimage: GIMP support missing.

...hints that xscanimage was compiled without gimp support.

Revision history for this message
youch (fchaillou) wrote :

Perhaps this could help :
- when you start gimp and directly select create -> xscanimage, the menu is grey
- if you create a new image and then select create -> xscanimage, the menu is accessible and yaou can scan an image.

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. The package your reporting is updated and the issue should be reproducible with the live environment of the Desktop CD development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

Revision history for this message
clou (thorsten-becker) wrote :

The issue can be reproduced with Mav. Meerkat beta live system:

-Start up live CD
-install sane
-open gimp
-"File" -> "create" -> "xscanimage" -> "Device dialog..." is still greyed out.

Opening a terminal and opening
xscanimage -gimp results in:

ubuntu@ubuntu:~$ xscanimage -gimp
xscanimage: GIMP support missing.
ubuntu@ubuntu:~$

Thanks for your work on this!

Revision history for this message
clou (thorsten-becker) wrote :

In Natty this error can be reproduced, still "xscanimage -gimp" says "GIMP support missing"

Revision history for this message
Bernd Porr (berndporr) wrote :

I can also confirm this for ubuntu LTS (lucid). Very annoying because it worked brilliantly on a 7 year old debian distro...

Revision history for this message
Bernd Porr (berndporr) wrote :

there is a simple fix:
Start GIMP. Create a new empty image and then click on create.

Changed in gimp (Ubuntu):
status: New → Confirmed
Revision history for this message
Saverio (saveriolibrary) wrote :

Hi Guys,

The problem is still there, and the workaround is to create an empty file first, then the menu entries for xscanimage will not be greyed out anymore.

This is probably a UI fix, always reproducible. It has been open 7 years now.

How can we get this moving again?

Thanks,
 Saverio

> GNU Image Manipulation Program version 2.8.10
> DISTRIB_DESCRIPTION="Ubuntu 14.04 LTS"

Revision history for this message
Gilles Schintgen (shigi) wrote :

@Saverio: thanks for the workaround! It really seems to be a minor UI fix.

Revision history for this message
Michael Schumacher (schumaml) wrote :

This should be filed as a bug in xcsanimage - most likely issue: they have to register their plug-in as being able to work without an image (more precisely, without a specific image type).

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.