Defect Catalogue
Deep-dive page: the recurring failure classes of LibreSocial across its life — legacy-build defects, runtime/OSGi defects, and the current 2026 defect list from GitLab work items.
Supersession note: the legacy error taxonomy is documented by Imam 2025 (master thesis), §5.3; user-facing symptoms and fixes by the Setup Guide 2025. With the 2026 Gradle/Java-17 build, classes A/D of the taxonomy largely disappear at build time — they survive only when compiling the untouched legacy sources with a wrong language level.
1. Build/toolchain defect classes (legacy path, ~120 issues fixed in 2025)
| # | Category | Typical message | Root cause | Fix pattern |
|---|---|---|---|---|
| A | Language level / compiler settings | Cannot instantiate the type ArrayList<?>, switch(String) rejected |
compiling Java-7 sources with Java-6 compliance (or Java 7-era syntax on Java-6-only toolchains) | set compliance to 1.7; or rewrite: new ArrayList<String>() instead of diamond, no switch on String, no try-with-resources (use try–finally) |
| B | Missing helpers / wrong imports | ConfigLoader cannot be resolved, unresolved OSGi classes |
bundle/jar not on the runtime; manifest imports/exports incomplete | add the bundle or jar; fix manifest wiring; thin local wrapper when a helper was genuinely absent |
| C | OSGi resource loading | getResourceAsStream(...) returns null |
resources packaged inside bundles are not on the flat classpath | context.getBundle().getEntry("/MyConfig.txt").openStream() |
| D | Collections / raw types | wildcard instantiation errors, raw-type warnings as errors | old javac + raw Collection usage |
explicit type parameters; wildcards only where needed |
| E | JDBC lifecycle | generated keys missing, connection/ResultSet leaks | driver quirks around getGeneratedKeys() |
try–finally around PreparedStatement/ResultSet, explicit "no ID obtained" branch |
2. Environment symptoms users hit (from the 2025 setup guide)
| Symptom | Meaning | Remedy |
|---|---|---|
Unsupported major.minor version at start |
class files compiled with Java 8+ while the app runs on Java 7 | run on JDK 1.7.0_80 (legacy path) or move to the 2026 Gradle build (Java 17) |
| Crypto calls fail / short keys | JCE policy restricts key strength | install Unlimited Strength local_policy.jar + US_export_policy.jar into jdk1.7.0_80/lib/security |
| Project not recognized in Eclipse | legacy PDE project files missing/incompatible | use Eclipse Indigo RCP/RAP distribution, import as plug-in project; modern IDEs only for Git, not for the PDE setup |
| GUI does not start (SWT errors) | SWT/JFace versions do not match the bundles | use exactly the SWT/JFace versions shipped with the release |
ClassNotFoundException for Commons/crypto |
missing Apache-Commons / crypto JARs | add the shipped jars; verify bundle manifests |
| Overlay nodes do not join | wrong bootstrap nodes / k / network config |
check .properties (bootstrap list, replication factor k ≥ 1 ≤ N); keep runs/<id>/configs/ copies — see revival & build |
3. Runtime error handling in the code
- The framework routes exceptions through an error-handling bundle
(
com.p2pframework.errorhandling);GetErrorCodeFromClass.javamaps exception classes to error codes. It carries redundantly imported exception types — an open work item assesses their removal (open, Prio-3). - A known open defect sits in the crypto helper: wrong call in
javax.crypto.specusage (open, Prio-5) — see security component.
4. Application-level defects (GitLab work items, 2026-11)
| ID | State | Defect | Notes |
|---|---|---|---|
| #134 | closed | repetitive WebSocket connection timeout in the web frontend | fixed in the 2026 course |
| #135 | open | mutual friendship not easily possible | friendship handshake/UX defect in friendsplugin; refactor item for the same bundle is Prio-1 |
| — | open | Docker cluster: audio error message when opening the noVNC browser instance | cosmetic, Prio-4 |
5. Patterns for avoiding regressions
- Never mix bundle versions — OSGi wiring defects (class B/C) dominate legacy breakage.
- One change layer at a time: build vs. runtime vs. protocol changes must not be combined in one experiment (run discipline from the 2025 thesis).
- Health gates before accepting any run: stable node count, exceptions ≈ 0, sent ≈ received.
- A proper automated test suite (including negative tests) is the agreed prevention strategy — it is open work: test safety net, testing methodology, tester component.
Sources
- Imam 2025, master thesis §5.3 fix log & Table 5.2 taxonomy
- Setup Guide 2025, troubleshooting chapter
- GitLab work items (export 2026-11-19): items labeled
bug, plus the two code-hygiene items above.