|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast2-scanner module fail in opensuse 11 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Pedro Piminchumo <pedropsalinas> |
| Component: | YaST2 | Assignee: | Johannes Meixner <jsmeix> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | gp, jsmeix, tonussi |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Pedro Piminchumo
2008-07-07 17:18:28 UTC
It doesn't look like a bug in yast2-scanner but looks more like a problem in the underlying YaST base system. To the reporter (Pedro Piminchumo): Does it perhaps work when you use the [Add] button? Yes, the option to add generates the same effect, initially I thought we could try and languages because one of the messages: 2008-07-07 12:01:01 <1> constructor(5736) [ui-shortcuts] YShortcutManager.cc(checkShortcuts):83 Shortcut conflict: 'A' used for YPushButton "Añadir" at 0x84546c4 2008-07-07 12:01:01 <1> constructor(5736) [ui-shortcuts] YShortcutManager.cc(checkShortcuts):83 Shortcut conflict: 'I' used for YPushButton "Editar" at 0x84b211c 2008-07-07 12:01:01 <1> constructor(5736) [ui-shortcuts] YShortcutManager.cc(checkShortcuts):83 Shortcut conflict: 'A' used for YQWizardButton "Atrás" at 0x848dcfc 2008-07-07 12:01:01 <1> constructor(5736) [ui-shortcuts] YShortcutManager.cc(checkShortcuts):83 Shortcut conflict: 'I' used for YQWizardButton "Siguiente" at 0x8490054 so it changed to German locale and this did not help, the result was the same. What exactly you mean as "failure"? Does application crashed or something? That warnings are not critical ... yast-scanner module crashed. I'm sorry, my English is very bad : ( A TextEntry/InputField messages are just warnings and should not cause a real problem. Without hardware I cannot reproduce the problem. Neither do I have the reporter's scanner model. It worked for me for all my scanner models. You can run the scanner module without any scanner. Try to activate the driver via the [Add] button for the reporter's model (HP ScanJet G3010), see comment #2: Via "add" it also crashes for the reporter. Of course I tried to reproduce the issue but it doesn't crash for me (but I have YaST installed from development trunk). Just because I'm backup of the yast2-maintainer doesn't mean I can do intensive debugging for various issues. According to http://www.sane-project.org/cgi-bin/driver.pl?model=G3010 the driver for a HP ScanJet G3010 is "hp3900" but I don't have any scanner which needs this driver. On the other hand the y2log in comment #0 (if this is really the full log) shows that it crashes before a driver can be chosen at all so that it looks as if this crash neither depends on the particular scanner model nor on the particular driver which matches to the reporter's comment #2 that it also crashes via "add" which runs the driver selection dialog regardless which model was detected. Because it worked for me for all my scanner models I can only close it as WORKSFORME. Pedro Piminchumo, to activate the driver manually, remove the comment character '#' (the first character) in the "hp3900" line in /etc/sane.d/dll.conf Read this driver's man page: http://www.sane-project.org/man/sane-hp3900.5.html in particular note ---------------------------------------------------------- This is ALPHA software. Keep your hand at the scanner's plug and unplug it, if scanner does not start to scan. ---------------------------------------------------------- Addidionally note that currently there is at most so called "basic" support for this model, see http://www.sane-project.org/cgi-bin/driver.pl?model=G3010 ---------------------------------------------------------- basic means it works at least in the most important modes but quality is not perfect. ---------------------------------------------------------- Hello Folks, I think the same is going on here. Yast has detected my Genius Colorpage Vivid 4 (GT68xx) scanner, but after clicking in edit button to continue the configuration task it seems to enter in a endless loop and I need to force the window to close. Thus, I never got the scanner enabled. I've been using this scanner since OS 9 without problems. reopen the bug? See also the last paragraph in https://bugzilla.novell.com/show_bug.cgi?id=434540#c10 *** This bug has been marked as a duplicate of bug 442173 *** |