| Summary: | [REGRESSION] Konqueror crashes when opening the navigation panel | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Julius Schwartzenberg <julius.schwartzenberg> |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED INVALID | ||
| Severity: | critical | CC: | bugwatch, darrella |
| Priority: | P5 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 892 | ||
|
Description
Julius Schwartzenberg
2012-06-14 13:30:47 CDT
Just in case this related to the recent XDG updates, would you please backup or
temporarily rename your $TDEHOME directory ($HOME/.trinity) and then restart
Trinity to force creating a new $TDEHOME profile directory? Then try accessing the konqueror navigation panel.
A missing navigation panel is one of the quirks a user will see in an existing profile, when the profile *.desktop files have not been updated correctly through starttde.
Please perform the following against your existing $TDEHOME profile:
find $HOME/.trinity -name "*.desktop" -exec sed -i 's|X-KDE-|X-TDE-|g' {} \;
find $HOME/.trinity -name "*.desktop" -exec sed -i 's|KDE\;|TDE\;|g' {} \;
In the updated starttde, the script needs to know the $TDEHOME and $tdehome variables. If those variables are unknown then the starrtde changes are not being executed and hence, the profile is not being updated to synchronize with the XDG changes.
With a hacked starttde (added -H) and after resetting the config option from true to false, restarting Trinity fixed this issue. I'll close this one as it is not a new problem. *** This bug has been marked as a duplicate of bug 892 *** Thanks Julius! I have an updated starttde that I will soon attach to bug report 892. I added: * Error checking against sym linked profile directories (a corner case but needed). * Usage of a verbose X message box to warn about the sym link, why an R14 XDG update will not occur, what fails to function properly because of that lack of update, and possible remedies for the user. * Nominal validation tests that the updates succeeded. When failures are detected then an X message box appears for each type of failure, thereby informing the user specifically what needs repairs. I have not yet but will split the R14 XDG updates to a new script. I am updating the migratekde3 script (bug report 709). That script will run the new R14 XDG update script too. I have been testing all afternoon. :-) Results: Had these changes been in place you would have been informed sufficiently what had failed and offered remedies to fix. :-) Yes, I'll be asking you to test. :-) This was fixed in a recent update. (I guess the XDG changes were only partly in the nightlies for a while.) |