This could be a software forum issue, but given that I had it working for a time, then upgraded to Mandriva 2008, I think this is the appropriate forum.

The issue is simply trying to use my Epson 4990 with Mandriva 2008, and for that matter, 2007.1 I had things working ok on the preview copy of VueScan, then I tried to install VirtualBox, ended that review with an uninstall, and then I could no longer boot VueScan. I upgraded with 2008 hoping to solve the problem: I download the .tgz file, extract it fine, and then I double-click or Open File on the x-executable file. Rather that opening, nothing happens. I've also tried using the system monitor to see if VueScan is being opened - nothing. I am perplexed. I've tried uninstalling/installing VueScan with no luck. Are there system logs or files I could be reading to find out what is happening when I try to run the program?

Thanks for your help.

Dell GX-260

Starting the program via the konsole should give an output of the startup process.

I've tried to start VueScan in the console, but I get a command not found error. I try VueScan and vuescan - no luck.

Right-click the icon, select edit menu item, now have a look at where the executable is located in the command box.

VueScan is located in a folder on my desktop. In case I am misunderstanding, when I right click on the icon I get the options: Open; Open with other application; Cut; Copy; Make Link; Rename; Move to Trash; Create Archive; Properties.

Assuming you mean Properties, I go here and get the location as: /Desktop/VueScan

It is Type: executable
MIME type: application/x-executable

The permissions show me with read/write access

I have tried changing directories (cd/) in the console to find the /VueScan directory, and then launching from there - but no luck on the launch.

I do not know what is the command box.

I hope I have been clear - thank-you very much for helping.

I'm sorry, I misunderstood what you were trying to do.

Ok, go into the VueScan folder, right click the vuescan file then left click on properties, now go to permissions and check you have a tick mark in the Is Executable, if you don't then click on the box to put one there then press ok.

Now while you are still in the VueScan folder press F4 this will open a konsole session where you are.

Now type this: ./vuescan and press enter, the program should now start up.

Ok, finally I think we're getting somewhere. The F4 trick didn't open a console, so I just opened it myself, navigated to the folder and ran ./vuescan, this is what I received:

./vuescan: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

Does this mean there is a C++ library that I don't have?

Yes, just add the libstdc++5 package using your package manager or from commandline with: urpmi libstdc++5. When using the commandline installation option, if other files need to be installed, choose y.

Ok, so I can urpmi the file, but then I get the following message. I have yet to answer yes, but I'm curious in that this error message pops up from time to time - what could be the consequences of saying yes, and how do I know when to say no?

The following package has bad signature:
/var/cache/urpmi/rpms/libstdc++5-3.3.6-3mdk.i586.rpm: Invalid Key ID (OK (DSA/SHA1, Wed 28 Mar 2007 01:12:03 PM PDT, Key ID e7898ae070771ff3))

This is the reason why you are seeing that message: Source: http://mandrivausers.org/index.php?showtopic=43713

You can continue to add the package (ignoring the warning) or if installing a package with invalid key warnings causes you concern, you need to remove, then re-add your repositories first before continuing.

Great! That worked (kind of, see below), and I can now run VueScan (haven't fully tested it out yet), but here are the errors I received, should I be concerned?

The following package has bad signature:
/var/cache/urpmi/rpms/libstdc++5-3.3.6-3mdk.i586.rpm: Invalid Key ID (OK (DSA/SHA1, Wed 28 Mar 2007 01:12:03 PM PDT, Key ID e7898ae070771ff3))
Do you want to continue installation ? (y/N) y
installing libstdc++5-3.3.6-3mdk.i586.rpm from /var/cache/urpmi/rpms
Preparing... #############################################
1/1: libstdc++5 #############################################
rpmdb: Page 2: overflow refcount 1, referenced 0 times
rpmdb: Page 5: overflow refcount 1, referenced 0 times
rpmdb: Page 11: overflow refcount 1, referenced 0 times
rpmdb: Page 13: overflow refcount 1, referenced 0 times
rpmdb: Page 15: overflow refcount 1, referenced 0 times
rpmdb: Page 17: overflow refcount 1, referenced 0 times
rpmdb: Page 18: overflow refcount 1, referenced 0 times
rpmdb: Page 19: overflow refcount 1, referenced 0 times
rpmdb: Page 20: overflow refcount 1, referenced 0 times
rpmdb: Page 21: overflow refcount 1, referenced 0 times
rpmdb: Page 24: overflow refcount 1, referenced 0 times
rpmdb: Page 30: overflow refcount 1, referenced 0 times
rpmdb: Page 31: overflow refcount 1, referenced 0 times
rpmdb: Page 32: overflow refcount 1, referenced 0 times
rpmdb: Page 34: overflow refcount 1, referenced 0 times
rpmdb: Page 38: overflow refcount 1, referenced 0 times
rpmdb: Page 39: overflow refcount 1, referenced 0 times
rpmdb: Page 40: overflow refcount 1, referenced 0 times
rpmdb: Page 44: overflow refcount 1, referenced 0 times
rpmdb: Page 52: overflow refcount 1, referenced 0 times
rpmdb: Page 57: overflow refcount 1, referenced 0 times
rpmdb: Page 60: overflow refcount 1, referenced 0 times
rpmdb: Page 65: overflow refcount 1, referenced 0 times
rpmdb: Page 66: overflow refcount 1, referenced 0 times
rpmdb: Page 67: overflow refcount 1, referenced 0 times
rpmdb: Page 70: overflow refcount 1, referenced 0 times
rpmdb: Page 71: overflow refcount 1, referenced 0 times
rpmdb: Page 72: overflow refcount 1, referenced 0 times
rpmdb: Page 77: unreferenced page
rpmdb: Page 77: totally zeroed page
rpmdb: Page 78: overflow refcount 1, referenced 0 times
rpmdb: Page 81: unreferenced page
rpmdb: Page 81: totally zeroed page
rpmdb: Page 83: overflow refcount 1, referenced 0 times
rpmdb: Page 92: overflow refcount 1, referenced 0 times
rpmdb: Page 93: overflow refcount 1, referenced 0 times
rpmdb: Page 94: overflow refcount 1, referenced 0 times
rpmdb: Page 97: overflow refcount 1, referenced 0 times
rpmdb: Page 99: overflow refcount 1, referenced 0 times
rpmdb: Page 100: overflow refcount 1, referenced 0 times
rpmdb: Page 102: overflow refcount 1, referenced 0 times
rpmdb: Page 106: overflow refcount 1, referenced 0 times
rpmdb: Page 107: unreferenced page
rpmdb: Page 110: overflow refcount 1, referenced 0 times
rpmdb: Page 111: overflow refcount 1, referenced 0 times
rpmdb: Page 112: overflow refcount 1, referenced 0 times
rpmdb: Page 125: unreferenced page
rpmdb: Page 127: overflow refcount 1, referenced 0 times
rpmdb: /var/lib/rpm/Provideversion: DB_VERIFY_BAD: Database verification failed
error: db4 error(-30973) from db->verify: DB_VERIFY_BAD: Database verification failed

No, there's no real cause for concern. As I explained in post #10, to resolve this problem and eliminate it from further urpmi or package manager installs, just remove your current repository locations (issue as root: urpmi.removemedia -a) then re-add them again.

You'll probably prefer to have a shortcut icon to start VueScan. Follow the directions below:

Right click on your desktop go to create New--> Link to Application.

Type the name VueScan where is says Link to Application. To the left of that box you will see an icon click it.

In the next window that appears where it says Applications click the upside down triangle and select Devices, in the Search box type scanner, when the scanner icon appears click on it.

That will take you back to the main window, click on the Application tab.

In the Name field type VueScan (you can add a description and comments if you wish).

In the Command field, click Browse and locate the folder that has the VueScan executable, click on the executable, then click Open.

In the Work path field, click the little folder icon, another window should now open with the vuesca84 folder already selected. Click ok then click ok again and voila you have a shortcut to start the program.

The final thing to do before using this icon is to right click it, click properties, select the permissions tab and make sure you have a tick in the Is executable box.

Now test the shortcut to make sure it works.

Fantastic! That did the trick - thank-you!