regression: hp laserjet 4L worked with jaunty, doesnt work with karmic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Hello,
i am experiencing the following problem.
my printer (hp laserjet 4L) is connected with a parallel-to-usb cable to the laptop and worked flawlessly with jaunty. after a complete new installation with karmic, the printer doesnt work. i tried to narrow down the problem and i dont think its a problem with hplip or cups. i reinstalled them both and even installed new versions from the developer site. i think the problem is before this "layer".
the printer doesnt even show up in the output of "lsusb"... it did before!
i tried this on 2 laptops (both with karmic). both dont work. i tried another windows laptop and it worked without a problem so its not a problem with the printer itself.
i am happy to support you with as many additional information as you need.
thanks in advance
dennis
tags: | added: kernel-series-unknown |
tags: | added: kernel-karmic |
tags: | removed: kernel-series-unknown |
tags: | added: regression-release |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Triaged |
tags: |
added: karmic removed: kernel-karmic |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it without more information.
Please run the following command which will attach necessary information:
apport-collect 486643
Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python- launchpadlib' . Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.
If you cannot use apport please at least add the following information (pay attention to lspci's additional options): signature > version.log
First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).
For your reference, the full description of procedures for kernel-related bug reports is available at https:/ /wiki.ubuntu. com/KernelTeam/ KernelTeamBugPo licies. Thanks in advance!