[Bug 1934592] [NEW] Skanlite fails with "sane_start= Invalid argument"
Public bug reported:
I have a Canon TS6350 connected to the WLAN to the Lubuntu 20.04.2. I
installed the official updated Canon drivers.
Skanlite is able to connect to the printer with or without encryption
(port 80 or 443). When I press the button, Scan, the scan is done by the
printer. At the end of the scan, Skanlite reports me "sane_start=
Invalid argument":
```
$ skanlite
"deviceOption value="
Icon theme "elementary" not found.
("image/bmp", "image/jpeg", "image/png", "image/tiff",
"image/vnd.microsoft.icon", "image/vnd.wap.wbmp", "image/webp", "image/x-icns",
"image/x-portable-bitmap", "image/x-portable-graymap",
"image/x-portable-pixmap", "image/x-xbitmap", "image/x-xpixmap")
"escl:https://xxx.xxx.xxx.xxx:443";
"escl:http://xxx.xxx.xxx.xxx:80";
"escl:https://xxx.xxx.xxx.xxx:443";
"escl:http://xxx.xxx.xxx.xxx:80";
Capability : [image/jpeg]
Capability : [image/jpeg]
"escl:https://xxx.xxx.xxx.xxx:443";
"escl:https://xxx.xxx.xxx.xxx:443";
"escl:http://xxx.xxx.xxx.xxx:80";
sane_start= Invalid argument
```
$ uname -a
Linux mikehal 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Skanlite version 2.1.0.1
** Affects: skanlite (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/1934592
Title:
Skanlite fails with "sane_start= Invalid argument"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/skanlite/+bug/1934592/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 335761]
Here we are, 20 years after the reporting of this bug/feature request/wish (which wasn't even the first report), and not that much happened. Monitors bacame 5-10x bigger in pixel count and windows popping up in unexpected places are progressively harder to find, but hey? I now could at length post one or antother episode from my life that happened during those 20 years, but - to sum it up - time progressed for me, I can't really afford to wait another 20 years to get this sorted out (via kwin, X11 or wayland), so, folks, lets be realistic, let's just close this bug 15329, collectively forget about it - it's not gonna happen, nobody capable of coding really cares about it enough - and just happily move on. If we're really passionate about it, we could come back in 20 years, take a look at bug 15329 and tell our children or grand-children a nice little episode from our lives about the nightmare of crazily positioned windows in KDE and how we eventually learned to live with it. I bid you a very warm farewell, live long and prosper Wolfi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/335761 Title: Placement policy 'Remember' by default for all windows To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-default-settings/+bug/335761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 668148] Re: pci using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Hello? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/668148 Title: pci using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/668148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 668148] Re: pci using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Can I post something else for completeness? Log files, shell output, anything? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/668148 Title: pci using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/668148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 668148] Re: pci using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
I get the same error: > PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug I use *L*ubuntu 18.04.2 64 bit on Lenovo b590 ** Changed in: linux (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/668148 Title: pci using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/668148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 668148] Re: pci using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
$ uname -a Linux marco-Lenovo 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/668148 Title: pci using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/668148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774428] [NEW] Hibernation does not work after kernel 4.13.0-21
Public bug reported: Hibernation does work on my Dell Latitude 5480 only with kernel 4.13.0-21 or prior versions. Since 4.13.0-25 hibernation starts, but hibernation resume stops before login page. A black screen is displayed instead. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-25-generic 4.13.0-25.29~16.04.2 ProcVersionSignature: Ubuntu 4.13.0-21.24~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: LXDE Date: Thu May 31 16:14:31 2018 InstallationDate: Installed on 2017-07-26 (309 days ago) InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) SourcePackage: linux-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-edge (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hibernation kernel-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/1774428 Title: Hibernation does not work after kernel 4.13.0-21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-edge/+bug/1774428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195260] Re: MailScanner won't start due to variable $FIELD_NAME
confirmed! Same error here in HARDY FINAL RELEASE! sulla -- MailScanner won't start due to variable $FIELD_NAME https://bugs.launchpad.net/bugs/195260 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112856] Re: [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo()
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/7571023/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7571024/Dependencies.txt ** Attachment added: "Disassembly.txt" http://librarian.launchpad.net/7571025/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7571026/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7571027/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/7571028/Registers.txt ** Attachment added: "Stacktrace.txt" http://librarian.launchpad.net/7571029/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://librarian.launchpad.net/7571030/ThreadStacktrace.txt -- [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo() https://bugs.launchpad.net/bugs/112856 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kde-guidance in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 112856] [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo()
Public bug reported: Binary package hint: kde-guidance since upgrade to feisty fawn I have this problem that guidance crashes upon login ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Sun May 6 16:52:31 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/share/python-support/kde-guidance/displayconfig-restore.py InterpreterPath: /usr/bin/python2.5 Package: kde-guidance 0.8.0-0ubuntu5 PackageArchitecture: amd64 ProcCmdline: /usr/bin/python /usr/bin/displayconfig-restore ProcCwd: /home/sulla ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=de_AT.UTF-8 Signal: 11 SourcePackage: kde-guidance StacktraceTop: ?? () from /usr/lib/libXrandr.so.2 XRRGetScreenInfo () from /usr/lib/libXrandr.so.2 ?? () PyEval_EvalFrameEx () PyEval_EvalFrameEx () Uname: Linux freespeech 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video ** Affects: kde-guidance (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo() https://bugs.launchpad.net/bugs/112856 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kde-guidance in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 96411] Re: [feisty] guidance-power-manager crashes on launch
I am experiencing the same problem since my dist-upgrade to feisty yesterday: System: PC with Asus A8V deluxe mainboard, AMD Athlon 3000+ Winchester, Nvidia 6600GT (bindary driver), dual DVI screens in Xinerama mode. There seems to be no updated packages available, at least adept does not offer any. (as of 2007-04-22 16:51 GMT) Every login KDE crashes guidance-power-manager. This is the log I get (I also get it when I run guidance-power-manager from a terminal (the command line feedback is ":KCrash: Application 'guidance-power- manager.py' crashing...", then a KDE Kcrash window pops up with the following backtrace): = (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47747381356272 (LWP 5628)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #5 0x2b6d126b4a45 in ?? () from /usr/lib/libXrandr.so.2 #6 0x2b6d126b4b68 in XRRGetScreenInfo () from /usr/lib/libXrandr.so.2 #7 0x2b6d178d4b4f in ?? () from /var/lib/python-support/python2.5/ixf86misc.so #8 0x0048875d in PyEval_EvalFrameEx () #9 0x00488ab1 in PyEval_EvalFrameEx () #10 0x0048973a in PyEval_EvalCodeEx () #11 0x004d3cf8 in ?? () #12 0x00417be3 in PyObject_Call () #13 0x0041e37d in ?? () #14 0x00417be3 in PyObject_Call () #15 0x0045a178 in ?? () #16 0x0045d072 in ?? () #17 0x00417be3 in PyObject_Call () #18 0x004844c0 in PyEval_EvalFrameEx () #19 0x0048973a in PyEval_EvalCodeEx () #20 0x004d3cf8 in ?? () #21 0x00417be3 in PyObject_Call () #22 0x0041e37d in ?? () #23 0x00417be3 in PyObject_Call () #24 0x0045a178 in ?? () #25 0x0045d072 in ?? () #26 0x00417be3 in PyObject_Call () #27 0x004844c0 in PyEval_EvalFrameEx () #28 0x0048973a in PyEval_EvalCodeEx () #29 0x004d3cf8 in ?? () #30 0x00417be3 in PyObject_Call () #31 0x0041e37d in ?? () #32 0x00417be3 in PyObject_Call () #33 0x004811b2 in PyEval_CallObjectWithKeywords () #34 0x00421e06 in PyInstance_New () #35 0x00417be3 in PyObject_Call () #36 0x004844c0 in PyEval_EvalFrameEx () #37 0x0048973a in PyEval_EvalCodeEx () #38 0x004d3cf8 in ?? () #39 0x00417be3 in PyObject_Call () #40 0x0041e37d in ?? () #41 0x00417be3 in PyObject_Call () #42 0x0045a178 in ?? () #43 0x0045d072 in ?? () #44 0x00417be3 in PyObject_Call () #45 0x004844c0 in PyEval_EvalFrameEx () #46 0x0048973a in PyEval_EvalCodeEx () #47 0x004d3cf8 in ?? () #48 0x00417be3 in PyObjec
