Re: [Bug 1631794] Re: 16.04 would not boot after installation
That's OK. Thank you for your attention. This is mute anyway. That particular, ancient, computer functions well with Red Hat version of linux. -- Janos G. Komaromi sent it NOT from iPhone nor Google facebook, instagram, viber, snapchat, twitter, #@*~| etc. - neither of those https://jgklinux.jankom.net/ On Sat, 2021-06-12 at 13:58 +, Paul White wrote: > Further to comment #3 I'm closing this bug report by changing the > status > to "Invalid". I'm sorry it took over four years for someone to read > your > comments. > > > ** Changed in: ubuntu >Status: New => Invalid > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631794 Title: 16.04 would not boot after installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1631794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797394] Re: Unable to locate models.dat file
This may help pinpoint the cause: I did a virgin install of 18.04 on the same machine, and now hplip works, printer is found, printing (and scanning as well) is OK. Therefore the problem must be with the distribution upgrade process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797394 Title: Unable to locate models.dat file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1797394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797394] [NEW] Unable to locate models.dat file
Public bug reported: Hp printer worked on 16.04 but it fails after distribution upgrade to 18.04. Based on solved bug #1744340 I checked libsane-hpaio and hplip packages. They were all OK after removing them and reinstalling them - just to make sure. However, apt install libsane-hpaio complained about missing /etc/hp/hplip.conf (?). Regardless, running hp-setup cannot complete the download step because of incorrect checksum. This is when I started this ubuntu-bug -w command. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xfce4-terminal 0.8.7.4-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 CurrentDesktop: XFCE Date: Thu Oct 11 15:59:14 2018 ExecutablePath: /usr/bin/xfce4-terminal InstallationDate: Installed on 2016-12-13 (667 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) SourcePackage: xfce4-terminal UpgradeStatus: Upgraded to bionic on 2018-10-01 (9 days ago) ** Affects: xfce4-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797394 Title: Unable to locate models.dat file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/1797394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1625265] Re: cannot connect to cups server
Hello G, Thank you for your attention to my problem. Please, close the ticket, basically because it is no longer relevant. Somehow I was able to make printing work on my Ubuntu installation. In the meantime I have made a distribution upgrade to 18.04. I must say that I also encountered a printing problem, which eventually I was able to solve on my HP laptop installation (most recent hp-15, 64-bit machine). However, we have an older, i386 desktop machine. Printing worked well with 16.04, but after the distribution upgrade to 18.04 (which went flawlessly) I have not been able to make printing work to an HP printer (new printer, not old as the computer). I searched the AskUbuntu and other sites, but so far the problem is not resolved. Unfortunately, the only way to print from that desktop is to boot it into Vindoooz Xp (this is how old the machine is!). I'm a supporter of Open Source systems, and am grateful to have Linux and the Ubuntu distribution. Hopefully this message is my modest contribution to make Ubuntu better. Janos On 10/06/2018 10:08 AM, gf wrote: > Hello Janos, > Thank you for submitting this bug and reporting a problem with the > system-config-printer package. You made this bug report in 2016 and Ubuntu > and the system-config-printer package have been updated since then. > > Could you confirm that this is no longer a problem and that we can close the > ticket? > If it is still a problem, are you still interested in finding a solution to > this bug? > If you are, could you let us know and, in the current version, could you run > the following (only once): > apport-collect 1625265 > and upload the updated logs and and any other logs that are relevant for this > particular issue. > > Thank you again for helping make Ubuntu better. > G > [Ubuntu Bug Squad volunteer triager] > > ** Changed in: system-config-printer (Ubuntu) >Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625265 Title: cannot connect to cups server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1625265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1622888] Re: cups server error after dist. upgrade to 16.04
Hi G, Thank you for following up on this item. Fortunately, I can report that this is no longer a problem. Since I reported the bug my laptop died and I was able to transfer the complete Ubuntu system to the hard drive of a new HP laptop. It came with a W10 installation and EFI booting, but managed to boot automatically to Ubuntu and, of course, I use exclusively the Ubuntu boot ever since. No issues since that time with updates, cups or anything else. I wish to thank the Ubuntu Team for their efforts to provide a decent open source Linux distro. Janos On 08/26/2018 10:44 AM, gf wrote: > Hello Janos, > Thank you for submitting this bug and reporting a problem with cups. You > made this I wish to thank Ubuntu Team for their efforts to provide a decent > open > source Linux distro.bug report some time ago and Ubuntu has been updated > since then. > > Could you confirm that this is no longer a problem and that we can close the > ticket? > If it is still a problem, are you still interested in finding a solution to > this bug? > If you are, could you let us know, and in the current version, run the > following (only once): > apport-collect BUGNUMBER > and upload the updated logs and and any other logs that are relevant for this > particular issue. > > Thank you again for helping make Ubuntu better. > G > [Ubuntu Bug Squad volunteer triager] > > ** Changed in: cups (Ubuntu) >Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622888 Title: cups server error after dist. upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1622888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631794] Re: 16.04 would not boot after installation
Update: System finally did boot - accidentally. I use this box rarely to boot Ubuntu, most of the time I boot into an old fedora-3. Just for info, and if it helps anybody, including the developers, I think the problem is related to system motherboard in power up state. If I completely cut power to the computer (pull the plug and remove Ethernet cable - I realize, cmos battery is still there, so strictly speaking this is not completely dead) then my computer did boot into 16.04. It looks like using reboot option from fedora-3, or even using a dual boot feature prevents 16.04 to complete the boot process and enter into the loop described above. I don't know if this is normal behavior, but I thought I'd bring this into the attention of anybody who reads this - and maybe help somebody with the same problem. As far as I'm concerned I would close this bug but don't know how. Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631794 Title: 16.04 would not boot after installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1631794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631794] Re: 16.04 would not boot after installation
** Tags added: boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631794 Title: 16.04 would not boot after installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1631794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631794] Re: 16.04 would not boot after installation
"This bug affects you" - well, I'm "you" on another similarly older desktop machine with the same behavior. So it really affects not only "you" but "others" as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631794 Title: 16.04 would not boot after installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1631794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631794] [NEW] 16.04 would not boot after installation
Public bug reported: This was a question but no answer or comments so I converted it to a bug report - jankom This is a "mature" 32 bit machine. Had 12.04, then distro upgraded to 14.04, and recently distro upgraded to 16.04. After that it did not boot, so I decided to rebuild the machine with a virgin installation (reformat, etc.) Installation completed successfully, but after that the machine would not boot into the new installation. Grub is there, boot process starts, even gets to the stage when the x-server starts, but then it falls back to VGA mode (screen shows fsck result being OK) and continues to start x-server, and so on and on, repeating this loop. Note (1): I can start 16.04 from the CD tray Ubuntu mode. If I look at syslog and xserver.0.log from the mounted 16.04 root filesystem (the one that would not boot) I can see no obvious reason for this behavior of getting stuck in a loop at boot process, although I have limited expertise in Ubuntu architecture. Note (2): Rescue mode does not help either Note (3): again, this is a 32 bit desktop machine with Athlon Duron CPU and nvidia chipsets. The machine has been running well with 12.04 or 14.04 (except for a still outstanding scanner bug on 14.04, but I don't think it has anything to do with this failure to boot on a shiny new 16.04 installation. Note (4): I checked, I have plenty of free disk-space, and if I dual boot into my old Fedora-3 installation everything is fine. Therefore I do not think the problem would be hardware failure. Note (5): finally (if it helps) the display is a 24" LCD. Booting from the 16.04 CD in live session mode the resolution is 1920x1080, and everything is fine. Just booting into the installed 16.04 on the hard disk fails with an endless loop between text and graphics mode. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631794 Title: 16.04 would not boot after installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1631794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608161] Re: printing not working after upgrade to 16.04
Printing finally works, but it was a lengthy and complicated process. Here are the steps I took, as best as I can remember: (1) installed 16.04 on a different machine (virgin install) - so that I can find out what the real picture is (2) ran gnome-software (because on the distro update this gnome-software command is not part of my gui menu, only the previous "Ubuntu Software Center" is there. (3) downloaded recommended 16.04 missing software, including cups (in fact, I removed cups related software with synaptic package manager when printing did not work) (4) Studied 16.04 wiki printing related stuff. Discovered that /etc/cups/cupsd.conf file did not exist on my machine, but there was a cupsd.conf.O file still there. (5) Edited the cupsd.conf.O file according to wiki instructions and saved it without the .O tail; restarted cups service according to wiki. (6) Now the cups web interface (127.0.0.1:631) worked, and the printer setting gui also worked. (7) The rest of the stuff was the same as when I installed printers years back with the first installation of xubuntu, then 12.04. Because I have an HP Laserjet P1102w printer I had to run hp-plugin -i command from terminal in order to avoid gui printer setup error. (8) I could also install my Lexmark color printer using samba network shared printer from my old Fc3 machine and selecting Generic Postscript driver. Same trick I did before because the Lexmark proprietary driver package installation did not work from Xubuntu. This was a workaround. My old Fc-3 linux machine shares the same Lexmark color printer to not only xubuntu bu also to old Windows machines as well. F.Y.I. - hope this helps developers and others with similar problems jankom -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608161 Title: printing not working after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1608161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625265] [NEW] cannot connect to cups server
Public bug reported: Bug-in-bug: after "ubuntu-bug -w" command and clicking on the problem window (cannot connect to cups server) the web page started with a message that it refreshes every 10 seconds. It may have, but the only way to move forward was to reload the web page so that I could get into this one - this has happened before, so apparently there is a bug with ubuntu-bug (apport?) as well. Now the real bug hopefully reported by "ubuntu-bug -w" is that I cannot print since distribution upgrade to 16.04. I tried to follow instructions on Ubuntu.wiki, and was unable to solve the problem. Fortunately, I have an old Linux installation on a different machine, so if I need to print something from this machine I just access the pdf version from the old Linux machine and print it from there. I'm more than happy to participate in helping to solve this problem, I do have some understanding of basic Linux (Fedora-3 level), but the current sophistication of Ubuntu is too much for me. I did a fresh install, not distribution upgrade, on a different machine. There printing works (well, at least it connects to the print server). So this bug is definitely related to distribution upgrade: some stray files and configurations from 14.04 confuse the 16.04 system. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: system-config-printer-gnome 1.5.7+20160212-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: XFCE Date: Mon Sep 19 12:22:42 2016 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationDate: Installed on 2013-10-31 (1053 days ago) InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820) InterpreterPath: /usr/bin/python3.5 Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0d62:0530 Darfon Electronics Corp. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer Aspire 5532 PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/LaserJet-P-1102w-Acerlinux.ppd', '/etc/cups/ppd/EvaIdaWindowsHP-Deskjet-1050-j410.ppd', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/LaserJet-P-1102w-Acerlinux.ppd: Permission denied grep: /etc/cups/ppd/EvaIdaWindowsHP-Deskjet-1050-j410.ppd: Permission denied grep: /etc/cups/ppd/PDF.ppd: Permission denied ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=b1ac29b9-b0d0-456f-b424-0c683ae107a7 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2009 dmi.bios.vendor: Acer dmi.bios.version: V1.08 dmi.board.name: Aspire 5532 dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnAcer:bvrV1.08:bd10/20/2009:svnAcer:pnAspire5532:pvrV1.08:rvnAcer:rnAspire5532:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.name: Aspire 5532 dmi.product.version: V1.08 dmi.sys.vendor: Acer ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625265 Title: cannot connect to cups server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1625265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622888] [NEW] cups server error after dist. upgrade to 16.04
Public bug reported: Yes - similar bug, but NO, not the same bug: There was an error during the CUPS operation: 'failed to connect to server'. Cannot print with my machine since I ran dist. upgrade. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.16 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Tue Sep 13 03:50:48 2016 InstallationDate: Installed on 2013-10-31 (1047 days ago) InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to xenial on 2016-07-30 (45 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622888 Title: cups server error after dist. upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1622888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621906] [NEW] LibreOffice Base table bottom section blank - 16.04 upgrade display issues
Public bug reported: Confusion-confusion: the ubuntu-bug -w command selected xfce4-panel. However, the bug I wanted to report (following instruction after ubuntu- buf -w command) was the "summary" above, i.e. LibreOffice Base data table bottom section is blank after running distro upgrade from 14.04 to 16.04. Actually, there were other problems, but I can live with them or fixed them myself. This one is not a big problem, but my be the indication of a much bigger and general problem: window manager or display manager mis-behavior after standard upgrade from 14.04 to 16.04. Here the problem has an easy fix and therefore the problem is just an annoyance. The easy fix (which only corrects the symptom, but not the bug) is to adjust the data table window frame right side larger or smaller a little. Immediately, the bottom part of the window (I don't know the official name of it, but it is where Record n of N + arrow for next record, last record or new record, + horizontal slider shows up) becomes visible. The reason I suspect this is a harbinger of bigger display/window problem is because on two separate older desktop machines (different graphics cards) a similar problem occurs, but more generally. Namely, on some application the window within application is blank, or worse yet, any pop-up or generated window appears totally black or white. The only way to shut down the machine decently is to switch to CTL-SH-f1 console mode, login, and type in a reboot or shutdown command. This has made the upgraded machine totally unusable. One more thing: on that other machine the symlink /etc/resolve.conf file is missing after upgrade. Hope this helps - jankom ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xfce4-panel 4.12.0-3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 9 10:52:10 2016 ExecutablePath: /usr/bin/xfce4-panel InstallationDate: Installed on 2013-10-31 (1043 days ago) InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-panel UpgradeStatus: Upgraded to xenial on 2016-07-30 (41 days ago) ** Affects: xfce4-panel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621906 Title: LibreOffice Base table bottom section blank - 16.04 upgrade display issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1621906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608161] [NEW] printing not working after upgrade to 16.04
Public bug reported: Yesterday I completed distribution upgrade from 14.04 to 16.04. While it was a lengthy process everything seemed ok (even though I lost my background picture on desktop but later was able to restore it to what it was before upgrade). However, today I tried to print something and it fails. I have an HP P1102w, and it worked perfectly before. I did all recommendations according to your wiki (network is OK, cups is seeing the printer, etc. etc.). I even deleted and reinstalled the printer, but when trying to print test page after installation an error shows up"hplip.plugin". I also reinstalled the hplip package but no help. Does this have something to do with HP proprietary software and agreeing to some license blah-blah? I remember originally when I installed the printer in 14.04 there was something like that. Now everything is hidden behind the fancy gui stuff and I'm stuck with no printing. I have another wireless printer, a Lexmark that I previously used as a shared printer from another linux box (where I was able to jury-rig the linux driver), and it worked well. Now I cannot use it, because there is a cups error: There was an error during the CUPS operation: 'Transport endpoint is not connected'. Again, now I have no printer at all. My network is working well, I can see the other linux box or files on it, but cannot use the shared Lexmark color printer. I remember, during the upgrade there were some terminal messages that could not delete some cups orr ppd related directories, because they were not empty (apparently the script did not use the -rf option for rm). Could this have anything to do with my complete shut out of printing capability? Needless to say, I can print to both HP P1102w or Lexmark printers from the other linux box (an old Fedora-3 distro). ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608161 Title: printing not working after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1608161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1542252] Re: Network unavailable after Libreoffice-5 PPA install
Most recently, after a few notified updates of my computer I tried to install Network Manager, just out of curiosity. Surprise-surprise, this time the system did not complain after reboot. Then I restored /etc/network/interfaces file to its minimum auto lo iface lo inet loopback and now the system works as before this bug showed up its ugly face. Network Managers works again. I don't know what happened, how it happened, but I thought I'd let developers know. N.B. When I lost my networking and Internet access I completely purged Network Manager and set up /etc/network/interfaces file so that I can use sudo ifup method - see initial bug description above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1542252 Title: Network unavailable after Libreoffice-5 PPA install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1542252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364033] Re: 14.04 upgrade display driver missing on Acer AMD64 laptop
** This bug is no longer a duplicate of bug 1058040 fglrx-installer not working with AMD Radeon/Mobility Radeon HD 2000-4000 cards in Quantal+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364033 Title: 14.04 upgrade display driver missing on Acer AMD64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1364033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1542252] [NEW] Network unavailable after Libreoffice-5 PPA install
Public bug reported: This bug is a result of solving bug #1454310. After rebooting various system error messages appeared. Networking was unavailable. According to one Askubuntu suggestion, removed trusty-security package sources, apt- get update, upgrade, reinstall network-manager but same problem. After almost a week's work I was able to reactivate networking via /etc/network/interface and sudo ifup xxx, first with wired then finally connecvting to hidden WiFi which I'm using now. If I reinstall network- manager and its gui companion installation goes well, but at reboot the same thing happens as described in the beginning. Presently network- maneger and its gui companion is completely removed. My system is on an Acer Laptop, 14.04.3 LTS and64, and it has been regularly updated according to notices. No special or custom programs are installed or no unusual customization was made. I'm attaching a file describing what happened a week ago leading to this system problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager (not installed) ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Feb 5 05:00:08 2016 InstallationDate: Installed on 2013-10-31 (826 days ago) InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820) SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-08-31 (522 days ago) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "BugBashHistory.odt" https://bugs.launchpad.net/bugs/1542252/+attachment/4564418/+files/BugBashHistory.odt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1542252 Title: Network unavailable after Libreoffice-5 PPA install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1542252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1454310] Re: LibreOffice 4.2 crashes vector::_M_range_check
Christopher M. Penalver, Thanks again, and THE BUG IS FIXED in LibreOffice 5! 1) sudo add-apt-repository ppa:libreoffice-5.0 - executed OK 2) sudo apt-get update - executed OK 3) "Software updater" notification appeared - ran it OK 4) Another "Software updater notification appeared, this time for LibreOffice - ran it OK 5) Opened the file where the query edit crash happened before - this time NO CRASH, works as expected. Please, close the bug as completed and fixed. Janos On 01/29/2016 09:59 PM, Christopher M. Penalver wrote: > sudo add-apt-repository ppa:libreoffice/libreoffice-5-0 > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454310 Title: LibreOffice 4.2 crashes vector::_M_range_check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1454310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1454310] Re: LibreOffice 4.2 crashes vector::_M_range_check
Christopher M. Penalver, sorry, I did my best to study the web site and try to fetch the ppa but failed. Must have missed something. Here is the terminal output: *janos@acerlinux:~$ sudo add-apt-repository 1:5.0.4-rc2-Oubuntu1-trusty1 [sudo] password for janos: Error: '1:5.0.4-rc2-Oubuntu1-trusty1' invalid janos@acerlinux:~$ sudo add-apt-repository 1:5.0.4-rc2-0ubuntu1-trusty1 Error: '1:5.0.4-rc2-0ubuntu1-trusty1' invalid janos@acerlinux:~$ *As you see, I tried with both "Oh"ubuntu and "zero"ubuntu. Please, help steer me in the right direction. ** On 01/29/2016 12:43 PM, Christopher M. Penalver wrote: > Janos G. Komaromi, to see if this is already resolved, could you please > use one of the 5.x PPAs via https://launchpad.net/~libreoffice and > advise to the results? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454310 Title: LibreOffice 4.2 crashes vector::_M_range_check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1454310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1454310] Re: LibreOffice 4.2 crashes vector::_M_range_check
Dear Christopher M. Penalver, Thank you for the quick reply. The attached text file is the copy of my terminal output according to your instructions. I recreated the bug before executing step #2. It looks like my computer (acerlinux) was communicating with launchpad. As far as creating unnecessary reports - I did not mean to cause any trouble, and will report eventual future bugs according to your email. Btw: the ^C at the end of the terminal output is due to the fact that the normal "paint text with cursor" then "right click" will copy and paste the painted (marked) text Unix/Linux method did not work. So I tried the Ctr-C / Ctr-V method. That did not work either. Finally the GUI right click in terminal gave me the opportunity to copy the terminal output into the clipboard. Why is this? Why do we have to emulate Vindooz? - just a little annoyance. It seems to me this change is recent. The "paint text" method used to work B4. regards, Janos On 01/27/2016 05:00 PM, Christopher M. Penalver wrote: > Janos G. Komaromi, to advise, please don't manually create new reports about > this issue as noticed in: > https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1538730 > > as it doesn't accomplish anything but creating unnecessary reports to > duplicate to this one. > > Despite this, I've recently encountered a situation where a crash bug > for a different problem with LibreOffice aren't "caught" by apport, > substantiating what you have experienced. So, while the reporting work > flow is valid (closing this report), the infrastructure to execute on > the work flow isn't. > > Hence, please perform the following to further debug this issue: > 1) Execute at a terminal: > sudo apt-get -y install libreoffice > > 2) Execute the following command only once, as it will automatically gather > debugging information, in a terminal: > apport-collect 1454310 > > When reporting bugs in the future please use apport by using 'ubuntu- > bug' and the name of the package affected. You can learn more about this > functionality at https://wiki.ubuntu.com/ReportingBugs. > > 3) Execute at a terminal and post the results here untarred/uncompressed: > apt-show-versions -r libreoffice* > > 4) Advise to any 3rd party add-ons, plugins, etc. that you downloaded > not expressed in 3). This wouldn't invalidate the report, but it helps > to fully understand the environment one is in. > > Thank you for your understanding. > > ** Changed in: libreoffice (Ubuntu) > Importance: Undecided => Low > > ** Changed in: libreoffice (Ubuntu) > Status: Invalid => Incomplete > ** Attachment added: "TerminalCaptureBug1454310.txt" https://bugs.launchpad.net/bugs/1454310/+attachment/4559319/+files/TerminalCaptureBug1454310.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454310 Title: LibreOffice 4.2 crashes vector::_M_range_check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1454310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454310] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1454310/+attachment/4559309/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454310 Title: LibreOffice 4.2 crashes vector::_M_range_check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1454310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454310] Re: LibreOffice 4.2 crashes vector::_M_range_check
apport information ** Tags added: apport-collected third-party-packages trusty ** Description changed: - LibreOffice Base, Query: The specific query works, but can only edit in - SQL view. If I try to edit in Base view mode it crashes. Only one of the - many queries have this problem. Also, as I was researching this I could - not find the Check for update option in the Tools menu. Is it not - available in the Ubuntu packaged version? - thanks, Janos + LibreOffice Base, Query: The specific query works, but can only edit in SQL view. If I try to edit in Base view mode it crashes. Only one of the many queries have this problem. Also, as I was researching this I could not find the Check for update option in the Tools menu. Is it not available in the Ubuntu packaged version? - thanks, Janos + --- + ApportVersion: 2.14.1-0ubuntu3.19 + Architecture: amd64 + CurrentDesktop: XFCE + DistroRelease: Ubuntu 14.04 + InstallationDate: Installed on 2013-10-31 (819 days ago) + InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820) + Package: libreoffice 1:4.2.8-0ubuntu3 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 + Tags: third-party-packages trusty + Uname: Linux 3.13.0-77-generic x86_64 + UpgradeStatus: Upgraded to trusty on 2014-08-31 (515 days ago) + UserGroups: adm apu audio cdrom dip lpadmin plugdev sambashare sudo x2gouser + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1454310/+attachment/4559308/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454310 Title: LibreOffice 4.2 crashes vector::_M_range_check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1454310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1538730] [NEW] bug 1454310 changed incorrectly
Public bug reported: I reported a bug a year ago, #1454310 and then somebody changed it to "invalid". I don't understand why this was done. The problem is still there. I realize this is a free software, but at the same time I'm willing to help make this better in whichever way I could. So please, re-instate it as a valid bug and investigate. Let me know how I can help resolve this. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538730 Title: bug 1454310 changed incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1538730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1454310] Re: LibreOffice 4.2 crashes vector::_M_range_check
Christopher M. Penalver, thank you for your response and instructions. I have executed the commands in the first paragraph, and everything went through without a problem. One minor thing, the very first command (cd /var/crash) complained that there is no such directory. Nevertheless, after executing all commands now I do have such directory. The problem is, that it is empty, i.e. no crash report is generated by LibreOffice. I did reproduce the crash, but var/crash directory is empty. Apparently, this is a crash within LibreOffice. In fact, when I open LibvreOffice the next time it remembers that there was a crash and recovers successfully the active file prior to the crash. By the way, I suspect the crash is due to the parser module that builds the "Design View" (sorry, I used the wrong terminology in my original bug report), because editing in SQL View or running the query itself does not produce a crash. I chose to file the bug report with Ubuntu and not with LibreOffice because my LibreOffice is from Ubuntu distribution, and as I mentioned, it does not have the standard "update" option. Evidently, Ubuntu has modified or customized the generic LibreOffice package to better suit Ubuntu's architecture. Thanks again, Janos On 05/13/2015 11:48 PM, Christopher M. Penalver wrote: > Janos G. Komaromi, thank you for reporting this and helping make Ubuntu > better. However, your crash report is missing. Please follow these > instructions to have apport report a new bug about your crash that can be > dealt with by the automatic retracer. First, execute at a terminal: > cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade > && sudo service apport start force_start=1 > > If you are running the Ubuntu Stable Release you might need to enable > apport in /etc/default/apport and restart. > > Now reproduce the crash, then open your file manager, navigate to your > /var/crash directory and open the crash report you wish to submit. > If this fails you will have to open a terminal and file your report with > 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash > is the crash you would like to report. If you get an error that you aren't > allowed to access this report you will have to file it with 'sudo ubuntu-bug > /var/crash/_my_crash_report.crash'. If you run the command against the crash > report and a window pops up asking you to report this, but then never opens a > new report, you would be affected by > https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to > WORKAROUND this, one would need to open the following file via a command line: > sudo nano /etc/apport/crashdb.conf > > and comment out the line: > 'problem_types': ['Bug', 'Package'], > > by changing it to: > # 'problem_types': ['Bug', 'Package'], > > Save, close, and try to file the crash report again via: > ubuntu-bug /var/crash/_my_crash_report.crash > > I'm closing this bug report since the process outlined above will > automatically open a new bug report which can then dealt with more > efficiently. > > Please feel free to subscribe me to this new report. > > Also, please do not attach your crash report manually to this report and > reopen it. > > Thank you for your understanding. > > Helpful bug reporting tips: > https://wiki.ubuntu.com/ReportingBugs > > ** Changed in: libreoffice (Ubuntu) > Status: New => Invalid > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454310 Title: LibreOffice 4.2 crashes vector::_M_range_check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1454310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454310] [NEW] LibreOffice 4.2 crashes vector::_M_range_check
Public bug reported: LibreOffice Base, Query: The specific query works, but can only edit in SQL view. If I try to edit in Base view mode it crashes. Only one of the many queries have this problem. Also, as I was researching this I could not find the Check for update option in the Tools menu. Is it not available in the Ubuntu packaged version? - thanks, Janos ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454310 Title: LibreOffice 4.2 crashes vector::_M_range_check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1454310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364458] Re: Hewlett-Packard ScanJet 4500C/5550C not recognized in 14.04, worked in 12.04
If the driver worked B4 upgrade why is it not working now? Why will this issue be closed in 36 days without resolution? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364458 Title: Hewlett-Packard ScanJet 4500C/5550C not recognized in 14.04, worked in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1364458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364458] Re: Hewlett-Packard ScanJet 4500C/5550C not recognized in 14.04, worked in 12.04
OK, so what can I do to make my scanner work in the distro-updated system? I did work before I did the distro-update. Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364458 Title: Hewlett-Packard ScanJet 4500C/5550C not recognized in 14.04, worked in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1364458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364458] Re: Hewlett-Packard ScanJet 4500C/5550C not recognized in 14.04, worked in 12.04
janos@andrasxubuntu:~$ scanimage -L [hp5590] hp5590_get_status: USB-in-USB: got non-zero device status (status 12) [hp5590] hp5590_init_scanner: scanner reports non-zero status: Device busy No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). janos@andrasxubuntu:~$ Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364458 Title: Hewlett-Packard ScanJet 4500C/5550C not recognized in 14.04, worked in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1364458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058040] Re: fglrx-installer not working with AMD Radeon/Mobility Radeon HD 2000-4000 cards in Quantal+
I removed fglrx, installed mesa-utils, rebooted, and now display (including cursor behaviour) is working fine. Note, I do not run games, but movies in full screen display OK. - Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058040 Title: fglrx-installer not working with AMD Radeon/Mobility Radeon HD 2000-4000 cards in Quantal+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364033] Re: 14.04 upgrade display driver missing on Acer AMD64 laptop
*** This bug is a duplicate of bug 1058040 *** https://bugs.launchpad.net/bugs/1058040 OK, thanks for the link. I removed fglrx, installed mesa-utils, rebooted, and now display (including cursor behaviour) is working fine. Note, I do not run games, but movies in full screen display OK. I do agree with one of the comments in the link that this problem should be noted in the distro-upgrade info - Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364033 Title: 14.04 upgrade display driver missing on Acer AMD64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1364033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364458] [NEW] scanner not recognized in 14.04, worked in 12.04
Public bug reported: After distro-upgrade from 12.04 to 14.04 simple-scan does not work. This has been an issue in the past when I tried 13.04 and I reported it as a bug. This is why I stayed with 12.04. Now that the new LTS upgrade is available I'm outof luck. I tested my Acer 64-bit laptop connecting to the scanner running the same 14.04 distro upgraded system and it works on the laptop. So this bug may not be distro related, rather desktop vs. laptop hardware related. You must have all hardware info on this particular desktop. As I said before scanner works on this desktop with 12.04 (or on Fedora-3 for that matter), but not with 13.xx or 14.04 Ubuntu. - Janos ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: simple-scan 3.12.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 CurrentDesktop: XFCE CurrentDmesg: [ 68.374923] type=1400 audit(1409670775.512:46): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cups-browsed" pid=1220 comm="apparmor_parser" [ 68.643709] init: plymouth-upstart-bridge main process ended, respawning [ 90.960515] type=1400 audit(1409670797.506:47): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=1784 comm="apparmor_parser" [ 90.960540] type=1400 audit(1409670797.506:48): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1784 comm="apparmor_parser" [ 90.961486] type=1400 audit(1409670797.506:49): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1784 comm="apparmor_parser" Date: Tue Sep 2 11:17:47 2014 DriverPackageVersions: libsane 1.0.23-3ubuntu3.1 libsane-extras N/A hplip 3.14.3-0ubuntu3.2 hpoj N/A ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2013-10-25 (312 days ago) InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820) Lsusb: Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 03f0:1205 Hewlett-Packard ScanJet 4500C/5550C Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System Manufacturer System Name ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=bb51ea36-9854-4643-ba11-4b57e040aef3 ro quiet splash vt.handoff=7 SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: Upgraded to trusty on 2014-08-13 (20 days ago) dmi.bios.date: 07/26/2004 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS A7N266-VM ACPI BIOS Rev 1008 beta 002 dmi.board.name: A7N266VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSA7N266-VMACPIBIOSRev1008beta002:bd07/26/2004:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA7N266VM:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System Name dmi.product.version: System Version dmi.sys.vendor: System Manufacturer ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364458 Title: scanner not recognized in 14.04, worked in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1364458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364033] [NEW] 14.04 upgrade display driver missing on Acer AMD64 laptop
Public bug reported: After a flawless upgrade I noticed that display is only generic, "default", i.e. 1024x768. When I try AMD Catalyst Control Center it complains that "No AMD graphics driver is installed or the display driver is not functioning properly". When I run the recommended command aticonfig it reports that "No supported adapter detected". lspci does show ATI Radeon HD 3200 controller. P.S. upgrade process is well designed, giving info and appropriate choices, congrats to developers - Janos ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.4 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CrashDB: ubuntu Date: Mon Sep 1 10:10:23 2014 InstallationDate: Installed on 2013-10-31 (304 days ago) InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to trusty on 2014-08-31 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364033 Title: 14.04 upgrade display driver missing on Acer AMD64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1364033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363778] [NEW] 14.04 upgrade display driver missing on Acer AMD64 laptop
Public bug reported: After flawless upgrade from 12.04 on Acer laptop with AMD 64-bit processor display has only generic 1024x768 mode. lspci does list ATI Radeon HD 3200 controller, but aticonfig has error "No supported adapter detected", and AMD Catalyst Control Center in Settings reports initialization error. Also, at boot "unable to detect WMID device" message comes up ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363778 Title: 14.04 upgrade display driver missing on Acer AMD64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1363778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259457] Re: Thunderbird Lightning no sound
SOLVED! Bug closed - stupid me... What happened was due to two things, I guess. (1) The unorthodox location of Tunderbird Profile. (2) *.wav file association was broken, probably because I removed distro based music player. Solution: (a) Right clicked on a wav file, Properties, and set "Open with" to VLC media player. (b) In Thunderbird and Lightnin Edit Preferences Browse and point back again to my chosen sound file. Tested and it works. Hope it'll help someone, jankom ** Changed in: thunderbird (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259457 Title: Thunderbird Lightning no sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1259457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259457] Re: Thunderbird Lightning no sound
Quinn Balazs: Thanks, I'll change status. I tried the instructions, but it did not produce the expected result, see below: Quote janos@acerlinux:~$ xprop WM_CLASS WM_CLASS(STRING) = "Mail", "Thunderbird" janos@acerlinux:~$ locate -b "\Mail" /mnt/DOS_E/BinWin/Thunderbird/Installed_backup_old_Dell/Thunderbird/Profiles/xl23icn4.default/Mail /mnt/DOS_E/emails/Thunderbird_Profile/j1k0vq2t.default/Mail /usr/share/perl5/Mail janos@acerlinux:~$ locate -b "\Thunderbird" /mnt/DOS_E/BinWin/Thunderbird /mnt/DOS_E/BinWin/Thunderbird/Installed_backup_old_Dell/Thunderbird janos@acerlinux:~$ dpkg -S /mnt/DOS_E/BinWin/Thunderbird/Installed_backup_old_Dell/Thunderbird/Profiles/xl23icn4.default/Mail dpkg-query: no path found matching pattern /mnt/DOS_E/BinWin/Thunderbird/Installed_backup_old_Dell/Thunderbird/Profiles/xl23icn4.default/Mail. janos@acerlinux:~$ whereis Mail Mail: janos@acerlinux:~$ whereis Thunderbird Thunderbird: janos@acerlinux:~$ Unquote Is this another bug in the instructions or in the locate or in the dpakg commands? Obviously, I have installed Thunderbird profile in an unorthodox way because of disk partitioning and available space. But why locate or whereis could not find it? Well, Thunderbird is lower case thunderbird, but then why did xprop found it as uppercase Thunderbird? As ras as mail it is not there either as mail or Mail. Just some thoughts as I was trying to follow instructions. So long... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259457 Title: Thunderbird Lightning no sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1259457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259457] [NEW] Thunderbird Lightning no sound
Public bug reported: Cannot activate sound alerts in Xubuntu 12.04 installation of Tunderbird 24.1.0. I googled and checked ubuntu forums. Lightning 2.6.2 is also installed, but calendar sound notification is silent. Same with 24.1.1 and 2.6.3. No answer in Ubuntu Launchpad questions forum (expired open after 15 days), and no answer in Mozilla "Get Satisfaction" forum. Sound works in VVindooz... ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259457 Title: Thunderbird Lightning no sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1259457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 [Asus A7N266VM] Scanner does not work: Simple scan gives a device busy error
Christopher M. Penalver, sorry for not expressing myself clearly: what I meant is that if two kernel versions have the same configurations then I would expect that they would work the same way. But maybe that is not the case. What made me suspicious is that a kernel version did work, then a later version did not, and yet an even later version worked again. I guess, everything is possible, so it would still make sense to do a bisect. Nevertheless, the execise would be academic, since 12.04 works well on the ASUS desktop as well, including scanner. So even if there were some obscure kernel reason for the 13.04 scanner busy malfunction it would not be an improvement benefitting the entire Ubuntu community. Therefore I'll mark this bug as Status Invalid. Again, thank you for your attention to this matter. Janos ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 [Asus A7N266VM] Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 [Asus A7N266VM] Scanner does not work: Simple scan gives a device busy error
Christopher M. Penalver, I'm again away from home till early February, so I do not have access to the home desktop coputer with Asus mother board. If it helps Ubuntu developers I'm willing to do the bisect project using the link you provided. Nevertheless, I would like to know and understand the following: (1) If the kernel configuration is the same for a kernel that scanner works and for another kernel that the scanner does not work what is the point of bisecting kernels? Please, explain. (2) Apparently the kernel recognizes the scanner devices, but something takes it over and causes it to report as being busy. Shouldn't we direct our investigation towards that? Note: before I left home I wiped out the hard drive again (you know, the dd stuff) and installed 12.04 flawlessly. Everything works on the Asus computer, and I do not have 13.04 installation anymore. But again, if it helps I can create an install and do the bisect. Also, I installed 12.04 on my Acer laptop, abandoned my W7 boot and use only my Xubuntu on it, completely happy. I'm writing this on my Acer laptop, from Xubuntu 12.04. Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 [Asus A7N266VM] Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
New information from Janos I did a diff on kernel configurations between 3.8.0-29 and -31 and found minimal, non-essential differences. Scanner works on -29 in ubuntu environment, but does not work on -31 in xubuntu environment. Scanner also works on different hardware (my Acer laptop) even on -31 xubuntu. My conclusion is that scanner problem is not related to kernel but to distribution itself (xubuntu going from 12.04 to 13.04). I suggest to go back to my initial report where sane finds the scanner, but scanimage thinks it is busy. I'm ready to give up on this bug. xubuntu is a good compliment to my linux experience. I can continue to play with my old, hacked and mangled FC3 installation where the scanner works and my color lexmark printer also works. On the other hand, xubuntu could make my new HP P 1102W printer work that I was unable to accomplish so far in FC3. But xubuntu cannot make the lexmark printer and the scanner work. That's OK, I'll use both linux installations, depending on what I need. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher, one more thing: I have installed the same 13.04 xubuntu (Raring) on my Acer 64 bit laptop, using a USB stick as the root filesystem. When I connect the laptop to the same scanner it works. I checked the kernel and it is 3.8.0.31. Well, this is a mystery, since my PC on which the scanner does not work is fully updated and yet the kernel is 3.8.0-19, as previously noted in this bug comment thread. So how come it was not updated to .31? OK, let that be a separate problem. So I was encouraged and wiped out my installation on the PC, repartitionad the hard drive and installed again 13.04 using the same DVD as I used before or used for the laptop. Installation. This new virgin installation, went well, and updated itself completely. Checked kernel, now it is the same as on laptop, that is .31. Fine, so I tried to scan, and it is the same problem, scanner not recognized. I guess, this test suggest that the problem is with kernel configuration. Apparently, because of the two different hardwares (laptop and my PC) some of the modules are not included in the kernel configuration. My Acer laptop can run the scanner without those modules, but my PC cannot. This, to me, makes it even more important to test .29 kernel on my PC which worked on Ubuntu live CD (not xubuntu). If I have to bisect I would only have to bisect between 29 and 31. Better yet, if I can run a diff between 29 and 31 kernel configurations I may be able to discover what is the problem with accessing the scanner. Summary: I still need to know how to load .29 kernel in my xubuntu so that I can test it before further research or bisect. Thank you or anybody else reading this. Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher, here is another question before I start digging into it. I would like to try 3.8.0-29 on my installed xubuntu. Yes, it worked on Ubuntu (not xubuntu) live CD, but just to make sure it is the kernel and not the distro around it I would like to test this idea. Specifically, how can I simply download and activate kernel 3.8.0-29? The "Ubuntu Software Center" application does not have such a choice. Thanks, Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher, OK. I'll start working on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher, OK. Forgive me for a stupid question: bisect what? If it is the kernel that to blame, and if kervel versions are sequential, how come 3.2 0-52 works, 3.8.0-19 does not, then 3.8.0-29 works again, then 3.11.0-8 does not? What does Precise, Raring or Saucy has to do with kernel working or not? My understanding is that the various flavors (Precis, Saucy, Raring) have different features and packaging, supposedly better user experience, but they are built around some kernels, such as 3.2, 3.8 or 3.11. I would like to fully understand what I'm doing before starting. Please, understand that I'm not trying to be difficult, but I'm confused about the fact that one kernel works, the next doesn't, the next works again, and so on. So should I simply bysect kernels in Xubuntu Precise and Raring? Raring already does not work, so why go to Saucy? Please, explain. Maybe I totally miss the point. I studied the "bysect" link you sent me and this is why I have these questions. Thanks, Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher: yes, reproducible. Installation DVD is fine, no problem with fonts . I did a live DVD test, and scanner is not recognized. Looks like kernel is 3.11.0-8. Just to recap: Ubuntu or Xubuntu in Precise version do recognize scanner. Ubuntu Precise kernel is 3.8.0-29 amd Xubuntu Precise kernel is 3.2.0-52. They both work with my scanner. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher, ok. I start to see the logic. However, I fail to understand why kernel 3.2 works on Xubuntu, but 3.8.0-19 does not, even though 3.8.0-29 works again in Ubuntu. Apparently something went bad going from 3.2.0-52 to 3.8.0-19 in Xubuntu, but going from 3.8.0-19 to 3.8.0-29 things became good again (I mean scanner recognition in Xubuntu). So before I bisect anything would you agree that I should first install 3.8.0-29 on my Xubuntu, and test the scanner. If it works then we can decide if we need to bisect 3.8.0-19 and -29 if we really want to find out what is the offending code. Let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher M. Penalver, I think we have a major confusion here, and it is mainly my fault. This is due to my lack of experience with Ubuntu community and with bug reporting. The bug I reported is for Xubuntu, not for Ubuntu. "X" is the key word here. When I studied the bisect notes and my previous tests I found out that Precise (a.k.a. 12.04) kernel for Ununtu on live CD (or DVD) is 3.8.0-29 but for xubuntu it is 3.2.0-52 Scanner works on both live CD. Raring (a.k.a. 13.04) kernel for xubuntu is 3.8.0-19, and scanner is not recognized, i.e. this bug. Both Ubuntu and Xubuntu CDs have kernels marked "generic". It looks like Xubuntu uses different kernels than Ubuntu. Why is that? Why should desktop user spoace software affect kernel? But these questions are only due to my "ask stupid questions" mentality. As far as bisecting is concerned, I don't know where to find the relevant Xubuntu kernel releases. The bisecting instructions refer only to Ubuntu releases, not to Xubuntu. It looks like Xubuntu is an .org and Ubuntu is a .com. Am I in the wrong place reporting the bug? The bottom line is: I need more help and directions how to proceed. Thanks, Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher M. Penalver, thank you. I'll do that. Give me some time to study the article and get down to work. This will be my first bisection. Will keep you posted if any problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher M. Penalver, I'm in live DVD (did not fit on CD) boot ("try
Ubuntu"). Looks good, if you allow me the opinion, it is much better
than the other version I tried, see comments #17 and #21.
Scanner does work, but I think I stated that in my initial bug report.
I was not sure exactly what you wanted, so I ran apport-collect three
ways. See attached file of terminal window transcript.
Hope this helps.
Janos
** Attachment added: "Precise_apport-collect"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+attachment/3843651/+files/Precise_apport-collect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184165
Title:
03f0:1205 Scanner does not work: Simple scan gives a device busy error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843644/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Card0.Codecs.codec97.0.ac97.0.0.regs.txt
apport information ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843634/+files/Card0.Codecs.codec97.0.ac97.0.0.regs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843643/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] AlsaDevices.txt
apport information ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843628/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843640/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Card0.Amixer.values.txt
apport information ** Attachment added: "Card0.Amixer.values.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843632/+files/Card0.Amixer.values.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] AplayDevices.txt
apport information ** Attachment added: "AplayDevices.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843629/+files/AplayDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843639/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843637/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843638/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] ArecordDevices.txt
apport information ** Attachment added: "ArecordDevices.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843630/+files/ArecordDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843631/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843636/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843641/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
apport information ** Tags added: precise running-unity ** Description changed: This is a virgin installation of 13.04. Scanner is not found - reported by Simple scan. I tried Ask Ubuntu, but got no answer. I have a parallel installation of 12.xx on the same computer, and scanner does work. So what is specific about 13.04? I have also an old FC-3 installation and the scanner works, using sane with xinetd. I notice that 13.04 does not use xinetd. So how is the scanner accessed? Whatever it is, it works on 12.xx and does not on 13.04. In terminal mode: sane-find-scanner found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1205 [hp scanjet scanner]) at libusb:002:002 scanimage -L [hp5590] hp5590_get_status: USB-in-USB: got non-zero device status (status 12) [hp5590] hp5590_init_scanner: scanner reports non-zero status: Device busy lsusb Bus 002 Device 002: ID 03f0:1205 Hewlett-Packard ScanJet 4500C/5550C Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-generic. + ApportVersion: 2.0.1-0ubuntu17.4 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 3396 F pulseaudio + CRDA: Error: [Errno 2] No such file or directory + Card0.Amixer.info: + Card hw:0 'nForce'/'NVidia nForce with ALC650E at irq 20' +Mixer name : 'Realtek ALC650E' +Components : 'AC97a:414c4722' +Controls : 50 +Simple ctrls : 33 + CasperVersion: 1.315.1 + DistroRelease: Ubuntu 12.04 + IwConfig: + lono wireless extensions. + + eth0 no wireless extensions. + LiveMediaBuild: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) + Lsusb: + Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Transcend JetFlash Flash Drive + Bus 002 Device 002: ID 03f0:1205 Hewlett-Packard ScanJet 4500C/5550C + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: System Manufacturer System Name + MarkForUpload: True + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 nouveaufb + ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity + ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 + RelatedPackageVersions: + linux-restricted-modules-3.8.0-29-generic N/A + linux-backports-modules-3.8.0-29-generic N/A + linux-firmware1.79.6 + RfKill: + + Tags: precise running-unity + Uname: Linux 3.8.0-29-generic i686 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + dmi.bios.date: 07/26/2004 + dmi.bios.vendor: Award Software, Inc. + dmi.bios.version: ASUS A7N266-VM ACPI BIOS Rev 1008 beta 002 + dmi.board.name: A7N266VM + dmi.board.vendor: ASUSTeK Computer INC. + dmi.board.version: REV 1.xx + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 7 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSA7N266-VMACPIBIOSRev1008beta002:bd07/26/2004:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA7N266VM:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: + dmi.product.name: System Name + dmi.product.version: System Version + dmi.sys.vendor: System Manufacturer ** Attachment added: "AcpiTables.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843627/+files/AcpiTables.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843642/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843635/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Card0.Codecs.codec97.0.ac97.0.0.txt
apport information ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3843633/+files/Card0.Codecs.codec97.0.ac97.0.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher M. Penalver, Sorry, I'm confused again. I thought comments 20 and 21 answered comment 19. As far as comment 23: i'm booted now, and all the time for this bug report, into my 13.04 (or Raring) installation. So I have run aggain the apport command, see attached file of the screen dialogue. You'll notice that I ran it both ways, with -p linux and without. I don't quite understand the errors, but it's OK. Again, what do you mean by "boot into a Ubuntu kernel (not a mainline/upstream one)"? How do I do that? Where do I get an "Ubuntu kernel"? See comment 17. I'm sorry, I'm not trying to be difficult. Janos ** Attachment added: "apport-collect in Raring" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+attachment/3839340/+files/apport-collect_2013Sep24Raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] HookError_cloud_archive.txt
apport information ** Attachment added: "HookError_cloud_archive.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3839334/+files/HookError_cloud_archive.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
apport information ** Tags added: apport-collected ** Description changed: This is a virgin installation of 13.04. Scanner is not found - reported by Simple scan. I tried Ask Ubuntu, but got no answer. I have a parallel installation of 12.xx on the same computer, and scanner does work. So what is specific about 13.04? I have also an old FC-3 installation and the scanner works, using sane with xinetd. I notice that 13.04 does not use xinetd. So how is the scanner accessed? Whatever it is, it works on 12.xx and does not on 13.04. In terminal mode: sane-find-scanner found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1205 [hp scanjet scanner]) at libusb:002:002 scanimage -L [hp5590] hp5590_get_status: USB-in-USB: got non-zero device status (status 12) [hp5590] hp5590_init_scanner: scanner reports non-zero status: Device busy lsusb Bus 002 Device 002: ID 03f0:1205 Hewlett-Packard ScanJet 4500C/5550C Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + --- + ApportVersion: 2.9.2-0ubuntu8.3 + Architecture: i386 + DistroRelease: Ubuntu 13.04 + InstallationDate: Installed on 2013-05-14 (134 days ago) + InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) + MarkForUpload: True + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: raring + Uname: Linux 3.8.13-030813-generic i686 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip fax floppy fuse plugdev sambashare saned scanner sudo tape video ** Attachment added: "HookError_cloud_archive.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3839333/+files/HookError_cloud_archive.txt ** Description changed: This is a virgin installation of 13.04. Scanner is not found - reported by Simple scan. I tried Ask Ubuntu, but got no answer. I have a parallel installation of 12.xx on the same computer, and scanner does work. So what is specific about 13.04? I have also an old FC-3 installation and the scanner works, using sane with xinetd. I notice that 13.04 does not use xinetd. So how is the scanner accessed? Whatever it is, it works on 12.xx and does not on 13.04. In terminal mode: sane-find-scanner found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1205 [hp scanjet scanner]) at libusb:002:002 scanimage -L [hp5590] hp5590_get_status: USB-in-USB: got non-zero device status (status 12) [hp5590] hp5590_init_scanner: scanner reports non-zero status: Device busy lsusb Bus 002 Device 002: ID 03f0:1205 Hewlett-Packard ScanJet 4500C/5550C Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2013-05-14 (134 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: raring Uname: Linux 3.8.13-030813-generic i686 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy fuse plugdev sambashare saned scanner sudo tape video + --- + ApportVersion: 2.9.2-0ubuntu8.3 + Architecture: i386 + DistroRelease: Ubuntu 13.04 + InstallationDate: Installed on 2013-05-14 (134 days ago) + InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) + MarkForUpload: True + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: raring + Uname: Linux 3.8.13-030813-generic i686 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip fax floppy fuse plugdev sambashare saned scanner sudo tape video -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher M. Penalver, - attachment #2 apparently I can only attach one file, so here is the other one referenced in my previous message, testing item (3) ** Attachment added: "Testing_Mainline_kernel_3.12.0-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+attachment/3832767/+files/Testing_Mainline_kernel_3.12.0-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher M. Penalver, testing update (1) Booted into live DVD of Raring. Same problem, scanner does not work. Apport collect did not work even after installing python - see attached file of terminal dialogue (2) Booted into live DVD of Saucy. Could not even find simple scan or any menu. I correct my previous message, the Saucy install DVD does give the option to try it, i.e. run a live DVD environment. I just could not read it, because as I mentioned in my previous message, the explanations were not readeable, just plane character squares. This is a bug in the ISO image. Somebody selected the wrong font. (3) I also trried to follow your instruction (quote: ...Please do not test the daily kernel folder, but the one all the way at the bottom...), and tested kernel 3.12 - see attached file. Saccer does not work. Problems: (A) Presently I can boot into three environments: Raring and Saucy on sda, of which Saucy is extremely slow and useless. The third environment is FC3 on sdb. The problem is that since I installed Saucy it looks like grub only looks at the Sacy environment for cfg file. Can you please tell me how to get rid of Saucy and make sure grub reads the Raring cfg file at boot? (B) After I installed kernel 3.12 for testing my Raring environment has an error indicator on the update gizmo on top of the right hand corner of my screen telling me to run the Package Manager from the right click menu. The right click menu of that gizmo (sorry, I don't know the official name panel? aplet? etc.) only gives me choices of More or Remove. So can you please help me how to fix this condition. Please, understand that I'm new to Ubuntu and am not familiar with Ubuntu lingo, shortcuts, etc. One final note: are you sure it is a kernel problem that scanner does not work? Please, read my first message on top of this thread. lsusb recognizes the scanner, sane-find-scanner finds it, but scanimage cannot access it because it is "busy". ** Attachment added: "for item (1)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+attachment/3832766/+files/Raring_LiveDVD_testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
apport information ** Tags added: apport-collected ** Description changed: This is a virgin installation of 13.04. Scanner is not found - reported by Simple scan. I tried Ask Ubuntu, but got no answer. I have a parallel installation of 12.xx on the same computer, and scanner does work. So what is specific about 13.04? I have also an old FC-3 installation and the scanner works, using sane with xinetd. I notice that 13.04 does not use xinetd. So how is the scanner accessed? Whatever it is, it works on 12.xx and does not on 13.04. In terminal mode: sane-find-scanner found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1205 [hp scanjet scanner]) at libusb:002:002 scanimage -L [hp5590] hp5590_get_status: USB-in-USB: got non-zero device status (status 12) [hp5590] hp5590_init_scanner: scanner reports non-zero status: Device busy lsusb Bus 002 Device 002: ID 03f0:1205 Hewlett-Packard ScanJet 4500C/5550C Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + --- + ApportVersion: 2.9.2-0ubuntu8.3 + Architecture: i386 + DistroRelease: Ubuntu 13.04 + InstallationDate: Installed on 2013-05-14 (130 days ago) + InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) + MarkForUpload: True + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: raring + Uname: Linux 3.12.0-031200rc1-generic i686 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip fax floppy fuse plugdev sambashare saned scanner sudo tape video ** Attachment added: "HookError_cloud_archive.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3832750/+files/HookError_cloud_archive.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher M. Penalver, problem update, a day later: (a) I was able to get back to the boot capability to boot into my trusted old FC3 installation. I had to do a "sudo update-grub" from the new installation (13.10). The only way I could do it by Ctr-Alt-F1 switching into terminal. The gui desktop was useless. Apparently the aborted installation changed but not finished MBR. Grub now looks at the new installation. When I did the sudo grub-update from the 13.04 boot it did recognize the FC3 installation, but it looks like grub from MBR now reads the cfg from the 13.10 installation. Anyway, I'm glad that at least I'm back to square one. (b) Also, from 13.10 terminal mode I did a "uname -a", see attached. This is to tell what kernel was installed. Let me know how to proceed, and thanks. Janos ** Attachment added: "uname -a from test installation (13.10)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+attachment/3830672/+files/JanosSaucySalamanderUnamea -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher M. Penalver, problem! I clicked on the link. It took me to a site to download images. I chose the 13.10 Desktop Image, PC (Intel x86). Created DVD from ISO image and rebooted to the DVD. It did not give me a chance to test it as live DVD, so I went ahead and chose "comtinue", but without checking "install 3rd party software" as instructed by you. Minor issue: explanations under choices were not readeable, just blank squares in place of characters. Apparently the display driver could not render the font. Created new secondary partition but without separate /boot partition and proceeded with installation. Minor issue: I got confused by "Ubuntu One" (what is it, why email, what register?), but went ahead as a good soldier. Instalaltion proceeded, but got stuck at the end: "copying installation logs..." I finally gave up and pulled the plug. When I rebooted grub was messed up, lost entry for my trusted old FC3 installation on the other hard disk. But I hope I can fix that. Booted into 13.10, but to a completely unfamiliar desktop and an extremely slow system. Finally I found the way to shut down the system normally, without pulling the plug. After that I rebooted into 13.04 whose grub entry was not lost. Now I can write this report. So we are still at STEP ONE. Can you please help? btw, what is PPA? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher M. Penalver, OK, we are getting somewhere. Before I do anything, please humor me, and allow me to understand what exactly I'm supposed to do. Let's go step by step. (One) - should I download the ISO image from link http://cdimage.ubuntu.com/daily-live/current/ and create a virgin installation? I can do that, I have plenty of hard disk place. Please, confirm this step ONE. After that we can go to my understanding of the next step. I'm more than happy to participate in this work. I do have the time and interest. Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher, sorry, how can I get an "Ubuntu reporsitory kernel"? This was a virgin installation from an Ubuntu downloaded DVD. I have not touched anything, just let itself update. Did the installation DVD not install the "Ubuntu repository kernel"? Is this a bug of the installation DVD? Here is the output of uname: janos@Andraslinux:~$ uname -a Linux Andraslinux 3.8.13-030813-generic #201305111843 SMP Sat May 11 22:52:24 UTC 2013 i686 athlon i686 GNU/Linux At any rate, please help me to obtain an "Ubuntu repository kernel". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher: I'm back and executed commands as per your instructions (broke-up the && sections to make sure I don't confuse the computer and myself). Everything went well, I suppose, but there are two isuues I cannot explain - see attached file also. (1) a warning window popped uo saying I'm not using official ubuntu kernel. This was a virgin installation and regularly updated. I did not mess with kernel (not on this installation; I do compile my own kernel for my FC3 original installation on a different partition, where both the scanner and lexmark printer do work). I copied the warning message to the attached file, top section. So how come I'm not using an official kernel? (2) see copy of terminal window output in attached file, below the separator. Is this relevant to the bug? Thank you and all others who read this and try with me to solve this problem. Janos ** Attachment added: "scanne_bug_log_Sep14_2013_jankom.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+attachment/3820886/+files/scanne_bug_log_Sep14_2013_jankom.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
apport information ** Tags added: apport-collected ** Description changed: This is a virgin installation of 13.04. Scanner is not found - reported by Simple scan. I tried Ask Ubuntu, but got no answer. I have a parallel installation of 12.xx on the same computer, and scanner does work. So what is specific about 13.04? I have also an old FC-3 installation and the scanner works, using sane with xinetd. I notice that 13.04 does not use xinetd. So how is the scanner accessed? Whatever it is, it works on 12.xx and does not on 13.04. In terminal mode: sane-find-scanner found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1205 [hp scanjet scanner]) at libusb:002:002 scanimage -L [hp5590] hp5590_get_status: USB-in-USB: got non-zero device status (status 12) [hp5590] hp5590_init_scanner: scanner reports non-zero status: Device busy lsusb Bus 002 Device 002: ID 03f0:1205 Hewlett-Packard ScanJet 4500C/5550C Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Can you please help? Thanks, Janos + + --- + ApportVersion: 2.9.2-0ubuntu8.3 + Architecture: i386 + DistroRelease: Ubuntu 13.04 + InstallationDate: Installed on 2013-05-14 (123 days ago) + InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) + MarkForUpload: True + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: raring + Uname: Linux 3.8.13-030813-generic i686 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip fax floppy fuse plugdev sambashare saned scanner sudo tape video ** Attachment added: "HookError_cloud_archive.txt" https://bugs.launchpad.net/bugs/1184165/+attachment/3820876/+files/HookError_cloud_archive.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: 03f0:1205 Scanner does not work: Simple scan gives a device busy error
Christopher: I'm away from home till mid-September. Will execute commands you suggested when I come back, and report on results. Thanks for picking up the ball - Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
I tested my 12.04 installation with apparmor disabled in grub for printing and it also segfaulted. However, this time it is not the printdriver, but libpthread - see below janos@andraslinux:~$ dmesg | tail [ 56.157663] composite sync not supported [ 56.614874] composite sync not supported [ 56.614886] composite sync not supported [ 57.031522] composite sync not supported [ 57.031534] composite sync not supported [ 57.501989] composite sync not supported [ 57.502001] composite sync not supported [ 121.161899] firefox[1798]: segfault at 4 ip 15684564 sp bfcbc3e0 error 4 in nouveau_vieux_dri.so[15676000+2f000] [ 121.171388] firefox[1801]: segfault at 4 ip 00a56564 sp bf93ea90 error 4 in nouveau_vieux_dri.so[a48000+2f000] [ 461.056973] printdriver[2199]: segfault at 0 ip (null) sp bff4987c error 4 in libpthread-2.15.so[11+17000] janos@andraslinux:~$ I'm going away for a week now. Will check status of this bug when I come back. Hopefully, we can find a solution. One more thing, the uname -a in my 12.04 is the following: janos@andraslinux:~$ uname -a Linux andraslinux 3.2.0-45-generic #70-Ubuntu SMP Wed May 29 20:11:31 UTC 2013 i686 athlon i386 GNU/Linux janos@andraslinux:~$ I also run updates on 12.04, and will keep both distributions alive until my scanner and printer works. At that point I'll keep only 13.04. Presently scanner works on 12.04 and printer works on neither. My old FC3 installation has both the printer and scanner working, but the system is all messed up, so I use it as a sanbox. I use there twm as window manager and emlfm for files. Thanks again for your interest in helping with this issue - and at the same time, hopefully, make Ubuntu better. Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
Thank you for the detailed explanation of restart. As far as my installation DVD is concerned I downloaded the ISO image from Ubuntu's web site and burned it myself. The only complication I had was that I already had a 12.04 installation on my 2nd hard drive (hdb or sdb) and the Ubuntu installation detected it and wanted me to upgrade, etc. I was not happy with the choices, so I disconnected the power supply to my 2nd hard drive and did the installation as a virgin installation. Previously, of course, I wiped out partitions on the main hard drive so the installation found nothing but an unpartitioned hard drive. Btw, this main hard drive is brand new, 250 Gig, because the original hard drive started to fail. I had a hard time finding an IDE ATA drive, because now everything is SATA and my motherboard is a few years old. Anyway, when I first installed 13.04 on the factory new hard drive it formatted and occupied the entire 250 Gig. So I wiped it out, created a smaller partition and this is how this 13.04 is installed. Probably this all is irrelevant. I can start all over again: download the ISO, burn the DVD, reinstall 13.04 and try again. My 12.04 installation is on the 2nd hard drive, and so is my old FC3 where the Lexmark printer does not segfault. Scanner works on 12.04, and I can try deactivating apparmor on 12.04 and see if I can print with Lexmark. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
I'm not familiar with the new grub. grub.cfg is more complex than the old grub I'm used to. So my first attempt to restart failed to deactivate apparmor. Then I edited grub.cfg and put the apparmor=0 statement dierctly after root=x and before ro This time I think apparmor is less effective. See below: janos@Andraslinux:~$ sudo aa-status [sudo] password for janos: apparmor module is loaded. apparmor filesystem is not mounted. janos@Andraslinux:~$ dmesg | tail [ 56.010269] composite sync not supported [ 56.010284] composite sync not supported [ 56.672092] init: plymouth-stop pre-start process (1095) terminated with status 1 [ 69.534864] composite sync not supported [ 69.534877] composite sync not supported [ 72.344126] composite sync not supported [ 72.344140] composite sync not supported [ 72.403431] composite sync not supported [ 72.403445] composite sync not supported [ 194.610821] printdriver[1974]: segfault at 0 ip (null) sp bfd013fc error 4 in printdriver[8048000+b000] janos@Andraslinux:~$ Howver, as you see I still get the segfault. Could it be because apparmor module is still loaded? I'm sorry, I'm confused a littbit about your last paragraph on restart. One more point: in your previous comment you state that "Alright, because you aren't using an Ubuntu kernel, or a kernel with the interface patches". My kernel is what came with the installation DVD and updated periodically by the updater. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
Output of the first two commands is below: janos@Andraslinux:~$ sudo aa-status [sudo] password for janos: apparmor module is loaded. You do not have enough privilege to read the profile set. janos@Andraslinux:~$ sudo /etc/init.d/apparmor restart * Reloading AppArmor profiles Warning from /etc/apparmor.d/lightdm-guest-session (/etc/apparmor.d/lightdm-guest-session line 13): profile /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper network rules not enforced Warning from /etc/apparmor.d/lightdm-guest-session (/etc/apparmor.d/lightdm-guest-session line 13): profile chromium_browser network rules not enforced Warning from /etc/apparmor.d/sbin.dhclient (/etc/apparmor.d/sbin.dhclient line 76): profile /sbin/dhclient network rules not enforced Warning from /etc/apparmor.d/usr.bin.evince (/etc/apparmor.d/usr.bin.evince line 160): profile /usr/bin/evince network rules not enforced Warning from /etc/apparmor.d/usr.bin.evince (/etc/apparmor.d/usr.bin.evince line 160): profile sanitized_helper network rules not enforced Warning from /etc/apparmor.d/usr.bin.evince (/etc/apparmor.d/usr.bin.evince line 160): profile /usr/bin/evince-previewer network rules not enforced Warning from /etc/apparmor.d/usr.bin.evince (/etc/apparmor.d/usr.bin.evince line 160): profile sanitized_helper network rules not enforced Warning from /etc/apparmor.d/usr.bin.evince (/etc/apparmor.d/usr.bin.evince line 160): profile /usr/bin/evince-thumbnailer network rules not enforced Warning from /etc/apparmor.d/usr.bin.evince (/etc/apparmor.d/usr.bin.evince line 160): profile sanitized_helper network rules not enforced Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Warning from /etc/apparmor.d/usr.sbin.cupsd (/etc/apparmor.d/usr.sbin.cupsd line 180): profile /usr/lib/cups/backend/cups-pdf network rules not enforced Warning from /etc/apparmor.d/usr.sbin.cupsd (/etc/apparmor.d/usr.sbin.cupsd line 180): profile /usr/sbin/cupsd network rules not enforced Warning from /etc/apparmor.d/usr.sbin.cupsd.original (/etc/apparmor.d/usr.sbin.cupsd.original line 176): profile /usr/lib/cups/backend/cups-pdf network rules not enforced Warning from /etc/apparmor.d/usr.sbin.cupsd.original (/etc/apparmor.d/usr.sbin.cupsd.original line 176): profile /usr/sbin/cupsd network rules not enforced Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Warning from /etc/apparmor.d/usr.sbin.tcpdump (/etc/apparmor.d/usr.sbin.tcpdump line 64): profile /usr/sbin/tcpdump network rules not enforced cat: /sys/kernel/security/apparmor/profiles: No such file or directory janos@Andraslinux:~$ Now rebooting, and will post results in a separate comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
root@Andraslinux:/home/janos# uname -a Linux Andraslinux 3.8.13-030813-generic #201305111843 SMP Sat May 11 22:52:24 UTC 2013 i686 athlon i686 GNU/Linux root@Andraslinux:/home/janos# bash -c "echo -n /usr/sbin/cupsd >/sys/kernel/security/apparmor/.remove" root@Andraslinux:/home/janos# bash -c "echo -n /usr/lib/cups/backend/cups-pdf >/sys/kernel/security/apparmor/.remove" root@Andraslinux:/home/janos# ls -l /sys/kernel/security/apparmor/ total 0 drwxr-xr-x 5 root root 0 Jun 14 20:31 features No luck with printing after the remove commands. I did the above from root account and copied the .features files to my user directory. File attached. I had to trick the system because the Attachment Browse button would not show hidden files. I'll be going away for the week-end - so you have a nice one, and I'll be back Monday continuing this quest. Thx ** Attachment added: "Dotfeatures" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+attachment/3703862/+files/Dotfeatures -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
Thank you, I'm learning new stuff. Besides, I like low level interfaces. Results were as expected - I think, except for the last step. After restarting cupsd "unconfined" disappeared. See below the output of commands you suggested: janos@Andraslinux:~$ sudo aa-status [sudo] password for janos: apparmor module is loaded. You do not have enough privilege to read the profile set. janos@Andraslinux:~$ ps -Z `pidof cupsd` LABEL PID TTY STAT TIME COMMAND /usr/sbin/cupsd 823 ?Ss 0:00 /usr/sbin/cupsd -F janos@Andraslinux:~$ sudo bash -c "echo -n /usr/sbin/cupsd >/sys/kernel/security/apparmor/.remove" janos@Andraslinux:~$ sudo bash -c "echo -n /usr/lib/cups/backend/cups-pdf >/sys/kernel/security/apparmor/.remove" janos@Andraslinux:~$ sudo aa-status apparmor module is loaded. You do not have enough privilege to read the profile set. janos@Andraslinux:~$ ps -Z `pidof cupsd` LABEL PID TTY STAT TIME COMMAND unconfined823 ?Ss 0:00 /usr/sbin/cupsd -F janos@Andraslinux:~$ sudo restart cups cups start/running, process 18702 janos@Andraslinux:~$ ps -Z `pidof cupsd` LABEL PID TTY STAT TIME COMMAND /usr/sbin/cupsd 18702 ?Ss 0:00 /usr/sbin/cupsd -F Nevertheless, I tried to print with Lexmark, but same result (printer wakes up, but then segfault). Here is dmesg: [ 3124.613956] type=1400 audit(1371215611.840:32): apparmor="STATUS" operation="profile_load" name="/usr/lib/cups/backend/cups-pdf" pid=18805 comm="apparmor_parser" [ 3124.614896] type=1400 audit(1371215611.840:33): apparmor="STATUS" operation="profile_load" name="/usr/sbin/cupsd" pid=18805 comm="apparmor_parser" [ 3186.971241] printdriver[18826]: segfault at 0 ip (null) sp bfc266dc error 4 in printdriver[8048000+b000] Another point: I booted up to the old, FC3 version, and Lexmark prints without segfault. As I mention, print files, etc. are exact copies in both FC3 boot or Ubuntu 13.04 boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
OK, let's fix apparmor first. I ran the commands, but as you see from the output the "remove" stuff failed. janos@Andraslinux:~$ ps -Z `pidof cupsd` LABEL PID TTY STAT TIME COMMAND /usr/sbin/cupsd 789 ?Ss 0:00 /usr/sbin/cupsd -F janos@Andraslinux:~$ sudo bash -c "echo /usr/sbin/cupsd >/sys/kernel/security/apparmor/.remove" [sudo] password for janos: bash: line 0: echo: write error: No such file or directory janos@Andraslinux:~$ sudo bash -c "echo /usr/lib/cups/backend/cups-pdf >/sys/kernel/security/apparmor/.remove" bash: line 0: echo: write error: No such file or directory janos@Andraslinux:~$ sudo aa-status apparmor module is loaded. You do not have enough privilege to read the profile set. janos@Andraslinux:~$ ps -Z `pidof cupsd` LABEL PID TTY STAT TIME COMMAND /usr/sbin/cupsd 789 ?Ss 0:00 /usr/sbin/cupsd -F janos@Andraslinux:~$ sudo restart cups cups start/running, process 2163 janos@Andraslinux:~$ ps -Z `pidof cupsd` LABEL PID TTY STAT TIME COMMAND /usr/sbin/cupsd 2163 ?Ss 0:00 /usr/sbin/cupsd -F janos@Andraslinux:~$ It looks like the entity " .remove" is a file in /sys/kernel/security/apparmor directory, not a directory. The only directory there is "features" that also has directories. I hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
Correct! That was exactly what I got last night. So I thought - excuse me - that you may have forgotten the sudo prefix. So I did not even bother to post this lengthy output. But this is exactly what I got without sudo. Could this explain the other problem I have (listed as confirmed bug) that my scanner does not work? See bug #1184165 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
I got stuck at the first command, here is the output: janos@Andraslinux:~$ sudo apparmor_parser -v [sudo] password for janos: Warning from stdin (line 1): apparmor_parser: cannot use or update cache, disable, or force-complain via stdin ^Cjanos@Andraslinux:~$ Note: I had to do sudo for the command, and then do Ctr-C to get back to prompt. I don't know what else should I have had to respond to the "force-complain via stdin" message. Recap: this is a virgin install of 13.04, and I have not really messed with it, just appled the occasional updates as they were announced. I did not do the rest of the commands in your message awaiting for your comments on the first one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
No problem. I had a little suspicion, but copied it anyway since I'm not familiar with Ubuntu's (or debian) file structure. Here is my terminal output now: janos@Andraslinux:~$ sudo apparmor_parser -R /etc/apparmor.d/usr.sbin.cupsd [sudo] password for janos: janos@Andraslinux:~$ sudo restart cups cups start/running, process 2033 janos@Andraslinux:~$ ps -Z `pidof cupsd` LABEL PID TTY STAT TIME COMMAND /usr/sbin/cupsd 2033 ?Ss 0:00 /usr/sbin/cupsd -F Aparently the "unconfined" label is not there. Printing process is still the same: printer comes alive, then failure is reported and dmesg says "...segfault at 0 ip..." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
another step closer - see below: janos@Andraslinux:~$ sudo apparmor_parser -R /etc/init.d/usr.sbin.cupsd [sudo] password for janos: Error: Could not read profile /etc/init.d/usr.sbin.cupsd: No such file or directory. janos@Andraslinux:~$ Could this be the problem (bug)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
I already did the /usr/local/lexmark thing, no difference. Here is an excerpt from my usr.sbin.cupsd ... # FIXME: no policy ATM for hplip and Brother drivers /usr/bin/hpijs Ux, /usr/Brother/** Ux, ## JGK 6/9/13 begin /usr/lexinkjet/** Ux, /usr/local/lexmark/** Ux, ## JGK 6/9/13 end # Kerberos authentication ... Note: I think we need both lexinkjet and lexmard dierctories because the way lexmark installs files and symlinks within. These two directories have printer setups for an entire family of lexmark printers. (A) Here is the cache after boot today, print producing denial: janos@Andraslinux:~$ ls -l /etc/apparmor.d/cache/usr.sbin.cupsd -rw--- 1 root root 87010 Jun 9 09:35 /etc/apparmor.d/cache/usr.sbin.cupsd janos@Andraslinux:~$ sudo md5sum /etc/apparmor.d/cache/usr.sbin.cupsd [sudo] password for janos: 04e342575436f1477a3f292e4043938a /etc/apparmor.d/cache/usr.sbin.cupsd (B) Here is the cache after applying apparmor_parser command: janos@Andraslinux:~$ sudo apparmor_parser -vTWr /etc/apparmor.d/usr.sbin.cupsd Warning from /etc/apparmor.d/usr.sbin.cupsd (/etc/apparmor.d/usr.sbin.cupsd line 180): profile /usr/lib/cups/backend/cups-pdf network rules not enforced Replacement succeeded for "/usr/lib/cups/backend/cups-pdf". Warning from /etc/apparmor.d/usr.sbin.cupsd (/etc/apparmor.d/usr.sbin.cupsd line 180): profile /usr/sbin/cupsd network rules not enforced Replacement succeeded for "/usr/sbin/cupsd". janos@Andraslinux:~$ ls -l /etc/apparmor.d/cache/usr.sbin.cupsd -rw--- 1 root root 87010 Jun 10 17:51 /etc/apparmor.d/cache/usr.sbin.cupsd janos@Andraslinux:~$ sudo md5sum /etc/apparmor.d/cache/usr.sbin.cupsd 04e342575436f1477a3f292e4043938a /etc/apparmor.d/cache/usr.sbin.cupsd printer came to life, but then error and dmesg segfault (C) After reboot: janos@Andraslinux:~$ ls -l /etc/apparmor.d/cache/usr.sbin.cupsd -rw--- 1 root root 87010 Jun 10 17:51 /etc/apparmor.d/cache/usr.sbin.cupsd janos@Andraslinux:~$ sudo md5sum /etc/apparmor.d/cache/usr.sbin.cupsd [sudo] password for janos: 04e342575436f1477a3f292e4043938a /etc/apparmor.d/cache/usr.sbin.cupsd printer denied -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
Don't know how to add multiple attachments, so here is the 2nd one ** Attachment added: "saved printer troubleshooter output" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+attachment/3698837/+files/troubleshoot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
Thanks. We are getting there, but the solution is still elusive. I did the apparmor_parser command, then tried to print. Result: printer not connected error So I deleted and reinstalled printer, and rebooted. Surprise: apparmor again denied execution after reboot. So I did apparmor_parser Result: almost OK. Printer came to life, tried to do something, then cups reported error dmesg indicated segmentation fault in print driver I verified the printdriver file with diff comparing it with the same file on my FC3 installation where the printer works - no difference. My FC3 installation is all bastardized. It is my sandbox. I compiled cups from source, it is 1.4.6 - but it works. Attached are two files: (1) dmsg outputs, and (2) print troubleshooter saved Aside from this it looks like reboot restores apparmor behaviour to original state and we have to do manual apparmor_parser which is definitely a bug. Thanks for your interest in this problem. ** Attachment added: "dmesg outputs" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+attachment/3698836/+files/Lexmark-apparmor.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
Re John Johansen's suggestion:
I did it with reboot, but dmesg still reports denial, see below:
[ 104.569090] audit_printk_skb: 24 callbacks suppressed
[ 104.569100] type=1400 audit(1370659781.774:26): apparmor="DENIED"
operation="exec" parent=831 profile="/usr/sbin/cupsd"
name="/usr/local/lexmark/08zero/bin/printdriver" pid=1911 comm="cupsd"
requested_mask="x" denied_mask="x" fsuid=7 ouid=0
Excerpt from the modified usr/sbin.cupsd file after reboot and trying
the print operation:
/usr/local/** rm,
/usr/local/lib/cups/** rix,
/usr/local/lexmark/08zero/bin/printdriver rix,
/usr/share/** r,
/{,var/}run/** rm,
Btw, I tried before reading your suggestion to modify the file based on
the Brother entry, such as
/usr/lexinjkjet/** Ux,
/usr/local/lexmark/** Ux,
because /usr/lexinkjet/ has the 08zero directory (symlinked from
/usr/local/lexmark) containing the "printdriver" file and a lib
directory housing so files. The /usr/lexinkjet has an etc directory
housing various ppd files for various other lexmark printers as well.
This did not work either.
Something else in the apparmor scheme still denies execution.
Janos
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1187970
Title:
apparmor prevents custom printer driver from executing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] Re: apparmor prevents custom printer driver from executing
I tried to change the source package but the link above gave me "error ID OOPS-a8afe36a1ef5ba57464e91d12a39c578" Anyway, based on the description of the problem the package is either cups or apparmor or both. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187970] [NEW] apparmor prevents custom printer driver from executing
Public bug reported: I'm trying to make my Lexmark Z2420 work on Xubuntu > = 10.04. The Lexmark provided installation does not work, package is bad, etc. I worked around it because I was able to extract either the deb or rpm package. In fact, the printer works on an old version of Linux installation (Fedore-3 based), on the same machine. So the driver is OK. It is basically a ppd and a related proprietary printer driver written by Lexmark. The problem is with Ubuntu, or specifically with some security system tyhat is part of 10.04, 12.04 or 13.04. Here is the output of dmesg. It explains the problem, but I'm new to debian (or Ubuntu), and therefore I don't know how to open up the security to enable running the printer driver. Quote: [ 2615.809241] type=1400 audit(1370314741.028:21): apparmor="DENIED" operation="exec" parent=720 profile="/usr/sbin/cupsd" name="/usr/local/lexmark/08zero/bin/printdriver" pid=2175 comm="cupsd" requested_mask="x" denied_mask="x" fsuid=7 ouid=0 Unquote Thanks, Janos ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: Scanner does not work: Simple scan gives a device busy error
New idea regarding why scanner does not work: It may not have anything to do with kernel. Just a thought: I tried to access cups through its built-in web interface (http://localhost:631), and it is not accessible in 13.04. If I go to my 12.04 installation (same machine, same hard drive, different boot) http://localhost:631 comes up without any problem. As I mentioned before, the scanner works on 12.04 and it does not work on 13.04. So my thinking is that 13.04 has some sort of security installed which is not on 12.04. The security prevents accessing ports on "localhost" (127.0.0.1). Even though the scanner is connected to the usb interface "sane" accesses it though the network as 127.0.1:6566. The reason I came to this idea is because (1) tried cups on 127.0.0.1:631, and (2) my custom print driver was prevented from executing by apparmor. So I put these two things together and concluded that ubuntu (or debian) has some sort of protection scheme preventing idiots like me to mess up the system. I have been playing with linux long enough to be dangerous. Unfortunately, I'm new to ubuntu and therefore do not know the internal workings of it. CONCLUSION: Normally scanner works through "saned", and the "xinetd" settings would allow it to use port 63566 on localhost. I do not see "xinetd" in ubuntu. What replaces its functionality? Apparently, the BUG is in the implementation of the alternate method and related other security schemes (apparmor??). Thank you for your understanding and help, Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: Scanner does not work: Simple scan gives a device busy error
Re Joseph: Installed 3.8.13 kernel and same problem. Upstream kernel tested, same bug. Thank you both (Brad and Joseph( Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] Re: Scanner does not work: Simple scan gives a device busy error
Commenting on Brad Figg tried "apport-collect 1184165" wanted me to "sudo apt-get install python-apport" which I did, and then ran "apport-collect 1184165" again error: "ERROR: The launchpadlib Python module is not installed. This functionality is not available." so I'll change status "Confirmed" Janos ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184165] [NEW] Scanner does not work in 13.04, device busy
Public bug reported: This is a virgin installation of 13.04. Scanner is not found - reported by Simple scan. I tried Ask Ubuntu, but got no answer. I have a parallel installation of 12.xx on the same computer, and scanner does work. So what is specific about 13.04? I have also an old FC-3 installation and the scanner works, using sane with xinetd. I notice that 13.04 does not use xinetd. So how is the scanner accessed? Whatever it is, it works on 12.xx and does not on 13.04. In terminal mode: sane-find-scanner found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1205 [hp scanjet scanner]) at libusb:002:002 scanimage -L [hp5590] hp5590_get_status: USB-in-USB: got non-zero device status (status 12) [hp5590] hp5590_init_scanner: scanner reports non-zero status: Device busy lsusb Bus 002 Device 002: ID 03f0:1205 Hewlett-Packard ScanJet 4500C/5550C Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Can you please help? Thanks, Janos ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: Scanner does not work in 13.04, device busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
