| Summary: | Konqueror is completely broken | ||
|---|---|---|---|
| Product: | TDE | Reporter: | linux |
| Component: | tdelibs | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | NEW --- | ||
| Severity: | major | CC: | bugwatch, darrella, kb9vqf, linux, michele.calgaro, slavek.banko |
| Priority: | P5 | ||
| Version: | R14.0.x [Trinity] | ||
| Hardware: | Other | ||
| OS: | Debian Wheezy | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Attachments: |
Attempt to open Home
Attempt to open a web page Attempt to open System |
||
Created attachment 2354 [details]
Attempt to open a web page
Created attachment 2355 [details]
Attempt to open System
Ha, exactly the same behavior I observed on my test notebook. When I tried a new Trinity profile, Konqueror works properly. Before I could investigate where the problem is, after subsequent update tdebase problem disappeared. After some fiddling with ~/.trinity and logging out/in, it started to work. The weird thing is that it now works with the same ~/.trinity that it did not work before. Hmm, so that we have the same situation. Annoying is that none of our cases help to detect and fix the problem. What now with this bug report? Mark as resolved - works for me? I suspect a call to 'tdebuildsycoca --noincremental' from inside the affected TDE session would have helped fix this... I tried 'tdebuildsycoca' (without '--noincremental') and it did not help. I'll be upgrading another machine soon, expecting the same problem to appear. (In reply to Timothy Pearson from comment #6) > I suspect a call to 'tdebuildsycoca --noincremental' from inside the > affected TDE session would have helped fix this... At the time I had this problem on my test notebook I've tried: 1) tdebuildsycoca (without --noincremental) => not helped 2) tdebuildsycoca --noincremental => not helped 3) logout / login => not helped 4) with new profile => works! 5) with old profile => not helped In the next update, I was careful to not carry out an update during an active session => old profile suddenly started working! That helps; I always recommend that users not upgrade major releases from within an active TDE session but it's even more critical for 3.5.13.x to R14. There is a migration script that runs on the first login after upgrade; if not run there could be a number of glitches that show up. > That helps; I always recommend that users not upgrade major releases from
> within an active TDE session but it's even more critical for 3.5.13.x to R14.
Perhaps all the packages and libraries renaming in v14.0.0 could be the cause if the upgrade was done from a live TDE instance.
(In reply to Michele Calgaro from comment #10) > > That helps; I always recommend that users not upgrade major releases from > > within an active TDE session but it's even more critical for 3.5.13.x to R14. > Perhaps all the packages and libraries renaming in v14.0.0 could be the > cause if the upgrade was done from a live TDE instance. Guys in my case it was the update from R14~pre to R14~pre - difference of about two months. Sounds familiar: Bug 1099 Bug 1388 TDE Dev mail list: http://trinity-devel.pearsoncomputing.net/?0::6858 I submitted a patch in bug 2202 to automatically run the migratekde3 script. Needs testing from others. Just upgraded another system - from 14.0 DEVEL to RC1 and the same problem appeared. /opt/trinity/share/apps/systemview/documents.desktop is correct (contains URL=, not Path=) This helped: killall konqueror tdebuildsycoca --noincremental |
Created attachment 2353 [details] Attempt to open Home Konqueror is completely broken after upgrading to 14.0 RC1 and cannot open any directory or web page. See the screenshots.