|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST reporting wizard shows no reports available to run | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Dominic W Reynolds <dreynolds> |
| Component: | Basesystem | Assignee: | Jesse Michael <jmichael> |
| Status: | RESOLVED FIXED | QA Contact: | Dominic W Reynolds <dreynolds> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | ro, suse-beta |
| Version: | RC 3 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Dominic W Reynolds
2006-02-28 22:31:41 UTC
This seems to be related to misconfigured perl on ppc. The yast modules can't find a dependency for a missing perl module. The rpm is installed but can't be found via the @INC list. The system is ppc32 (powerbook g4). The problem appears that the perl installed (and all other modules) are installed and built for: * ppc-linux-thread-multi-64int while the dependent module (perl-DBD-SQLite) is built for: * ppc-linux-thread-multi So the sqlite module is the only module installed under: * /usr/lib/perl5/vendor_perl/5.8.8/ppc-linux-thread-multi everything else is under * /usr/lib/perl5/vendor_perl/5.8.8/ppc-linux-thread-multi-64int and so can't be resolved via @INC (which defaults to the 64int dir). Why is this denoted as 64int for a 32bit install? Why is perl-DBD-SQLite built for different base than the other modules? -- Rudi, Olaf, Sorry I don't really know who to assign this to so I cc'd you guys (ppc, and build system). Sorry for the noise... perl-$foo doesnt build, apparmor wants one of these non-building packages. quick workaround would be a disabled make check. So perl-DBD-SQLite package is failing to build (the build date from rpm qi is 2006-01-30) and we are picking up an older version - i see. Thanks. dom Dominic, what is the status here? Is this a candidate to be closed? I see this on a i586 system with RC2 for "Executive.Security.Summary" and "Security.Incident.Report" - therefore: no candidate to close :-( BTW1: Who has added the dots in the report title? Please replace them with spaces. BTW2: The "not populated" message doesn't have any linebreak and is therefore cut off. It should break to multiple lines if the window is too small. BTW3: I use german language, but the whole problem (including my BTWs) is most likely language-independent. "Applications.Audit" shows a list of running daemons bound to any port and if they are confined or not - so at least this seems to work. I'll update to RC3 after having some sleep - just ask me if you need logs or other information. I just tested with LANG=C and found that the english "not populated" message is much shorter than the german one. This might be the reason why nobody complained yet ;-) Still unchanged in RC3 :-( BTW: I'll open another report for the cut-off german text (BTW2 from comment #5) David can you please look at this? looks like this might be related to aa-eventd and storing to the events.db. Jesse? We're currently testing a fix for this, but haven't submitted it to autobuild yet. submitted fix to abuild |