https://bugzilla.novell.com/show_bug.cgi?id=304316 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=304316#c6 Stanislav Brabec <sbrabec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Component|Basesystem |Basesystem Product|openSUSE 10.3 |openSUSE 11.0 Resolution|WONTFIX | Version|Beta 2 |Factory --- Comment #6 from Stanislav Brabec <sbrabec@novell.com> 2008-04-30 07:17:40 MST --- Reopening. I did not notice another way, how it could break: Third party supplier provides hal addon, which is 32-bit only. I think that it could work on 64-bit system without any problem, but it will not. Hald daemon will read FDI file and search for addon in /usr/lib64/hal. But the addon will be installed to /usr/lib/hal and will not be found. It would be nice to fix it for 11.1 and SLES11. There are upstream problems related: hald_runner correctly uses PACKAGE_LIBEXEC_DIR, but PACKAGE_SCRIPT_DIR is (very probably incorrectly) derived from libdir. Reporting as https://bugs.freedesktop.org/show_bug.cgi?id=15767 This upsteam problem has to be fixed first. And yet another related (upstream) problem: hal.pc provides no way to detect location of hald addon directory. Reporting as https://bugs.freedesktop.org/show_bug.cgi?id=15768 -- 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.