[Bug 412593] New: iscan segfault after kernel update
https://bugzilla.novell.com/show_bug.cgi?id=412593 Summary: iscan segfault after kernel update Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: addictedtox@hotmail.it QAContact: kernel-maintainers@forge.provo.novell.com Found By: --- Created an attachment (id=230244) --> (https://bugzilla.novell.com/attachment.cgi?id=230244) Console output After kernel was updated to 2.6.22.18-0.2-default, iscan won't start due to an error about module lp.ko. Console output attached. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 Luca Giusti <addictedtox@hotmail.it> changed: What |Removed |Added ---------------------------------------------------------------------------- Platform|i586 |i686 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 User gregkh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412593#c1 Greg Kroah-Hartman <gregkh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |addictedtox@hotmail.it --- Comment #1 from Greg Kroah-Hartman <gregkh@novell.com> 2008-07-28 10:20:52 MDT --- Does this also happen in the 11.0 release? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 User addictedtox@hotmail.it added comment https://bugzilla.novell.com/show_bug.cgi?id=412593#c2 --- Comment #2 from Luca Giusti <addictedtox@hotmail.it> 2008-07-28 12:29:19 MDT --- No problems with a 2.6.25.11-0.1-pae 11.0 machine. No console output available with it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 Luca Giusti <addictedtox@hotmail.it> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|addictedtox@hotmail.it | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |kernel-maintainers@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412593#c3 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com Status|NEW |NEEDINFO Info Provider| |addictedtox@hotmail.it --- Comment #3 from Jeff Mahoney <jeffm@novell.com> 2008-08-08 12:47:22 MDT --- Can you provide the output of dmesg? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 User addictedtox@hotmail.it added comment https://bugzilla.novell.com/show_bug.cgi?id=412593#c4 Luca Giusti <addictedtox@hotmail.it> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|addictedtox@hotmail.it | --- Comment #4 from Luca Giusti <addictedtox@hotmail.it> 2008-08-09 06:27:45 MDT --- Created an attachment (id=232555) --> (https://bugzilla.novell.com/attachment.cgi?id=232555) dmesg -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412593#c5 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.provo.novell.com |jsmeix@novell.com Priority|P5 - None |P3 - Medium --- Comment #5 from Jeff Mahoney <jeffm@novell.com> 2008-08-11 09:51:27 MDT --- There's no kernel failure, but I won't rule out kernel involvement. I'm going to assign to the iscan maintainer for triage. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412593#c6 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #6 from Johannes Meixner <jsmeix@novell.com> 2008-08-12 02:22:09 MDT --- For a workaround see https://bugzilla.novell.com/show_bug.cgi?id=406112#c2 It seems to help to run the scanning frontend program once as root to have sufficient permissions - after this it also works as normal user. *** This bug has been marked as a duplicate of bug 406112 *** https://bugzilla.novell.com/show_bug.cgi?id=406112 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 User addictedtox@hotmail.it added comment https://bugzilla.novell.com/show_bug.cgi?id=412593#c7 Luca Giusti <addictedtox@hotmail.it> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE | --- Comment #7 from Luca Giusti <addictedtox@hotmail.it> 2008-08-16 05:33:56 MDT --- Unfortunately, this won't solve my problem. When running iscan as root, a message in Italian appears in a window that in English sounds, more or less, like this: it is impossible to send commands to the scanner. Check the scanner status. Since then, btw, running iscan as normal user gives me a laconic "Segmentation fault message". Nothing else. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412593#c8 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |addictedtox@hotmail.it --- Comment #8 from Johannes Meixner <jsmeix@novell.com> 2008-08-19 01:14:59 MDT --- Iscan works for me. Because it fails "After kernel was updated", it looks very much like a kernel related issue. Luca Giusti, did it work for you before the kernel update? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 User addictedtox@hotmail.it added comment https://bugzilla.novell.com/show_bug.cgi?id=412593#c9 Luca Giusti <addictedtox@hotmail.it> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsmeix@novell.com |bnc-team-screening@forge.provo.novell.com Status|NEEDINFO |NEW Info Provider|addictedtox@hotmail.it | --- Comment #9 from Luca Giusti <addictedtox@hotmail.it> 2008-08-19 04:08:06 MDT --- I never had problems with iscan before. I tried uninstalling and re-installing the package, but it did not work. Of course, when the kernel was updated, other packages were updated, too. So it could be a problem not directly related to the kernel, afaik. I also tried to get something like a stack trace like I recently did for a Firefox bug in the current openSUSE version, but gdb does not display any informations after typing bt with iscan. Since I am not experienced in debugging, is there anything I can do to provide more useful informations? Thank you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 Robert Vojcik <rvojcik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |kernel-maintainers@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 User addictedtox@hotmail.it added comment https://bugzilla.novell.com/show_bug.cgi?id=412593#c10 --- Comment #10 from Luca Giusti <addictedtox@hotmail.it> 2008-09-14 11:06:58 MDT --- Hello, I have some news. I was inspired by this post about a Samsung scanner: http://forums.opensuse.org/1601662-post13.html that is the last post of this discussion: http://forums.opensuse.org/archives/sf-archives/archives-hardware/344566-sam... Thus, I did as follows: - added my user in the lp group; - changed my /etc/fstab according to the suggestion: changed the 'usbfs /proc/bus/usb usbfs noauto 0 0' line in 'usbfs /proc/bus/usb usbfs default,devmode=0660 0 0'. - replaced the /usr/lib/libmfp.so.1.0.1 with the suggested one - rebooted the system At this point, I can run iscan without functional problems, but the segfault remains. I noticed one thing, though: if I run iscan as root, I temporary eliminate the segfault problem. After that, I can run iscan as normal user without segfault, too. After reboot, though, the segfault is there again. Apart from that, the software seems to work properly. I do not know what else to do. I hope this information can be useful to completely solve the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 Greg Kroah-Hartman <gregkh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.provo.novell.com |bnc-team-screening@forge.provo.novell.com Component|Kernel |Basesystem QAContact|kernel-maintainers@forge.provo.novell.com |qa@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 Michal Seben <mseben@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mseben@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |jsmeix@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412593 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412593#c11 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #11 from Johannes Meixner <jsmeix@novell.com> 2008-10-15 13:50:49 MDT --- I have no idea how to reproduce it. It just works for me. Therefore I can only close it as "worksforme". For your informnation: Since a longer time normal-user access for scanners is granted via the udev/HAL/hal-resmgr machinery which sets an ACL for the scanner's device file. Run 'lsusb' to determine the current USB bus number and device number and then run getfacl /dev/bus/usb/xxx/yyy (replace xxx and yyy with bus number and device number from your particular 'lsusb' output) to see if an ACL is set and if yes, which one and for which user. By default only users which are logged in directly at the computer (i.e. via console "login" or via KDM/XDM but not via remote login) get access granted via the udev/HAL/hal-resmgr machinery. To access the scanner as normal user, udev, HAL, and hal-resmgr are needed to grant appropriate access permissions automatically. Therefore the scanner model must be known to HAL. If the scanner is not known to HAL, a re-plug of a USB scanner should help. Otherwise a reboot should be done to restart the whole udev/HAL/hal-resmgr machinery. Check if the scanner is listed in the 'lshal' output. If even a reboot does not help, you could access the scanner via the 'saned' as a workaround. For this workaround choose 'scanning via network' and select the 'local host configuration' in the YaST scanner config module. Additionally see http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2 -------------------------------------------------------------------- libusb + resmgr + PAM Note that the details change from version to version. Additionally there will be further enhancements (e.g. "udev", "HAL", "hal-resmgr",...). An article regarding scanner setup cannot describe all the details about USB, hotplug, udev, HAL, resmgr/hal-resmgr, PAM, and so on. Refer to the appropriate specific documentation if there are problems in one of these areas. -------------------------------------------------------------------- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com