By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2209 - Konqueror is completely broken
Summary: Konqueror is completely broken
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdelibs (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Debian Wheezy
: P5 major
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2014-11-23 10:21 CST by linux
Modified: 2018-05-27 10:49 CDT (History)
6 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Attempt to open Home (304.07 KB, image/png)
2014-11-23 10:21 CST, linux 		Details
Attempt to open a web page (31.47 KB, image/png)
2014-11-23 10:21 CST, linux 		Details
Attempt to open System (29.84 KB, image/png)
2014-11-23 10:21 CST, linux 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description linux 2014-11-23 10:21:05 CST 
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.
Comment 1 linux 2014-11-23 10:21:30 CST 
Created attachment 2354 [details]
Attempt to open a web page
Comment 2 linux 2014-11-23 10:21:57 CST 
Created attachment 2355 [details]
Attempt to open System
Comment 3 Slávek Banko 2014-11-23 10:27:23 CST 
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.
Comment 4 linux 2014-11-23 10:37:08 CST 
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.
Comment 5 Slávek Banko 2014-11-23 11:50:38 CST 
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?
Comment 6 Timothy Pearson 2014-11-23 16:34:10 CST 
I suspect a call to 'tdebuildsycoca --noincremental' from inside the affected TDE session would have helped fix this...
Comment 7 linux 2014-11-23 17:10:57 CST 
I tried 'tdebuildsycoca' (without '--noincremental') and it did not help.

I'll be upgrading another machine soon, expecting the same problem to appear.
Comment 8 Slávek Banko 2014-11-24 19:24:00 CST 
(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!
Comment 9 Timothy Pearson 2014-11-24 20:19:24 CST 
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.
Comment 10 Michele Calgaro 2014-11-24 21:53:32 CST 
> 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.
Comment 11 Slávek Banko 2014-11-24 22:12:11 CST 
(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.
Comment 12 Darrell 2014-11-25 15:35:29 CST 
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.
Comment 13 linux 2014-11-30 13:39:30 CST 
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