[Bug 229881] New: YaST hangs during parallel port printer setup
https://bugzilla.novell.com/show_bug.cgi?id=229881 Summary: YaST hangs during parallel port printer setup Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: U.Koehler@gmx.de QAContact: jsrain@novell.com I have a combination of bugs, some of which might be reported elsewhere, but I doubt it. When first setting up my Cannon BJC 6200, the parallel port was left completely unusable by Yast (no devices worked on the port until I rebooted). YaST also did not choose the recommended driver. I then set the printer up with CUPS (http://localhost:631/) every thing worked fine. Later access to the YaST printing module leads to hangup at 4% of building driver database. For the experienced user this is not much of a problem, but a newbie??? How does YaST probe the port? To be honest, since YaST is now hanging up, I cannot reproduce the first part. This might be easiest solved by adding documentation. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229881 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |U.Koehler@gmx.de ------- Comment #1 from mhorvath@novell.com 2006-12-20 07:08 MST ------- Could you attach the yast logs, please? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229881 ------- Comment #2 from U.Koehler@gmx.de 2006-12-21 13:38 MST ------- Created an attachment (id=110759) --> (https://bugzilla.novell.com/attachment.cgi?id=110759&action=view) hwinfo Output of hwinfo > /tmp/info.txt lspci -v >> /tmp/info.txt -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229881 ------- Comment #3 from U.Koehler@gmx.de 2006-12-21 13:59 MST ------- Created an attachment (id=110765) --> (https://bugzilla.novell.com/attachment.cgi?id=110765&action=view) YaST2 Log accessing printer dialog Accessed the printer dialog. That got stuck at 4% build driver databased for 12 minutes. Then I nuked the process. By looking at the last line I am not sure it helps. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229881 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |mzugec@novell.com |screening@forge.provo.novell| |.com | Status|NEEDINFO |NEW Info Provider|U.Koehler@gmx.de | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229881 mzugec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #4 from mzugec@novell.com 2007-01-04 02:04 MST ------- I see two bugs here (please next time report two SEPARATE bugs) 1 - it's proabably #189805 2 - duplicate of #229231 - workarround: delete /var/lib/YaST2/ppd_db.ycp Closing bug as invalid - if you have additional comments, continue in one of these bugs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com