http://bugzilla.novell.com/show_bug.cgi?id=562282
http://bugzilla.novell.com/show_bug.cgi?id=562282#c4
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |jsmeix@novell.com
Component|Printing |Mobile Devices
Info Provider| |peter-mailbox@web.de
AssignedTo|jsmeix@novell.com |mobile-bugs@forge.provo.nov
| |ell.com
QAContact|jsmeix@novell.com |qa@suse.de
--- Comment #4 from Johannes Meixner 2009-12-15 08:16:03 UTC ---
"laptop freezes suddenly on detecting the printer"
has nothing to do with bug #229231 which is only
about a hangup in an old yast2-printer.
A complete and sudden machine freeze (i.e a stop of the kernel)
is again a low level issue.
When it works directly (printer->parallel->laptop)
it proves that it works regarding the printing system
(i.e. when the low level parpoprt stuff works, the
printing system works too - of course).
When it does not work with the docking-station in between
it is a lower level issue that the communicatin via
parport and/or USB does not work normally with the
docking-station in between and of course you see
then various errors in the printing system layer
as a consequence.
udev-configure-printer is a only magic full automated
printer setup tool and when it fails the only consequence
is that you won't have an automated printer setup.
In your case I recomend to remove the udev-configure-printer RPM
(you could use in yast2-printer the "Autoconfig Settings")
to get it out of your way because in your case it doesn't work
and in the worst case it might even cause whatever unexpected
trouble.
Because of all this it is not an issue in the printing system
but a lower-level device communication issue because
the printing system (CUPS and printer drivers)
uses the existing device communication stuff
but the printing system does not do any kind of setup
of the lower level device communication stuff.
Perhaps it might be even a kernel related issue but
I have no knowledge at all about docking station issues
and therefore I assign it back to "Mobile Devices", hopefully
someone there has better knowledge how to debug such issues.
From what I see in your log messages:
Without the docking-station in between you have
------------------------------------------------------------------
kernel: ... parport1: Printer, Hewlett-Packard HP LaserJet 1100
..
kernel: [ 1448.119427] lp0: using parport1 (interrupt-driven).
------------------------------------------------------------------
and the device communication works via /dev/lp0 and
the CUPS device URI is accordingly parallel:/dev/lp0
But with the docking-station in between you have
------------------------------------------------------------------
kernel: ... parport3: Printer, Hewlett-Packard HP LaserJet 1100
..
kernel: ... lp1: using parport3 (interrupt-driven).
------------------------------------------------------------------
so that with the docking-station in between the number
of the parport where the printer is connected to has changed
so that device communication may now works via /dev/lp1 and
a matching CUPS device URI of parallel:/dev/lp1
Test if device communication works via /dev/lp1 according to
http://en.opensuse.org/SDB:Installing_a_Printer
as root with
echo -en "\rHello\r\f" >/dev/lp1
To change the CUPS device URI use as root
lpadmin -p hplaserjet1100A -v parallel:/dev/lp1
Please report if it works via /dev/lp1.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.