[Bug 1904230] Re: System freeze after logging onto desktop session
'journalctl -b -1' comes back with: Specifying boot ID has no effect, no persistent journal was found I'm assuming though you're after the boot log for the previous session (that froze) so I've manually extracted this from /var/log/syslog in the attached archive (prevboot.txt). Unfortunately nothing new was added to /var/crash as a result of the freeze. Something additional to mention which may be related (given it's display related), I had to reboot the machine a couple of times to get this as it seemingly had issues starting the display manager. Visually the display kept flicking between the boot log and another one with some further logging info. The graphical login screen was never displayed. Syslog was showing messages as follows: Nov 18 19:58:57 monolith systemd[1]: Starting LXDE Display Manager... Nov 18 19:58:57 monolith systemd[1]: Started LXDE Display Manager. Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Main process exited, code=exited, status=1/FAILURE Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Unit entered failed state. Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Failed with result 'exit-code'. Nov 18 19:59:03 monolith systemd[1]: lxdm.service: Service hold-off time over, scheduling restart. Nov 18 19:59:03 monolith systemd[1]: Stopped LXDE Display Manager. Only fix was to reboot it. I've attached the boot log for this one as 'prevboot1.txt'. This problem happened on two different boots. ** Attachment added: "boot logs" https://bugs.launchpad.net/ubuntu/+bug/1904230/+attachment/5435802/+files/logs.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] Re: System freeze after logging onto desktop session
I have managed to upload the crash report via another machine, the ID is 1904626. For some reason it appears to be associated with bash which makes me wonder if it is related - the timestamp is roughly 6 minutes after restarting the machine from the freeze which puts it in the right time frame but could be coincidental. I will endeavor to repeat the crash and see if a new one is reported. I've noted your comments regarding support and understand. The fact it crops up with two different desktops though - LXDM and Openbox could suggest though it's possibly part of 'X' rather than one of these. Unfortunately as you know, it's not possible to move from 2016 to 2020.04 in one move without going via 2018 first, I plan to do that over the next few months but there is a fair amount of work involved in ensuring everything is working after an upgrade so it's not something I have time for right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] Re: System freeze after logging onto desktop session
There is one crash report in the /var/crash folder which corresponds to the last time the system restarted due to this issue (other instances are >7 days so will have been removed). Running ubuntu-bug as requested generated a lot of dots but did not provide a bug ID: jon@monolith:/var/crash$ ubuntu-bug _bin_bash.500.crash *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (583.0 KB) E: Examine locally V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/E/V/K/I/C): S *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. [..] . jon@monolith:/var/crash$ There does not appear to be anything captured recently on https://errors.ubuntu.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] [NEW] System freeze after logging onto desktop session
Public bug reported: After performing a recent update, I am encountering a complete system freeze shortly after logging on to a graphical session but only for a single user (which may suggest a corrupted configuration file somewhere). This is repeatable - happens every time I attempt to login. The desktop is LXDE however it also occurs with Openbox as well. Furthermore, it also happens when launching a desktop with vncserver which suggests it is not a graphics driver issue. I've tried deleting (renaming) the .config and .cache folders in the account, neither of these have had any effect. Am fairly sure I have seen this once or twice in the past but it was a pretty rare event. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.25 Architecture: amd64 Date: Fri Nov 13 17:44:30 2020 InstallationDate: Installed on 2013-07-25 (2668 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to xenial on 2018-12-28 (686 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 940030] Re: rsyslog stops working after logrotate until restarted
I'm seeing something similar with 14.04 since upgrading from 12.04 only in this case, I'm still getting kernel messages written to the logs however nothing else is until I force a restart of rsyslog. File permissions look ok though (syslog:adm). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/940030 Title: rsyslog stops working after logrotate until restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/940030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656302] Re: USB sound card intermittant/unable to play audio
I'll give it a go when I get 5 minutes, having just performed the upgrade to 14.04 and spent several days getting everything fully working again, I'm loathed to do another upgrade so soon. Is this likely to be more a kernel issue? If so, upgrading that may prove a better short term option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656302 Title: USB sound card intermittant/unable to play audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1656302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656302] [NEW] USB sound card intermittant/unable to play audio
Public bug reported: I have a EDIROL UA-1A USB soundcard which for the most part under 12.04 worked however after a period of uptime, ALSA calls started failing with messages of this nature: ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave and the kernel ring buffer would have streams of: [673754.825092] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD [673754.830412] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD and: [673429.575699] retire_capture_urb: 596 callbacks suppressed sometimes unplugging/plugging the card would fix this, other times a system reboot was required. Since the upgrade to 14.04 this seems to have got worse in that most of the time it behaves in this manner and the unplugging/plugging approach never works. From a kernel perspective, I was already running a 3.13.x release with 12.04 so there's not been a major update on this front since the upgrade. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 Uname: Linux 3.13.0-106-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jon 25970 F pulseaudio /dev/snd/pcmC0D0c: jon 25970 F...m pulseaudio /dev/snd/pcmC0D0p: jon 25970 F...m pulseaudio CurrentDesktop: LXDE Date: Fri Jan 13 12:56:13 2017 InstallationDate: Installed on 2013-07-25 (1268 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to trusty on 2016-12-28 (15 days ago) dmi.bios.date: 02/22/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9SBAA dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/22/2013:svnSupermicro:pnX9SBAA:pvr0123456789:rvnSupermicro:rnX9SBAA:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: X9SBAA dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Package changed: pulseaudio (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656302 Title: USB sound card intermittant/unable to play audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1656302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654018] Re: mpd segfaults playing m4a (aac) audio
Ok, so I've tracked this down to mpd picking up a different version of libavutil which I built some time ago from source: ldd /usr/bin/mpd | grep local libavutil.so.52 => /usr/local/lib/libavutil.so.52 it's picked this up in preference to the stock version in /usr/lib/x86_64-linux-gnu/ - if I comment this version out then the problem is resolved. ** Changed in: mpd (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/1654018 Title: mpd segfaults playing m4a (aac) audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/1654018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654018] Re: mpd segfaults playing m4a (aac) audio
Well I've only just completed the update to 14.04 which took a few days to get sorted so I'd like to have that running and stable for a while first before contemplating the next one. Only additional thing I can add at this point is that it was working fine in 12.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654018 Title: mpd segfaults playing m4a (aac) audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/1654018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654018] Re: mpd segfaults playing m4a (aac) audio
Here's a backtrace from gdb: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f09fb78d700 (LWP 18966)] 0x7f0a0a2b9f96 in frame_configure_elements (avctx=0x7f09f0003f00) at /build/libav-dVKvK5/libav-9.20/libavcodec/aacdec.c:194 194 /build/libav-dVKvK5/libav-9.20/libavcodec/aacdec.c: No such file or directory. (gdb) backtrace #0 0x7f0a0a2b9f96 in frame_configure_elements (avctx=0x7f09f0003f00) at /build/libav-dVKvK5/libav-9.20/libavcodec/aacdec.c:194 #1 aac_decode_frame_int (avctx=avctx@entry=0x7f09f0003f00, data=data@entry=0x7f09f0013e40, got_frame_ptr=got_frame_ptr@entry=0x7f09fb78a5bc, gb=gb@entry=0x7f09fb78a510) at /build/libav-dVKvK5/libav-9.20/libavcodec/aacdec.c:2491 #2 0x7f0a0a2bc4fd in aac_decode_frame (avctx=0x7f09f0003f00, data=0x7f09f0013e40, got_frame_ptr=0x7f09fb78a5bc, avpkt=) at /build/libav-dVKvK5/libav-9.20/libavcodec/aacdec.c:2645 #3 0x7f0a0a5a5652 in avcodec_decode_audio4 (avctx=0x7f09f0003f00, frame=0x7f09f0013e40, got_frame_ptr=got_frame_ptr@entry=0x7f09fb78a5bc, avpkt=avpkt@entry=0x7f09fb78a5d0) at /build/libav-dVKvK5/libav-9.20/libavcodec/utils.c:1384 #4 0x7f0a0b063158 in try_decode_frame (st=st@entry=0x7f09f00025e0, avpkt=avpkt@entry=0x7f09f0013d80, options=) at /build/libav-dVKvK5/libav-9.20/libavformat/utils.c:2097 #5 0x7f0a0b068a8b in avformat_find_stream_info (ic=0x7f09f0001b60, options=) at /build/libav-dVKvK5/libav-9.20/libavformat/utils.c:2477 #6 0x004458f2 in ffmpeg_decode (decoder=..., input=...) at src/decoder/FfmpegDecoderPlugin.cxx:390 #7 0x0041d9c4 in StreamDecode (this=0x4703c0 , is=..., decoder=...) at src/DecoderPlugin.hxx:131 #8 decoder_stream_decode (plugin=..., decoder=..., input_stream=...) at src/DecoderThread.cxx:131 #9 0x0041dde5 in decoder_run_file ( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654018 Title: mpd segfaults playing m4a (aac) audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/1654018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654018] [NEW] mpd segfaults playing m4a (aac) audio
Public bug reported: This problem looks almost identical to 519787 however that is somewhat old now and is marked as fixed - of course that's not to say something of a similar ilk has crept back in again. The problem is repeatable, on an attempt to play any m4a audio files, mpd segfaults inside libavcodec. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mpd 0.18.7-1 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 Uname: Linux 3.13.0-106-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Jan 4 16:25:46 2017 InstallationDate: Installed on 2013-07-25 (1259 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) SourcePackage: mpd UpgradeStatus: Upgraded to trusty on 2016-12-28 (7 days ago) mtime.conffile..etc.mpd.conf: 2016-12-28T14:58:40.850990 ** Affects: mpd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654018 Title: mpd segfaults playing m4a (aac) audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/1654018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250196] Re: HP Scanject 2100c not working on USB 3 root hub
I've performed the upgrade from 12.04 to 14.04 over the Christmas break which has restored all the repositories back to default (I was using the PPA from Rolf's PPA to work round this) and can confirm it's all working now. There's still the massive delay on the start of the initial scan (as mentioned in #32) which consumes 100% of the CPU but I can live with that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250196 Title: HP Scanject 2100c not working on USB 3 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1250196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250196] Re: sane plustek backend not working on USB 3 root hub
re #31, in my original bug report, I'd tentatively concluded this was an issue with USB3 and I note in your report you also have issues with USB3. For me, as I mentioned in #23, installing the updated sane backends pretty much fixed this problem for me on a USB3 root hub. It's still fairly temperamental though, the major annoyance being it seems to take 30s to a minute to start scanning. Personally, I think the USB3 subsystem is as buggy as anything, particularly with slower devices. I have encountered numerous spurious messages emitted from the kernel and complete system lockups all related to USB regardless of the type of peripheral in use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250196 Title: sane plustek backend not working on USB 3 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1250196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250196] Re: sane plustek backend not working on USB 3 root hub
Allow me to retract my last comment, those eagle eyed amongst you may have spotted the syntax error in my use of the scanimage command (should be --format not -format, clearly operator incompetence there). With that corrected, I too can also confirm correct operation with the Scanjet. There does appear to be a slight permissions thing going on with the saned daemon itself, in that unless I launch it as root (as opposed to the sane user) I get: Jan 24 17:45:52 monolith saned[30265]: io/hpmud/musb.c 139: unable get_string_descriptor -1: Operation not permitted Jan 24 17:45:52 monolith saned[30265]: io/hpmud/musb.c 2040: invalid product id string ret=-1 Jan 24 17:45:52 monolith saned[30265]: io/hpmud/musb.c 139: unable get_string_descriptor -1: Operation not permitted Jan 24 17:45:52 monolith saned[30265]: io/hpmud/musb.c 2045: invalid serial id string ret=-1 Jan 24 17:45:52 monolith saned[30265]: io/hpmud/musb.c 139: unable get_string_descriptor -1: Operation not permitted Jan 24 17:45:52 monolith saned[30265]: io/hpmud/musb.c 2050: invalid manufacturer string ret=-1 Jan 24 17:45:54 monolith saned[30265]: quit: exiting and it doesn't then scan - but that's a separate issue.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250196 Title: sane plustek backend not working on USB 3 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1250196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250196] Re: sane plustek backend not working on USB 3 root hub
I installed sane-backends - 1.0.25-git20150121-precise0 and upgraded libsane, sane-utils and libsane-common but this didn't fix the issue for me. scanimage -L now appears to consistently identify the scanner: device `plustek:libusb:001:019' is a Hewlett-Packard Scanjet 2100c flatbed scanner but issuing a scanimage command just bails out after a few seconds: scanimage -vvv -format pnm >outfile.pnm Calling sane_exit scanimage: finished there is no activity from the scanner. When I first raised the bug I'd been playing around with various sources from sane & libusb so it's possible something isn't quite linking together but I'm pretty sure I've removed all those remnants from the /usr/local area and everything now appears to be linking to the "correct" (ie. in the /usr/lib/x86...) area. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250196 Title: sane plustek backend not working on USB 3 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1250196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250196] Re: sane plustek backend not working on USB 3 root hub
This same bug I posted on the SANE developers page - #314472, https://alioth.debian.org/tracker/?func=detail&atid=410366&aid=314472&group_id=30186 has now been marked as fixed by one of the developers (Gerhard Jaeger) as follows: "I close this PR now, as it is fixed in the sources since 16.12.2014. Successfully tested with USB 3 and a LiDE30." So I guess at some point this will make it's way into the Ubuntu sources ** Bug watch added: alioth.debian.org/ #314472 http://alioth.debian.org/support/tracker.php?aid=314472 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250196 Title: sane plustek backend not working on USB 3 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1250196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250196] Re: sane plustek backend not working on USB 3 root hub
No it isn't a gneral USB3 problem - I would imagine far more people would be getting excited if it was (although I've seen some sporadic disconnects with USB1 printers but not convinced that is related). My guess (and it is just a guess) is that it is something about the userspace interface that the kernel exposes which isn't quite right OR something fundamental has changed in that arena and the libusb developers have yet to pick up 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/1250196 Title: sane plustek backend not working on USB 3 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1250196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250196] [NEW] sane plustek backend not working on USB 3 root hub
Public bug reported: I have a HP Scanject 2100c and a Canoscan LIDE-25 both of which use the Sane plustek backend for comms. My PC only has a USB 3 root hub, when either of these devices are connected, either directly or via an external USB 2 hub, they do not work. In general (although not always), 'scanimage -L' will detect the scanner ok: device `plustek:libusb:001:012' is a Hewlett-Packard Scanjet 2100c flatbed scanner however there is always about a 30s delay before the shell prompt is returned. Scanning always fails however, using the suggested method on the sane HOW-TO page: scanimage -vvv -format pnm >outfile.pnm Calling sane_exit is the usual response. By enabling debug on the plustek backend, the response I normally get results in the following: [plustek] Vendor ID=0x03F0, Product ID=0x0505 [plustek] usbio_DetectLM983x [plustek] * could not read version register! [plustek] open failed: -1 [plustek] sane_get_devices (0x7fff0686dbc8, 0) In an effort to try and diagnose this, I've build the latest SANE backends from scratch and tried out the latest libusb none of which has resolved the issue. My original kernel was a 3.5.x, I pushed it up to 3.8.0-30 this also made no difference. My guess based on what I've seen is that this is related to the USB 3 hub. The HP Scanjet worked ok on my old Linux box (a 2.6.27 kernel with USB 2 hub) and I've had the Canon one working (albeit not that reliably) on a Raspberry Pi with a 3.6.11 kernel. The key difference (aside from this being a 64 bit flavour of Linux) is the USB. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libsane 1.0.22-7ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44~precise1-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.5 Architecture: amd64 Date: Mon Nov 11 19:41:08 2013 InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250196 Title: sane plustek backend not working on USB 3 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1250196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
