https://bugzilla.novell.com/show_bug.cgi?id=434540 User mseben@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434540#c1 Michal Seben changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mseben@novell.com Status|NEW |NEEDINFO Info Provider| |maacruz@gmail.com --- Comment #1 from Michal Seben 2008-10-14 02:34:33 MDT --- Please attach y2logs. If you are in doubt follow:http://en.opensuse.org/Bugs/YaST. Also if it's possible attach /var/log/messages after connecting a usb Thanks for report! -- 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=434540 User maacruz@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434540#c3 --- Comment #3 from Miguel Angel Alvarez 2008-10-16 10:54:54 MDT --- Created an attachment (id=246053) --> (https://bugzilla.novell.com/attachment.cgi?id=246053) /var/log/messages from oct 5 to oct 13 I've cleaned the log of some unrelated events (sshd, susefirewall, dhcp, ntpd,...) In this messages file you have plenty of normally working usb disk events at oct 05, before scanner installation. The scanner was installed at 14:46 oct 8 I attached again usb disk devices at 02:19 oct 11, noticing then the hal problem; I tryed rebooting and with several usb devices. At 3:16 oct 11 the usb disks mount again, after I reinstalled the hal package. -- 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=434540 User dkukawka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434540#c4 Danny Kukawka changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|dkukawka@novell.com |bnc-team-screening@forge.provo.novell.com --- Comment #4 from Danny Kukawka 2008-10-21 09:44:02 MDT --- Reassigning back. Since YaST is causing the problem, the YaST developer should find out what they did (wrong) and how they influence HAL. -- 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=434540 Stanislav Visnovsky changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |visnov@novell.com AssignedTo|yast2-maintainers@suse.de |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=434540 User dkukawka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434540#c6 Danny Kukawka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|dkukawka@novell.com | --- Comment #6 from Danny Kukawka 2008-10-28 02:59:48 MDT --- Because obviously everything worked before installing the scanner with YaST an it worked after reinstalling HAL. Looks to me clearly as if the YaST scanner installation changed something that caused the trouble. -- 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=434540 User maacruz@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434540#c8 Miguel Angel Alvarez changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|maacruz@gmail.com | --- Comment #8 from Miguel Angel Alvarez 2008-10-28 13:10:04 MDT --- Created an attachment (id=248408) --> (https://bugzilla.novell.com/attachment.cgi?id=248408) /etc/hal/fdi/policy/10osvendor/80-scanner.fdi /etc/hal/fdi/policy/10osvendor/80-scanner.fdi, but current file, after hal reinstall. -- 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=434540 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434540#c10 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix@novell.com AssignedTo|jsmeix@novell.com |bnc-team-screening@forge.provo.novell.com --- Comment #10 from Johannes Meixner 2008-10-29 02:17:54 MDT --- Attachment #248408 looks perfectly o.k. for me. It has no real entry for HAL at all (only a comment) which is as I expected it because your scanner model Epson Perfection 640U with USB IDs 0x04b8:0x010c is already listed in /etc/hal/fdi/policy/10osvendor/70-scanner.fdi so that the YaST scanner module does not add it to /etc/hal/fdi/policy/10osvendor/80-scanner.fdi. Both files do not belong to the hal package so that reinstalling of the hal package would not have any effect regarding those files. The first paragraph in comment #9 shows that there are indeed whatever problems in the HAL layer or perhaps in lower level layers e.g. udev or in the kernel USB subsystem. You can ignore the "Cannot execute /usr/bin/hp-makeuri" part because it is needed only for HP all-in-one devices (/usr/bin/hp-makeuri belongs to the hplip package). In particular when a model is already listed in /etc/hal/fdi/policy/10osvendor/70-scanner.fdi it works normally out of the box without the need for any reboot. The YaST scanner module only reports that there are possible problems (i.e. no bug in YaST). The second paragraph in comment #9 is a bug in the YaST base GUI system which needs very very much time when it should display a so called SelectionBox or a Table with many entries. In your case after clicking "Add" you would get a list of all known scanner models (several hundred up to about two thousand). This is also no bug in the YaST scanner module (but in the YaST base GUI system). -- 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=434540 User aorlovskyy@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434540#c14 Alexander Orlovskyy changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aorlovskyy@novell.com Status|NEW |NEEDINFO Info Provider| |maacruz@gmail.com --- Comment #14 from Alexander Orlovskyy 2008-10-30 06:34:09 MDT --- Miguel, can you try this out: 1. get root user or use sudo 2. open /etc/init.d/haldaemon in an editor of your choice and change: HALDAEMON_PARA="--daemon=yes"; to HALDAEMON_PARA="--daemon=yes --verbose=yes --use-syslog"; 3. call: logger =============================== 4. then restart HAL via: rchal restart 5. check if hal is ready by calling lshal and checking if device information get printed 6. reproduce the problem 7. attach the part of /var/log/messages since the =============================== in the syslog to the bug. -- 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=434540 User aorlovskyy@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434540#c16 Alexander Orlovskyy changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|maacruz@gmail.com | Resolution| |NORESPONSE --- Comment #16 from Alexander Orlovskyy 2008-11-21 00:52:18 MST --- If you can provide the requested information, please reopen this bug. -- 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.