|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2 scanner hangs in busy loop | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Bernhard Wiedemann <novellbmw> |
| Component: | YaST2 | Assignee: | Johannes Meixner <jsmeix> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | jsmeix, ma |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | Community User | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
y2log from both unsuccessful (qt) and successful (ncurses) scanner setup
y2log from both unsuccessful (qt) and successful (ncurses) scanner setup with debug and nothreads yast2/qt/scanner debug nothread log |
||
|
Description
Bernhard Wiedemann
2008-12-06 11:10:49 UTC
Really openSUSE-11.0, not 11.1? The backtrace from comment #0 might be misleading: It shows only one of the two threads. Can you try again with full debug logging and no threads? cd /var/log/YaST2 mv y2log y2log.old export Y2DEBUG=1 cd /usr/share/YaST2/clients gdb /usr/lib/YaST2/bin/y2base (gdb) run ./scanner.ycp qt --nothreads (wait for a while until starting up with verbose logging should be finished, then hit Ctrl-C) Please also attach the resulting /var/log/YaST2/y2log (preferably bzip'ed). Created attachment 259244 [details]
y2log from both unsuccessful (qt) and successful (ncurses) scanner setup with debug and nothreads
This is definitely 11.0-final.
# cat /etc/*release
openSUSE 11.0 (X86-64)
VERSION = 11.0
Now I also tested this issue with the 11.1-RC1 that I installed on the other partition of the same machine and found no problem there.
Both installations are very clean as I only bought this machine 2 weeks ago.
I also reproduced the bug with the scanner turned off by mistake (clicked "add" in the initial "yast2 scanner" screen).
Sorry, that y2log from comment #3 only contains (the last part of) the succesful program run with the NCurses UI. The problematic part with the Qt UI is already rotated out. But the y2log-1, y2log-2 etc. files that contain the relevant parts should still be in that directory. save_y2logs can package them all. But anyway, if the problem was a scanner that was swithched off, it might be some hardware probing still waiting for the device to come online. Johannes? Created attachment 259816 [details]
yast2/qt/scanner debug nothread log
I don't think that the problem is with the scanner because it works with yast/ncurses without changing anything else with both the scanner on and off
and I think that yast/ncurses should use the same hardware-access and scanning code as the QT-version.
The Assignee: of this bug currently in vacation, please bear with us, while we wait for him to come back. :-) Thanks. *** This bug has been marked as a duplicate of bug 442173 *** |